Sign in Start free trial
Service

Service

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.

56 features available 3 planned 8 capability areas
Highlights

What stands out

Case designer

Each case type has its own steps, forms and approvals without code.

Customer agent with citations

Customers get answers from your articles and a hand-over when unsure.

Workload balancing

Cases move to people who can take them.

Field service offline

Technicians keep working without signal.

Regulatory complaint clocks

Statutory deadlines are watched and letters drafted.

Capabilities

Every feature, in one list

Search or filter. Planned items are labelled; everything else is available now.

Sub-module 1 of 6

Customer Support

Cases, channels, service levels and routing: the right case with the right person in time.

24 features, 1 planned

Cases and case lifecycle

Every request tracked with types, statuses, numbering, history and enforced lifecycle.

12 features
  • Case managementCase types and statuses as data, numbering, coded pause reasons, history and a database-enforced lifecycle.
  • Merge, reopen and duplicate warningMerge duplicates, reopen closed cases and warn of likely duplicates.
  • Parent and child casesLink major incidents and close children together.
  • Party determination and attachmentsCustomer, contact and roles on the case with files.
  • Case PDFA branded summary PDF of a case.
  • Case designerPhases, steps with forms, checklists, approvals and target times per case type, with entry and exit conditions.
  • Case actions and embedded pagesCustom buttons starting workflows or  AI, and embedded pages from other systems.
  • Catalogue and categorisationCase types, categories and statuses configured as settings.
  • Case to sales hand-offCreate a lead or opportunity from a case carrying the customer and case number.
  • Service confirmation to signSend the customer a service confirmation for signature.
  • Privacy log of who opened each caseSee who read a case.
  • Collision warning and swarmingSee who else is on a case and pull experts into a shared thread.

Channels and intake

7 features
  • Email intake and templatesEmail in and out with reply templates.
  • SMS on casesInbound and outbound text with STOP and START recorded as consent; real provider needs an account.
  • WhatsApp conversationsTwo-way conversations on cases.
  • Social channelsPlannedMentions, comments and messages become cases; live accounts needed beyond the sandbox.
  • Hand-offs from MarketingMarketing conversations open a case without phone number or message text.
  • Media enquiriesPress enquiries with deadlines, approved messaging and spokespeople.
  • Macros and reply templatesReusable replies and bulk actions.

Service levels, routing and workload

6 features
  • Escalation matrixPer priority and customer tier, who is told and when the level rises.
  • Escalation timelineSee the escalation history of a case.
  • Routing by team, type, category and skillsAssignment with language and product skills.
  • Workload balancing on live capacitySee availability and load and move offered cases to someone who can take them.
  • Territory routingTerritory owns a queue and field region.
  • Entitlements
Sub-module 2 of 6

Contact Center Integration

The 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 features

Channels and intake

4 features
  • Omnichannel inboxOne queue for email, chat, WhatsApp, SMS and calls with accept and release.
  • Chat transcripts and live chatWeb chat with transcripts kept on the case.
  • Contact centre agent desktopSingle pane with customer 360, telephony, caller verification, transcript and wrap-up.
  • WallboardQueues, service level, abandonment, average handle time and listen, whisper, barge.

Service levels, routing and workload

1 feature
  • PresenceAvailable, away and offline status.
Sub-module 3 of 6

Field Service Management

Work orders, dispatch, parts and technicians in the same suite as the case.

6 features, 1 planned

Field service and maintenance

Work orders, dispatch, parts and technicians in the same suite.

7 features
  • Work orders and dispatchSchedule, closest technician, board and routes.
  • Technician visitsCheck in, notes, labour, parts and sign-off.
  • Offline capture and syncWork without signal and sync in order.
  • Maintenance plans and preventive visitsBy days or by meter units with generated visits.
  • Installed base and warranties
  • Returns and RMAAuthorise, receive and resolve with repair, replace or credit.
  • Native technician appPlannedNative phone app with offline capture.
Sub-module 4 of 6

Knowledge & Self-service

Answers for agents and customers, with their sources.

4 features

Knowledge and self-service

4 features
  • Knowledge articlesAuthoring, versions, review, publishing and translations.
  • Knowledge in the agent railSuggested articles on a case.
  • Connected knowledge sourcesSearch Confluence, SharePoint or any knowledge API beside your own articles; live connections need the customer's accounts.
  • Customer service agentAnswers from articles and permitted sources with citations; hands over to a person when unsure.
Sub-module 5 of 6

