An after-sales promise becomes operational only when one case ID, one clock definition and one accountable state model survive every email, chat, time zone and handoff.
A hotel reports a door that will not lock through a sales chat at 18:00 local time. The factory sees it the next morning in another time zone, a distributor starts a second email thread and the site team sends photos without an opening mark. Everyone says they responded quickly, but no record proves when the case entered the agreed channel, whether security containment was arranged, which clock applied, what information was missing or who could authorise a remedy. A useful service-level agreement does not begin with an impressive number of hours. It begins with a controlled intake, project-approved severity rules, explicit business-calendar arithmetic and evidence for every transition from receipt to verified closure.
Targets must be approved: Every response, restoration, update, escalation and closure target in this framework is a blank project field. The contract owners, operators, technical teams and legal advisers must approve values, calendars, exclusions and remedies; this article supplies none.
1. Design one controlled intake without losing human accessibility
Publish approved intake channels by case type and territory: portal, monitored email, phone or emergency/safety route where the project establishes one. Define which channel creates the system-of-record timestamp and what happens when a request arrives through salesperson chat, social messaging or an unmonitored mailbox. Staff should forward and register it without making the reporter repeat available information; the case log preserves both original receipt and formal registration times.
Capture the minimum viable case: unique case ID; reporter and contact authority; customer/project/site; opening and unit/part identifiers; exact location; event and discovery times with time zones; current condition and safety/security/weather exposure; neutral symptoms; photos/video/documents; affected population; access/occupancy; temporary actions; requested assistance; language; and privacy/confidentiality constraints. Missing data is a visible state, not a reason to discard the request.
Acknowledge receipt separately from technical acceptance or warranty entitlement. The acknowledgement should echo the case ID, recorded issue and time basis; identify missing critical information; state current owner/status and next update under the approved target; and route immediate hazards to the project's competent safety/emergency parties. It must not promise a cause, repair, cost or completion date before review.
| Field | Required controlled entry | Evidence/source | If missing |
|---|---|---|---|
| Case and source | Unique ID, channel, original/formal timestamps | Raw message/system event | Register and flag gap |
| Physical identity | Project, building, opening, unit/part | As-built/label/photo | Identity pending; no guessed part |
| Condition/event | Neutral symptom, event/discovery time | Media/log/site record | Request bounded evidence |
| Immediate exposure | Safety/security/weather/operation state | Site assessment | Escalate to competent local route |
| Reporter/authority | Contact, role, language/time zone | Project directory | Verify authority |
| Case ownership | Queue, named owner, next update | Workflow record | Escalate unowned case |
2. Define severity from consequence and scope—not emotion or customer rank
Build a project-approved severity rubric using observable consequence: immediate life safety, falling glass or unsafe operation; inability to secure/egress/access as applicable; active water entry and property exposure; critical operational shutdown; number and type of affected openings; availability of a safe temporary state; occupied/vulnerable areas; regulatory or evidence-preservation need; and rate of spread. The rubric must name who can classify and reclassify.
Keep urgency, technical complexity, warranty entitlement and commercial priority separate. A high-severity condition may ultimately be outside supplier responsibility but still require immediate local containment. A low-consequence cosmetic concern may be contractually valid without needing emergency escalation. Customer status or message volume should not silently change safety classification.
Use provisional severity when facts are incomplete and define automatic review triggers: new injury/hazard information, additional affected units, loss of containment, weather change, recurrence, expert finding or correction failure. Preserve old/new classification, reason, author and timestamp. Never downgrade solely because the response target is at risk.
| Dimension | Evidence question | Approved level mapping | Reclassification trigger |
|---|---|---|---|
| Safety/security/access | What cannot be safely used or secured? | [project values] | Condition/user context changes |
| Weather/property | Is exposure active and what is at risk? | [project values] | Containment fails/weather changes |
| Population | One unit, group or systemic indicator? | [project values] | New cases/configuration link |
| Operational consequence | Which service/space is unavailable? | [project values] | Business state changes |
| Temporary state | Is it authorised, safe and monitored? | [project values] | Expiry/deterioration |
| Evidence uncertainty | Which critical facts are missing? | [provisional rule] | Verified facts arrive |
3. Make the clock reproducible across time zones and holidays
For every target, define clock start event, stop event, elapsed or business time, authoritative time zone using an IANA time-zone identifier, covered hours, working days, holiday calendar and calendar owner/version, daylight-saving handling, pause states, evidence required to pause/resume and treatment of customer or third-party waiting. Store timestamps in a machine-stable form and display the reporter's local time as an aid. A bare ‘CST’ or ‘within two days’ is ambiguous.
Separate targets: acknowledgement/registration; initial triage; safety-containment coordination; substantive technical response; diagnostic plan; periodic update; approved remedy plan; restoration/work completion; verification; and administrative closure. ISO 10002 provides complaint-handling guidance, but it does not select project service times. ISO 8601 supports date/time representation, while the IANA Time Zone Database records civil-time rules; neither defines the contract calendar.
Define pause governance narrowly. Waiting for a required opening-mark photo may pause a technical-analysis clock only if the approved SLA says so, the missing item is necessary, the request and timestamp are recorded and other safe work continues. Internal handoffs, staff absence or supplier investigation should not be silently excluded. Recalculate deadlines from logged events so both parties can audit them.
| Target/state | Start and stop events | Calendar/time zone | Pause/resume evidence | Approved value/owner |
|---|---|---|---|---|
| Acknowledgement | Formal receipt → acknowledgement issued | [calendar/IANA zone] | [rule] | [blank/owner] |
| Initial triage | Receipt → severity/owner recorded | [calendar/zone] | [rule] | [blank/owner] |
| Technical response | Complete-enough state → issued assessment/plan | [calendar/zone] | [missing-info rule] | [blank/owner] |
| Update cadence | Prior update → next status | [calendar/zone] | [rule] | [blank/owner] |
| Resolution/restoration | Authorised start → verified result | [calendar/zone] | [dependencies] | [blank/owner] |
| Closure | Closure evidence complete → authorised close | [calendar/zone] | [reopen window if any] | [blank/owner] |
4. Track response, containment, resolution and closure as different states
Use a controlled state machine: received; registered; triaged; awaiting identified information; local containment active; technical investigation; remedy proposed; awaiting approval/access/material; work scheduled; work completed awaiting verification; verified; closed; reopened or cancelled with reason. Define entry/exit evidence and permitted authority for each. Free-text notes supplement but do not replace state transitions.
Response means communication or substantive analysis under its named target; it is not resolution. Containment reduces immediate consequence without necessarily correcting cause. Resolution may mean authorised repair, replacement, adjustment, accepted deviation, information provision or another contract-defined outcome. Closure requires the named criterion and customer/project authority evidence, not simply shipment of a part or a technician visit.
Maintain the action/evidence log: timestamp/time zone, actor/organisation, event, decision, source, attachment hashes or stable references where used, next owner/date and customer-visible status. Link parts shipments, site visits, NCRs, expert reports, costs and warranty/commercial decisions without merging their separate authority.
| State | Minimum entry evidence | Required exit evidence | Authority |
|---|---|---|---|
| Registered/triaged | Identity + symptom + provisional severity | Owner, severity and next action | Service coordinator |
| Containment | Named immediate risk | Local competent action + monitoring | Site/safety authority |
| Investigation | Approved scope and evidence | Finding/unknowns + recommended route | Technical authority |
| Remedy approved | Method/material/scope and consequences | Authorised decision | Design/contract parties |
| Work completed | Execution records | Ready for reinspection | Contractor/service party |
| Verified/closed | Requirement-linked result | Named acceptance + records | Verifier/closure authority |
5. Control escalation, regional handoff and verified closure
Create escalation paths for severity, target-at-risk, unowned case, repeated failure, systemic population, safety/regulatory concern, data/privacy issue, commercial dispute and customer communication failure. Each route names primary and backup roles across customer, local site/distributor and manufacturer/specialists, plus what evidence accompanies escalation. Escalation is not blame; it changes attention and authority while preserving ownership.
For follow-the-sun or cross-border handoff, require a structured brief: case/severity and local time; physical state and containment; last verified facts; actions/decisions and sources; open questions; customer commitment and next deadline; contacts/language; access/parts/shipping state; and explicit accepting owner. The outgoing owner remains accountable until acceptance is logged. Translation must distinguish source text, translated text and unresolved technical terms.
Closure evidence includes physical identity, original issue/requirement, final disposition, actual work/parts, tests or reinspection, containment removal/transfer, affected population, as-built/archive updates, customer/project acknowledgement where required, commercial/warranty status separately and lessons/actions. Define reopen handling so recurrence links to the prior case. Report performance from event logs with excluded/paused time visible; do not improve metrics by duplicate closure or premature downgrading.
| Control | Required evidence | Failure signal | Owner/status |
|---|---|---|---|
| Escalation | Trigger, timestamp, recipient and acceptance | No response/authority gap | [record] |
| Cross-region handoff | Structured brief + accepting owner | Forwarded email only | [record] |
| Customer update | Facts, limits, next action/time basis | Promise without owner | [record] |
| Closure verification | Requirement-linked evidence | Work done but unverified | [record] |
| Archive/config update | As-built/part/case links | Future traceability gap | [record] |
| Metric audit | Raw timestamps, calendar and pause log | Manual overwritten duration | [record] |
FAQ
What response time should an international window SLA promise?
This article provides none. Approve targets from consequence, coverage model, territories, staffing, logistics, specialist dependencies, contract and customer need, then define the clock exactly.
Does an automatic email count as a response?
Only if the approved SLA defines it as acknowledgement. It should not be reported as substantive technical response or resolution.
When does the SLA clock start?
Use the project-approved event, channel, calendar and time zone. Preserve both original out-of-channel receipt and formal registration so routing delay is visible.
Can a case pause while waiting for the customer?
Only under a defined pause rule with necessary missing information, request and timestamps recorded. Safety containment and other possible work should continue.
Is sending a replacement part resolution?
Not automatically. Correct identity, delivery, installation where applicable, verification and closure authority may remain.
Should each email create a case?
No. One physical issue may have multiple messages. Deduplicate by project/opening/event while preserving sources; never merge distinct conditions merely to reduce counts.
When can a case close?
When the contract-defined resolution and verification evidence, population scope, record updates and named closure authority are complete—not because the last message went unanswered.
Continue the project review
Connect this guide with the proposed window and door systems, then review how Cavorlen approaches manufacturing and quality control. When your schedule is ready, send it through the project review form.
Official sources used
ISO — ISO 10002 quality management and customer satisfaction complaints handling ↗ISO — ISO 10001 customer satisfaction codes of conduct ↗ISO — ISO 8601-1 date and time representation ↗IANA — Time Zone Database ↗ISO — ISO 10007 configuration management guidance ↗ISO — ISO 9001 quality management systems ↗Related buyer guides
This article is not an SLA offer, warranty, service commitment, legal interpretation, entitlement decision, emergency service, repair promise or statement of Cavorlen availability. It supplies no response/resolution time, coverage hour, business-day calendar, severity target, staffing level, remedy, credit or escalation deadline. It does not assign fault or approve technical work. Only signed project documents and named authorised parties establish obligations, targets, safety response and commercial consequences.