Preserve lead source and permission at capture.
A web form, referral, inbound call, purchased lead, renewal inquiry, and cross-sell opportunity do not arrive with the same context or communication permission. Store the lead source, original request, received time, contact details, product interest, permission record your agency relies on, and any promised response window before the first automated touch.
Search the agency system before creating a new person. A household may already have another policy, a business owner may also be a personal-lines client, and a referral may use a different email address. Put uncertain matches in a duplicate-review queue rather than auto-merging or building a second history.
| Lead condition | Automation can do | Human owner |
|---|---|---|
| Complete inbound request | Acknowledge receipt, assign, and set a response due time | Licensed producer or assigned service role |
| Missing key fact | Ask one approved clarifying question | Review if the answer affects eligibility or advice |
| Existing client match | Attach the inquiry to the known account | Account owner confirms routing |
| High-value, complex, or sensitive request | Skip the ordinary cadence and create priority work | Named producer |
| Reply, decline, or opt-out | Apply the stop condition across the sequence | Staff resolves any open question |
Automate response discipline, not licensed advice.
The system can confirm receipt, collect factual information, offer approved scheduling options, create tasks, and draft a follow-up from the known context. Licensed staff owns recommendations, coverage interpretation, quote presentation, binding, and any promise about price or availability.
Use different paths only when the next action truly changes. Personal versus commercial, new versus existing client, urgent certificate need versus general quote, or referral versus cold lead may justify distinct ownership and timing. Avoid dozens of campaigns based on marketing labels nobody maintains.
Stop rules are part of the customer experience.
Stop ordinary follow-up on reply, scheduled conversation, explicit decline, invalid contact, opt-out, disqualification, or manual pause. A response should not merely alert staff while the next automated message remains queued. All channels need to write to the same lead state or create an exception.
If automated texts are used, make opt-out easy and honor a reasonable revocation method. The FCC has explained that people may revoke consent through several reasonable words and methods, not only a single exact command. Confirm the rules that apply to your message type and lead source before launch. Read the FCC order on consent revocation.
Message test: Could the recipient understand why your agency is contacting them, what happens next, and how to stop? If not, personalization tokens will not make the outreach trustworthy.
Build the first path around accountability.
- Sample leads by source and identify the actual first actions staff take.
- Define valid lead, duplicate review, assignment, due time, and close-out reason.
- Connect one source to the existing agency record and prove identity matching.
- Add immediate acknowledgement only where the content and permission are approved.
- Create an owned work queue for replies, exceptions, and overdue response.
- Apply stop conditions before adding a multi-step cadence.
- Review lead records and outcomes weekly until staff trust the state.
Measure time to assigned response, leads with no owner, overdue tasks, duplicate records, meaningful conversations, quotes or meetings reached, opt-outs, and closed reasons by source. Do not judge the system by how many touches it sends. Judge it by whether fewer legitimate inquiries disappear between inboxes.