Engage Automation
Draw the conversation once. It runs for everyone.
Menus, questions, bookings and hand-overs, drawn on a canvas and tested before they go live — plus follow-ups and reminders that send themselves.
- Visual builder, no code
- Tested before it goes live
- Follow-ups that stop on reply
- Started by your systems
The builder
Everything a journey needs, from a menu.
Pick a step, write its words, draw a line to the next. Connect checks that every path ends somewhere before it lets you publish.
Starts
A first message, a keyword, a button tapped, or a signal from your own system.
Buttons and menus
Give customers choices to tap, each leading somewhere different.
Questions
Ask for a name, an order number or a date — and keep the answer on their contact.
Decisions
Go one way or another based on what the customer said or who they are.
Bookings
Offer free slots and book an appointment or a callback.
Your systems
Look something up or record something in your own system mid-conversation.
Hand to a person
End with your team, who see everything the customer chose.
A built-in tester
Walk through the journey as a customer would, before anybody else can.
Versions
Publishing is deliberate; earlier versions are kept to go back to.
Follow-ups
Every enquiry chased — until they answer.
Set a sequence once — the brochure today, a nudge in two days, the quote on day five — and every new enquiry gets it, without anyone keeping a list.
- A series of messages, days apart
- Stops as soon as they reply
- Started from a chat, a lead or your system
- Never sent to people who opted out
Scheduled and recurring
The messages you send every month, sent for you.
Payment reminders on the first, tomorrow’s appointments every evening, the monthly newsletter — set them once and get on with your day.
- Daily, weekly or monthly
- Lists read fresh each time
- Change or cancel before it goes
- On SMS, WhatsApp, RCS or email
Getting started
Your first journey, in an afternoon.
Sketch it
Start from your greeting and the questions customers ask most.
Try it
Test it as a customer would, and adjust the words.
Publish it
It answers every customer from now on — and you can change it any time.
Checked before publishing: no dead ends.
Drafts save as you work.
Loops back to the menu, never in circles.
Do we need a developer to build a journey?
No. You draw it on a canvas: messages, buttons, questions and hand-overs, joined by lines. If you can sketch it on paper, you can build it.
Can we test a journey before customers see it?
Yes. Try it in the built-in tester exactly as a customer would, then publish it when you are happy. Earlier versions are kept.
What happens when a person replies in the middle of a journey?
The journey steps aside for that conversation, so a customer is never answered by a menu and a person at once.
Can a follow-up stop when the customer answers?
Yes. Follow-up sequences stop by themselves as soon as the customer replies, so nobody is chased after they have answered.
Can our own systems start a journey?
Yes. A new order, a payment due or a form filled on your site can start the right journey for that customer.
Let the routine conversations run themselves.
Existing customers can log in now. New to Connect? We set your account up with you, service by service, and you start where it helps most.