RCS interactive product recommendation flow
Use case description
The RCS interactive product recommendation flow enables you to create personalized shopping experiences through conversational messaging. This use case transforms traditional product discovery by engaging customers in interactive conversations that capture their preferences and deliver tailored product recommendations.
Customers receive RCS messages with quick-reply buttons that guide them through a preference-gathering journey. Based on their responses, the system automatically segments customers and delivers personalized product recommendations that align with their stated needs. This approach creates a win-win scenario: you collect valuable zero-party data while customers receive curated product suggestions that help them find what they're looking for more efficiently.

Key features
- Interactive conversation flow: Multi-step RCS messaging sequence with intuitive quick-reply buttons
- Dynamic segmentation: Automated grouping based on response combinations across multiple touchpoints
- Zero-party data collection: Direct capture of customer preferences through conversational interactions
- Personalized recommendations: TTargeted product suggestions based on individual customer response patterns
- Campaign event tracking: Comprehensive monitoring of customer interactions and response data
- Flexible configuration: Customizable message sequences and response options to match campaign objectives
Use case items
When you deploy this use case, you'll receive:
- RCS response flow: Complete multi-message conversation sequence
- Segmentation structure: Pre-built customer segments covering all response combinations
How to deploy the use case
Prerequisites
Before implementing this use case, ensure you have:
- RCS integration: Active RCS Business API integration in your Bloomreach Engagement project
- Link shortener: Required module for RCS functionality (the use case can't be deployed without this module)
Need assistance?
Contact your Customer Success Manager if you need to add WhatsApp as a channel or have integration questions.
Understanding the flow logic
The recommendation flow works through a structured conversation process:
- Initial engagement: Customers receive an RCS message with quick-reply buttons asking about their preferences.
- Response collection: Each customer selection triggers the next message in the sequence while recording the response as a campaign event.
- Preference gathering: The conversation continues through multiple questions (typically 3 messages) to develop a comprehensive customer preference profile.
- Recommendation delivery: Based on the complete response pattern, customers receive a final message with personalized product recommendations.
Response tracking
Customer responses are tracked as campaign events with these specifications:
- Action type:
RCS
- Status:
incoming_message
- Message field: Contains the customer's actual response text

Message structure
The default template includes:
- Message 1: 3 quick-reply options for initial preference capture
- Messages 2-3: 4 quick-reply options each for detailed preference gathering
- Message 4: Personalized product recommendation based on response combination
You can adjust the number of messages and response options to match your campaign needs.
Set up RCS templates
Configure the initial message
- Access message configuration: Double-click the Initial Message node in your conversation flow
- Configure message content:
- Sender: Select your RCS integration
- Title: Create your message subject line
- Description: Write your main message content
- Button name: Name your options list
- List items: Define the customer selection options
- Apply message settings:
- Frequency policy: Select your relevant frequency policy
- Consent: Choose the appropriate consent category

Configure message 2
- Access message configuration: Double-click the Example Message 2 node in your conversation flow
- Configure message content:
- Sender: Select your RCS integration
- Title: Create your message subject line
- Description: Write your main message content
- Button name: Name your options list
- List items: Define the customer selection options
- Apply message settings:
- Frequency policy: Select your relevant frequency policy
- Consent: Choose the appropriate consent category

Configure message 3
Follow the same configuration process as Message 2, customizing the content and settings for your third preference-gathering message.
Update trigger keywords
After configuring your message content, update the event triggers to match your response options:
- Access trigger configuration: Double-click the On Event trigger for Message 2
- Remove default keywords: Delete the placeholder responses ('response 1', 'response 2', 'response 3')

- Add your keywords: Input the actual response text from Message 1
- Repeat for subsequent messages: Update triggers for Messages 3 and 4 to match their respective previous message responses
Set up product recommendation messages
Configure recommendation content
- Access recommendation node: Double-click the Product Recommendation #1 node
- Configure message content:
- Sender: Select your RCS integration
- Message: Write your recommendation message and include the product link
- Images: Contact your customer success manager if you want to include product images (requires additional configuration)
- Apply message settings:
- Frequency policy: Select your relevant frequency policy
- Consent: Choose the appropriate consent category
Connect segments to recommendations
- Link to customer segments: Connect your recommendation node to the relevant customer segment within the segmentation node
- Create additional recommendations:
- Select your configured node and click the 'duplicate' icon
- Update the message content and settings for each unique customer segment
- Continue until all segments have corresponding recommendation messages
Configure customer segmentation
The use case includes two types of segmentations that work together to deliver personalized recommendations:
Customer segmentations
The use case creates three primary customer segmentations that encompass all possible response combinations:
- Initial Response 1: Customers who selected the first option in Message 1
- Initial Response 2: Customers who selected the second option in Message 1
- Initial Response 3: Customers who selected the third option in Message 1
Each primary segmentation contains multiple sub-segments representing every possible combination of answers across all three questions (for example: 1,1,1 or 2,4,3).

Event segmentations
Event segmentations manage the keyword logic centrally, making updates more efficient. These control what responses the customer segmentations look for:
- Initial Message Response (RCS): Defines keywords for Message 1 responses
- 2nd Message Response (RCS): Defines keywords for Message 2 responses
- 3rd Message Response (RCS): Defines keywords for Message 3 responses
Update segmentation keywords
To customize the segmentation for your responses, you only need to update the event segmentations:
- Access event segmentations: Navigate to Data Manager > Definitions > Event Segmentation
- Update initial message responses: Select Initial Message Response (RCS) event segmentation
- Modify response keywords: For each Response option, update the message field to match your actual response text

- Update subsequent messages: Repeat this process for 2nd Message Response (RCS) and 3rd Message Response (RCS) segmentations
Important
You can adjust customer segmentation names ("Initial Response...") but never change event segmentation names ("Initial Message Response").
Other resources
For additional RCS implementation guidance:
Updated about 2 hours ago