Answer inbound enquiries, book tours and trials, and follow up only where the consent record allows it — then hand the lead to the named sales rep, who decides what is sold.
Break the amendment rate down by lead source before you read it in total. Over every enquiry it looks small; concentrated in the sources whose provenance is thinnest, it does not.
Slice performance — reported separately, not only in aggregateIllustrative example
Slice
Failure rate
Lift
Lift vs. threshold
Status
Purchased and aggregated leads
5.1%
3.5×
Review
Shared comparison-form leads
3.0%
2.1×
Review
Reactivated lapsed enquiries
2.3%
1.6×
Watch
Leads from the club's own forms
1.3%
0.9×
Normal
Bar: amendment-rate lift vs. the all-lead baseline · scale 0–4.0× · tick marks the 2.0× review threshold2 of 4 slices over threshold
Evidence-linked improvement
Each cycle ends with one more case
Nothing closes because it was understood. It closes when the next release has to pass a case, and that suite is what the next reply out is measured against.
Improvement cycle · five stagesSwitchback — the path turns at Improve and returns at Learn
01Detect
Amendments and post-send corrections rise in one lead source.
02Diagnose
If the consent record was wrong, the reply was wrong before it was written — so both are read.
03Improve
Changes ship against a version with the conversations that caused them.
04Verify
A failing case blocks release until it clears.
05Learn
The case is permanent, and the outreach rules move with it.
Learn → DetectThe return edge. The next detection is measured against the longer suite.
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, response workflow, evaluation, integration, then production validation and handover.
WorkstreamWeek 1Week 2Week 3Week 4Week 5Week 6
01Enquiry workflow discovery and boundary definition.
02CRM, telephony and messaging assessment.
03Consent, calling-window and state mini-TCPA mapping.
04Enquiry ingestion and consent normalisation.
05Response logic and consent binding.
06Confidence scoring and handover routing.
07Sales handover workflow.
08CRM and messaging integration.
09Consent-path regression cases.
10Guardrails and outreach controls.
11Contact-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 site, one lead sourceProductionProduction lead volumeAdvancedMultiple sites / brands
Introduced at Pilot
Replies from your published information✓✓✓
Sales-rep handover✓✓✓
Response-quality baseline✓✓✓
Introduced at Production
Reporting by lead source—✓✓
Handover workflow in your CRM—✓✓
Approved write-back to the CRM—✓✓
Sales-CRM integration—✓✓
Introduced at Advanced
Multi-state rule sets——✓
Multi-stage sales approvals——✓
High enquiry volume——✓
Multi-site sales 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 enquiry channels and the consent captured on each→Enquiry workflow discovery and boundary definitionWeek 1
02Representative answered enquiries→Response baseline, source binding and disclosure wordingWeek 2
03Your published membership card and club information→Consent, calling-window and state mini-TCPA mappingWeek 1
04Access to relevant APIs, feeds or exports→CRM, telephony and messaging assessment, then integration setupWeek 2
05Follow-ups that should not have been sent→Consent cases and failure-mode testingWeek 4
06Where follow-up must hand over to a person→Confidence scoring, handover routing, guardrails and outreach controlsWeek 3
07Named sales reps to take leads over→Sales handover 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
Each band covers the weeks it genuinely occupies, so the fifth week holds two kinds of work.
PhaseW1W2W3W4W5W6
DiscoveryW1
BuildW2 – W3
EvaluateW4 – W5
Pilot & LaunchW5 – W6
Week focusW1Enquiry workflow discovery, consent mapping and the automation boundaryW2Channel integration and the response baselineW3Response workflow, confidence logic and handover controlsW4Evaluation suite, consent checks and failure-mode testingW5CRM integration, pilot enquiries and targeted correctionsW6A live enquiry queue worked under the sales team, then Agent Care handover
Reading the bandEach band covers the weeks its work is named in, and no others. The week 5 overlap is real, not padding.
At the end of W6Live enquiries close the validation and monitoring moves to Agent Care.
DurationSix-week plan shown · typical delivery 4–6 weeks depending on scope confirmed in discovery.
Next step · Fitness AI agent
Build a lead-conversion agent around the consent you already hold.
Show us your enquiry channels and who takes a lead over. If you can show us where each lead's consent came from, we'll map the follow-up, set the automation boundary and name what stays with the rep.
