Client Support Retainer Out-of-Scope Redirect Pack With AI

Your support retainer covers break/fix, small tweaks, and agreed maintenance—not a surprise website rebuild, a two-day training program, or legal review of a vendor contract. When the client drops that request into the same inbox as "the logo looks blurry," you need a fast, professional redirect: acknowledge the ask, show why it sits outside the retainer, and offer a written path to a change request or fixed quote—without making them feel brushed off.

This pack uses ChatGPT to classify and draft neutral language, Google Docs for a one-page scope boundary memo the client can forward internally, and Gmail for a short reply that keeps the retainer relationship warm. It complements your monthly retainer review (where you spot scope drift early) and differs from hours top-up (bank empty, not wrong type of work) and from urgent P1 (outage, not new deliverable).

More playbooks in guides.

When to run this pack

Trigger it when:

• The ticket reads like a new deliverable (feature, integration, campaign, audit) rather than keeping existing systems healthy.
• Work would exceed a reasonable retainer slice (e.g., "migrate us to a new CRM this month" on a 10-hour bank).
• The ask is explicitly excluded in your kickoff or SOW (training marathons, net-new design, compliance/legal sign-off).
• The client says "just add it to the retainer" for something you would normally estimate and quote.

Do not use this pack for:

• Genuine bugs or regressions in scope (P1 pack if live impact).
• Clear change requests where they already expect a memo—go straight to the CR workflow, but reuse the boundary language here.
• Your SLA miss (service credit pack).

What you will produce

1. FACT / ASSUMPTION classification of the request vs signed retainer scope.
2. Out-of-scope boundary memo (Google Doc): what's included, why this ask is outside, options (CR, fixed quote, defer).
3. Gmail reply (and optional follow-up) with doc link and next step.
4. Internal note so your team does not start billable work without approval.
5. A line for the next monthly review: "Scope redirect sent [date] for [theme]."

Step 1 — FACT / ASSUMPTION snapshot

Paste into ChatGPT (no secrets—use initials):

You help a support retainer provider decide if a client request is in scope.

FACTS (only what I provide):
- Retainer tier / hours / SLA summary:
- SOW or kickoff scope bullets (paste):
- Client request (paste ticket/email):
- Hours used this cycle:

ASSUMPTIONS (label clearly):
- Whether this is net-new deliverable vs maintenance:

Output:
1) In-scope | out-of-scope | needs clarification (one line each why)
2) Three risks if we silently do the work on retainer hours
3) Neutral client-facing paragraph explaining the boundary (no blame)
4) Suggested options: (A) change request, (B) fixed quote, (C) defer to next cycle

You edit every line before it goes client-facing.

Step 2 — Boundary memo in Google Docs

Title: [Client] — Retainer scope note — [date]

Section	Purpose
Summary	One paragraph: we received X; retainer covers Y
What's included	3–5 bullets from kickoff/SOW
Why this request is outside	FACT-based bullets (size, new system, excluded category)
What we can do on retainer	Honest small slice, if any (e.g., 30-min triage)
Options A / B / C	CR path, fixed quote, or defer with date
Next step	"Reply with A, B, or C by [date]"

Ask ChatGPT to expand Why outside and Options from your FACT block. Keep tone collaborative—SMB clients often do not know what "retainer" legally includes.

Step 3 — Gmail reply (paste-ready)

Subject: Re: [ticket subject] — retainer scope + next steps

Hi [Name],

Thanks for sending this over—we want to handle it properly rather than half-finish it inside the support retainer.

Our monthly retainer covers [one-line included scope]. The request below is best treated as [new project / change / training block] because [one factual reason].

I've attached a short scope note (link) with three options:
A) Formal change request with estimate
B) Fixed quote for the described outcome
C) Defer to [month/quarter] if timing is flexible

If you reply with A, B, or C (or a tweak), we'll move on the same thread. Retainer tickets for [ongoing area] stay on the normal channel.

Best,
[You]

Send from the same inbox you use for retainer SLA so timestamps stay auditable.

Step 4 — Internal guardrail (2 minutes)

Slack or task note to yourself/team:

OOS redirect sent [date] — [Client] — [theme].
Do NOT log retainer hours until CR/quote approved.
Approver: [client contact from kickoff or contact-change addendum].

If the client's primary contact recently changed, confirm approvers match your primary contact change addendum before quoting.

Step 5 — Route to CR or quote

When they pick A or B:

• Open a fresh thread or CR doc using your change request pack—do not bury estimates inside the original support ticket comment.
• Reference the boundary memo link so finance and their manager see one story.
• If the work is large and the hour bank is already low, combine with hours top-up only after scope is approved—not as a substitute for quoting net-new work.

If they pick C, set a calendar reminder and mention it in the next monthly review so it does not look forgotten.

Step 6 — Clarification path (when ChatGPT said "needs clarification")

Sometimes the ticket is ambiguous ("make the site faster" could be cache tweak or full rebuild). Send a micro-questionnaire in the same Google Doc:

• Is this fixing a regression since [date] or net-new performance work?
• Acceptable budget band if outside retainer?
• Hard deadline?

One Gmail with the doc link beats three Slack pings.

Common mistakes

• Silent heroics — burning retainer hours on a mini-project trains the client to skip approvals.
• Cold "that's not included" — always pair boundary with options A/B/C.
• Quoting in Slack only — no audit trail when someone leaves the company.
• Confusing with SLA breach — if you declined because you were overloaded, that may be a service credit conversation, not scope.

Scenario notes

Agency client: Marketing opens tickets; engineering owns access. Address the memo to both if the ask spans systems—avoids "marketing said you would do it."

SMB owner: They often treat retainer as "unlimited questions." The included-scope bullets from kickoff are your friendly citation.

Vendor transition: If they are also ending the retainer, do not mix this with termination offboarding—finish OOS redirects on approved work only.

Human-in-the-loop

AI classifies and softens tone; you verify contract language, hour math, and whether a small in-scope fix exists. Never auto-send without reading. If they push back emotionally, offer a 15-minute scope call—still document outcomes in the Doc.

Quick checklist

• FACT / ASSUMPTION snapshot saved
• Google Doc boundary memo shared
• Gmail sent with A/B/C options
• Team blocked from retainer time until approval
• CR or quote thread opened when client chooses
• Monthly review log updated

You protect margin and trust by naming boundaries early—while keeping the retainer channel fast for work that truly belongs there.