A SaaS company's website chat receives two very different kinds of conversation. Prospects asking about pricing, features and fit. Customers asking why their export failed. When both land in the same queue, prospects wait behind support tickets, and support agents field sales questions they cannot answer.
Routing chat between sales and support is a small process decision with a big effect. Get it right and prospects reach sales quickly, customers get help without friction, and nobody's time is wasted.
Why mixed queues cause problems
In a single queue, whoever is available picks up the next chat. Support agents get pricing questions and either guess or pass them on. Sales reps get technical questions and do the same. Every handoff adds delay and forces the visitor to repeat themselves.
Worse, high-intent prospects can wait behind routine support questions. A buyer ready to talk about a large plan leaves while the queue clears.
Sorting conversations early
One question does most of the sorting:
Assistant: Are you currently using the product, or exploring whether it's right for you?
Signals confirm it. Questions about plans, demos, migration and fit are sales. Questions about errors, settings, billing and account access are support.
Routing rules
Write simple rules and share them:
- Prospects with qualifying signals go to sales, with the conversation and qualification answers attached. Qualification is covered in qualifying demo requests before they reach sales.
- Existing customers with problems go to support, as tickets or live handovers.
- Routine questions from anyone are answered instantly from docs, without taking either team's time.
- Everything else goes to a named owner, so nothing falls between teams.
Want a 24/7 AI Employee for Your Website?
See how SpideyChat can answer customer questions, capture leads and handle enquiries while your team is offline.
Covering hours when teams are offline
Sales and support rarely keep the same hours, and neither covers nights. SpideyChat for SaaS companies answers routine questions at any hour, captures sales leads for the morning, and opens support tickets with context. Both teams start the day with sorted conversations.
Onboarding questions blur the line
New customers in their first weeks ask questions that are part support, part sales: "Which plan do we need now that the team is bigger?" These deserve careful routing because they are also churn signals, as described in onboarding questions that predict churn. Many teams route them to customer success.
Keeping both teams involved
Routing works best when both teams help shape the answers. Support knows which questions confuse users; sales knows which ones decide deals. Both should contribute to what the assistant knows, a point made in why your support team should help train the chatbot.
Routing is not unique to software. Property developers route buyers, agents and investors differently, as seen in new build sales teams and repetitive spec questions.
Signs routing is failing
Watch for prospects who say "I already explained this," support tickets that arrive with pricing questions, and sales reps spending time on password resets. Each is a sign that the sorting question is missing or the rules are unclear. Review a sample of handed-over conversations each month and adjust. The fix is usually small: a clearer sorting question, or a rule for a type of conversation nobody had assigned.
Setting it up
Agree your routing rules, add the sorting question to your first reply, and decide who owns each category. The installation guide and training guide cover setting up an assistant with your docs, pricing and routing questions.