PSA 42 of 50

Build an org macro

Create a shared macro with a reply, merge fields and ticket changes, then test it on a real ticket.

Applies to Admin

An org macro is shared. Everyone in your organization can run it from a ticket. Only people with Manage Macros, and PSA admins, can create, edit, delete or reorder them. Everyone else sees org macros but cannot change them. They can still choose Copy to my macros.

Open the page#

  1. Open PSA settings, then Service Desk, then Macros.
  2. The Org macros tab lists the shared macros. My macros lists your own.

The table shows Macro, Category, Actions, Uses, Status and Issues. Uses counts runs and the last time it ran.

Build one#

  1. Choose New macro. Or choose Start from template and pick one. Acknowledge & Self-Assign replies to the customer, sets In Progress, assigns the ticket to the person who runs it, moves it to their primary queue, and suggests an issue type.
  2. Set Name, Description, Category, Icon and Color. Enabled controls whether it shows on tickets.
  3. Write the Customer reply. Under it, Preview with example values shows how it reads.
  4. Add an Internal note if you need one.
  5. Under Actions, choose Add an action. Use the arrows to reorder. Use the bin to remove.
  6. Choose Create macro.

Merge fields

Choose Insert merge field to add the contact's name, the company, the ticket number and more. They look like {{contact.first_name}}. Add a fallback after a bar: {{contact.first_name|there}} prints "there" when the contact has no first name. The text is filled in on the server, so the stored note and the customer email match.

Actions

You can have one action in each of these groups: status (Set status or Pause SLA), priority, queue (Move to a queue or Move to my primary queue), assignee (Assign to a person or Assign to me), issue type (Set issue type or Suggest issue type), and Log time. You can add as many tags, CC contacts and follow-ups as you need.

Move to my primary queue uses the queue each person picked on My macros. If they picked none and are on one queue, that queue is used.

Checks while you build#

The editor checks the macro against your organization as you type. It flags a queue that is gone or inactive, a status that is off, a person who has left, a retired issue type, and a merge field that does not exist. The message shows on the field. Save macro stays off until all of them are fixed.

On the list, Issues shows a macro that has gone bad since it was saved, for example Queue "Support" is inactive. Technicians see that macro greyed out on tickets.

Test it on a ticket#

  1. On the row, open More actions and choose Test run.
  2. Pick a Ticket and choose Run test.
  3. Read what it would change, the reply as it would be sent, and anything it would refuse.

Nothing is changed or sent in a test.

Other row actions#

  • Duplicate makes a copy called "Copy of …".
  • Disable hides it from tickets without deleting it.
  • Delete asks you to confirm.
  • Move up and Move down set the order on tickets.

If it goes wrong#

  • You do not see New macro. You do not have Manage Macros. Ask a PSA admin.
  • The macro would not run on the test ticket. The test run says why, for example the ticket has no contact.
  • A person's queue move is skipped. They have no primary queue and are on several. Ask them to set one on My macros.