Library › Customer Support & Success AI › Customer support teams
Find invalid merge fields in five macros
- For Customer support teams
- You practice Catching mistakes and made-up facts
- Time about 5 minutes
- Level Intermediate
About this exercise
The only valid merge fields are {{first_name}}, {{order_id}} and {{agent_name}}, exactly as written (lowercase, no spaces). Output a table with the header "Macro | Invalid fields" and five rows M1 to M5, listing each invalid field exactly as it appears or "none", then a last line "Fix: M#, M#". Plain text, under 60 words.
Common mistakes when you ask AI for this
- Missing the spaced field. The AI passes {{ order_id }} because it looks right. Try: Say: "No spaces inside the braces."
- Ignoring case. The AI passes {{First_name}}. Try: Say: "Field names are case-sensitive."
- Missing the summary line. The AI stops at the table. Try: Give the last-line format.
- 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
- Gives the header
- Lists the valid fields
- States case and spacing rules
- Asks for plain text
- Sets a length limit
Related exercises
- Accrue unpaid wages for the working days after the last pay period (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)
- Alert sales to a competitor's price change, facts only (Research & AI Search · Product managers)