Quick Start
What is respond.io?
Setting Up an Account
Connecting Channels
Inviting Your Teammates
Getting Contacts to Message You
Automated Welcome and Away Messages
Responding to Messages
Glossary of Terms
Channels
WhatsApp Business API Quick Start
Getting Ready for Inbound Conversations
Getting Ready for Promotional Messaging
WhatsApp Official Business Account (Green Tick)
Grow your WhatsApp Audience by Maximizing Entry Points
Get WhatsApp API Account for Government Agencies
Meta Business Verification
WhatsApp Message Templates
WhatsApp Pricing
WhatsApp Business API Channel Configuration
WhatsApp Messaging Limits
Change Your WhatsApp Business Display Name
Migrating from WhatsApp Personal or WhatsApp Business App
Phone Number Migration to respond.io WhatsApp Business API
Turn-off WhatsApp Number Two-Step Verification
WhatsApp Cloud API
360dialog WhatsApp
Twilio WhatsApp
MessageBird WhatsApp
Vonage WhatsApp
Phone Number Migration to WhatsApp Cloud API
Facebook Messenger
Facebook Messenger Overview
Facebook Messenger Quick Start
Facebook Chat Plugin
Facebook Private Replies
Facebook Message Tag
LINE
Viber
Telegram
Google Business Messages
Website Chat Widget
Website Chat Widget Overview
Website Chat Widget Quick Start
Install Website Chat Widget on WordPress
Install Website Chat Widget on Shopify
Install Website Chat Widget on Wix
Install Website Chat Widget on Joomla
Install Website Chat Widget on Squarespace
SMS
Custom Channel
Channels Overview
Product
Dashboard & Reporting
Dashboard
Reports Overview
Reports: Conversations
Reports: Responses
Reports: Resolutions
Reports: Messages
Reports: Contacts
Reports: Assignments
Reports: Leaderboard
Reports: Users
Reports: Broadcasts
Messages
Contacts
Contacts Overview
Contact Details
Merge Suggestions
Contact Activity
Contact Channels
Contact Import
Segments
Broadcasts Module
Workflows
Workflows Overview
Workflow Triggers
Workflow Steps Overview
Step: Send a Message
Step: Ask a Question
Step: Assign To
Step: Branch
Step: Update Contact Tag
Step: Update Contact Field
Step: Open Conversation
Step: Close Conversation
Step: Add Comment
Step: Jump To
Step: Wait
Step: Date & Time
Step: HTTP Request
Step: Add Google Sheets Row
Dynamic Variables
Workspace Settings
Managing a Workspace
Workspace Settings: General
Workspace Settings: Users
Workspace Settings: Teams
Workspace Settings: Channels
Workspace Settings: Contact Fields
Workspace Settings: Integrations
Workspace Settings: Closing Notes
Workspace Settings: Snippets
Workspace Settings: Files
Workspace Settings: Data Export
Workspace Settings: Data Import
Workspace Setting: Respond AI
Workspace Settings: Growth Widgets
Organization Settings
Organization Overview
Organization Settings: General
Organization Settings: Users
Organization Settings: Workspaces
Organization Settings: WhatsApp Fees
Organization Settings: Billing & Usage
User Account
Mobile App
Installing respond.io Mobile App
Messaging From Your Mobile
Managing Notifications On Your Mobile
Configuring Mobile App Settings
Help Menu
Handling Inbound Conversations
Managing Spam
Create Automated Welcome and Away Messages
Get Contacts’ Consent for Personal Data Collection
Create Automated Chat Menus
Collect Contacts’ Emails and Phone Numbers
Route Contacts by Shifts
Route Contacts by Team Functions
Route New & Returning Contacts
Route VIP Contacts
Assignment Strategy: Automatic Contact Distribution & Load Balancing
Assignment Strategy: Unassign Agents after Conversations Closed
Support Use Cases
Inbound Support: Identify Contacts by Email and Phone Number
Inbound Support: Enrich Customer Data from a CRM or other Business Software
Inbound Support: Route Customers to the Right Team Automatically
Inbound Support: Auto-Assign Customers to a Team or Dedicated Agent
Send Outbound Support Messages
Support: Closing Conversations
Supervising Your Support Agents
Reporting for Support
Send CSAT to Customer and Save Data in Google Sheets or CRMs
Sales Use Cases
Inbound Sales: Collect Leads' Email and Phone Number
Inbound Sales: Enrich Contact Data and Qualify Leads
Inbound Sales: Routing Leads
Inbound Sales: Auto-Assign Leads to Sales Agents
Sending Outbound Sales Messages
Track Productivity by Closing Conversations
Supervising Sales Agents
Reporting for Sales
Broadcasts Use Cases
Sending a Simple Broadcast
Start a Workflow Based on Broadcast Response
Troubleshooting a Failed Broadcast
Integrations
Dialogflow
Dialogflow Overview
Dialogflow: Connecting to Dialogflow
Dialogflow: Creating a Chatbot
Dialogflow: Managing Intents
Dialogflow: Parameters
Dialogflow: Events
Dialogflow: Response Templates
Dialogflow: Custom Payloads
Dialogflow: Fulfillment Webhook Request
E-Commerce & CRM Integrations
E-Commerce Integration: Shopify
E-Commerce Integration: BigCommerce
E-Commerce Integration: WooCommerce
E-Commerce Integration: Magento
CRM Integration: HubSpot
CRM Integration: Salesforce
CRM Integration: Pipedrive
CRM Integration: ActiveCampaign
Zapier
Make (formerly Integromat)
Developer API
Webhooks
Partnership
We love to hear from you!
Table of Contents
- Home
- Handling Inbound Conversations
- Route VIP Contacts
Route VIP Contacts
Updated
by Joshua Lim
Benefits of Routing VIP Contacts
- Treating VIP Contacts differently ensures a more personalized and expedited service. This can lead to enhanced customer satisfaction and loyalty.
- Having a different route for VIP contacts allows businesses to efficiently allocate resources, ensuring that highly skilled agents cater to VIP customers’ unique needs.
Workflow Setup
Learn how to use the Workflow Template to identify and route VIP Contacts.
- Check Contact for an existing email
- If Contact has an Email: Get Contact Data and Route VIP Contact
- If Contact has no Email: Ask for Email and Route Contact
Check Contact for an Existing Email
In the Workflows module, click + Add Workflow > Click Routing: VIP Contacts > Click Use Template.

