Build the follow-up list from the consent record, hold every number a check cannot clear and draft from approved wording — your BDC manager owns the campaign and any figure comes from a person.
Take the follow-up list from the CRM, the DMS, the service file and the campaign your BDC manager approved.
02
Read the consent on each number — what was given, for what, on which channel, and every stop that has landed since.
Reason
03
Check the number against the suppression lists it is connected to, and name the ones it could not reach.
04
Read the local hour at the number rather than the area code, against the calling hours that state allows.
05
Draft from the wording approved for the reason this customer is on the list, with every figure left out.
Decide
06
Hold a number when a check does not clear, and say which check held it instead of working it anyway.
07
Route a reply that reads as a stop, a wrong number or a complaint to a person before the cadence runs again.
Out
08
Put the draft in front of the named BDC person with the consent evidence and the checks that ran beside it.
09
Retain what went out, on what consent, at what local hour, from whom, and every stop that landed after it.
→Product statement
The agent works only numbers the consent record clears and only wording your BDC manager approved. Any figure in a message, and any reply that is not a simple answer, comes from a person.
Example workflow
One follow-up, end to end
AgentHuman
1List builtUnsold showroom traffic, a lead gone quiet, declined service, an open campaign or a lease maturing
2Consent record readWhat consent was given, for what, on which channel, and every stop that has landed since
3Contactability checkedInternal suppression, the registries and reassigned-number data, then the local hour at the number
4Message draftedApproved wording for the reason this customer is on the list, with every figure left out
No human action required
Stages 1 to 4 run without a person in the loop — the list, the consent record and the contactability checks all finish before anyone is asked to read a draft, and nothing has gone out.
5DecisionSplits on whether the consent record and the checks clear the number
Cleared, and no figure needed
Reaches the BDC person ready to send.
A check held it, or a figure is wanted
Goes to the BDC with the check named.
BDC manager or the named salesperson
Reads the draft, the consent evidence behind it and the check that held the number, then sends under their own name or takes the number off the list.
Send · Edit · Suppress
Sent — logged against the consent▼
6Sent by a named person, or heldGoes out under the named BDC person who sent it, inside the boundary agreed at implementation
7Outcome evaluatedStops honoured and how fast, wrong numbers, complaints, held numbers and replies, by cohort
Stops
Every stop, wrong number and complaint is counted in the evaluation.
What should not run autonomously
Human approval stays in control
Outside the boundary — human approval required8 items
Sending a message that states a price or payment.
Quoting an APR, a term or a rebate.
Putting a trade or payoff figure in writing.
Releasing a number the consent check held.
Automation boundaryAgent acts unaided
✓Build the list from your BDC manager's approved campaign.
✓Read the consent, the suppression lists and the local hour.
✓Draft from the wording approved for that reason, with every figure left out.
✓Hold a number when a check does not clear, and name the check.
A message goes out under the BDC person named against it, and only inside the boundary agreed at implementation.
Adding a customer to a campaign they never joined.
Answering a complaint, a dispute or a legal demand.
Making a commitment the dealership must keep.
Changing the cadence, the wording or the suppression rules.
Example output
One follow-up message, annotated
Everything the agent drafts is attached to the consent record and the checks that ran behind it.
Outbound draft · one customer, one channelIllustrative example
On the list because
Channel
Local hour
Message
Confidence
Figures in it
Service declined at the last visit
Text, written consent on file
Inside hours
Drafted — cleared to send
86%
None — left to the advisor
As receivedThe reason this customer is on the list and the channel their consent covers — the agent adds neither.
Evidence usedWritten consent, this storeNo stop on any channelNot on a suppression list
Why no figureA price or a payment in a text is an advertisement, and the store can be held to it.
ActionSendEditSuppress
What the score decidesConfidence decides how closely the BDC reads the draft, not who may be contacted.
Value
Where AI adds value
The same four claims, placed at the point in the workflow where each one applies.
Where the value landsValue 01 – 04
Every number on the listCRM, DMS, service file or campaign
03Consent & cadence
Check the record before the message
Use the consent on file, the stops already landed, the suppression lists you connect and the hours that state allows.
01Approved path
The list arrives already checked
Consent, suppression, reassigned-number and calling-hours checks have all run before a BDC person opens the first draft.
02Human review
A stop reaches the next campaign too
A reply that reads as a stop goes to a person, and the number is suppressed across the lists we connect before the cadence runs again.
04Build an evidence trail
Retain the consent read, the checks that ran, the wording drafted, who sent it, and every stop, wrong number and complaint that followed.
Integrations
Typical integrations
Five system groups connect to the same agent. Which of them are in scope is decided in discovery.
CRM & DMSVinSolutions · Elead · DealerSocket Tekion · CDK and Reynolds records
Consent & suppressionConsent records · internal do-not-call Registry scrubs · reassigned-number data
A customer who asks in their own words to be left alone has revoked consent as surely as one who writes STOP, and a reassigned number carries consent its new owner never gave. Nestack reports contact quality by slice, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Freeform stop wording
6.6%
4.1×
Review
Reassigned or ported numbers
4.2%
2.6×
Review
Aged consent records
2.9%
1.8×
Watch
Recent service customers
1.1%
0.7×
Normal
Bar: unwanted-contact rate lift vs. recent-service baseline · scale 0–4.0× · tick at 2.0×2 of 4 slices over threshold
Evidence-linked improvement
A complaint is a list problem before it is a person problem
Taking one customer off one list does not close it. The same gap sits in the consent read, the suppression sync or the cadence behind it.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Complaints, stops honoured late or wrong-number replies rise in a cohort.
02Diagnose
Read back through the consent read, the suppression sync, the hours check, the wording and the cadence itself.
03Improve
The suppression rule, the cadence or the approved wording changes under your BDC manager's sign-off, version-linked.
04Verify
Re-run on stored campaigns from that cohort, including the numbers that should never have been worked.
05Learn
The complaint becomes a standing check, and the number it came from stays suppressed.
Learn → DetectThe return edge. A stop written in a customer's own words becomes a case the next campaign is tested against before it is sent.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, consent and suppression, cadence and wording, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Workflow discovery and automation-boundary definition.
02CRM, DMS and telephony access assessment.
03Consent-record mapping and evidence rules.
04Internal suppression list and registry scrubs.
05Reassigned and wrong-number handling.
06Calling-hours and quiet-hours rules by state.
07Campaign lists, cadence and frequency caps.
08Approved wording and withheld-figure rules.
09Reply handling and stop routing to a person.
10Evaluation suite and revocation-latency testing.
11Named-sender workflow and CRM write-back.
12Observability, deployment and Agent Care handover.
12 workstreams · 6 weeks · bar shows the weeks a workstream is active — several run in parallelFinal scope and sequence confirmed in discovery
Engagement tiers
What each tier includes
Rows are the capabilities named in each tier's scope. Higher tiers include everything below them.
Capability✓ in scope · — not at this tierPilotOne list, one channelProductionLive campaigns, live sendingAdvancedMulti-rooftop / group
Introduced at Pilot
Message drafting from approved wording✓✓✓
Consent and calling-hours checks on every number✓✓✓
Suppression, registry and reassigned-number checks✓✓✓
Stop and complaint routing, with stop write-back✓✓✓
Every message leaves under a named sender✓✓✓
Baseline evaluation✓✓✓
Introduced at Production
Campaign lists, cadence and frequency caps—✓✓
Lead and appointment write-back to the CRM—✓✓
Observability and evaluation—✓✓
Introduced at Advanced
Multi-channel outreach and language coverage——✓
Multi-rooftop and group controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on rooftops, CRM, DMS and telephony integrations, contact volume, the number of campaigns and channels, consent-record complexity and deployment requirements.
Separate from buildBuild pricing is separate from recurring Agent Care, which covers managed monitoring, evaluations, incidents and verified improvements after launch.
What we need from you
What you bring, and what we build with it
Each input maps to a piece of build scope and a week in the delivery timeline.
You bringWe build with it
01Your consent records, and where the evidence for each one actually lives→Consent-record mapping and evidence rulesWeek 1
02Read access to your CRM, DMS and texting or dialler platform→CRM, DMS and telephony access assessmentWeek 2
03Your internal do-not-call list, and everywhere a stop has to land→Internal suppression list and registry scrubsWeek 2
04The campaigns you run, and why a customer lands on each list→Campaign lists, cadence and frequency capsWeek 3
05The wording you already approve, and the figures you keep out of writing→Approved wording and withheld-figure rulesWeek 3
06Complaints, wrong numbers and the messages you wish had not gone out→Evaluation suite, regression cases and failure-mode testingWeek 4
07Named BDC people to send what the agent drafts and to own each campaign→Named-sender workflow, then supervised campaigns and validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases are drawn over the weeks they actually occupy. Week 5 carries both the last of the evaluation and the first messages a named person sends.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Automation boundary, and the consent record behind every number you workW2CRM, DMS and telephony access, the suppression list and the registry scrubsW3Calling hours, cadence caps and the wording a message is allowed to carryW4Evaluation suite, revocation-latency testing, reply and stop routingW5CRM write-back, slice testing and the first messages a named person sendsW6Your BDC works live lists from drafts, then Agent Care starts
Reading the bandRevocation-latency testing runs in week 4, before a message reaches a customer in week 5. A stop honoured late is worse than a campaign that never ran.
At the end of W6Drafts have run beside your existing follow-up, with every figure still coming from a person and each stop written back across the systems we connect.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Automotive AI agent
Build an outbound agent around the consent you actually hold.
Show us a quarter of outbound follow-up — the lists, the messages that went out and the complaints, wrong numbers and opt-outs behind them. We'll re-run those campaigns against your own consent record and mark every number that should never have been worked.
