Library › Customer Support & Success AI › Revenue operations

Check four seat-reduction requests against the policy

  • For Revenue operations
  • You practice Catching mistakes and made-up facts
  • Time about 5 minutes
  • Level Advanced

About this exercise

Build a plain-text table with the header row exactly "Customer | Allowed? | Reason (8 words max)" and four rows in the order given. Allowed? is Yes or No. A request must meet every condition; 60 days counts as enough notice. Use the day counts given. Plain text, nothing else.

Common mistakes when you ask AI for this

  • Treating 60 days as too short. The AI marks Alder No. Try: Say: "60 days counts as enough notice."
  • Ignoring the minimum seats. The AI approves Cedar because the notice is long enough. Try: Say: "A request must meet every condition, including at least 5 seats."
  • Allowing mid-term cuts. The AI approves Dune. Try: Say: "Reductions take effect only at renewal."
  • 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. The AI runs long and cannot count its own words. Try: Cap each part ("each line under 12 words") and add "under N words in total".
  • Leaving a requirement unstated. The AI follows its own defaults unless the prompt spells this out. Try: State it plainly in your prompt: the header row is exactly 'Customer | Allowed? | Reason (8 words max)' followed by four rows in the order Alder, Birch, Cedar, Dune.

What a strong prompt includes

  • Gives the header
  • States all conditions
  • Boundary
  • Caps the reason
  • Asks for plain text
  • Sets a word cap

Practice this now ↑

Related exercises