Customer inquiry and service request
External inquiry, service request, communications and resolution. An incident is a separate fact of disruption linked to many inquiries.
Bundle → Layer → Finding → Questions Filled
2 bundles · 4 layers · 5 findings · 11 questions
Inquiry Who asked what, through which channel, and how it was answered.
Case and requester
The customer case with its requester or anonymous mode.
Case identity
A case with a requester, a channel and a subject.
- Who is the requester, or is the case explicitly anonymous?
- Which channel and subject does the case record?
Repeated inquiries
Linking repeated contacts without losing their history.
- Is this inquiry a repeat of an existing case?
- Were merged cases kept with their own interactions and timestamps?
Interactions
Communications on the case in time order.
Case interaction
Each message or call with its direction and author.
- Which responses were sent to the requester, and when?
- Which commitments were made to the requester during the case?
Resolution and incidents How cases are resolved and linked to wider disruptions.
Incident link
Many cases referencing one incident or piece of work.
Incident reference
The incident or work item a case depends on.
- Does the case reference an existing incident rather than open a new one?
- When did the request trigger an incident or a work item?
Closure
What closure means, including the customer's view.
Case resolution
The resolution, its reason and the requester's response.
- What resolution was given, and for what reason?
- Did the requester confirm, dispute or not respond to the closure?
- Can the case be reopened if the problem recurs?
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseCOM
- Industry
- Cross-industry
- Tags
- EM-COM-04W1subjectCustomerCaseServiceRequestCaseInteractionCaseResolution
What it is Filled
External inquiry, service request, communications and resolution. An incident is a separate fact of disruption linked to many inquiries.
Why it exists Filled
External inquiry, service request, communications and resolution. An incident is a separate fact of disruption linked to many inquiries.
Distinguishing features Filled
- A case belongs to a requester or is explicitly anonymous, unlike an incident which is a fact of disruption.
- Many cases can reference one incident, and each keeps its own responses.
- Closing a case records the provider's resolution and does not prove that the customer agreed.
- Distinct from internal work items, which a case may trigger but does not replace.
What robots and AI may and may not do Filled
Must not
- Open a separate technical incident for every complaint about the same disruption.
- Record a closed case as customer agreement without the customer's response.
- Merge cases in a way that deletes their individual history.
- Share one requester's case details with another requester.
Only with a human decision
- Sending compensation or goodwill gestures to customers.
- Closing a case the requester has disputed.
May
- Link new inquiries to an existing incident when they describe the same disruption.
- Draft individual responses to requesters based on the case history.
- Report open cases by incident, age and channel.
Moral aspects Filled
- Case records hold personal data and complaints that must be kept confidential.
- Customers depend on fair and timely handling, especially during mass outages.
Who is affected
- Requesters and customers
- Service desk staff
- Engineering teams handling incidents
Owners Filled
Steward
The commercial director who answers for customer, supplier and partner relationships.
Master systems
- CRM
- Order management system
- Service desk
Links to other meta-models Filled
neighbor
- EM-WRK-01
references
- WM-ACT-021 - conceptual-candidate
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Identified by case number in the service desk, with interactions numbered within the case.
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition optional Filled
- A case record names a requester or anonymous mode, a channel, interactions and a status.
- Often confused with the technical incident it reports or the work item it triggers.
Capabilities and actions required Filled
- Groups many cases under one incident while keeping individual replies.
- Shows customer-facing response times separately from fix times.
Hazards and failure modes required Filled
- Incident flooding when each complaint becomes its own incident.
- Premature closure that hides unresolved problems.
- Exposure of personal complaint details across cases.
Standards and interfaces required Filled
- ISO 10002 for complaint handling in organisations.
- TM Forum SID customer interaction entities.
- ISO/IEC 20000-1 for service management.
Context of use required Filled
- Used in customer service desks, contact centres and support portals.
- Consumer complaints are subject to consumer protection and data protection law.
Sources Filled
- TM Forum SID: party/customer/product/service
- OASIS UBL: trade documents and exchange
- CRM/CPQ/order management practice: stages and source boundaries
- OASIS Universal Business Language Version 2.3 - Checked live (HTTP 200) on 2026-10-07.
- OASIS Universal Business Language (UBL) Technical Committee - Checked live (HTTP 200) on 2026-10-07.
Open questions
- How to merge repeated inquiries without losing history?
- When does a request trigger an incident or work?
- What does closure mean from the customer's point of view?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-com-04/brief.json, ver-cy/world-models/card-supplements/em-com-04.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.