From customer insight to completed order.

Three jobs, one customer journey.

Workflow: bring a guest back.

1. Start with the customer relationship. Use visit or purchase history from a connected system to identify guests who may be ready to return. Apply the brand’s audience rules and contact permissions.
2. Prepare a relevant reason to return. The AI CRM assistant helps draft the message, select the audience, and plan timing. The brand team reviews the campaign before it is sent.
3. Continue the conversation. A guest can ask about the offer, the menu, or a suitable time. BrandRep uses the brand information available to it to help the guest choose a next step.
4. Connect to a booking. Where the booking workflow is enabled, BrandRep can guide the guest through a reservation in the conversation. Read the Melting Pot booking example.

Workflow: turn a reorder prompt into an order.

A repeat purchase starts with context: what the customer bought, when they bought it, and whether they have agreed to receive messages. Kubbly helps the team turn that context into a relevant campaign.

When the customer responds, BrandRep can answer product questions and guide an order through the brand’s enabled commerce workflow. Product availability, order submission, payment, and confirmation depend on the connected systems and the workflow configured for that brand.

Customer-data sync and transaction completion are different capabilities. Importing purchase history does not by itself enable new orders. Review the supported integrations and their scope before choosing a workflow.

Where RCS fits.

RCS is a messaging channel within the platform. It can bring verified branding, rich content, and interactive actions into supported messaging experiences. Kubbly’s RCS preview helps a brand see that experience; activating campaigns and BrandRep commerce requires the appropriate setup, permissions, and connections.