GP Gameplanned Drills
Back to scenario drills

Automation Scenario Drill

Customer asks how AI-assisted CS work is reviewed

A security-conscious customer asks whether account summaries and renewal emails are AI-generated and human-reviewed.

Executive Communication CS Leader 35 minutes CS LeaderTeam Drill

Safe Composite Note

Safe composite inspired by recurring public CS patterns. No direct post, name, company, screenshot, or traceable detail is reused.

Decision Prompt

How should the CS leader respond and turn the question into a better operating standard?

Situation Brief

An enterprise customer asks your CSM whether recent account summaries, QBR drafts, and renewal emails were generated with AI. Their procurement questionnaire asks: 'List any AI tools used on our account data, who reviews AI-generated outputs, and whether restricted data is excluded.' The team uses approved internal tools, but has no simple customer-safe explanation of the review policy.

Available Evidence

  • The customer procurement team added an AI-use questionnaire to renewal prep.
  • CSMs use AI for drafts, summaries, and first-pass risk notes inside approved tools.
  • No customer data is pasted into public tools, but not every CSM can explain that clearly.
  • One renewal email sounded generic enough that the customer asked whether a bot wrote it.
  • Legal has a formal policy, but it is too long for a CSM response.
  • The VP CS wants the team to sound transparent without inviting a legal negotiation.
  • Managers review customer-facing work, but the review gate is not documented in a customer-friendly way.
  • Security wants the answer back in five business days or procurement will pause renewal review.
  • Restricted fields include credentials, private employee notes, raw contract terms, and unresolved security incidents.

Answer Rubric

What strong judgment sounds like.

Strong answer

Answer transparently, then codify the review boundary.

  1. Give a short customer-safe policy snippet naming approved-tool use, restricted data, and human review owner.
  2. Avoid claiming AI is never used if the team uses it for preparation.
  3. Document which outputs can be AI-assisted and which require named human approval.
  4. Create a manager checklist for customer-facing AI-assisted artifacts.
  5. Route formal policy questions to the approved legal/security path without over-answering.
  6. Set a five-day response owner so procurement does not stall renewal review.

Weak answer patterns

  • Saying 'we do not use AI' because that feels safer.
  • Sending the full internal policy instead of a customer-appropriate answer.
  • Treating the question as procurement friction rather than a trust signal.
  • Letting each CSM improvise the answer differently.

Manager Coaching Notes

  • Ask whether the response is truthful, short, and operationally enforceable.
  • Check if the team can name the review owner for customer-facing outputs.
  • Require a follow-up operating habit, not just a one-off answer.

AI Practice Prompt

Practice with your AI tool of choice.

          Draft a customer-safe AI review policy snippet and an internal manager review gate. Be transparent about approved AI-assisted preparation, restricted data, named human review owner, and escalation path for formal procurement/security questions. Keep it short enough for a renewal questionnaire.
        

Team CTA

Run this as a team drill

Use this scenario to calibrate how your team reads evidence, communicates risk, and decides the next move.

Open offer

Practice tools.

Open the CX pack
Automation CS Leader Analysis

Human Review Guardrails

Set safe boundaries for AI-assisted CS workflows.

Use in the CX pack →
Automation RevOps Checklist

Automation Candidate Audit

Find CS workflows worth automating.

Use in the CX pack →
Automation RevOps Plan

Knowledge Bot Brief

Define a safe internal knowledge assistant.

Use in the CX pack →