Skip to content
Right On Call

Technology

How the receptionist books, texts, and stays inside its limits.

Most voice AI is a prompt and a hope. Right On Call splits the live conversation from the systems that book, dispatch, and text, then puts guardrails in code so the agent cannot invent a slot or quote a repair.

The voice

A real-time orchestrator owns the phone call: speech in, a live model, speech out. We configure it with your script and the tools it is allowed to use. Vendors are swappable. We aren't locked to one voice stack.

The hands

Our backend answers those tools during the call: service area, availability, booking, dispatch, SMS. Every external system sits behind an adapter, so going live is configuration, not a rewrite.

Your business, as config

Name, hours, coverage, emergencies, fees, and technician roster live in structured config. Changing how the receptionist behaves doesn't mean changing application code.

What the agent is forbidden to do

Invent availability

Booking re-checks the live calendar. If the slot is gone, it offers another. It does not bluff.

Diagnose or quote a repair

It captures symptoms and unit details. Price and diagnosis stay with your technician.

Wing a safety call

Gas, smoke, or spark reports take a bounded script and a human callback, immediately.

More on why these limits are the product, not a caveat: What the Receptionist Is Forbidden to Do.

How we get you live

A first working version within 24 hours of a complete onboarding pack, and live within 7 days as the target. When it runs longer, it is usually because hours, coverage, or on-call numbers are still missing, or a field-service integration is part of the build.

  1. Day 0

    You send the onboarding pack

    Hours, service area, emergency rules, on-call numbers, greeting, and the tools you already use. The clock starts when this is complete, not when you first email us.

  2. Day 1

    You hear a first version

    Script, triage, dispatch rules, and the calendar or Jobber hook. Within 24 hours of a complete pack you hear a working first pass and mark what sounds unlike your shop.

  3. Days 2–5

    We wire the phones

    Included Twilio number, recording disclosure, SMS templates, dashboard access, and a private test line so you can argue with it before customers do.

  4. Days 6–7

    You go live

    Forward the public number, publish the included Twilio number, or port. We sit on the first real calls with you and tune anything that feels off. A field-service or property-system integration can take longer.

Curious which calendars and field-service tools this plugs into? See the integration catalog.