All work
LEAD ROUTING
Leads that route themselves, and flag when they're unsure
Oliver (Full Throttle Adrenaline Parks) — multi-venue entertainment operator
Client
Oliver (Full Throttle Adrenaline Parks)
Work
LEAD ROUTING
Built with
Zoho CRM · Twilio · Resend
Result
Leads assigned in seconds
Situation
The starting point
Event inquiries landed in a shared inbox with no reliable owner. Some sat a day, some were worked twice. There was no confident measure of lead wait time, and no honest way to answer the question of what happened to a specific inquiry.
What we built
Scope
- 01A signed webhook endpoint taking inquiries from the web form, with duplicate detection on the way in
- 02A routing rules engine keyed on location and event type
- 03Immediate dispatch to the assigned rep by SMS and email, plus an automatic push into the rep's CRM record
- 04A review queue for the sales director, and response-time reporting that didn't exist before
Details that mattered
Where the work actually went
- 01Every lead is scored by a language model from 0–100. Anything below threshold routes to the director for a human ruling rather than being auto-assigned.
- 02Each ruling is written to a training log with the model version attached, so routing gets measurably better over time and you can see when and why it changed.
- 03SMS opt-in is captured at submission and STOP requests are honoured automatically.
What it proves
The question every owner asks about AI is what happens when it's wrong. This is the answer: a person sees the uncertain cases, their correction is recorded, and the system's mistakes are on the record instead of buried.
Stack
- Zoho CRM·
- Twilio·
- Resend·
- Anthropic Claude·
- Supabase
Have something like this?
Tell us what's broken, in your own words. We'll come back with whether we can help and roughly what it would take.