How it works
One elegant connection, not a pile of integrations.
The Sovereign core keeps doing exactly what it does. The Lead Engine subscribes to what the core already knows, and hands work back through the one door the core already validates.
The connection
Signed events out. Accept-contract in.
Sovereign core — frozen
Rating, filings, premium, ledger, equity and cession stay exactly where they are. The core emits signed lifecycle events. It is never written to by the module.
quote.startedlead openedquote.ratedpremium knownquote.declinedappetite missapp.abandonedstep capturedpolicy.bounduniversal kill switch
Lead Engine — the module
Reads events, builds the lead record, decides the next action. The only write path back is the checked doorway the core already uses: reopen a quote, requote, submit an application. Nothing else.
- Nothing of ours sits beside your policy records
- Never re-rates and never pins a filing version
- policy.bound halts every sequence and pulls every auction entry
- Only what the shopper agreed to share ever leaves
Nothing lands twice
Every event carries a signature and an idempotency key. Replays are safe; a duplicate quote.rated never produces a second lead or a second touch.
Resume, do not re-key
The resume link reopens the consumer's own session state in the core quote flow. Follow-up continues the transaction rather than sending them to a generic form.
Bind is the kill switch
policy.bound stops every sequence, cancels every queued touch and withdraws the lead from every auction before the next dispatch window.
Follow-up that fits the reason
Non-buyers are not one bucket.
Most systems drop every shopper who did not buy into the same email chain. Here the reason they stopped decides what happens next — and in several cases the right answer is no marketing at all.
| Why they did not buy | What the engine does next |
|---|---|
| Started a quote, never finished it | A link that reopens the quote at the exact step — nothing to re-key |
| Saw the price, did not buy | Coverage and deductible alternatives, plus a direct question about what stopped them |
| Left on the payment page | Immediate rescue call or text — the highest-yield moment you have |
| Declined in underwriting | No marketing at all; straight into the waterfall |
| Outside your appetite | One of your other programs first, then your panel or an outside buyer |
| Price objection | Different limits, deductible or pay plan inside the same program |
| Wants coverage later | A requote scheduled for the effective date they asked for |
| Still shopping | A short, capped follow-up series, weighted to email |
| Something broke | Service recovery and a person to help, not a marketing message |
| Did not agree to be contacted | No marketing outreach; service messages only |
| Asked not to be contacted | Immediate, permanent stop across every channel and every partner |
Recovery cadence
A default rhythm you can change to suit your book.
This is a starting hypothesis to be A/B tested against your own funnel, not an industry standard. Speed matters most in the first hour; after that, email carries explanation and SMS carries action.
| Timing | Channel | Purpose |
|---|---|---|
| T + 0 | Email, plus SMS where consented | Quote confirmation with the real price and a one-click resume link back to the exact step. |
| T + 5 min | Agent alert | High-intent and high-value only — payment abandonment and large premium first. |
| T + 2–3 hr | Email or SMS | Ask the diagnostic question: was it price, coverage, or something unanswered? |
| Next morning | Coverage comparison and pay-plan options against the quoted premium. | |
| Day 2 | SMS or agent task | Offer help finishing the application. |
| Day 4 | Alternative deductible, limit and coverage configuration inside the same filing. | |
| Day 7 | Quote expiration and, if eligible, the alternative-market option. | |
| Day 14 | Final short-term follow-up before the lead moves to long-term nurture. | |
| Day 30 or effective date | Email or SMS | Requote timed to the consumer's stated effective date or renewal. |
Every sequence stops immediately when
- The shopper buys — anywhere in your company
- The consumer opts out on any channel
- The lead is transferred or sold under an exclusive arrangement
- The consumer indicates they bought elsewhere
- The risk becomes ineligible
- Your limit on how often to reach out is reached
Dispatch is gated, not scheduled
Touches sit in a due-queue and are re-checked at dispatch against consent state, suppression, frequency cap and the consumer's local quiet hours. A message that became impermissible between scheduling and sending is dropped, not sent.
SMS is deliberately capped — typically two or three genuinely useful messages in the first seven days. It produces the fastest response and carries the greatest consent exposure.