Intercom adds required fill-in fields to support macros

Personalization becomes a controlled input

Intercom’s October 6 update adds fill-in fields to macros. A macro author can insert text, long-text or choice fields into a prepared reply and mark them required or optional. When a teammate applies the macro, Intercom presents the fields as a form and shows a live preview. The completed reply is inserted into the composer rather than sent automatically, leaving a final human review point before the customer receives it.

For support and RevOps leaders, the important shift is from an informal placeholder to a visible input contract. A reminder such as ‘add the account date here’ depends on memory and can survive into a customer message. A required field creates a gate, while a bounded choice can standardize language that should not be improvised. The control is still only as good as the field definition, source evidence and review behavior that teams attach to it.

Sources: Intercom changelog, October 6, 2026 · Intercom: Personalize macro replies with fill-in fields

Choose fields from customer consequence, not convenience

Use required fields for facts that materially change the meaning of the response: an approved resolution, account-specific deadline, verified amount, plan entitlement or next owner. Optional fields are better for context that improves clarity but is not always relevant. Choice fields work well when the approved language is finite, such as a small set of verified escalation states. Free text is appropriate when the operator must explain a case-specific fact that cannot be safely reduced to a menu.

Every required field should have a named source. If an agent cannot tell whether a renewal date comes from the CRM, billing system or a customer email, making the field mandatory only guarantees that something is entered. Define the label as a question the operator can answer, link the internal procedure to the authoritative record, and avoid asking teammates to infer financial, contractual or compliance facts from incomplete conversation context.

Sources: Intercom: Personalize macro replies with fill-in fields

Optional sections need deliberate absence rules

Intercom says an optional fill-in field is inserted as a whole section: if the teammate leaves it blank, the associated section is omitted. That is useful for conditional context, but operators should test the grammar and meaning of both states. A message should remain complete when the optional section is absent, and the omission must not remove a required caveat, commitment or ownership statement.

Build test cases for the shortest and longest allowed values, every choice, an empty optional section and a missing required answer. Preview how punctuation, line breaks and surrounding sentences behave. Then test the final result in the channels where the macro will be used. A macro that reads clearly in an editor may become confusing when a customer sees it without internal context or when a long account name changes the visual structure.

Sources: Intercom: Personalize macro replies with fill-in fields

Preserve the human release step

The finished reply is inserted into the composer and is not automatically sent. That boundary should remain explicit in training: completing the form does not mean the communication is approved. The teammate should compare the preview with the source record, check the customer identity and current conversation, confirm any promised action has an owner, and read the assembled response as a customer would. Required input and human review solve different problems.

For sensitive macros, sample both the input form and the sent output. Keep the macro version, applied fields, actor, conversation and final message available for quality review under the organization’s data-retention policy. Intercom’s help article documents the creation and use workflow; it does not claim a particular error reduction or response-time improvement. Teams should measure their own rework, omission and escalation outcomes after rollout.

Sources: Intercom: Personalize macro replies with fill-in fields

Pilot where revenue and support meet

A strong pilot is a high-volume macro with one or two meaningful variables, such as a service-credit review, implementation delay update or renewal-risk escalation. Give the macro an owner, define the authoritative source for each field, publish approved choices, and run paired reviews for the first week. Include a case where the optional section is intentionally omitted and a case where the operator must stop because the required evidence is unavailable.

Intercom notes that the capability is tied to its new Inbox and describes a gradual rollout. Administrators should confirm availability in their workspace before changing procedures. After the pilot, review field-completion failures, edited output, wrong-source incidents, customer replies and cases where the teammate abandoned the macro. The opportunity is not generic personalization at scale; it is a more inspectable path from reusable policy to a case-specific, human-approved response.

Include governance for change as well as first publication. A macro owner should re-test required inputs when policy, product terms or the source-system field changes, and retire choices that are no longer approved. Publish the effective version and review date in the internal procedure. When a customer-facing incident occurs, investigators should be able to identify the macro version, the values supplied and the actual sent message without assuming the template remained unchanged.

Sources: Intercom changelog, October 6, 2026 · Intercom: Personalize macro replies with fill-in fields