Client Hypercare Closure Pack With AI (Feedback + Testimonial Ask)

Your 30-day hypercare window worked: bugs got fixed, how-to questions got answers, and scope creep got routed to a change request. The end date on the policy is real. If you ghost the client, they feel abandoned. If you keep answering for free, you train them to ignore paid support.

This guide is the other bookend: a client hypercare closure pack with AI you can finish in one afternoon. You will send a clear “support window closed” message, capture honest feedback, and—only if the project went well—ask for a testimonial or referral without sounding desperate. Tools: ChatGPT, Google Docs, Google Forms, and Gmail. You review and send every email yourself.

Why a formal closure beats “we’re done, thanks!”

Hypercare ends on a calendar, not on vibes. A written closure:

• Confirms what was fixed during the window (fewer “you never finished X” disputes later)
• Sets what happens next (hourly, retainer, or no ongoing support—pick one honestly)
• Opens the door to feedback while the work is still fresh
• Separates goodwill (short survey) from marketing asks (testimonial/referral in a second, optional message)

This is not a handoff pack (that was delivery day) and not ongoing weekly status emails. It is the exit ceremony for hypercare.

You will leave with:

• A one-page Closure Summary in Google Docs
• A 5-question Google Forms feedback link
• ChatGPT prompts for testimonial, Google review, and referral asks
• Paste-ready Gmail templates you personalize once
• A simple rule for when not to ask for public praise

What you need before you start

• Your hypercare issue log (same Google Doc from hypercare setup)
• End date from the Hypercare Policy (no extensions unless you write a new date)
• Agreement on post-hypercare support (even if the answer is “email us for a quote”)

The closure flow (at a glance)

Step 1 — Audit the hypercare issue log

Open the log table from hypercare week. For every open row:

1. Mark Done with a one-line resolution note
2. Move unpaid Change rows to your CR template or quote draft
3. Export or copy the table section—you will paste it into ChatGPT in Step 2

If anything critical is still open, do not send closure yet. Send a short “hypercare extended 7 days for item #12” note instead, with a new end date in writing.

Step 2 — Draft the Closure Summary (Google Docs)

Create [Client] – Hypercare Closure Summary. One page, bullet-heavy:

• Window: start/end dates
• Tickets closed: count by type (Bug / How-to / Change routed)
• Known limitations: anything you documented as out of scope
• Next support path: hourly rate, retainer link, or “new work starts with a fresh proposal”

ChatGPT prompt (paste anonymized log + policy excerpt):

You are helping a freelancer close a 30-day client hypercare window professionally.

Inputs:
- Issue log table: [PASTE]
- Hypercare policy excerpt: [PASTE]

Write a one-page Closure Summary for the client Google Doc:
- Plain English, no blame
- Bullet list of resolved items (group by type)
- Explicit statement that hypercare ends on [DATE]
- One paragraph on how to request future help (quote/retainer)
Max 350 words. No invented fixes—only use items from the log.

Paste the output into Docs. Fix any hallucinated ticket IDs before sending.

Step 3 — Build a short Google Forms feedback survey

Create a form titled [Client] – Project feedback (2 min). Suggested fields:

1. Overall: 1–5 rating (required)
2. What worked well? (paragraph)
3. What could we improve? (paragraph)
4. Would you recommend us? NPS 0–10 (required)
5. May we follow up by email? Yes/No

Keep it anonymous-friendly unless you need attribution for testimonials later—in that case add: “Name (optional)” and “Company (optional).”

Copy the public form link; you will embed it in the closure email.

Step 4 — Write the closure Gmail (human sends)

Subject: [Client] – Hypercare window closed + quick feedback

ChatGPT prompt:

Draft a professional Gmail to a client closing a 30-day hypercare period.

Include:
- Thank you for clear communication during hypercare
- Link placeholders: [CLOSURE_DOC_LINK] and [FEEDBACK_FORM_LINK]
- Hypercare ends today; future requests follow [SUPPORT_PATH]
- Tone: warm, firm boundaries, no guilt
Max 180 words. No emojis. Sign off as [YOUR_NAME].

Replace placeholders with real links to the Closure Summary (view-only or PDF export) and the Form.

Send once from the same address you used during hypercare so threading stays sane.

Step 5 — Wait, then decide on testimonial or review asks

Wait 3–5 business days after closure for form responses. Rules:

Situation	Action
Rating ≥4 and positive comments	Proceed to Step 6
Mixed feedback	Reply privately; fix or document; no public ask
Angry or silent	Offer a paid remediation path; no testimonial ask

Do not ask for a Google review in the same email as the closure summary—it feels transactional. Sequence matters.

Step 6 — Optional: testimonial, case study, or referral ask

Only after positive feedback, send a second email (new thread is OK).

Testimonial prompt:

Draft a short Gmail asking a happy client for a 2–3 sentence testimonial we can use on our website.

Mention:
- They can edit any draft we write
- We need permission to use name, role, and company
- Optional: logo use only with explicit yes
Include a draft testimonial they can edit based on: [PASTE THEIR FORM COMMENTS]
Max 150 words.

Referral prompt (use sparingly):

Draft a gentle referral ask for a B2B client after successful project delivery.
One intro email template they could forward.
No discount bait unless [DISCOUNT_POLICY] is true.
Max 120 words.

Store signed permission in the same Google Doc folder as the Closure Summary (screenshot of “yes” email is enough for small clients).

Step 7 — Archive and protect yourself

• PDF the Closure Summary + final log snapshot to your project archive
• Note the closure date in your CRM or invoice tool
• If you use milestone acceptance docs, cross-link the hypercare closure date in your internal notes

Common mistakes

• Extending hypercare verbally without updating the policy date
• Bundling feedback form + testimonial + referral in one wall of asks
• Publishing a quote without written permission
• Ignoring negative feedback—fix or close the loop before chasing referrals

Quick checklist

• All hypercare log rows closed or explicitly carried to paid work
• Closure Summary in Google Docs reviewed for accuracy
• Google Forms link tested on mobile
• Closure Gmail sent from your hypercare address
• Testimonial/referral only after positive signal

More step-by-step playbooks for freelancers and SMBs live in our guides section.