PSA 19 of 50

Apply a ticket macro

Run a saved macro on a ticket. It sends the reply and makes the ticket changes for you.

Applies to Technician Admin

A macro is a saved reply plus ticket changes. You run it from the ticket in one click. The server does all of it: it sends the reply, changes the ticket, and writes one entry in the ticket history.

There are two kinds. My macros are yours. Only you see them. Org macros are shared. Everyone in your organization can run them.

Run one#

  1. Open the ticket and choose Macros at the top of the ticket. You can also press Ctrl+M, or Cmd+M on a Mac.
  2. Search with Search macros. Your own macros are under My macros. Org macros are grouped by category.
  3. Point at a macro. The right side lists what it does and shows the reply with example names.
  4. To see the real result first, choose Preview on this ticket. Nothing is changed or sent.
  5. Choose the macro, or choose Run macro.

The reply goes to the customer by email, the same as a reply you typed. The text uses this ticket's contact, company and number.

If the ticket is in Triage#

The ticket must leave Triage before most macros can run. The dialog Move out of Triage opens. Pick the Destination queue, then choose Run macro.

If a macro is greyed out#

A macro with a problem cannot run. It shows the reason, for example that its queue is inactive. Point at it to read the full reason. Ask an admin to fix it. If it is yours, open it and fix it. See Create a personal macro.

Make a macro from a reply#

  1. Type the reply in the composer, but do not send it.
  2. Open Macros and choose Save current reply as macro. For an internal note it says Save current note as macro.
  3. Give it a name and choose Create macro.

To start from nothing, choose New macro. A macro you make here is always personal.

If it goes wrong#

  • The macro says it stopped. The message names the action that failed. Actions before it are kept. Read the ticket history.
  • Nothing changed. The ticket may already have had those values. The result says which actions were skipped.
  • A change was refused. A macro has the same limits as doing the change by hand. If you cannot change the status yourself, the macro cannot either.
  • A queue move was skipped. The macro uses your primary queue. See Create a personal macro to set it.