What Replyee's voice receptionist must do for a bail-bond agency (using Big Mike's Bail Bonds as the live case), how each capability is delivered through Replyee + Retell, what's ready vs. what to build, and the real cost to run + what to charge.
Straight from the client spec — the receptionist has to:
| Capability | How it's delivered | Status |
|---|---|---|
| 24/7 pickup + bond/rate Q&A + routing | Retell always-on voice + Replyee shared knowledge base (same RAG the chatbot uses). Routing = Retell transfer_call. | Config + KB |
| "What do I need to get someone out?" | Answered from the knowledge base (bond process, docs, collateral). | KB content |
| Spanish support | Retell multi-language; agent answers in caller's language from the same KB. | Ready |
| Custom voice (gender/accent/tone) | Retell voice selection in the agent config (adapter already maps this). | Ready |
| Full call transcripts | Retell posts transcripts to Replyee's /api/voice/webhook → stored per bot for follow-up. | Wire webhook store |
| Spam/robocall filtering | Retell call screening + agent guardrails; only qualified calls forwarded. | Config |
| Custom voice + setup ~10 min | Create Retell agent from the bot (adapter does this) + assign a phone number. | Ready |
| Text intake link to ready leads | Retell function-call → Replyee sends SMS via the shared @boom/sms rail with the agency's intake URL. | Build |
| Recognize repeat clients + case | Retell function-call on inbound number → Replyee looks up the caller in the agency's client/case data → primes the prompt. | Build |
| Alert if forwarded call unanswered | Watch the transfer result from the webhook; if unanswered, fire an SMS/email alert to the team. | Build |
| Portal on/off toggle | BMBB portal calls Replyee's internal API (Bearer-authed) to activate/deactivate the agent. | Wire endpoint |
Read: the whole core (pickup, Q&A, transcripts, voice, language, spam) is Ready/config — Retell + Replyee's shared knowledge already do it. The 4 build items (SMS intake, repeat-client lookup, unanswered-alert, portal toggle) are small, well-scoped additions — and SMS reuses the @boom/sms rail you already planned.
Costs are dominated by talk minutes. Retell is pass-through COGS you mark up. Rough all-in per-minute stack:
| Component | Rate | Notes |
|---|---|---|
| Retell voice engine | ~$0.07–0.10 / min | STT + turn-taking + orchestration |
| Telephony (Twilio via Retell) | ~$0.01–0.02 / min | inbound minutes |
| LLM (Claude Haiku) | ~fractions of a ¢ / min | cheap; your ANTHROPIC key already set |
| Premium voice (optional, ElevenLabs) | ~$0.07 / min | only if using a premium custom voice |
| Phone number | ~$2 / mo | fixed, per number |
| Volume | Calls/mo | Minutes | ~Cost/mo |
|---|---|---|---|
| Light | 150 | 450 | ~$45–55 |
| Typical bail agency | 300 | 900 | ~$90–110 |
| Busy | 600 | 1,800 | ~$180–220 |
Replyee already exposes what the portal needs:
/api/internal/bots, Bearer-authed) — the portal creates/reads/updates the bot and gets the embed snippet. Extend it with an activate/deactivate voice action to power the portal's "Deactivate AI Receptionist" toggle.<script src="https://replyee.online/widget.js" data-bot-id="…" async></script> drops the AI chat onto the site./api/voice/webhook receives Retell events (transcripts, call status) to log + trigger alerts.So the BMBB portal shows one card ("24/7 AI Receptionist") with the on/off toggle → calls Replyee's internal API → Replyee manages the Retell agent. Chat + voice share the same bot + knowledge, so they answer identically.