Turn repeated team questions into reusable answers

A support macro is useful when the answer path is stable, but a personal reply is safer when the user’s context changes the outcome. This guide helps teams choose between speed and judgment without sounding robotic.

## Use a macro for stable paths
A macro works when the same question has the same next step for most people. Password reset, access request intake, invoice download, or basic troubleshooting can often start with a macro. The macro should include the next action, what information to provide, and where the user can go if the case does not match.

## Use a personal reply for context-heavy cases
A personal reply is better when the answer depends on account status, billing history, contract terms, security review, or prior conversation. In those cases, a macro may sound efficient but create wrong expectations. The responder should explain which detail changes the answer and what will happen next.

## Combine both when possible
The best support reply often starts with a macro and adds one personal sentence. The macro provides the standard path; the personal sentence names the user’s specific condition. This keeps replies consistent without pretending every case is identical.

## Watch for stale macros
A macro should have an owner and review date. If users keep replying with the same confusion, the macro is not saving time; it is moving the burden to the next message. Track repeated follow-up questions and update the macro when the same gap appears.

## Avoid hidden policy in macros
Do not encode sensitive thresholds, private pricing, or internal review logic into public macro text. If a policy cannot be public, the macro should explain the intake step rather than the decision rule.

## Practical rule
Use a macro when the next step is stable and safe. Use a personal reply when the outcome depends on private context. Use both when the standard path is clear but the user needs to know how their case fits it.

Support macro or personal reply: how to choose the right response

// COMMENTS

ON THIS PAGE