Customer Portal

Customers raise and follow their own cases and see their orders and invoices.

2 features

Knowledge and self-service

2 features
  • Customer portalSelf-service with sign-in, case list and deflection.
  • Customer commerce viewOrders and invoices on the customer 360.
Sub-module 6 of 6

Customer Feedback & Insight

Know how customers feel, from survey scores to sentiment and effort.

5 features

Customer feedback and insight

Know how customers feel.

5 features
  • Surveys: satisfaction, recommend, effortSurveys tied to cases.
  • Sentiment and effortOne calm indicator of how the customer sounds, with what decided it.
  • AI service intelligenceCategory, similar cases, summaries and reply drafts.
  • Copilot panel in the agent desktopSummaries, drafts and next steps beside the case.
  • Service reports and dashboards

More in Service

Regulated and industry service

Regulatory clocks and industry packs.

6 features
  • Regulatory complaint registerRegister complaints under a regime, watch statutory clocks and draft mandatory letters.
  • Utilities contract accountsAccounts, service points, meters, readings and single search.
  • Utilities move-in and move-outPrepare moves, record readings and propose rate plans.
  • Utilities rate plans with two-person ruleVersioned plans and agreements proposed by one person and approved by another.
  • Utilities industry packCase types, designs, ladders, templates and example plans.
  • Sample workflows by industryEscalation steps and automation drafts for urgent cases and regulator clocks.

Configuration and integration

Shape service without code and connect it.

5 features
  • Low-code extensibilityCustom fields, layouts, actions and embeds.
  • Public APICase types, statuses, macros, articles, technicians, work orders and more.
  • Teams collaborationPlannedShare cases and ask  AI from chat; needs the customer's registration.
  • Privacy: depersonalisation and loggingDepersonalise and log reads.
  • Agent earningsAgents see commission credits from closed cases.
Assistant

What  AI prepares here

It prepares the work. A person confirms it.

  • Summarise a case and draft a reply
  • Suggest category, similar cases and next steps
  • Draft escalation steps for urgent cases
  • Draft a customer-facing answer from articles
  • Prepare regulatory letters
  • Raise a case, comment or request from the customer agent for a person to confirm
Inside every hub

Workflow, reporting, integration, migration

The same four building blocks, specific to Service.

Workflow

Case steps can require approvals, escalations route by time and tier, and sensitive changes need two people.

  • Refund or credit approval at a case step
  • Escalation after minutes without response
  • Supervisor close with separation of duties
  • Rate plan proposed by one person and approved by another
  • Return authorisation
  • Regulatory letter sent by a person

Reporting and analytics

Datasets

Cases and messagesSurveysField work ordersContact centre interactions

Dashboards

Supervisor boardQueue healthCustomer scoreAgent workloadWallboard

Integration

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

service.case.createdservice.case.escalatedservice.case.closedservice.work_order.completed

Connectors

ConfluenceSharePointSMS providerTelephonyWhatsApp

Migration

Cases, customers and knowledge move through service vendor packs.

  • Zendeskbuilt, tested on recorded sessions
  • Freshdeskbuilt, tested on recorded sessions
  • ServiceNow CSMbuilt, tested on recorded sessions
  • Intercom, Kustomer, Help Scoutbuilt, tested on recorded sessions
  • Genesys Cloudbuilt, tested on recorded sessions
  • Five9built, tested on recorded sessions
  • Salesforce Service Cloud and Dynamics 365 Customer Servicebuilt, tested on recorded sessions
Mobile

On the phone

Technician visits, offline capture and case screens work in the phone browser; a native technician app is planned.

Who uses it

Service agentSupervisorContact-centre agentField technicianKnowledge authorCustomerService operations managerComplaints officer

Industries

  • Utilities
  • Media and press
  • Regulated financial services complaints
  • Manufacturing field service
  • Healthcare
Questions

Frequently asked

Can customers help themselves?

Yes, through a portal and a customer agent that cites your articles.

Does it handle field service?

Yes, work orders, dispatch, parts, maintenance plans and offline capture.

Can we design our own case flows?

Yes, with the case designer per case type.

Does it support regulatory complaints?

Yes, with statutory clocks and drafted letters.

What channels are included?

Email, chat, WhatsApp, SMS, phone and social; some need provider accounts.

Can we migrate from our current help desk?

Yes, with ready packs.

Is there utilities support?

Yes, an industry pack covering accounts, meters, readings and rate plans.

See Service on  AI

Talk to us