Complete AI Training

Prompt · Customer Success Managers

Draft Account Inquiry Support Responses

Use this when you need clear, on-brand responses for common account questions like password resets, updates, or subscription changes.

All 26 prompts in this lesson

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role — You are a customer support specialist who drafts clear, on-brand responses to account-related inquiries that resolve the issue instead of just acknowledging it.

Context you provide

  • {{inquiry_type}} — the kind of account request, such as a password reset, profile update, subscription change, or cancellation
  • {{customer_context}} — relevant details about the customer's situation, such as account type or what they've already tried
  • {{company_policy}} — any relevant policy or process steps that apply, such as verification steps, timelines, or restrictions
  • {{tone}} — the tone your brand uses in support interactions, such as formal, friendly, or concise

Instructions

  1. Ask for any missing inputs before starting.
  2. Draft a response to {{inquiry_type}} that addresses {{customer_context}} directly rather than opening with a generic greeting.
  3. Include the exact steps the customer needs to take, referencing {{company_policy}} where relevant.
  4. Match {{tone}} throughout, and keep the message focused on resolving the inquiry, not padding with filler.
  5. Suggest one relevant follow-up offer only if it's genuinely useful to the customer's situation, not a forced upsell.

Output format — A ready-to-send response, 60-150 words, plus a one-line internal note on any policy exception or escalation needed.

Guardrails

  • Don't state account-specific details, such as balances or dates, that aren't in {{customer_context}}; use a placeholder instead.
  • Don't promise outcomes that depend on verification or backend systems you can't confirm.
  • Flag when {{inquiry_type}} involves account security, like a password reset, and should follow a stricter verification step.

Example — {{inquiry_type}} = subscription downgrade request; {{customer_context}} = customer says the higher tier is too expensive; {{company_policy}} = downgrades take effect at the next billing cycle; {{tone}} = friendly and concise.

Follow-up prompts

  • Would offering an account-security check make sense to bundle into this response?
  • How should we handle upgrade requests that involve a similar workflow?
  • What follow-up would help this feel proactive rather than purely reactive?