1. Trigger: The Workflow starts when a conversation is opened by a Contact.
2. Have Email Already?: This Branch step checks if the Contact has an email or not in the Contact’s Email Address field.
If Contact has an Email: Get Contact Data and Route VIP Contact

If the Contact has an Email in the Contact’s Email Address field, the Contact will be routed to the Have Email branch. In this branch, the Contact’s data will be retrieved from an external CRM or data warehouse via a HTTP request step to identify if the Contact is a VIP. If the Contact is a VIP, the Contact will be routed to the VIP Contact branch.
3. Get Contact Data from CRM or Data Warehouse: This is an HTTP request step that will retrieve the Contact’s details from a data warehouse such as a CRM. Click on the Workflow step to configure the Method, URL, and Header to retrieve the Contact’s data.
In the Response Mapping section, map the $.customerType(name of key from the response based on your CRM or Data Warehouse) key to store its value as a variable named CustomerType. Learn how to configure HTTP request step here or get a developer to assist with this configuration.

4. Route VIP & Regular Contact: In this Branch step, the Contact will be routed based on the CustomerType variable. If the CustomerType is VIP, it will be routed to the VIP Contact branch. If the CustomerType is not VIP, it will be routed to the Regular Contact branch.
Next Steps after Routing Contacts
Here are steps to consider after Routing VIP and Regular Contacts:
- VIP Contact: Add an Assign To step to assign to a specific user or dedicated agent to attend to the VIP Contact.
- Regular Contact: Add an Assign to step to assign to a user in a team or Workspace with an assignment logic that fits your business needs. Learn more about Assignment Strategy: Contact Distribution & Load Balancing.
If Contact has no Email: Ask For Email and Route Contact

If the Contact does not have an Email in the Contact’s Email Address field, the Contact will be routed to the No Email branch. In this branch, the Contact will be prompted with a question to ask for their email. Once you have received the Contact’s email, a Success Message will be automatically sent and the Workflow will Jump to Get Contact Data where the Contact’s data will be retrieved from an external CRM or data warehouse via a HTTP request step to identify if the Contact is a VIP. If the Contact is a VIP, the Contact will be routed to the VIP Contact branch.
5. Ask for Email: Ask for the Contact’s email with the Ask a Question step.
6. The Ask for Email step can have a Success or Failure outcome:
- Success Message (Success): Once you have received the Contact’s email, the automation will send a Success Message to the Contact.
- Jump to Ask for Email (Failure: Invalid): If the Contact sent an invalid response to the Ask for Email question, the automation will jump back to the Ask for Email step up to 3 times. By the 4th time, if the response is still invalid, you may consider routing to an agent or a manager to manage this Contact.
7. Jump to Get Contact Data: After sending a Success Message, the Workflow will continue by getting Contact’s data and identifying if the Contact is a VIP using a Jump to step.
Feeling stuck? Do not fear.
Need assistance? Contact us for support. Help is here!This is the text block that will appear when the button is clicked.
Route New & Returning Contacts
Assignment Strategy: Automatic Contact Distribution & Load Balancing
Related Articles
Step: Branch
Learn about the configuration, best practices and use cases when implementing the Branch Step.
Step: HTTP Request
Learn about the configuration, best practices and use cases for implementing the HTTP Request Step.
Workflows Overview
Learn how to view, set up and manage Workflows automation.