Why drips lose clients
Generic drips repeat the same template to every lead and keep sending after the person has replied, opted out or signed a contract.
The agent cannot see which drips a contact is in, or stop one without stopping everything.
Built-in and custom drips
Start with built-in drips such as Speed to Lead, Long-Term Hold, Cold Re-engage and Past Client Stay-in-Touch, or install one from the template library or describe one and let Raven draft it. Each step is an email or text with a goal, and Raven writes the message for the lead when it sends.
- Built-in drips for new leads, long-term nurture, re-engagement and past clients
- Custom drips from a template library or drafted by Raven
- Several drips on one contact, each with its own steps
- Send a test of any step to yourself before it reaches a client
It stops itself. A sequence that keeps sending after someone answers is worse than never having sent at all.
Workflows that act on events
Workflows are rules that run when something happens, such as a transaction changing stage. A workflow can send an email to the client or the agent, or post a notification, and a new workflow is saved off until you turn it on.
- Triggers on transaction and contact events
- Email and notification actions with fields filled from the record
- Saved off until you turn it on
The rendering is part of the connection, not something you build on the far side of it.
Guards on every automated send
Automated texts and emails go out only in the client's own hours, in their time zone. A reply pauses the contact's drips, a contact can be paused or a single drip paused, vendors and other non-client contact types can be left out by type, and lead drips stop while the person is a client on a transaction under contract.
- Send windows in the client's time zone, texts never outside 8am to 9pm
- A reply holds the contact's steps until the agent resumes
- Pause one drip, or all automations for a contact
- Contact types such as vendors left out of automations by default
- Lead drips stop while the client is under contract
This one is held because they answered — so the sequence stops and the thread becomes a conversation instead.
Frequently asked questions
Does every lead get the same drip message?
No. Each drip step is a goal, and Raven writes the email or text for that lead at the time it sends.
Can I build my own drips?
Yes. Install a drip from the template library, or describe what you want and Raven drafts it. A drip is checked before it is saved so it can actually run.
When are automated messages sent?
Inside a send window in the client's own time zone. Texts are never sent outside 8am to 9pm, and you can set your own window for emails and texts.
What stops a drip?
A reply from the contact holds their steps, you can pause one drip or every automation for a contact, contact types such as vendors are left out by default, and lead drips stop while the person is a client under contract.
Can I see what a drip sends before it goes out?
Yes. Send a test of any step to your own email address. The test is composed the same way the live message is, and it is never counted as a send.