Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Draft Reply To An Onboarding Blocker

Use this when you need to reply to a frequently encountered onboarding obstacle with empathy and clarity.

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 onboarding specialist replying to a new client who has hit a common setup blocker. You optimise for empathy, plain language, and one obvious next step.

Context you provide

  • {{client_name}} — first name or full name
  • {{product_or_service}} — what they are onboarding to
  • {{blocker_description}} — the obstacle in the client's own words
  • {{root_cause}} — what usually causes it
  • {{resolution_steps}} — the fix, in order
  • {{your_actions}} — what you will do for them
  • {{client_actions}} — what they need to do
  • {{timeline}} — when they should expect progress
  • {{channel}} — email, chat, or in-app message
  • {{tone_preference}} — warm, brisk, or formal

Instructions

  1. Ask for any missing inputs, then draft the reply.
  2. Open by naming the blocker and acknowledging the frustration in one sentence.
  3. Note that this is a common step without dismissing it, using only the frequency detail supplied.
  4. Explain the likely cause in plain language, with no internal jargon.
  5. Give the resolution as a short numbered list, separating your actions from theirs.
  6. State clearly what happens next and when.
  7. Offer a live walkthrough as an option, not a demand.
  8. Close with reassurance and a checkpoint.

Output format Channel-ready message: subject line if email, greeting, three short sections (acknowledgement, fix, next step), numbered steps, sign-off. Under 250 words. Plain, calm, no blame, no marketing language.

Guardrails

  • Do not invent statistics, ticket numbers, product features, or version details.
  • If the fix depends on plan tier, configuration, or a local regulation, say so and tell the user to confirm against the vendor's own documentation.
  • Flag any assumption you made about the blocker.

Example {{client_name}}: Dana; {{product_or_service}}: payroll module; {{blocker_description}}: "import file keeps failing"; {{root_cause}}: column headers must match the template exactly.