How can we help?
Find setup guidance, product concepts, workflow patterns, and practical answers for running customer service on Protocol. Start with a topic if you are learning a product area, or use the guides when you have a specific operating decision to make.
Browse help topics and practical guides below.
Plan your first Protocol workspace
Map the channels, teams, ownership rules, customer data, and service workflows that should be included in the first rollout. Keep the initial scope focused enough to validate routing, handoffs, permissions, and reporting before expanding to more teams.
Decide when to use a ticket
Use a conversation for the live customer interaction and create a ticket when the issue needs structured work beyond the reply itself. Tickets are most useful when ownership, dependencies, due dates, tasks, or service targets need to remain visible over time.
Design a routing model that can handle exceptions
Combine issue intent, language, priority, customer context, expertise, and workload only where those signals affect a real ownership decision. Define a visible fallback path for conversations that cannot be classified confidently instead of forcing uncertain work into an arbitrary queue.
Set review points for AI-assisted actions
Match the level of human review to the consequence of the action being proposed. Drafting and summarization can be treated differently from changes involving billing, access, sensitive account data, or commitments made to a customer.
Turn recurring questions into better knowledge
Use repeated customer questions and agent feedback to identify missing, unclear, or outdated articles. Prioritize the knowledge backlog by customer impact, frequency, policy risk, and the amount of repeated service work the gap creates.
Standardize service automation safely
Begin with predictable decisions that have clear inputs, actions, and exception paths. Document each workflow's trigger, owner, permissions, failure behavior, and customer impact before adding more complexity.
Build a useful quality review program
Define observable criteria for accuracy, clarity, empathy, process adherence, and resolution quality so reviews can be applied consistently. Use broader automated review to find conversations that deserve manager attention, then calibrate the scorecard against real coaching decisions.
Investigate a changed service metric
Move from the dashboard number to the conversations, queues, customers, workflows, and exceptions that explain the change. Review related signals together so improving one metric does not quietly make transfer rate, reopens, or resolution quality worse.
Getting started
Set up your workspace, teams, ownership model, and first service workflow. Start here if you are mapping Protocol to an existing support operation or preparing an initial rollout.
Inbox
Learn how conversations enter the workspace, how teams assign and organize them, and how internal collaboration stays separate from customer replies. Use these guides for queues, views, notes, channels, and routing decisions.
Tickets
Use tickets when a customer issue becomes structured work with owners, dependencies, dates, tasks, or an SLA. The guidance focuses on keeping the original conversation and customer context attached as the issue moves between teams.
Customers
Understand how customer records bring service history together with connected account, billing, product, and company context. These guides also explain when an external CRM or other system should remain the authoritative source.
Protocol Intelligence
Understand summaries, recommendations, source context, permissions, and approved actions. The goal is to make AI-assisted work reviewable and useful inside the service process rather than treating it as a separate chatbot.
Automation
Build workflows with explicit triggers, conditions, actions, approvals, and exception paths. Start with stable service decisions such as routing or follow-up, then expand only when the operating rule is clear.
Knowledge
Create and maintain internal guidance and customer-facing help content from the same knowledge system. Learn how recurring customer questions can reveal missing, unclear, or outdated documentation.
Reports
Review response, resolution, SLA, backlog, quality, and workflow signals, then investigate the service activity behind a changed metric. Use reporting to decide what should change operationally instead of treating dashboards as an endpoint.
Integrations
Connect communication, CRM, commerce, engineering, data, and automation tools while keeping each system's role clear. These guides also cover APIs and webhooks for custom integration patterns.
Account
Learn how workspace access, permissions, and administrative controls shape what people can see and do in Protocol. Use this area when planning team access or reviewing security-related setup choices.
Billing
Understand Protocol's guided sales, plan selection, onboarding, and commercial setup. Pricing is tailored to the service operation rather than handled through a self-service checkout.
Developers
Work with APIs, webhooks, events, and custom applications when a packaged integration is not enough. Developer guidance should be used alongside your workspace permissions and system-of-record decisions.