Topic hub
Support operations and knowledge-base guides
Plan a help desk, customer-support reporting and SLAs, then structure public knowledge, portals and self-service around real customer tasks.
Start with the support process, not the software settings. A useful rollout decides which messages become tickets, who owns the queue and when work is escalated. The same discipline makes self-service useful: a customer needs a findable, accurate answer and a clear route to a person when it does not fit.
Start with the buying decision
Shared inbox vs help desk
Know when collaborative email is enough and when formal ticketing becomes worthwhile.
Compare the models → PricingHelp desk software pricing explained
Model seats, tickets, AI, onboarding, integrations and future growth.
Understand the whole cost → Selection processHow to choose help desk software
Turn queue problems into requirements, run a fair trial and verify the exit route.
Use the selection process →Cost, security and procurement
Use these guides to compare a working configuration, test data-handling claims and turn a sales demonstration into a verifiable buying decision. The privacy pages are buyer guidance, not legal advice.
Calculate the total cost of a help desk
Model seats, usage, AI, setup and renewal across normal, peak and growth cases.
Build the cost model → Pricing modelPer-agent vs per-ticket pricing
See which changes drive the bill as your team or ticket volume grows.
Compare the models → Free plansFree help desk plan limits
Check seat, channel, automation and exit constraints before relying on a free tier.
Check the limits → AI costBudget for AI support add-ons
Forecast usage, overages and human review before turning on paid AI features.
Model AI spend → SecurityHelp desk security checklist
Test access, authentication, exports, integrations and incident evidence.
Use the checklist → UK GDPRUK GDPR questions for help desk buyers
Review roles, processor terms, subprocessors, transfers and rights handling.
Ask the privacy questions → Data locationHelp desk data residency
Trace hosting, backups, support access and integrations separately.
Map the data path → Data lifecycleHelp desk data-retention settings
Connect a justified retention schedule to deletion, backups and exports.
Test the settings → ProcurementHelp desk procurement checklist
Collect workflow, commercial, security and exit evidence before signing.
Review the decision → Vendor demoQuestions to ask in a help desk demo
Make suppliers prove the exact tasks your support team needs to run.
Prepare the demo →Run the support operation
When to move beyond a shared inbox
Audit ownership, duplicate replies and follow-ups before buying a ticket queue.
Check the signals → ReportingHelp desk reporting for small teams
Measure backlog, demand and response quality without misleading averages.
Build a useful report → Service promiseSet customer-support SLAs
Match response targets to staffed hours, priority and real customer outcomes.
Set realistic targets →Understand the numbers
Use the small-team reporting overview to choose a focused set, then go deeper on the measure you need to improve.
First-response time explained
Define the first human reply, calculate the wait and find the slowest cases.
Measure first response → OutcomeTicket resolution time explained
Separate first and full resolution, reopens and customer waiting.
Measure resolution → FeedbackCustomer satisfaction score
Calculate support CSAT and read the response rate behind it.
Interpret CSAT → Queue riskSupport-ticket backlog
See unresolved work by age, owner and blocker.
Review backlog → QualityTicket reopen rate
Distinguish repeat reopen events from unique cases and find the cause.
Check reopens → CapacitySupport-agent workload
Balance active cases with complexity and staffed hours.
Plan fair workloads → Self-serviceMeasure self-service success
Track solved tasks and failed searches, not merely page views.
Assess outcomes → PlanningForecast ticket volume
Turn historic demand and business events into a staffing range.
Forecast demand →Knowledge bases and self-service
Build a small-business knowledge base
Choose real customer questions, publish complete answers and assign content owners.
Build the first release → StructurePlan a knowledge-base structure
Use task-based categories, stable article URLs and findable cross-links.
Plan the structure → AccessInternal vs external knowledge base
Separate public answers from staff-only decisions and sensitive procedures.
Set the boundary → SearchKnowledge-base SEO
Make useful public articles discoverable without duplicating or stuffing content.
Improve findability → Self-serviceCustomer portal vs knowledge base
Know when public answers need a signed-in case and status experience.
Compare the surfaces → AI and peopleAI chatbot vs live chat
Use automation for safe routine answers and people for judgement and trust.
Choose the right model →For practical setup and migration, visit the support workflows and operations hub.