Unified Customer Service & Engagement Platform
Customer interactions, cases, knowledge, service workflows and operational intelligence in a single environment, so that the person serving the customer has everything required at the moment it is needed.
as of Oct 4, 2026, 9:53 AM
X.Orbit dashboard, shown with sample data.
A representative view of the X.Orbit interface, built from the product’s own model.
Before the modules
The detail below is relevant if you are comparing service platforms. If the service operation itself is not performing as required, begin with the capability rather than the product.
What it does
Everything a service team needs to handle a customer is available in one place, so that the person serving is not the integration layer between five systems.
Voice, WhatsApp, web chat, email, social or the portal - into one queue rather than into six inboxes with six owners.
Identity, history, open cases and prior interactions assembled before the conversation starts, not searched for during it.
An owner, a service level, a defined path to closure, and escalation that happens by rule rather than by somebody remembering.
The approved answer is surfaced against the case in hand, with the Copilot preparing the next step so that the agent does not need to switch screens to find it.
Volume, ageing, resolution path, reopen rate and satisfaction read from the same records the work was done in.
Overview
X.Orbit is a unified customer service and engagement platform. It comprises five areas, each substantial enough to be procured on its own, all operating on the same customer record, with the AI Copilot working across them rather than sitting inside one.
One record underneath
The reason to run these together is not licensing, but that a case, an interaction, an article and a score all refer to the same customer.
Every channel arriving in one service workspace, with identity and history carried between them.
Every request becomes a case with an owner, a clock and a defined path to closure.
Curated once, surfaced inline on the case rather than in a portal nobody opens.
The training system inside the platform people already work in, built from the same approved content.
The daily pulse and the weekly review, from the same operational data.
Omnichannel
Connect and serve customers wherever they arrive, in a single service workspace that carries identity, history and context between channels.
The customer arrives
Scroll sideways to see every channel.
The challenge
In most service operations, the customer’s context exists but is spread across five systems. The person on the call becomes the integration layer, and the customer waits while the information is assembled.
The agent does the integration work.
Context carried, work already done.
Case management
Every request becomes a case with an owner, a clock and a defined path to closure. The lifecycle is enforced by the platform rather than remembered by the team.
01
A single case object carrying the customer, the request, the history and the outcome.
and 6 more below
02
Complaint handling with severity, regulatory classification and closure requirements.
and 6 more below
03
Catalogued request types with eligibility, required information and routing rules.
and 6 more below
04
Response and resolution targets applied per case type, channel and customer segment.
and 6 more below
Rule-driven escalation on breach risk, severity change or explicit customer request.
Clear accountability at every stage, with queue, skill and workload-based assignment.
Configurable service workflows including approvals, dependencies and parallel steps.
Every prior case and interaction available in context, not in a separate search.
A status model the customer can be told and the organisation can report on.
Volume, ageing, reopen rate, resolution path and root cause across the case estate.
AI Copilot
The Copilot is not a separate assistant the agent switches to. It works inside the case - reading what has happened, preparing what comes next and removing the administrative work that sits between the agent and the customer.
Illustrative agent workspace with Copilot assistance - not a product screenshot
Knowledge
Knowledge fails in service operations for a structural reason: it is written as documents and consumed as questions.
X.Orbit includes an integrated knowledge portal. Rather than searching a document library and interpreting a PDF, the agent or the customer asks a direct question: what is the approved procedure, what documents are required, how do I process this request. The answer comes back from approved content, with the source attached.
Knowledge
Four areas, with each capability named rather than summarised. The capabilities most often sought by buyers (Ask AI, visual guides, guided flows and knowledge analytics) are called out on their own line.
Included, not an add-on
The knowledge module is included with X.Orbit. It is neither a separately licensed product nor a separate portal that customers must learn.
A direct question, answered from approved content with the source attached.
Where a request follows a defined procedure, the platform walks the user through it.
One approved source, owned and versioned, with a defined path to publication.
What is being asked, what is answering it, and what is missing.
Content types and platform capabilities as published in the X.Orbit module specification.
Knowledge UI
Answers are generated from approved content only, and the article behind the answer is one click away. Where a request follows a defined procedure, the platform walks the user through it step by step rather than returning the document that describes it.
Learning
Most service organisations run their knowledge base in one system and their training in another, so the course teaches a process the article has already changed. Here they are the same content, governed once.
01
A course is assembled from knowledge articles already published and approved, so what an agent is trained on and what they tell a customer cannot drift apart.
and 2 more below
02
A defined sequence by role, team and service area, so a new joiner works through what their queue actually requires rather than a generic induction.
and 2 more below
03
Structured assessment with pass thresholds, certifying that somebody is cleared for a service area before they are routed work from it.
and 2 more below
04
Where evaluation identifies a specific gap, the relevant module goes to that agent - rather than the whole team sitting through a refresher nobody needed.
and 2 more below
Completion, scores and certification sit on the same record as performance and quality, so capability and outcome are read together.
When an article or policy is republished, the people certified against the previous version are re-notified instead of continuing on superseded guidance.
Analytics
Service reporting that answers management questions rather than describing yesterday's volumes.
01
Volume, ageing, backlog, reopen rate and resolution path by type and owner.
and 6 more below
02
Attainment, breach risk and breach cause across case types and segments.
and 6 more below
03
Throughput, handling time and first-contact resolution by team and channel.
and 6 more below
04
Cost, volume, containment and satisfaction compared across channels.
and 6 more below
What customers are contacting about, and how that is shifting.
Demand against capacity, by skill, by queue, by interval.
Role-based views for team leaders, service managers and executives.
Scheduled and on-demand reporting for service governance forums.
Identification of the drivers behind repeat contact and repeat failure.
Long-run movement in demand, resolution and experience indicators.
Modules
The five areas above describe how the platform is procured. The modules below describe how it is administered: the modules an administrator configures, each with its own settings, permissions and audit trail.
01
Case types, categories, dynamic fields, SLA policies, escalation tiers, routing and closure rules.
and 9 more below
02
Authoring and editorial workflow, categories, languages, publication state and which teams see which content.
and 9 more below
03
The services the organisation offers, the request types under each, and the forms and rules behind them.
and 9 more below
04
Courses, onboarding paths, assessments, certification and assignment rules for service teams.
and 9 more below
The customer and entity record - contact detail, preferred language, full request history, and merging of duplicate records.
Dashboards, operational reports and the measures each role sees when they open the platform.
Channel configuration and connection detail, with the default handling and routing for each one.
The automated agent and the Copilot beside the human one - what each may answer, retrieve and act on.
Feedback capture against interactions and cases, and what is asked after which service journey.
Extensions, queues, numbers and call handling for the browser-based softphone.
APIs, webhooks and integration configuration for connecting the platform to the systems around it.
Activity logging and traceability - who changed what, when, across every module.
Platform configuration, roles and permissions, and the tenant-level controls the rest of the modules inherit.
Inside X.Orbit
This is X.Orbit from the inside: cases with owners and clocks, approved knowledge with analytics, AI built into the work, and every channel in one queue. Figures shown here are illustrative.
Cases, knowledge, the service catalog, training, channels, telephony, surveys and AI are configured in one place and share one record of the customer. Nothing is stitched together after the fact.
Each case moves through statuses you define, from new to closed, and every status maps to a category that drives reporting and SLA behaviour. Custom fields, field rules and validation keep the record complete.
SLA policies attach response and resolution targets to each case by priority and type. The clock pauses while a case is on hold, and the forecast shows whether a case is likely to meet its SLA, based on similar cases already resolved.
Automation rules act on cases the moment something happens: they route, alert and escalate. Problem rules spot when many customers report the same fault, and AI can link new cases to an open problem instead of handling each one alone.
Articles, FAQs, documents, guided flows and picture guides live in one knowledge base, in Arabic and English. Every item goes through draft, approval and publishing, so agents and customers only see approved content.
Guided flows walk an agent through a decision tree, one question at a time, to the right resolution. Picture guides show a procedure screen by screen. Both work in Arabic and English.
1 · Open sign-in
2 · Choose “Forgot”
3 · Set new password
Knowledge analytics shows how often searches succeed, which content is opened and rated helpful, and where people searched and found nothing. The gaps tell authors exactly what to write next.
The service catalog holds each service with its steps, requirements, documents, SLA, fees and delivery channels. Completeness is measured section by section, so gaps are visible before they reach a customer.
Courses, quizzes and certificates are built from approved knowledge articles, so training and day-to-day answers never drift apart. Completion and assessment results are tracked by course and by team.
Ready-made reports cover volume, resolution time, productivity, SLA compliance, backlog and channel mix. Custom reports come from the report builder, and any report can be delivered to inboxes on a schedule.
Web chat, WhatsApp, Messenger, Instagram, X, email and voice arrive in one workspace as conversations and cases. Customers can also open and follow up on cases through a self-service portal backed by the same knowledge base.
X.Orbit puts AI where the work happens: answering agents from the knowledge base, summarising cases, filling fields, translating content, answering customers, writing call wrap-ups and suggesting the next step on a live call. Each feature is switched on separately and runs on your own AI provider key.
Queues, IVR menus, ring groups, time conditions and call routing are set up in the same console, with recording and call-privacy settings. When a case closes, a survey asks the customer how it went.
A read-only audit log records who did what, to what and when. Roles, teams and permissions control access, and an API with webhooks connects X.Orbit to the rest of your estate.
| When | Who | Action | Outcome |
|---|---|---|---|
| 12:41 | Admin | sla_policy.updated | Success |
| 12:38 | Supervisor | case.reassigned | Success |
| 12:30 | Agent | customer.updated | Success |
| 12:22 | Unknown | auth.signin | Denied |
Use cases
X.Orbit is usually introduced where the customer's context already exists and the difficulty is that it exists in five places. These are the situations that shape most deployments.
A ministry consolidates service enquiries from several affiliated entities into one contact operation, and each entity keeps its own case types, service levels and escalation rules.
One workspace holds every entity's case model, so an advisor serves any of them without switching system or losing history.
Commonly applied in Government and across other sectors
Complaints arrive on branch forms, email and social channels, each with a regulatory response deadline, and nobody can see the whole population in one place.
Every complaint becomes a case with an owner, a classification and a clock the platform enforces rather than the team remembering.
Commonly applied in Banking and across other sectors
A customer reports the same connection fault repeatedly through different channels, and each advisor opens a new ticket because none of them sees the earlier ones.
Interactions and cases sit against one customer record, so repeat contact is visible on arrival and joined to the open fault.
Commonly applied in Telecommunications and across other sectors
Approved answers surface inside the case as the enquiry is handled, with the source article attached for the advisor to check.
HealthcareThe request runs as one case through its workflow steps, with each handover recorded and a status the customer can be told.
UtilitiesThe Copilot drafts the response and surfaces the approved policy in the case, so a new advisor answers without waiting for one.
RetailEnquiries and applications are handled from one queue, and the knowledge portal answers the repeated questions before they reach an advisor.
EducationCase, channel and service-level analytics run on the same records the teams work in, so client reporting is drawn rather than rebuilt.
BPOSeasonal demand is handled in one workspace with routing by language and service, and the knowledge base carries the answers advisors need.
GovernmentIllustrative applications rather than delivered engagements; which of them applies depends on the channels and systems already in place.
Common questions
It includes customer and case records, but describing it as a CRM would undersell its knowledge and analytics layers and would imply a sales system, which it is not. X.Orbit is a service platform. Pipeline and opportunity management belong to a different product category, and we will say so if that is what you require.
Yes. This is a common arrangement, with X.Orbit running the service operation against an existing system of record. It requires agreement on which system owns which field, a design decision best settled before configuration rather than after.
That depends far more on how many channels are in scope and how clean the case taxonomy is than on the platform. Operations with a defined service catalogue move quickly; operations where the catalogue is being agreed for the first time spend most of the time on that, and should.
It is migrated, but migration is the easy half. Most knowledge bases contain a large proportion of content nobody has reviewed in years, and moving it unchanged reproduces the problem in a new system. We normally recommend a review pass as part of the work.
Next
A walkthrough of case handling with the Copilot active, against a request type from your own service catalogue.
When you already know the service lifecycle you want and are judging whether a platform can hold it.
Request a demonstrationCustomer Service Process Design settles classification, service levels, authority thresholds and the exception path - independently of any platform.
When the same request type takes two days in one team and two weeks in another.
Customer Service Process DesignMost organisations need the second before the first: configuring a platform around an unsettled process is the most common reason these programmes go wrong.
Industry applications
The platform is the same in each of these. What changes is what it is configured to do and which systems it connects to.
Beneficiary channels, case handling and compliance evidence, built as one programme.
How the portfolio applies here TelecommunicationsService cost per subscriber, handled through channel mix, AI and interaction analytics.
How the portfolio applies here Banking & Financial ServicesRemote branch service, tracked cases and service journeys that stand up to audit.
How the portfolio applies here HealthcarePatient access, case follow-up and remote consultation across a connected care network.
How the portfolio applies here UtilitiesBilling, outage and connection demand handled across channels, field and back office.
How the portfolio applies here Retail & E-CommerceWhat shoppers say online, what staff do in store, measured against the same standard.
How the portfolio applies here AutomotiveAftersales service, dealer networks and the retention that depends on both.
How the portfolio applies here EducationApplicant and student service that holds up through admissions peaks and audit.
How the portfolio applies here BPO & Shared ServicesThe platform, quality and managed operations layer behind outsourced service providers.
How the portfolio applies here InsuranceClaims, policy servicing and remote assessment, held against one customer record.
How the portfolio applies here Real Estate & Property ManagementTenant and owner service, maintenance cases and property condition, evidenced.
How the portfolio applies here Energy & Oil & GasSafety compliance, contractor governance and asset condition across distributed sites.
How the portfolio applies here Manufacturing & IndustrialLine safety, quality evidence and customer service across plants and distributors.
How the portfolio applies here Logistics & Supply ChainShipment enquiries, exception handling and condition verification across the chain.
How the portfolio applies here Aviation, Transport & MobilityPassenger service at scale, terminal conditions and disruption handling.
How the portfolio applies here Hospitality & TourismGuest service across languages and channels, with requests that close.
How the portfolio applies hereThese are the sectors in which this platform is most often applied. It is not limited to them; the requirement, not the industry, determines applicability.
Built on this
A solution is built from this platform, scoped to your organisation and delivered through to go-live.
One customer, one context, every channel - voice and digital.
Customer Service & EngagementEvery request owned, tracked and closed - under SLA.
Customer Service & EngagementOne approved answer, available to customers, agents and employees.
SERVICES THAT SUPPORT THE DECISION TO DEPLOY IT Contact Center Transformation Customer Service Process Design CX Technology Advisory & Integration Digital Application & Platform Development
See it in context
We run demonstrations on a journey you actually handle rather than on a script written to show the product well.
See X.Orbit on your own operation
Bring one of your real service journeys. We set it up in X.Orbit with your case types, SLA targets and knowledge, and walk your team through it from the first message to the closed case.
Tell us how requests reach you today, and we will show X.Orbit routing and closing them under SLA, on one record.
Book an X.Orbit demo
