FAQs
FAQs
Do I need a dedicated service hub if I am small and can handle support from a shared inbox? A shared inbox works right up until it does not, and the switch-over is painful because you have no structure to migrate. Even small, a real service hub gives you ownership, SLAs you can keep, and the ticket data that becomes your knowledge base and your churn signal. Configure a lightweight version early rather than retrofitting structure onto a year of unstructured email.
How many ticket pipelines should I have? Start with one and split only when a workflow is provably distinct in its stages, owners, and SLAs. Support, onboarding, and bug escalations are common candidates for separate pipelines because they are genuinely different processes. The failure is the dozen-pipeline sprawl that fragments your reporting and makes agents guess where a ticket belongs, so add a pipeline because the work demands it, not because you can.
What is a sensible first-response SLA target? It depends on your customers and your channels, so set it deliberately rather than copying a number. The principle that holds across cases: first response is the promise that protects the relationship, so make it fast enough that the customer never feels abandoned, tier it so your enterprise and severe cases get a tighter target, and crucially configure the system to enforce and escalate it rather than trusting people to remember.
Will a chatbot annoy my customers more than it helps? Only if you configure it to trap them. A bot that answers common questions well and hands off to a human the instant a customer is frustrated or asks for a person is a genuine improvement to response time. The line to draw in configuration is that the bot serves the people who want a fast self-serve answer and never blocks the people who need a human, so always wire an obvious, immediate escape to a person.
How do I know if my knowledge base is actually working? Measure deflection, not article count. Track which articles get read, which resolve the question, and how many tickets still come in on topics you have covered. A working knowledge base shows falling ticket volume on its covered topics and articles that customers read and rate as helpful. If you cannot see those numbers, you have a content pile, not a deflection system, so configure the tracking before you judge the result.
Should support metrics be shared with sales and the rest of the business? Yes, the few that signal revenue risk. An account owner needs to see that a strategic customer just raised its third escalation or that its satisfaction dropped, because that is often the earliest warning of churn. Push open tickets, recent escalations, and satisfaction onto the CRM record as read-only and wire an alert on the high-value cases, so a support signal becomes a business action rather than a number stuck in the support team's dashboard.