Case designer
Each case type has its own steps, forms and approvals without code.
Resolve customer requests faster across channels, knowledge and field visits.
Service gives support teams one place to run cases from any channel, with service levels, knowledge, a customer portal and field service. It shares customer, installed base and order data with CRM and finance, and AI prepares summaries and replies for people to confirm.
Each case type has its own steps, forms and approvals without code.
Customers get answers from your articles and a hand-over when unsure.
Cases move to people who can take them.
Technicians keep working without signal.
Statutory deadlines are watched and letters drafted.
Search or filter. Planned items are labelled; everything else is available now.
Cases, channels, service levels and routing: the right case with the right person in time.
24 features, 1 plannedEvery request tracked with types, statuses, numbering, history and enforced lifecycle.
12 featuresThe contact-centre agent desktop and its interactions: calls, chat, WhatsApp and SMS in one inbox, with customer 360, caller verification and a live wallboard.
5 featuresWork orders, dispatch, parts and technicians in the same suite as the case.
6 features, 1 plannedWork orders, dispatch, parts and technicians in the same suite.
7 featuresAnswers for agents and customers, with their sources.
4 featuresCustomers raise and follow their own cases and see their orders and invoices.
2 featuresKnow how customers feel, from survey scores to sentiment and effort.
5 featuresKnow how customers feel.
5 featuresRegulatory clocks and industry packs.
6 featuresShape service without code and connect it.
5 featuresIt prepares the work. A person confirms it.
The same four building blocks, specific to Service.
Case steps can require approvals, escalations route by time and tier, and sensitive changes need two people.
Datasets
Dashboards
Service has a public API and events for cases, knowledge, field work and more; connectors are available for external knowledge sources and enterprise service orders.
/v1 service_cases, service_case_types, service_kb_articles, service_macros, service_maintenance_plans, service_rmas and more (31 resources)
Events
Connectors
Cases, customers and knowledge move through service vendor packs.
Technician visits, offline capture and case screens work in the phone browser; a native technician app is planned.
Yes, through a portal and a customer agent that cites your articles.
Yes, work orders, dispatch, parts, maintenance plans and offline capture.
Yes, with the case designer per case type.
Yes, with statutory clocks and drafted letters.
Email, chat, WhatsApp, SMS, phone and social; some need provider accounts.
Yes, with ready packs.
Yes, an industry pack covering accounts, meters, readings and rate plans.