Route VIP Customers Around the AI Queue

The problem with treating every ticket the same

Your AI agent handles the repetitive work well — password resets, billing lookups, plan comparisons. But when your largest enterprise customer opens a ticket at 9 a.m. on the day of their renewal, the last thing you want is a bot asking them to 'describe the issue in more detail.'

The default queue is a blunt instrument. It optimizes for volume, not for relationship risk. A routing layer that can't distinguish a trial user from a customer paying you $4,000 a month will treat them identically, and that's an operational choice with a real cost: slower human response for the accounts where speed matters most, and a sense — however unfair — that they're just another ticket.

The fix isn't to turn the AI agent off. It's to build routing rules that intercept specific accounts before the AI ever responds.

What you need before you build the rules

Three inputs make this work:

• A reliable VIP signal. This is usually a custom attribute on the contact or company record in your CRM — something like plan_tier: enterprise, arr_band: high, or a boolean is_vip: true. If that attribute doesn't exist yet, create it. Routing is only as good as the data feeding it.
• A way to pass that signal to Chattering. When a visitor opens the chat widget, Chattering can receive identity data you pass via the embed snippet — company ID, plan tier, account owner. That handshake is what lets routing rules act on CRM attributes in real time.
• A named human queue or team inbox. VIP bypass only works if there's somewhere specific to send those conversations. 'Human agents' is too vague — you want a dedicated inbox that your most senior support reps actually watch.

Building the routing rule in Chattering

In Chattering's routing configuration, rules are evaluated in priority order before the AI agent handles anything. A rule sits at the top of the stack and says: if the incoming contact matches these conditions, skip AI and assign directly.

A working VIP rule looks like this in plain logic:

If contact.plan_tier equals enterprise or contact.is_vip equals true → assign to Enterprise Support inbox → skip AI queue

Once that rule fires, Chattering opens the conversation in the shared inbox with the full context already attached — contact name, company, plan, any previous conversation history. The agent picks it up without needing to ask for account details. The AI never sends a first reply.

You can layer conditions. Say you want to catch high-value accounts on any paid plan, not just enterprise — add contact.arr_band equals high as an OR condition. You can also trigger on conversation metadata: if the subject line contains 'cancellation' or 'data export', route to human regardless of plan tier. Urgency signals matter as much as account value.

What happens at the human end

Routing a VIP conversation to a human inbox is step one. Making sure it's actually handled quickly is step two.

We recommend a few operational practices alongside the rule itself:

• Set a strict first-response SLA for the VIP inbox — something shorter than your standard queue. If a conversation sits unacknowledged for more than a few minutes, it should trigger a notification or an escalation ping to the team lead.
• Assign account ownership. When Chattering passes the conversation to the inbox, the agent who owns that account should be the default assignee. Chattering lets you map company attributes to specific agents, so 'Acme Corp' automatically lands with the rep who knows them.
• Keep the AI in the thread for internal use. Even when the AI doesn't send a customer-facing reply, you can still use Chattering's internal suggestions to surface relevant docs or draft a reply for the agent to review. The agent gets the efficiency benefit without the customer seeing bot-generated first contact.

Handling gaps in the data

The rule only fires reliably when the identity data is clean. In practice, you'll hit edge cases: a VIP reaches out from a personal email not in your CRM, or a new enterprise contact hasn't been tagged yet.

A fallback rule handles this. Below your VIP rule, add a catch-all for any contact whose plan tier is unknown or missing — route them to a general human review queue, not straight to AI. It's a conservative default, but it means an unidentified enterprise contact doesn't accidentally get the self-serve bot experience.

Over time, gaps in your data show up as a trickle of 'unknown tier' conversations in that review queue. That's a useful signal: it tells you which records in your CRM need enrichment.

Keeping the rules maintained

Routing rules are infrastructure, and infrastructure drifts. Schedule a monthly review — fifteen minutes, not a meeting — to check whether the VIP conditions still match how your sales team defines high-value accounts. If sales changed the CRM field name from plan_tier to subscription_level, your routing rule silently stops working.

Version-control your routing logic in a shared doc alongside your CRM field definitions. When the rule breaks, you want to debug it in under five minutes, not spend an hour reconstructing what it was supposed to do.

Done right, VIP routing is invisible to the customer — they just get a fast, personal response. That's exactly the point.