Problem
Intercom currently has no way to auto-generate a unique, per-conversation or per-ticket URL and insert it dynamically into a Workflow message. When a Workflow sends a customer-facing message, there is no variable available that resolves to a direct link for that specific conversation or ticket.
The Customer Portal URL variable exists in macros and saved replies, but it is not available in Workflow message steps. More broadly, there is no native mechanism for a Workflow to construct or reference a unique URL for the conversation it is acting on — regardless of whether a Customer Portal is enabled.
Use Case
When a Workflow sends an auto-close reminder or a follow-up nudge to a customer, the message has no way to include a direct link back to the specific ticket or conversation. The customer must log into the portal independently or locate a previously received notification. A dynamically generated link in the message itself would remove that friction entirely.
Requested Feature
A native Workflow variable — for example, {{conversation.url}} or {{ticket.portal_url}} — that resolves at send time to the unique URL for the conversation or ticket the Workflow is acting on. This would allow any Workflow message step to include a direct, per-record link without requiring API customization or pre-stored attributes.
Current Workaround
The only available alternatives are: storing a pre-generated URL in a custom conversation attribute via the API and inserting that attribute into the Workflow message, or directing customers to the general Customer Portal home page rather than their specific record. Both require significant custom engineering and are not practical at scale.
Business Impact
- Any Workflow message that touches a customer about an open case could include a single-click path back to that specific record.
- Eliminates a common gap for auto-close reminders, ticket creation confirmations, and follow-up sequences where customers lose context between messages.
- Removes the need for API-based workarounds to achieve basic deep-linking behavior in outbound Workflow communications.