S2C 202 ยท CAPTURE
How is a customer service need captured?
A service request records the customer, installed product, issue, priority, channel, and service-level commitment.
READ THE CAPABILITY
Make the customer need identifiable before promising work
Record customer, installed product, location, symptom, priority, channel, and requested outcome. Check warranty, contract, SLA, installed-base identity, and the response obligation before routing.
OPERATIONAL FLOW
How the service capability performs
Follow the service decision through the evidence that makes the customer result explainable.
Capture the service need
Record customer, installed product, location, symptom, priority, channel, and requested outcome.
Validate entitlement
Check warranty, contract, SLA, installed-base identity, and the response obligation before routing.
Create an actionable request
Assign queue, skill, priority, response target, and the next responsible owner.
Preserve the request story
Keep the original need, decision, timestamps, changes, and hand-off visible to later service work.
DESIGN & CONTROL
Keep promise, execution, charge, and cash distinct
The service result is trustworthy only when each hand-off has an owner and evidence.
Business decision
State what the customer is entitled to receive, what work is approved, and who owns the response.
Source evidence
Capture identity, status, quantities, time, acceptance, commercial treatment, and exceptions at the record that knows them.
Financial hand-off
Reconcile confirmation, billing, receivables, payment, and clearing without correcting a later record in isolation.
DIAGNOSTIC EVIDENCE
What proves the service result?
Start with the last trusted service object, then follow the boundary that owns the difference.
Customer, site, equipment, serial number, installed base, and service history.
Warranty, contract, SLA, coverage, priority, channel, and response commitment.
Request status, owner, routing decision, due date, and successor service order or activity.
SERVICE MOMENT
A machine alarm arrives without a serial number
The service desk matches the customer site and installed base before creating a promise. The request remains actionable only after the technical object, coverage, priority, and response owner are credible.
- Customer and entitlement remain identifiable
- Operational evidence is captured at the source
- Commercial or settlement action is traceable
Compare how the shared service promise executes when equipment comes to the service centre or technicians go to the customer site.