Customer Support and Voice AI
AI receptionist for small business: calls, bookings and handoffs
What an AI receptionist does on a real call, the rules that apply, a sample greeting and a pass/fail checklist to launch one safely.
Inbound
AI Voice Routing
The decision engine that sends each call to the right department, person or queue, based on what was actually said.
Where a call goes often depends on who answers it. One person sends billing questions to finance, another to support, and callers bounce between teams. AI Voice Routing replaces those judgment calls with your written rules. It listens to what the caller says, weighs factors such as time of day or caller history, and sends the call to the right person or queue.
- Sends each call to the right team based on what was said
- Applies written rules instead of informal judgment calls
- Logs every routing decision so you can spot patterns
$4,900
20–30 working days
Optional maintenance $249/mo
What it is
AI Voice Routing is the backend decision logic that sends an inbound call to the right department, person or queue based on what the caller says. It can sit behind your existing greeting or a natural-language front door, applying the rules you set to decide where each call belongs.
Why businesses buy it
Misrouted calls are expensive in a quiet way. Callers repeat themselves, colleagues spend time transferring, and some people give up before reaching anyone who can help. This build gives every call the same documented decision, whoever or whatever greets the caller first. When no rule fits, the call goes to your fallback instead of a guess, and every decision is logged for review. The Scope Card fixes the rule sets, systems and testing before you buy, so routing stops depending on who happens to be on shift.
Problems this solves
Calls land in a general queue and get passed around
AI Voice Routing listens to what the caller says and applies your rules to choose the department, person or queue. The call reaches the right place first time more often.
Your greeting works but the routing behind it does not
The routing logic can sit behind your existing greeting or a natural-language front door. You keep the caller experience you have and improve where calls end up.
Routing rules live in one person's head
The workflow, prompt and guardrail configuration writes your routing rules down in one place. The admin guide explains each rule, so others can follow and adjust them.
Urgent callers wait behind routine enquiries
Rules can send urgent requests to a named person or priority queue, using up to five call flows. Live transfer to a person remains available on every route.
A good fit if
You already have a way of greeting callers, but the decision about where the call should go is inconsistent or depends on whoever answers.
Routing needs to weigh more than one factor, such as caller history, time of day, or which team is currently available.
You want routing logic that can plug in behind more than one front door, such as a receptionist today and a different greeting later.
You track misrouted or re-routed calls and want a documented rule set instead of informal judgment calls.
Not the right fit if
You need the caller-facing menu experience itself, not just the backend decision. See AI IVR Intelligence, which replaces the keypad menu callers hear.
You want a single build that greets, answers questions and books, with routing as one part of a bigger job. See AI Voice Receptionist.
Most calls need a full conversation, not a routing decision. See AI Inbound Call Agent, the flexible base build.
You are routing outbound dialing attempts, not inbound calls. See AI Outbound Calling Agent.
How it works
- The call arrives through your existing greeting or front door, and the caller's request is captured as text and intent.
- The routing engine checks that intent against the rules you set: which team handles which topic, time-of-day coverage, and any caller history you have connected.
- Where more than one team could take the call, it applies your priority order rather than picking arbitrarily.
- The call is sent to the destination the rules point to, along with a short note on why that destination was chosen.
- If no rule matches confidently, the call goes to the fallback destination you set, rather than defaulting to guesswork.
- Every routing decision is logged, so you can see exactly why a call landed where it did.
What you provide within 72 hours
Your portal lists these the moment you order. Delivery starts the working day after everything is in and your access is checked.
- Access to the telephony or contact-center platform this routing logic should connect to, such as Twilio, RingCentral or Aircall.
- Your routing rules: which topics go to which team, any time-of-day coverage, and your fallback destination.
- Any caller-history or CRM data you want factored into a routing decision.
- The phone numbers or queues each destination in your rules should reach.
- Your preferred disclosure wording, if this build sits in front of the caller rather than purely behind another front door.
- Admin access and API keys for every connected system, shared by adding our team as a user or creating a key you control, never by email.
- One person who can approve the routing rules and sign off the test calls.
- An API key for your own AI model account (for example OpenAI or Google Gemini), created for this build with a spending limit.
The 72-hour rule. Send everything on your checklist, including access, within 72 hours of ordering so your build starts on time.
Timeline
Start
Intake confirmed and your routing rules documented.
Weeks 1–2
Routing logic and rule sets built against your destinations and priorities.
Week 3
Telephony platform and CRM connected, routing decisions tested end to end.
Weeks 3–4
Fifty test calls run across every rule set, transcripts and routing logs sent to you.
Week 4
Your review, with two rounds of changes to the rules.
Go-live
Live behind your call flow, recorded handoff session held, support begins.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 20–30 working days | $4,900 |
| Express | 15–25 working days | $5,750 |
| Rush | 10–20 working days | $6,600 |
What you receive at handover
- AI Voice Routing, configured and deployed on one phone number
- Your routing rules captured in workflow, prompt and guardrail configuration across up to five call flows
- Connection to up to two agreed systems, such as a CRM for caller lookup
- A test report from 50 test calls, with transcripts showing where each call was routed
- An admin guide and recorded 60-minute handoff session
- 30 days of post-launch support
Expected benefits and how to measure them
- More calls can reach the right team without a second transfer.
- Routing rules become documented and easier to change.
- Urgent callers can be separated from routine ones.
- First-time routing accuracy
- Sample calls each week and check whether the first destination was correct, before and after launch.
- Internal transfers
- Compare transfer counts in your phone system report for the month before and after go-live.
- Time to reach a person
- Use queue reports to compare average wait before connection across the same two periods.
Before you start: Pull a month of transfer and queue data from your phone system. Write down the current routing rules and who maintains them.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
The build price is paid one time. Running it is billed in your own telephony and AI accounts, roughly $0.13 to $0.31 per call minute all in, covering the voice platform, the AI model and telephony, plus number rental where this build owns the number directly. Because routing decisions happen quickly, the minutes this build itself adds to a call are usually small.
AI usage during build and testing is also billed to your own accounts, so every provider relationship stays yours.
Ask about running costsCustom requirements
Need more than five rule sets, or routing logic that spans more than two systems? Add a note at checkout and you get a written Change Quote, with work starting only once you accept it. Larger or bespoke projects go through the Custom AI request form instead.
Request a custom versionKeep it running
Monthly maintenance covers monitoring, fixes, updates, a monthly health report and change hours to adjust rules as teams or coverage hours shift. It starts after the thirty days of included support and can be cancelled any month.
$249/mo (the minimum fee, includes 2 change hours)
Optional. Starts after the post-launch support period. Cancel any month.
How maintenance worksHow this compares
| Do it yourself with a SaaS tool | Hire a custom agency | Upmark Labs | |
|---|---|---|---|
| Price | A contact-center platform's routing module is a per-seat add-on | A custom build gets quoted after discovery calls | Ours is one fixed price, shown on this page before you buy |
| Rule complexity | Most tools route on a single factor like time of day | Depends entirely on what the agency scopes | Ours can weigh intent, history and coverage together |
| Delivery | Routing rules are self-serve but take your team's time to build | An agency build usually runs several weeks | Ours has a fixed delivery time shown before you buy, with faster options |
| Transparency | Basic logs with limited reasoning detail | Depends on what was agreed with the agency | Ours logs why each call was routed where it was |
Questions about this product
Can AI Voice Routing work behind our existing receptionist or greeting?
Yes. It is built to sit behind whatever front door you already have, whether that is a live receptionist, an AI Voice Receptionist build, or a simple recorded greeting. It takes over once the caller's request is understood and applies your rules to decide the destination, without needing to own the greeting itself.
How is this different from AI IVR Intelligence?
AI IVR Intelligence replaces the caller-facing menu experience itself, the part the caller hears and speaks to. This build is the decision engine behind that experience, or behind any other front door, and focuses purely on where a call should go. Many businesses use both together, or this build alone behind an existing greeting.
What happens when no routing rule matches confidently?
The call goes to the fallback destination you set at intake, rather than being routed on a guess. That fallback is logged the same way as every other routing decision, so you can see how often calls fall through to it and adjust the rules if a pattern shows up.
What does AI Voice Routing cost to run each month?
Call minutes run roughly $0.13 to $0.31 all in, covering the voice platform, the AI model and telephony, plus number rental where applicable, paid directly in your own accounts. Because routing itself takes only seconds of a call, the cost this build adds is usually a small part of your overall call spend.
How long until our routing rules are live?
The delivery panel on this page shows the timeline for each speed. The clock starts once intake is complete: your destinations, routing rules, coverage hours, fallback number and system access. We test those rules across fifty calls with varied requests, share every routing decision with you, and give you two rounds of changes before live calls depend on them.
Do we need a recorded disclosure if this build never greets the caller directly?
If this build sits purely behind another AI or human greeting, that front door carries the disclosure. If it answers the call itself, in cases without a separate greeting, you provide the disclosure wording at intake, and it plays before the caller's request is processed.
Can we adjust the routing rules after launch?
Yes. Changes to priorities, coverage hours or fallback destinations all fit inside the monthly change hours included in maintenance, so routine adjustments do not need a new quote. A structurally new rule set beyond the five included is scoped and quoted as an Additional Workflow before that work starts.
Guides on this topic
All guides Stop letting call routing depend on who happens to answer.
Order AI Voice Routing and calls are being sent to the right destination by rule, not by chance, on a fixed delivery date.
Works well with
Inbound
AI Voice Booking Agent for Calendly
Books, reschedules and cancels appointments by phone, connected natively to Calendly so it reads and updates event types, availability and bookings.
Inbound
AI Voice Booking Agent for Outlook Calendar
Books, reschedules and cancels appointments by phone, connected natively to Outlook Calendar so it reads and updates availability and events.
Inbound
AI Voice Booking Agent for Google Calendar
Books, reschedules and cancels appointments by phone, connected natively to Google Calendar so it reads and updates availability and events.