Customer Journey Builder for SMS, WhatsApp and RCS: A Guide

Most Indian brands already send the right messages. The trouble is timing and sequence: the cart reminder goes out after the customer has bought elsewhere, the EMI nudge arrives the day after the due date, and the welcome series ignores whether the user has even logged in.

A customer journey builder fixes that by turning one-off campaigns into flows that react to what each customer does. This guide explains how journey builders work inside a CPaaS, how to design a journey for Indian channels and rules, and the mistakes that quietly break them.

What a customer journey builder actually does#

A journey builder is a visual canvas where you connect blocks into a flow. Each customer who meets the entry condition moves through the flow on their own clock.

Most builders share the same building blocks:

The exit block matters as much as the trigger. A journey without a clear exit keeps nudging people who have already converted, which wastes money and invites complaints.

Three journeys Indian teams build first#

Cart recovery for a D2C brand#

Trigger when a logged-in user leaves items in the cart. Wait a short while, then send a WhatsApp marketing template with the product and a "Complete order" button. If the customer does not open it, follow up later with an RCS card or a DLT-approved SMS, then exit as soon as an order is placed.

EMI and bill reminders for a lender or utility#

Trigger a few days before the due date. Send a utility reminder, check payment status before each later step, and escalate to a voice call only for customers who are still unpaid close to the deadline. Payment confirmation is the exit.

Onboarding for an app or fintech#

Trigger on sign-up. Branch on whether KYC is complete: those who finished get a "how to use" sequence, those who did not get a reminder with a deep link back to the KYC screen. Exit when KYC is complete or after the last step.

How to build a journey, step by step#

1. Pick one goal and one metric. "Recover abandoned carts" measured by orders placed from the journey, not "engage users".
2. Define the trigger event and the data it carries. The event from your app or CRM should include the customer's phone number, consent status, language and the fields your templates need (name, amount, product).
3. Map each step to a channel and a template category. Decide in advance which steps are marketing, utility or authentication. Our guide to WhatsApp template categories explains how Meta classifies each one.
4. Get templates approved before launch. WhatsApp templates need Meta approval and SMS templates need DLT registration. A journey that waits on approvals in production simply fails at that step.
5. Set waits in customer time, not system time. "Wait until 10 am" usually beats "wait 12 hours", which can land a message at midnight.
6. Add conditions before every follow-up. Check whether the customer has already acted. This one check prevents most of the annoying duplicate messages.
7. Configure fallback per step. Decide what happens if a rich message is not delivered and how long to wait before falling back.
8. Test with real numbers across operators. Run internal numbers on Jio, Airtel, Vi and BSNL, on Android and iPhone, through every branch.
9. Launch to a slice of your audience first. Compare against a holdout group so you know the journey caused the result.

Build compliance into the journey, not around it#

Indian messaging rules apply to every automated step, and a journey builder will happily send a non-compliant message thousands of times if you let it.

DLT templates and headers. TRAI's TCCCPR 2018 requires businesses sending bulk messages to use a registered content template and an assigned header, as MediaNama reported in its summary of the regulations. Every SMS step's text, including its variables, must match an approved DLT template. Our TRAI DLT registration guide walks through the process.

Registered telemarketers. In a February 2023 press release, TRAI directed access providers to ensure that all promotional messages go through registered telemarketers using approved headers and templates on the DLT platform.

The promotional time window. Under TCCCPR 2018, promotional SMS and calls are limited to 9 am to 9 pm IST, according to Exotel's developer documentation on the regulation. Any promotional step that could fire at night needs a "hold until 9 am" rule.

Consent and opt-outs. Store consent status with the customer record and check it at the trigger. An opt-out on any channel should exit the customer from every marketing journey, not just the one they replied to.

WhatsApp's 24-hour window. Meta's documentation states that a 24-hour customer service window opens when a user messages or calls you, and resets if they do so again before it expires. Inside that window you can send free-form replies; outside it, a journey step must use an approved template.

Choosing channels and fallbacks#

Each channel plays a different role in a journey:

• WhatsApp suits rich, two-way steps such as order updates, buttons and catalogues. See how it compares in WhatsApp Business API vs SMS.
• RCS shows branded cards, carousels and suggested replies in the phone's default messaging app. Our explainer on RCS Business Messaging in India covers when it fits.
• SMS reaches almost any phone and works as the fallback layer.
• Voice works for high-stakes, time-bound steps such as a final payment reminder.

A sensible default is "rich first, SMS second": try RCS or WhatsApp, wait for a delivery receipt, and send a DLT-approved SMS only if the first message fails. Make sure the fallback SMS carries the same offer and link, so the customer gets one consistent message rather than two different ones.

Mistakes to avoid#

• No suppression check. Sending "Complete your order" after the order is placed.
• Too many steps. Five reminders in two days reads as spam, whatever the channel.
• Ignoring language. Send templates in the language the customer uses in your app, and register those versions too.
• Variables that break templates. A long product name can push an SMS outside its approved DLT template and get it blocked.
• Measuring clicks only. Track the business outcome and the opt-out rate side by side.
• Never reviewing live journeys. Prices, offers and rules change; a journey left running for months often promotes something that no longer exists.

A quick checklist before you hit publish#

• Goal, metric and exit condition written down
• Every message step mapped to an approved template and category
• Consent and opt-out checked at entry
• Promotional steps held inside 9 am to 9 pm IST
• Conditions before every follow-up step
• Fallback rules and wait times set per step
• Tested on all major operators and both Android and iPhone
• Holdout group set up for measurement

Sources#

• MediaNama, "TRAI consultation paper reviews 2018 spam regulations" (2024): https://www.medianama.com/2024/09/223-trai-consultation-paper-review-2018-spamregulations/
• TRAI, Press Release No. 12/2023 on misuse of headers and message templates under TCCCPR-2018: https://cms.trai.gov.in/sites/default/files/2024-08/PR_No.12of2023.pdf
• TRAI, Press Release No. 11/2025, "TRAI Strengthens Consumer Protection with Amendments to TCCCPR, 2018": https://cms.trai.gov.in/sites/default/files/2025-02/PR_No.11of2025.pdf
• Exotel Developer Docs, "TCCCPR 2018": https://developer.exotel.com/docs/faqs/tcccpr-2018
• Meta for Developers, WhatsApp Business Platform, "Send messages" (customer service windows): https://developers.secure.facebook.com/documentation/business-messaging/whatsapp/messages/send-messages