Place check calls that open with who is calling, that it is an AI and that the line is recorded — with a consent record on file first, and a person on request.
A total across call reasons is the wrong number to read
Break the log down by call reason before reading the total — first contact and in-transit calls carry most of the hand-offs, and a blended figure hides both. Nestack reports the hand-off rate by call reason, not only in total.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
First contact with a new carrier
3.9%
3.5×
Review
In-transit status on a moving load
2.6%
2.4×
Review
Detention and appointment changes
1.8%
1.6×
Watch
Scheduled pickup confirmations
0.8%
0.7×
Normal
Bar: hand-off-rate lift vs. scheduled-pickup baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
If there is no case, the cycle is open
Explaining a bad call does not close the cycle. A standing regression case does, and that suite is what the next check call placed is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Hand-off rate rises in a call reason.
02Diagnose
Every call is replayed against the consent state it was placed under, and one cause is kept.
03Improve
The fix is versioned against the calls that produced it.
04Verify
The release stops until every affected case is passing.
05Learn
The case stays in the suite, and the calling rules are amended.
Learn → DetectThe return edge. What comes next is tested against a suite that grew.
Typical build scope
Twelve workstreams across six weeks
The build scope read against the delivery timeline. Week structure follows the six-week plan — discovery, sources, calling workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Check-call workflow discovery and boundary definition.
02Telephony and visibility assessment.
03Consent record, disclosure and duty-status rule mapping.
04Consent-state and load ingestion.
05Call scripting and disclosure binding.
06Confidence scoring and hand-off routing.
07Person-on-request workflow.
08Telephony and TMS integration.
09Disclosure and recording cases.
10Guardrails and consent controls.
11Call-trail instrumentation.
12Deployment, documentation 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 lane set, one number poolProductionProduction telephony and TMSAdvancedMultiple entities / regions
Introduced at Pilot
Calling on your own consent records✓✓✓
Person on request✓✓✓
Call-quality baseline✓✓✓
Introduced at Production
Reporting by call reason—✓✓
Hand-off workflow in your systems—✓✓
Approved write-back—✓✓
Visibility-platform integration—✓✓
Introduced at Advanced
Multi-entity calling rules——✓
Multi-stage desk approvals——✓
High call volume——✓
Multi-state calling controls——✓
Build priceFrom $5,000From $8,000Custom quote
Final build priceConfirmed after discovery based on integrations, workflow complexity, transaction volume, approval controls 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 calling policy→Consent-state and load ingestion and disclosure mappingWeek 1
02Representative past check calls→Calling baseline, disclosure binding and the duty-status gateWeek 2
03Your disclosure text and revocation route→Consent record, disclosure and duty-status rule mappingWeek 1
04Access to relevant APIs, feeds or exports→Telephony and visibility assessment, then integration setupWeek 2
05Calls you would not want placed→Consent cases and the evaluation suiteWeek 4
06What a call may never ask a moving driver→Confidence scoring, hand-off routing, guardrails and consent controlsWeek 3
07Named people to take handed-over calls→Person-on-request workflow, then pilot and production validationWeeks 5–6
Nothing else is requiredDeployment, documentation and Agent Care handover are ours.
Delivery timeline
Four phases across six weeks
Phases occupy the weeks the work really needs, so week 5 runs evaluation and launch side by side.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Check-call workflow discovery, consent mapping and the boundaryW2Telephony and visibility integration and the calling baselineW3Calling workflow, confidence logic and hand-off controlsW4Evaluation suite, consent cases and failure-mode testingW5TMS integration, a pilot lane set and targeted correctionsW6One week of check calls run under the desk, then handover
Reading the bandEach bar covers only the weeks its work is named in. The week 5 overlap is real, not padding.
At the end of W6The week closes validation and Agent Care picks up the monitoring.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Transportation AI agent
Build a check-call agent that discloses before it asks anything.
Show us your numbers, your consent records and your call reasons. Name the person who signs off the disclosure text and owns the consent register — the calls go out in your name, and that is who we build around.
