RAIntegration · Customer Service

Connect Re:amaze support conversations to Salesforce Agentforce

Re:amaze is the customer support and messaging platform designed for e-commerce and direct-to-consumer businesses — combining live chat, email, SMS, and social messaging in a unified inbox, with strong integrations to Shopify, WooCommerce, and BigCommerce. For brands using Re:amaze as their customer support platform alongside Salesforce as a CRM or marketing platform, the support conversation history in Re:amaze is the operational context that complements the contact and transaction record in Salesforce. When a customer escalates a support interaction, their prior conversation history in Re:amaze is the context an agent needs. When a commercial event in Salesforce triggers a customer notification, Re:amaze is the channel for that communication. When Emerge Digital connects Re:amaze to Agentforce, support conversation context is available to agents during escalated interactions — and Salesforce commercial events can coordinate with Re:amaze customer communications.

All integrations

What this unlocks

Support conversation history context during escalated interactions: when a customer escalates from Re:amaze self-service or first-level support to a commercial team interaction, an Agentforce agent can retrieve the full Re:amaze conversation history for the customer — the issue timeline, the prior responses, and the current resolution status — providing the escalating agent with the complete context before the next interaction.
Multi-channel support touchpoint visibility in Salesforce account views: Re:amaze aggregates customer conversations from email, chat, SMS, and social channels — an agent can surface the customer's recent support touchpoints from Re:amaze in a Salesforce account view, giving the account team a complete picture of the customer's recent service experience alongside the commercial history.
Salesforce commercial events trigger Re:amaze customer notifications: when a Salesforce commercial event requires a customer notification — a subscription renewal reminder, an order status update, an account change confirmation — an Agentforce agent can trigger the Re:amaze message in the customer's preferred channel, using Re:amaze's multi-channel delivery rather than a separate email tool.
Support volume and CSAT trends for account health monitoring: Re:amaze tracks support volume, response times, and customer satisfaction scores — an Agentforce agent can surface the CSAT trend and support volume for a customer account during a customer success review, identifying service quality signals relevant to the commercial relationship.

In the customer journey

Escalation context retrieved from Re:amaze before account team contact

A customer contacts a brand's e-commerce support through Re:amaze about a defective product — after four days and three support interactions, the customer requests to speak with an account manager. The Agentforce agent retrieves the Re:amaze conversation history: three chat sessions, the product images the customer submitted, the replacement offered but not yet fulfilled, and the customer's expressed frustration level. The account manager contacts the customer with the full context of the prior interactions, able to acknowledge the specific timeline and take a resolution action rather than asking the customer to re-explain the issue.

Support CSAT decline surfaces in account health review

An account manager is preparing a quarterly review for an enterprise brand customer. The Agentforce agent queries Re:amaze for the brand's CSAT scores and support volume over the past 90 days — CSAT has declined from 4.3 to 3.8 over the quarter, and chat response times have increased by 40% following a staffing change. The account manager enters the review aware of the service quality signals, prepared to discuss the support performance trend and the relevant platform features that could improve response time without additional headcount.

Subscription renewal reminder sent through Re:amaze preferred channel

A Salesforce workflow identifies a customer's annual subscription renewal date in 30 days. An Agentforce agent determines from the Salesforce contact record that the customer's preferred communication channel is SMS. The agent triggers a Re:amaze SMS conversation to the customer with the renewal reminder, the current plan details, and a link to the renewal page. The reminder reaches the customer in their preferred channel rather than a generic email from the billing system.

Why not managing customer support directly in Salesforce Service Cloud?

Salesforce Service Cloud is the enterprise customer service platform — it is the right choice for large organisations running complex, multi-tier service operations. Re:amaze is purpose-built for e-commerce and DTC brands where the support workflow is tightly coupled to the order management and customer messaging context from Shopify, WooCommerce, and social commerce channels. For brands on these platforms, Re:amaze provides native integrations and channel management that Salesforce Service Cloud requires significant customisation to replicate. The Agentforce integration connects the Re:amaze support context to Salesforce commercial data without requiring the brand to migrate to a different support platform.

Re:amaze's Agentforce integration is most relevant for e-commerce and DTC brands that use Re:amaze as their primary customer support platform alongside Salesforce for commercial and contact management — where support conversation history and CSAT trends are relevant to commercial account interactions and where multi-channel notification delivery through Re:amaze complements Salesforce commercial workflows.

How Emerge integrates Re:amaze

Emerge Digital connects Re:amaze to Salesforce Agentforce as a consulting engagement. We map Re:amaze customer conversation records to Salesforce contacts and accounts, design the conversation history retrieval for escalated interaction context, configure the CSAT monitoring triggers for account health alerts, and integrate the multi-channel notification delivery for Salesforce commercial event communications.

How we structure an engagement

Related integrations

FAQ

We use Gorgias or Tidio rather than Re:amaze for e-commerce support — can the same pattern work?

Yes. The e-commerce customer support integration pattern applies to Gorgias, Tidio, Richpanel, and other DTC-oriented support platforms. Emerge builds to the support platform your brand uses, adapting the integration to the specific API and data model of the platform.

Re:amaze is primarily for Shopify stores — does the integration work if we also use Salesforce Commerce Cloud?

Re:amaze integrates with multiple e-commerce platforms including Shopify, WooCommerce, BigCommerce, and Salesforce Commerce Cloud. The Agentforce integration is at the Re:amaze → Salesforce CRM layer, connecting support conversation context to the commercial CRM. The underlying e-commerce platform powering the store does not affect the Re:amaze → Salesforce integration.

Can the agent respond to customer support conversations in Re:amaze directly?

The integration is designed primarily for reading Re:amaze conversation history to inform Agentforce commercial interactions and for triggering new Re:amaze outbound messages for commercial notification purposes. Autonomous agent responses to existing Re:amaze support conversations require specific governance design to ensure the agent responses are appropriate for the support context — this is a more complex integration pattern that Emerge can design for specific use cases.

How long does a Re:amaze + Agentforce integration take?

A focused engagement typically runs three to five weeks: mapping Re:amaze customer records to Salesforce contacts and accounts, designing the conversation history retrieval and CSAT monitoring, configuring Salesforce commercial event triggers for Re:amaze multi-channel notifications, and testing escalation context retrieval, CSAT alert routing, and notification delivery scenarios.

Ground your agents in Re:amaze.

Tell us what your agents need to read and write in Re:amaze, and we'll design the integration and the governance around it.

Talk to the practice

Prefer email? Write to the practice instead.