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.
Support Operations
AI Ticket Routing for Intercom
Each Intercom conversation is assigned to the right team inbox or teammate from what the customer says, not the menu they clicked.
Customers often pick the wrong option in an Intercom menu, or skip it entirely and just start typing. This workflow reads each new conversation and assigns it to the right team inbox or teammate based on the customer's messages, their contact attributes and the skills you define. It applies agreed tags and leaves a note with the reason, so every routing decision can be checked.
- Conversations routed by what customers say, not menu clicks
- Contact attributes used to reach the right team inbox
- Tags and a reason note added to every conversation
$3,400
20–30 working days
Optional maintenance $249/mo
What it is
AI Ticket Routing for Intercom reads each new Intercom conversation and assigns it to the right team inbox or teammate, based on the customer's messages, their contact attributes and the skills you define. It applies agreed tags, leaves a note with the reason, and runs in the background.
Why businesses buy it
Intercom conversations that land in the wrong inbox get bounced between teams, and every reassignment adds minutes to the response time a customer sees. Meanwhile someone keeps an eye on the unassigned view instead of helping customers. After launch, conversations reach the right team inbox or teammate as they arrive, tagged and explained. The Scope Card lists the inboxes, routing fields and fallback rules before you order, so you know exactly how conversations will move through your workspace.
Problems this solves
Intercom conversations sit unassigned in the main inbox
Each new Intercom conversation is assigned to the right team inbox or teammate. The choice uses the customer's messages, their contact attributes and the skills you define.
High-value customers wait in the same line as everyone else
Contact attributes, such as plan or account type, can steer routing under your rules. Conversations from the customers you prioritize go to the right teammate first.
Intercom tags are applied by hand, if at all
The workflow applies agreed tags to each conversation and leaves a note with the routing reason. Your Intercom reports gain consistent tags without extra effort from the team.
A good fit if
Chats and emails pile into one Intercom inbox, and someone spends the start of each shift reassigning them.
Your assignment depends on which option customers pick in a menu, and many skip it or choose the wrong one.
Contact attributes such as plan or company already sit in Intercom, but nothing uses them to decide who answers.
You can create an Intercom app access token, and an Intercom admin can join a thirty-minute setup call.
Not the right fit if
You want conversations answered directly, not just assigned. See AI Customer Support Agent for Intercom.
Teammates need drafted replies once a conversation reaches them. See AI Support Copilot for Intercom.
New customers need guided onboarding conversations. See AI Customer Onboarding Agent for Intercom.
Gaps in your help center are what create the volume. See AI Support Knowledge Agent for Intercom.
How it works
- Your support lead and we map the team inboxes, the teammates in each, their skills, and which kinds of conversation belong where.
- On a thirty-minute call, your Intercom admin agrees what the router may change: assignee, team inbox and tags.
- When a conversation starts, the router reads the customer's messages and contact attributes, such as plan or company, then makes one AI routing decision.
- It assigns the conversation, applies the agreed tags and adds a note with the reason for whoever picks it up.
- Conversations that match no route go to a fallback inbox you choose, rather than to a guess.
- Your existing assignment rules are reviewed at intake so the two never compete, and failed updates are retried, then reported.
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.
- An Intercom app access token, created by your admin.
- Your Intercom admin for the thirty-minute mapping call.
- A description or short recording of how conversations are assigned today.
- Your team inboxes, teammate skills, tags, escalation rules and support hours.
- Five to ten real conversations showing typical routing choices.
- Who receives alerts and errors, plus access to the second system if used.
- A decision-maker to approve the inbox and skills map.
- 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 verified; Intercom admin call booked.
Weeks 1–2
Inbox and skills map documented; routing workflow built.
Week 3
Intercom and the second system connected; tags and notes tested.
Weeks 3–4
Twenty test runs on past conversations, results shared.
Week 4
Support lead reviews routes; two rounds of changes.
Go-live
Routing live conversations; recorded handoff; support starts.
| Option | Delivery time | Price |
|---|---|---|
| Standard | 20–30 working days | $3,400 |
| Express | 15–25 working days | $4,000 |
| Rush | 10–20 working days | $4,600 |
What you receive at handover
- The routing workflow running in the background on your Intercom workspace
- Two-way Intercom connection with documented field mapping, plus up to one more system
- One workflow of up to twelve steps, set to your team inboxes, skills and tags
- Access through invites or keys you control, with no keys sent by email
- Test report from 20 test runs on sample data
- Admin guide, recorded 45-minute handoff session and 30 days of post-launch support
Expected benefits and how to measure them
- Conversations can reach the right team inbox straight away.
- Priority customers can be routed the way you choose.
- Consistent tags help Intercom reports reflect real demand.
- Time to assignment
- Compare time from conversation start to assignment in Intercom reports for four weeks before and after launch.
- Conversations reassigned
- Count conversations reassigned between inboxes. Compare the month before and after launch.
- Tagged conversations
- Report on the share of conversations carrying an agreed tag, before and after launch.
Before you start: Save Intercom reports on assignment time, reassignments and tag coverage for the month before setup.
These are things to track, not promised results. Outcomes depend on your data, your team and your market.
Running costs
The build is a one-time cost. Running it costs roughly $20 to $100 a month for the automation platform and AI usage, in your own accounts, mostly depending on conversation volume. Your Intercom subscription is unchanged.
Usage during testing is billed to your accounts as well.
Ask about running costsCustom requirements
Routing across several Intercom workspaces, a third connected system, or more than twelve workflow steps needs a written Change Quote. Leave a note at checkout and the quote follows.
Request a custom versionKeep it running
Monthly maintenance covers monitoring, fixes, updates, a monthly health report and change hours for work such as a new team inbox, new tags or a revised skill. It starts after the post-launch support period, bills monthly 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 | AI add-ons bill per resolution or seat | An Intercom consultant bills per project | Ours is one fixed price, shown on this page before you buy |
| Decision basis | Menu choices and simple conditions | Rules written during the project | Ours reads the messages and contact attributes |
| Unclear cases | Fall into a default inbox unexplained | Depends on the build | Ours sends them to your fallback inbox with a note |
| Delivery | Rules are quick to add, slow to tune | Set per project | Ours has a fixed delivery time shown before you buy, with faster options |
Questions about this product
Does AI Ticket Routing for Intercom handle chats as well as emails?
Yes. It works on Intercom conversations whichever channel they started in, provided they arrive in your Intercom inbox. Chat, email and other channels you have connected to Intercom are treated the same way, so routing does not depend on how the customer chose to get in touch.
Can the Intercom router use contact attributes like plan or company?
Yes. It reads the contact attributes named in the mapping, such as plan, company or account owner, alongside the messages. That lets you send a large account's conversations to the team that manages it. Contact records are read for routing and are not edited unless the mapping says so.
When does the Intercom router make its decision?
Usually when the customer's first message arrives, though the trigger is agreed at intake. If that message is too vague to place, the conversation goes to your fallback inbox with a note, rather than being assigned on a guess. Teammates can still reassign any conversation manually.
Which Intercom tags can the router apply?
The tags listed in the agreed mapping, such as product area or request type. It does not create new tags on its own, which keeps your tag list tidy for reporting. Adding a tag later is a small change that fits inside the monthly change hours in maintenance.
What is the delivery time and price for Intercom ticket routing?
One fixed price covers the whole build and is shown on this page before you buy, with express and rush delivery listed beside it at a set extra cost. Each includes twenty test runs on your past conversations, two rounds of changes and a recorded 45-minute handoff, followed by 30 days of support.
Will customers notice any change in the Intercom Messenger?
No. The router works in the background and has no customer-facing channel. Customers write to you exactly as before. The only differences are behind the scenes: conversations land with the right team inbox or teammate sooner, carry the agreed tags, and include a note explaining the choice.
Guides on this topic
All guides Route Intercom conversations by what customers actually say.
Order the Intercom edition and new conversations go to the right team inbox or teammate, tagged and explained, based on the customer's own words.
Works well with
Support Operations
AI Ticket Classification
Tags incoming tickets by topic, product, urgency and sentiment.
Support Operations
AI Support Copilot
Drafts replies and surfaces relevant articles for human agents inside the helpdesk.
Support Operations
AI Support Knowledge Agent
Finds gaps in your help center and drafts new articles from resolved tickets.