A table booking starts with a conversation.

The workflow at a glance.

From the guest’s request to the restaurant’s booking system.

1. The guest starts with the brand. The public RCS example presents The Melting Pot with its brand name and logo in the messaging experience.
2. The guest asks about a table. The request stays conversational. The guest can express what they need in a message.
3. BrandRep helps find a time. Kubbly’s AI representative carries the conversation on behalf of the restaurant, helping the guest reach a suitable reservation option.
4. The reservation flows into OpenTable. The example connects the conversation to the restaurant’s booking system. This is the step that turns an exchange of messages into a booking workflow.

This walkthrough describes the publicly shared workflow. It is not a verbatim guest transcript.

How this fits the Kubbly platform.

Kubbly is an agentic customer engagement and commerce platform. Its AI CRM assistant works with the brand team on customer opportunities, audiences, messages, and timing. Campaign execution delivers approved outreach. BrandRep is the customer-facing assistant that continues the conversation and helps complete an enabled order or booking.

The Melting Pot example focuses on that last part: a brand representative helping a guest make a reservation. Customer-data preparation and retention marketing provide context for the broader customer relationship. Read the customer engagement workflows for the full sequence.

See the original example.

Kubbly founder Piyush Jain publicly shared the Melting Pot RCS booking example, describing a guest conversation that finds a time and connects the reservation to OpenTable.

View the original Melting Pot booking post on LinkedIn

This page documents the workflow shown in Kubbly’s public example. Channel and location availability depend on the brand’s deployment. It does not report measured conversion lift, incremental revenue, or results for every Melting Pot location.

What another brand needs.

Start with an approved messaging presence, the information the assistant needs to represent your brand, and a connected booking workflow with permission to perform the intended action. Confirm the supported locations, availability handling, and booking confirmation path before launch.

OpenTable guest-data sync and reservation creation serve different purposes. The integrations page explains which data connections support CRM and why a transaction workflow must be confirmed separately.