Trigger
Someone writes. A comment appears under a post. A promise falls due. Or simply nine in the morning, because that’s when you said.
ProductAutomation Studio
Set the path once, then let it run
A journey waits for something to happen, holds until the hour you chose, then sends the reply you’d have written anyway. Campaigns and follow-ups come out of the same four blocks. Start typing into the thread yourself and the journey goes quiet until you’re done.
What it does
What a journey is made of
Condition
A gate — the step goes through for one tag, one stage of the deal, or when Conversation Lens has read the last message as an objection about price.
Wait
An hour, or Monday morning, or the day their budget opens. This is the part everyone skips, and it’s the part that decides whether your message reads as attention or as pestering. Something that arrives at four in the morning gets remembered for the wrong reason.
Action
Send the reply you wrote in advance, or ask an agent to write a fresh one against what this person actually said. The same step can tag the card, open a task, or pull a colleague into the thread.
How it works
How it works in practice
Sketch it out
You put the steps in order and see the whole shape on one screen, with no branch hiding behind another.
Decide how far each step goes
Each step carries its own setting — advise, prepare, or act. A step that could embarrass you stops and waits for you, even inside a journey that otherwise runs on its own.
Check without sending
Pull the draft apart, rebuild it, sit on it for a week — a journey in draft sends nothing to anybody, so there’s no such thing as a rehearsal that reaches a customer.
Switch it on
Dialog Man checks the boring things first. Is the channel connected, did this person agree to be written to, can the step even run.
Watch it work
Open any run and read it line by line. When something breaks, the reason sits right there in plain words instead of an error code. A week later the behavior of the journey is still explainable, and that’s the only reason it’s safe to leave one running.
What is guaranteed
A journey holds only the permissions you handed it
It doesn’t widen its own rights, and it can’t reach a channel or a person you never connected it to. It fires where you said, at the level you chose, and it gives the conversation back to a person the moment the situation asks for one.
Questions
What matters about journeys
- Could a journey answer the wrong person?
- It replies inside the same thread the trigger fired in, and there’s no road from that thread to anybody else.
- Can a journey write to someone who never agreed to hear from you?
- No. Consent is checked at the moment the step runs rather than the moment you built it. Somebody who withdrew it yesterday is out of reach today, and you don’t have to go back and edit the journey for that to be true.
- Can I take a conversation back from an agent?
- Any second. Open the thread, start typing, and the journey goes quiet.
- What if the channel drops mid-run?
- The run stops and says so, in words, in its own history. You see which step it reached and what it was about to do, and you can finish that conversation by hand.
- How fast can I switch a journey off?
- New runs stop starting the same second you switch it off. Anything already in flight stays on screen with its status, so nothing disappears while you’re deciding what to do about it.
Automation Studio
Take back the hour that goes into one repeated reply
Start with the question you answer ten times a week. Switch it on at Prepare, read what it writes for a few days, and move it to Act once you stop correcting it.