Permit Lead Alerts for Dynamics 365 Business Central

New building permits in your trade area matched to the customer card in Business Central or flagged as new, with the outreach drafted in the rep’s voice. The rep sends it; nothing contacts anyone on its own.

Sales & estimatingUpdated Oct 202620 ERPs

See it work on Business Central.

Click through the steps. Fictional data, in Business Central’s terms; the real thing runs on Business Central.

Permits · this week, three towns

Illustrative

Issued	Address	Work	Contractor	Value	Match
Oct 17	Lot 22 Birchwood Dr	New single-family · 2,600 sf	Harbor Point Builders	$480,000	Account · C10422
Oct 17	48 Elm Ridge Rd	New single-family · 2,400 sf	Oak Hill Builders	$410,000	Account
Oct 20	221 Route 9	Warehouse addition	Granite Peak Builders	$1,150,000	Account · quoting
Oct 20	17 Quarry Ln	Deck and screened porch	Kestrel Homes LLC	$68,000	No account · new
Oct 21	6 Birch Ct	Kitchen remodel	Owner	$45,000	Homeowner · skipped by rule

Rep on the account shown to that rep only.

Three towns, read into contractor, address, work and value, matched to the customer card.

1 / 4

Request a demo See it for NetSuite →See it for Sage 100 →

The problem, as it happens in Business Central.

Permits are public, and every dealer in the county could read them. Almost nobody does. The towns post them as PDFs and spreadsheets in five formats, the rep looks once a month if at all, and by the time the yard hears about the twelve-lot subdivision the framer already has a supplier. The customer card has no idea a current account just pulled a permit for a bigger job than anything it bought last year.

The leads that get worked are the ones a rep happened to drive past. Existing customers starting a big job are never told the yard noticed, and the new builder in town gets a cold call from everyone except the dealer two miles away.

How it works.

1
The permits are read each week
Residential and commercial permits from the towns in your trade area, in whatever form they publish them. A model reads each one into owner, contractor, address, type of work and value, and the originals are kept beside it.
2
Matched to your accounts
Contractor and owner names matched to the customer card, with the rep on the account. A permit that matches an account is a job for that rep; one that matches nothing is a new lead, flagged with what the permit says. An uncertain match is shown as uncertain.
3
The outreach is drafted
For an existing account, a note in the rep’s voice that names the job and offers a quote. For a new lead, an introduction. Nobody on a do-not-contact list, nobody already contacted this quarter. The rep sees them in one queue, biggest job first.
4
The rep sends
Each note is a draft until the rep sends it, or skips it. A new lead the rep wants to keep is started as a prospect in Lunica; the account is opened in Business Central by your team when they buy.

How it connects to Business Central.

Lunica reads the customer card and recent sales through Business Central’s API, under a user that can only read: account names, contacts, jobsites and the rep on each account, so a permit can be matched to the people you already sell to. Permits come from the towns and counties you name, read from what they publish.

Nothing lands in Business Central without a person and nothing is sent on its own. A permit never becomes an account; a prospect stays in Lunica until your team opens the account in Business Central, as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared. Every note to a contractor or owner is a draft until the rep sends it, and nothing contacts anyone on its own.

What a week looks like.

This week’s permits in your towns, read and matched by Friday.
An existing customer’s new job in front of their rep before the first delivery.
New builders in the area flagged, with what the permit says about them.
Outreach that names the job, sent by a rep, or not at all.

Questions

Does it contact the contractor?

No. It drafts the note; the rep sends it or skips it. Nothing contacts anyone on its own.

Does it write to Business Central?

No. A new lead is a prospect in Lunica. The account is opened in Business Central by your team when they buy.

Where do the permits come from?

The towns and counties you name, from what they publish. Where a town publishes nothing, there is nothing to read; Lunica does not buy lead lists.

How does it match a permit to an account?

By contractor and owner name, jobsite and past job addresses on the customer card. An uncertain match is shown as uncertain, not assumed.

What about homeowners pulling their own permits?

Flagged separately. Many dealers skip them by rule; some have a rep for retail. It is your rule.

What does the model see?

The permit being read and the account it is being matched to. Not the whole customer card.

Does it need a server?

Lunica runs on one server inside your network, whether Business Central is in Microsoft’s cloud or on your own server, set up and maintained by Lunica. It reads Dynamics 365 Business Central through Business Central’s API, under a user that can only read. There is no inbound connection from outside your network.

What does Lunica read in Business Central?

The customer card, open items and terms, purchase orders and receipts, the item card, quotes and order history, as each workflow needs them. Read-only, and only the rows a task is about.

Can it post to Business Central?

Nothing lands in Business Central without a person. What belongs in Business Central goes back as a Business Central API call or import where one exists, or keyed by your team from what Lunica prepared.

What about our documents?

Invoice copies and scans keep living in the attachments on the record. Lunica reads them when a workflow needs one and never writes to them.

The same workflow, on another ERP.

Permit Lead Alerts is written for every system on the list. You’re reading the Business Central version.

Lumber and building materials

Wholesale distribution

General business

Another system? Tell us which →