Library › Customer Support & Success AI › Customer success managers
Map five stakeholders with a stance backed by evidence
- For Customer success managers
- You practice Keeping the AI to your sources
- Time about 5 minutes
- Level Intermediate
About this exercise
Build a stakeholder map as a table with the header row exactly "Name | Role | Stance | Next touch" and five rows. Stance is exactly Champion, Neutral or Blocker, based only on the evidence in the notes. Next touch is a short action with a date. Plain text, table only, under 90 words.
Common mistakes when you ask AI for this
- Guessing a blocker by title. The teammate says the CFO must be a blocker. Try: Say: "Base the stance only on evidence in the notes."
- Missing a champion. The AI marks Bea Neutral because she is junior. Try: Say: "Quotes of strong support count as Champion."
- Undated actions or wrong table. The AI writes 'follow up' with no date. Try: Say: "Next touch: action with a date from Nov 9 to Nov 20."
- Getting markdown back. AI adds bold and headings by default, which show up as stray symbols where this is pasted. Try: Say "plain text, no bold, no headings, no asterisks".
- Trusting the AI to count words. AI is bad at counting and usually runs long, so a vague "keep it short" lands well over the limit. Try: Cap each part instead of the total, for example "each line under 15 words".
What a strong prompt includes
- Asks for plain text
- Sets a length limit
- Gives the header
- Bases stance on evidence
Related exercises
- Accept a job offer and confirm the exact terms (Writing AI · Job seekers)
- Accrue unbilled legal fees from a range using the midpoint policy (Finance AI · Accountants)
- Acknowledge an accessibility bug without a promised date (Customer Support & Success AI · Customer support teams)
- Acknowledge an executive escalation within the hour (Customer Support & Success AI · Executives)
- Age a returns queue in business days and flag the ones over the limit (Customer Support & Success AI · Customer support teams)