How to use the Support Macro Generator.
Macros should make required customization obvious. A reusable reply becomes harmful when it confidently states facts that vary by customer.
Make the workflow fit your task.
Identify the repeated issue and separate stable guidance from account-specific facts. Mark required substitutions clearly, include an appropriate next step and preserve the user's problem context. Test the macro with realistic cases before adding it to a reply library.
- What you provide
- Repeated issue and approved resolution policy.
- What you get
- Reusable response template with required variables.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Repeated issue: missing required CSV column; actual column name varies.
Completed example
Template: Your file is missing [column]. Add it to the header row and retry. Replace the placeholder before sending.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Should a support macro promise that retrying will always fix the issue?
Only when that behavior is established for the specific case. Otherwise describe the expected check and what to send if the problem remains.
Why does a reusable reply feel irrelevant to the customer's message?
It may skip their actual error or previous attempts. Require the agent to confirm the issue and customize the relevant fields.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