Intercom adds admin control over personal support macros

What Intercom changed

Intercom's October 9 changelog introduces Macro Admin Mode. Teammates with the Can manage shared macros permission can view everyone's personal macros in Macro settings. From there, Intercom says they can convert a useful personal macro into a shared macro or delete one that is out of date.

The release is compact, but the operating consequence is meaningful. Personal libraries can contain the strongest field-tested language and the most persistent policy drift. Giving a permissioned role visibility across them creates a practical curation surface for support operations, enablement and customer-success governance.

• Verify the permission in the target workspace.
• Name the administrators allowed to review personal macros.
• Record the release date and tenant availability.

Sources: Intercom: Macro Admin Mode

Promotion is a publishing decision

A useful personal reply should not become shared merely because it is frequently used. Promotion expands its audience and can turn one operator's shorthand into the organization's apparent policy. Require a named owner, source policy, intended conversations, approver, effective date and next review date.

Review claims about pricing, refunds, security, data handling, service levels and contractual terms with the appropriate owner. Keep placeholders and escalation triggers explicit. A shared macro should help a teammate respond consistently while preserving the judgment required for customer-specific facts.

• Require a policy source and owner.
• Review commercial and contractual statements.
• Set an expiry or review date before promotion.

Use evidence to find candidates

Personal macro visibility creates a candidate pool. Rank candidates using usage, repeat edits, resolution context and teammate feedback, but do not treat any one signal as proof. A popular response may be convenient and still be outdated; a rare macro may cover a high-consequence exception that deserves formal guidance.

Sample the conversations in which a candidate was used. Check whether the reply matched the actual issue, required later correction or produced an escalation. Preserve counts and denominators. The goal is not to score individual agents; it is to identify reusable knowledge and risk.

• Separate popularity from correctness.
• Sample outcomes before promotion.
• Avoid individual surveillance metrics without purpose and safeguards.

Deletion needs a retirement record

Deleting an outdated macro reduces future reuse, but it does not erase copied variants or correct messages already sent. Capture the reason, policy change, owner and replacement before deletion. Search for near-duplicates and common copied phrases so the team does not retire only one visible instance.

For high-consequence changes, sample recent conversations that used the retired language and decide whether proactive correction is required. Keep the retirement record outside the deleted artifact so reviewers can later explain why the response disappeared.

• Link the replacement before removal.
• Search personal and shared near-duplicates.
• Assess recent customer impact for material policy changes.

Preserve a safe personal workspace

Personal macros are useful because teammates can capture a repeated pattern quickly. Governance should not turn every experiment into a committee decision. Define a light personal lane for low-risk drafts and a controlled shared lane for reusable operational language.

Tell teammates who can inspect personal macros and why. Limit the administrator permission to the curation role, review access periodically and avoid using the view as a productivity-monitoring shortcut. Trust improves when the purpose, scope and decision process are explicit.

• Document visibility and purpose.
• Keep least-privilege administrator access.
• Separate knowledge curation from performance management.

Build a macro lifecycle

Give each shared macro a stable ID, owner, audience, policy source, approval time, review date and status. Add tags for product area, customer segment, language and escalation class. Record material edits as new versions so the team can connect a response to the guidance active at that time.

Run a weekly candidate review and a monthly stale-content review. Trigger an immediate review after pricing, policy, product, legal or service-level changes. Archive the decision record even when Intercom's operational action is deletion.

• Assign every shared macro an owner.
• Version material changes.
• Use event-driven and scheduled reviews.

Measure library quality

Track candidate-to-promotion time, shared macros with current owners and sources, overdue reviews, duplicate clusters, retired macros with replacements and sampled conversations requiring correction. Keep usage as context rather than a quality score. Report the size of each reviewed population.

Measure downstream effect carefully. Faster replies or fewer edits can support a local hypothesis, but volume, staffing and issue mix also change. Use controlled samples and qualitative review rather than claiming a macro alone caused service improvement.

• Publish denominators and review coverage.
• Separate usage, quality and outcome measures.
• Avoid unsupported causal claims.

The operator takeaway

Macro Admin Mode gives support operations a stronger way to find the knowledge already being created at the edge of the team. Used well, it can turn effective personal practice into governed shared guidance and prevent obsolete replies from accumulating unnoticed.

The control is a lifecycle, not the permission alone. Identify candidates with evidence, review the customer promise, assign ownership, publish with dates, search for duplicates and retain a retirement record. That preserves the speed of personal learning while improving the reliability of shared responses.

• Treat promotion as publication.
• Treat deletion as governed retirement.
• Keep personal experimentation and shared policy distinct.