The prompt
Score 10 of 10, Excellent
Use it when Your team's macros or canned responses read stiff or out of date, and you want them clearer and warmer without losing any policy detail.
- {{macro_text}}
- {{must_keep}}
- {{voice_notes}}
- {{channel}}
- {{company}}
Full prompt and why it works
Prompt
<macro> {{macro_text}} </macro> <must_keep_word_for_word> {{must_keep}} </must_keep_word_for_word> <voice> {{voice_notes}} </voice> <constraints> - Keep every fact, condition, number, link, time limit and step from the macro. A rewrite that drops a condition creates wrong answers at scale, because agents send this text many times a day. - Keep the macro's fill-in fields, such as [ORDER_NUMBER] or a first-name field, exactly as written. - Keep the text listed under must_keep_word_for_word unchanged. - Do not add promises, apologies for things that did not happen, or facts that are not in the macro. - Avoid stock phrases such as "We apologize for any inconvenience", "Thank you for reaching out" as an opening, and "Please do not hesitate to contact us". - Use plain words, short sentences, and "you" and "we". </constraints> <format> 1. The rewritten macro for {{channel}}. 2. A version of no more than 60 words for live chat. If it cannot fit without dropping a condition, say so instead of shortening it. 3. A Markdown table with the columns Fact or condition in the original, and Where it appears in the rewrite, so a reviewer can confirm nothing was lost. </format> <task> Using the macro and voice notes above, rewrite the macro for agents at {{company}} so customers read it as written by a helpful person on our team. It should be clearer and shorter than the original where possible, and must not change what it tells the customer. If a sentence in the original is unclear or seems out of date, keep its meaning and list it under "Check with the macro owner" after the table. </task>
Variables
- {{macro_text}}
- The saved reply as it is today, including its fill-in fields.
- {{must_keep}}
- Wording that must not change, such as legal text or a plan name. Write "none" if nothing must.
- {{voice_notes}}
- How your team sounds, in a few words or a sample reply you like.
- {{channel}}
- Where agents mainly send it, for example email or in-app messages.
- {{company}}
- Your company or product name.
Why it works
- What to avoid. Every condition, number and fill-in field must survive, because a macro is sent hundreds of times and one dropped condition becomes hundreds of wrong answers.
- Format. A checklist table maps each fact in the original to its place in the rewrite, so a reviewer can approve it in a minute.
- Layout. Material first in tags, constraints and format next, and the task last: the order Google recommends for Gemini.