Supp/Blog/How to Write Support Macros That Don't Sound Like a Robot Wrote Them
How-To6 min read· Updated

How to Write Support Macros That Don't Sound Like a Robot Wrote Them

Canned responses save time, but bad ones destroy trust. Here's how to write macros that feel like a real person typed them.


The Problem with Most Macros

Every support team has them. Pre-written responses for common questions. Password resets, billing inquiries, shipping status, refund requests.

And every customer has received one that made them feel like they were talking to a vending machine.

The issue isn't that macros exist. They're necessary. A team handling 200 tickets a day can't write every response from scratch. The issue is that most macros are written once by someone in a hurry, then copied verbatim for the next two years without anyone reconsidering whether they actually sound like something a human would say.

Start with the Greeting

Kill "Dear valued customer" immediately. Nobody has ever felt valued by being called "valued customer." It's the support equivalent of a form letter from your insurance company.

Use their name. If your help desk supports variables, {{first_name}} is the bare minimum. If you don't have their name, skip the greeting entirely and open with the answer.

Good:

  • "Hi Sarah,"
  • "Hey there,"
  • Just start with the answer. No greeting needed.

Bad:

  • "Dear valued customer,"
  • "Hello! Thank you for reaching out to us today!"
  • "Greetings,"

Write Like You Talk

Read your macro out loud. If it sounds like something you'd never say in conversation, rewrite it. Support is a conversation, and your macros should reflect that.

Compare these two:

Before: "We sincerely apologize for any inconvenience this may have caused. Please be advised that your request has been received and is currently being processed by our team."

After: "Sorry about that. We've got your request and we're working on it now."

Same information. Half the words. Ten times more human.

Use Contractions

"We are" becomes "we're." "It is" becomes "it's." "You will" becomes "you'll." This alone makes macros 40% less robotic.

Cut the Filler

"Thank you for your patience and understanding" adds nothing. "I hope this helps" is fine once in a while but becomes white noise after the tenth ticket. Every sentence in your macro should either provide information or move the conversation forward.

Variables Make the Difference

Most help desk tools support variable insertion. Use them aggressively.

  • {{first_name}} for personalization
  • {{ticket_id}} or {{order_number}} for reference
  • {{agent_name}} so the customer knows who's helping
  • {{product_name}} when you support multiple products

A macro that says "Hi {{first_name}}, I checked your order {{order_number}} and it shipped yesterday" reads completely differently from "Your order has been shipped."

When NOT to Use a Macro

Some situations require a fully custom response. Don't reach for a template when:

  • The customer is visibly upset or frustrated (they'll notice the canned response and get angrier)
  • The situation is unusual or complex (a macro won't cover it, and partial macros look worse than no macro)
  • You're delivering bad news (cancellations, denials, account closures deserve a personal touch)
  • The customer explicitly says "please don't send me a canned response"

Building Your Macro Library

Start with your top 10 ticket categories. Look at your actual data. If you're using an intent classification system, you already know exactly which issues come up most.

For each category, write a macro that:

  1. Acknowledges what the customer asked
  2. Gives the answer or next step
  3. Ends with an invitation to follow up

That's it. Don't over-engineer it.

Review Quarterly

Macros go stale. Products change, policies update, and language that felt fresh in January sounds tired by June. Put a recurring calendar event to review your macro library every quarter. Delete the ones nobody uses. Rewrite the ones that get poor satisfaction scores. Add new ones for emerging ticket types.

Supp's Approach

Supp classifies incoming messages into 315 intents automatically. That classification can trigger the right macro before an agent even opens the ticket, or auto-resolve simple requests entirely. At $0.20 per classification and $0.30 per resolution, you pay only for what you use.

The best macro is the one that's selected and personalized automatically, so the customer gets an instant, accurate, human-sounding answer without waiting in a queue.

Try Supp Free

$5 in free credits. No credit card required. Set up in under 15 minutes.

Try Supp Free
support macroscanned responsessupport templatescustomer service templatesmacro exampleshelp desk macros
How to Write Support Macros That Don't Sound Like a Robot Wrote Them | Supp Blog