E-commerce

How to document support exceptions without creating a commercial precedent

How to document support exceptions without creating a commercial precedent

July 1, 2026

"The April agent granted me the late return, why are you refusing?" "I have the screenshot: you promised free shipping." "Finance says there's no trace, the customer cites the chat." Three tickets where a well-intentioned exception becomes an implicit business rule that the customer repeatedly demands.

The DEC ledger #237 tracks who approved what. This guide #480 addresses the other risk: documenting the exception without anchoring it as a reusable promise in customer language, macros, or the bot.

Policy EXCPREC-SUP, flow EP-1 to EP-8, customer vs. internal templates. Completes DEC documentation (#237) and goodwill gestures (#238): here, governance of precedents and anti-citation phrasing.

Summary

Why can a documented exception become a toxic precedent?

How does EXCPREC-SUP complement DEC #237 without duplicating it?

Which exc_prec_* typologies should be mapped?

Which fields should be added to the PREC-LOG register?

How to write the EXCPREC-SUP policy in eight rules?

Flow EXCPREC EP-1 to EP-8

EXC-CLIENT vs EXC-INTERNAL Templates

How do you decline a citation of precedent without ruining the relationship?

Which exc_prec_* KPIs should be tracked?

Agent errors and bot sync

How does Qstomy limit previous bots?

EXCPREC checklist, FAQ, and going further

Why can a documented exception become a toxic precedent?

A support exception granted once can be cited a hundred times if the customer perceives a general promise, rather than a one-time gesture.

Three mechanisms of precedent

  • Customer language too broad: "we accept late returns" instead of "one-time exception"

  • Public chat without internal note: customer screenshot, next agent denies

  • DEC without non-replicable flag: register #237 completed but reusable as is

GetVocal reiterates that non-negotiable rules must remain deterministic and separate from case-by-case handlings (GetVocal, decision maps 2026).

Angle #480 vs neighboring content

Example DTC mode: 14% of tickets cite "last time". Without EXCPREC-SUP: exc_prec_repeat_rate 11%, exceptions margin +23% vs budget. After EXC-CLIENT-* templates: exc_prec_repeat_rate 4%.

How does EXCPREC-SUP complement DEC #237 without duplicating it?

DEC traces the audit. EXCPREC frames what the client can quote tomorrow.

Document → role matrix

  • #237 DEC-*: DEC-ID, reason code, approver, impact amount

  • #480 PREC-LOG: replicate field Y/N, client_wording_used, policy_unchanged confirm

  • #238 gesture matrix: credit note gift discount cap

  • #280 policy: standard rule unchanged after exception

Four EXCPREC-TYPEs

  • exc_one_time_ops: proven warehouse error, non-replicable

  • exc_one_time_goodwill: one-off relational gesture, client flag

  • exc_vip_discretion: VIP tier, policy unchanged for base

  • exc_policy_review_candidate: code recurs 5×/month → update REP, not a new precedent

Promise #480: policy EXCPREC-SUP, PREC-LOG registry, 8 typologies exc_prec_*, flow EXCPREC EP-1 to EP-8, macros EXC-CLIENT-* vs EXC-INTERNAL-*.

Which exc_prec_* typologies should be mapped?

Eight typologies previous ticket exception for routing.

Eight exc_prec scenarios

  1. exc_prec_client_cites_prior: client cites chat or prior DEC

  2. exc_prec_return_late_granted: late return granted once

  3. exc_prec_free_ship_repeat: free shipping requested again

  4. exc_prec_discount_screenshot: screenshot of previous agent discount

  5. exc_prec_vip_expects_same: VIP demands same gesture as third-party neighbor

  6. exc_prec_bot_promise: bot or agent formulated too broadly

  7. exc_prec_family_account: spouse or same household address

  8. exc_prec_social_pressure: threat of review if not the same exception

Helpdesk tags

exc_prec, exc_prec_citation, exc_prec_repeat, dec_exception cross-tag #237.

Intake data EP-1

prior_dec_id if any, prior_ticket_id, reason_code, replicate_flag N default, client_verbatim cite, segment LTV, approver_tier.

Which fields should be added to the PREC-LOG register?

Extension of the DEC #237 registry with anti-precedent fields.

Mandatory PREC-LOG fields

  • replicate: N by default, Y only if policy update is formalized

  • client_wording_template: EXC-CLIENT-ONE-01 used

  • policy_section_unchanged: REP-RET-003 remains canonical

  • one_per_customer_window: e.g. 12 months max 1 EXC-RET-LATE

  • internal_only_note: ops justification, never copied to client

Example PREC-LOG line

DEC-2026-00891 | EXC-RET-LATE | replicate N | EXC-CLIENT-ONE-01 | Policy REP-RET-003 unchanged | 1×/customer/12 months | Internal reason: ops delay D+32 receipt.

How to write the EXCPREC-SUP policy in eight rules?

Eight EXCPREC-SUP rules validated by support lead + finance.

  1. EXCPREC-01: Any exception = DEC #237 + PREC-LOG replicate N

  2. EXCPREC-02: Customer message = EXC-CLIENT-* template, never broad ad hoc phrasing

  3. EXCPREC-03: Prohibited to use "we now accept" or "as usual for you"

  4. EXCPREC-04: Repeat refusal cites public policy + internal DEC if same customer

  5. EXCPREC-05: Bot never promises exception, handoff #237 workflow

  6. EXCPREC-06: VIP exception ≠ change to base customer policy

  7. EXCPREC-07: EXC-* code 5×/month → REP policy review, not DEC multiplication

  8. EXCPREC-08: Customer screenshot: verify DEC-ID before granting repeat

Flow EXCPREC EP-1 to EP-8

Flow agent EXCPREC-FLOW before and after action.

  1. EP-1 Intake: exception request or prior citation

  2. EP-2 Lookup: 12-month customer DEC history, repeat count

  3. EP-3 Classify: exc_prec_* typology

  4. EP-4 Approve: tier threshold #193 + DEC if approved

  5. EP-5 Client message: EXC-CLIENT-ONE-* template only

  6. EP-6 PREC-LOG: replicate N, wording, policy unchanged

  7. EP-7 Refuse repeat: EXC-CLIENT-REFUSE-* if out of window

  8. EP-8 Close: tag exc_prec_resolved, log DEC-ID

SLA

Prior citation ticket: lookup DEC < 10 min before customer response. PREC-LOG entered < 24 h post-action.

EXC-CLIENT vs EXC-INTERNAL Templates

Separate customer language and internal note.

EXC-CLIENT-ONE-01 (one-off agreement)

"For this case only, we are making an exception to our standard return policy documented here: [return page link]. This decision does not modify our general terms and conditions and does not apply to future orders."

EXC-CLIENT-REFUSE-01 (refusal repeat)

"We understand your reference to a previous exchange. Our return policy remains [X days]. An exception had been granted on a one-off basis for that case; we cannot generalize it. Here are the compliant options: [standard return / credit note according to #238]."

EXC-INTERNAL-01

DEC-ID, approver, replicate N, factual ops reason, abuse flag if 3+ requests within 90 days. Never paste EXC-INTERNAL into the customer chat.

Forbidden formulations for customers

"We will make an exception for you in the future", "this is our rule for loyal customers", "normally no but for you yes without limit".

How do you decline a citation of precedent without ruining the relationship?

Repeat refusal = fragile CSAT moment. CALME protocol (#214) then EXCPREC.

Four steps of refusal

  1. Acknowledge: recognize the previous exchange without validating a general promise

  2. Policy cite: link to unchanged public page

  3. Explain one-time: EXC-CLIENT-REFUSE-01

  4. Offer standard path: compliant return or gesture #238 within limit if new incident

Anger or review threat: CALME #214, tier 2 escalation #193, no new exception to buy silence.

Which exc_prec_* KPIs should be tracked?

Dashboard previous exceptions.

  • exc_prec_citation_rate: tickets citing prior exception / total

  • exc_prec_repeat_grant_rate: repeat approved vs refused

  • exc_prec_client_reopen: reopen post-refusal repeat

  • exc_prec_dec_without_prec_log: DEC without PREC-LOG, target 0

  • exc_prec_policy_update_from_code: EXC-* converted into REP

Alert if exc_prec_citation_rate > 8%: audit templates EXC-CLIENT and agent training.

Agent errors and bot sync

Five anti-patterns of commercial precedent.

  1. Exception in chat without template: client quotes word-for-word

  2. DEC without replicate N: finance approves, client replicates

  3. "I can ask for an exception" bot: implicit promise, see #142

  4. Same gesture for family account: without policy, different address

  5. Social pressure yields: viral TikTok precedent or reviews

Bot guardrail: intent exception_request → human handoff, never EXC-CLIENT template. See AI governance (#142).

How does Qstomy limit previous bots?

Qstomy applies standard policy and handoff exception with DEC-ready payload, via Shopify integration.

Key capabilities

  • NO-EXCEPTION-PROMISE: bot cites policy, no gesture

  • Handoff payload: customer DEC history, prior tickets, LTV

  • EXC-CLIENT suggestion: agent chooses template, no free LLM

  • Repeat detection: flag if EXC-RET-LATE 12 months

Scenario: brand with 1,900 tickets/month, 12% prior citations. Qstomy + EXCPREC-SUP: exc_prec_citation_rate 12% → 5% in 8 weeks.

Explore AI support and request a demo.

EXCPREC checklist, FAQ, and going further

8-Step Checklist

  1. EXCPREC-SUP : 8 rules validated by lead + finance

  2. PREC-LOG : replicate + client_wording fields on DEC register

  3. Templates : EXC-CLIENT-ONE-01, REFUSE-01, INTERNAL-01

  4. Flow EP-1 to EP-8 : agent training 30 min

  5. Lookup DEC : helpdesk macro customer history 12 months

  6. Bot guardrails : no exception promise #142

  7. Monthly review : top EXC-* → REP policy or reinforced standard rejection

  8. KPI dashboard : exc_prec_* section 9

FAQ

Is DEC #237 sufficient?
DEC = audit. PREC-LOG = client anti-precedent. Both are mandatory on exception.

Can we grant 2 exceptions to the same client?
Yes if distinct incidents and one_per_customer policy window allows it. replicate N each time.

Permanent exception for VIP client?
No. VIP #207 = higher limits, not a different published policy.

Going further

This week: add replicate N to DEC register, publish EXC-CLIENT-ONE-01 as macro, test repeat rejection on 3 historical tickets.

Comment utiliser les questions support pour prioriser vos tests A/B ?

Support client pour escalade refusée ou non disponible

Enzo

July 1, 2026

Convert over 2,000 customers on average per month with Qstomy.

The world’s 1st Shopify AI dedicated to customer conversion

Empowering 200+ e-commerce merchants

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

Sign up for the waitlist

*Unsubscribe at any time. We do not send spam.

Subscribe to the newsletter and get a personalized e-book!

No-code solution, no technical knowledge required. AI trained on your e-shop and non-intrusive.

Sign up for the waitlist

*Unsubscribe at any time. We do not send spam.