Create automated journeys via SMS, email and RCS

Define the entry point, organise queues and conditions, and trigger the most appropriate message at each stage of the journey

From a single message to a journey that evolves over time

A Journey is an automated sequence of steps that starts with an event or an audience and proceeds according to defined rules.

It can wait until a specified time, check a condition and trigger an SMS, email or RCS message.

In this way, each message becomes part of a journey, rather than a standalone activity.

Map out the logic of the journey, step by step

It specifies who or what event initiates the process.

It specifies how long must elapse before the next step.

It checks a piece of data or a behaviour and directs the flow.

Trigger a notification or the scheduled action.

It allows you to observe what is happening and improve your subsequent reasoning.

Build and monitor the route in a single space

The visual editor helps you organise the sequence and see how each step leads to the next. You can set up the logic of the journey, configure the messages and check the flow before activation, without losing sight of the bigger picture.

Create the course structure

Set up times, conditions and notifications.

Check the steps before activation.

Amend the Journey when objectives or processes change.

Choose the channel based on the stage of the customer journey

SMS, email and RCS can play different roles within the same customer journey. The channel chosen depends on the content, the urgency, the level of interaction required and the data available. The Journey Builder allows you to organise communications within the same framework, whilst maintaining a clear link between one step and the next.

SMS

A confirmation, notice or reminder that requires immediate attention.

Discover more

Email

Detailed content, onboarding or follow-up.

Discover more

RCS

A visual and interactive message with integrated actions.

Discover more

Start with a real moment in the relationship

Welcome

Registration
welcome message
waiting
next content.

Reminder

Booking
confirmation
pending
reminder
follow-up.

Recovery

Incomplete interaction
Pending
Verification
New message.

After-sales

Purchase
useful information
waiting
request for feedback.

Anniversary

Date or event
dedicated message
proposal or next step.

Riattivazione

Lack of interaction
segment
communication
verification of results.

Automate the repetitive tasks. Stay in control of what changes

Activate Journeys using data and events from your systems

Journeys become more useful when they interact with CRM systems, e-commerce platforms, business management systems and other applications. Through the available integrations, APIs and webhooks, data and events can contribute to the start of the journey and to the rules governing its stages.

Journey Builder is part of the inTouch ecosystem

Journey Builder works in conjunction with contact and audience management, content editors, SMS, email and RCS channels, analytics and inTouch integrations. The platform is developed by rdcom and backed by in-house expertise in business messaging, integration and delivery.

Frequently asked questions

What is inTouch’s Journey Builder?

This is inTouch’s visual editor for creating automated journeys consisting of entry points, delays, conditions and actions. Journeys can include SMS, email and RCS messages.

What is the difference between a campaign and a journey?

A campaign is a configured mailing targeted at an audience. A journey is an automated sequence of steps that can unfold over time and change based on the rules, data and events available.

Which channels can I use in Journeys?

Journey Builder allows you to include SMS, email and RCS communications. Features and configurations depend on the channel and the use case.

What can a Journey start with?

A Journey can start from an audience or from an event specified in the configuration. The available entry methods must be checked based on the data and integrations used.

Can I link a Journey to the CRM or the e-commerce platform?

Yes. inTouch can connect to CRM, e-commerce and other applications via APIs, webhooks and available integrations, so that data and events can contribute to the activation and logic of the customer journey.

Do you need to write code to create a Journey?

The workflow is built in the visual editor. Additions or more complex scenarios may require technical work, but configuring the sequence does not require writing code.

What sort of Journeys can I create?

Some of the most common examples include welcome messages, onboarding, reminders, post-purchase communications, anniversary messages and reactivation. Feasibility depends on the data, events and channels available.

How can I view the Journey Builder?

You can request a demo of inTouch to see the editor and discuss an initial use case with the rdcom team.