Creating and using Macros
Create reusable replies for Requests and include an optional Request status change.
Written By Robi Rohumaa
Last updated About 1 hour ago
Overview
Macros save reply text your team uses often. A Requests Macro can also select a Request status, so you can prepare a consistent reply and status update together.
Applying a Macro only prepares the reply in the editor. Review it before you send.
Create a Macro for Requests
Click 'New macro'
Enter a Macro name your team can search for
Write the Reply text
Under Available in, select Requests
Optional: select Change request status and choose a status
Click 'Create'
Keep the reply specific enough to save work, but leave out commitments that do not apply to every Request, such as a delivery date.
Choose Requests, Support, or both
Select both Requests and Support under Available in when the same reply belongs in both places. The reply text is shared, but the actions depend on where you apply the Macro:
Requests: An optional Request status change
Support: Conversation assignment actions, described in AI replies & Macros
Note: Assignment actions apply in Support only. Applying the Macro to a Request does not assign the Request to anyone.
Apply a Macro to a Request
Open the Request's comment editor
Click the lightning-bolt button and search for the Macro's name
Select the Macro to insert its reply text
Review the text and any selected status change
Check whether the comment is public or private and whether Requesters should be notified
Send the comment
The inserted text stays editable, and nothing is sent until you send the comment.
Important: A selected status change makes the comment a public status update. To send the reply as a private comment, remove the selected status first.
Edit or delete a Macro
Return to Settings → Requests → Macros. Open a Macro to edit its name, reply text, availability, or status action, then click 'Update'.
To remove a Macro, open its menu, choose the delete action, and confirm with 'Delete macro'.
Note: Deleting a Macro removes it from future selection. Comments already sent with it stay on their Requests.