Service
From the first issue
to a recorded resolution.
01 / CUSTOMER SUPPORT
Keep the case moving.
Hand over the customer context,
pick up the work and resolve it.
CAPABILITIES
Service, in detail.
Features, workflows and the setup they need.
View moreView less
| Area | Capability | What you can do | Availability |
|---|---|---|---|
| Cases | Native case records | Keep case identity, subject, status, priority and customer relationships in native CRM. | Included |
| Cases | Account and contact links | Connect a customer issue to the same Account and Contact used by sales. | Included |
| Cases | Case lifecycle | Track New, In progress, Waiting for customer, Resolved, Closed and Spam states. | Included |
| Cases | Resolution text | Require a recorded resolution when resolving or closing a case. | Included |
| Cases | Customer reply reopening | Reopen waiting, resolved or closed work when an eligible customer replies. | Included |
| Cases | Case history | Retain authorized field changes, messages and lifecycle evidence. | Included |
| Queues | Support queues | Organize intake and team membership in active customer support queues. | Configuration required |
| Queues | Manual assignment | Claim eligible cases or let a supervisor reassign work to an eligible agent. | Included |
| Queues | Mailbox routing | Route enabled inbound correspondence to the configured intake queue. | Mailbox setup required |
| Conversation | Public comments | Record customer-visible correspondence separately from internal investigation. | Included |
| Conversation | Private notes | Keep internal diagnosis out of the customer page and email composer. | Included |
| Conversation | Outbound email | Review To, CC, subject, body and allowed public attachments before dispatch. | Mail setup required |
| Conversation | Email templates | Use configured correspondence templates for the support workflow. | Configuration required |
| Conversation | Delivery visibility | Distinguish queued, accepted and failed mail with retained delivery evidence. | Mail setup required |
| Case relationships | Child cases | Create related work with independent owners, conversation and SLA milestones. | Included |
| Case relationships | Case merge | Move ongoing intake to the destination while retaining source messages and audit navigation. | Included |
| Service levels | Priority-based targets | Track first human response and resolution obligations for Low through Urgent priorities. | Included |
| Service levels | Business calendars | Configure timezone, weekdays, one daily working window and holiday dates. | Configuration required |
| Service levels | Waiting and reopening | Pause resolution while waiting for the customer and create a new cycle after reopening. | Included |
| Service levels | Policy snapshots | Retain the policy behind each obligation when queue or policy settings later change. | Included |
| Service levels | Warnings and breaches | Show deduplicated in-app warning and breach events from the enabled service worker. | Worker setup required |
| Operations | Notifications | Review authorized assignment, customer activity and delivery-problem alerts. | Included |
| Operations | Service reports | Group visible cases by status, priority, queue or agent; inspect age and SLA compliance. | Included |
| Customer access | Case-specific links | Issue expiring, revocable passwordless links for an explicit case participant. | Configuration required |
| Customer access | Public conversation | Allow only the granted view, comment or upload actions; keep internal notes private. | Grant required |
| Files | Case attachments | Upload and share files through current access and verified-clean scan policy. | Scanner setup required |
| Administration | Custom fields and access | Reuse native case fields, custom metadata, queue membership and sensitive-field controls. | Configuration required |
| Scope | Current service scope | Manual assignment and simple SLA. No automatic workload balancing, automatic escalation reassignment or entitlement engine. | Scope boundary |