Sales & pipeline
Answering a new lead in ninety seconds
Because the one who replies first usually wins
Speed to lead is the least glamorous and most reliable finding in sales research. It is also almost impossible to hit consistently with people, because people are in meetings.
- Fires on a new contact, from any source
- Reaches out before the lead has closed the tab
- Remembers anything you have dealt with them before
- Opens the deal so nothing is only in a thread
We reply in under an hourOr message us on WhatsApp
Today
A lead added at 14:10, noticed at 17:40, called at 11:00 the next day — by which point they have three quotes.
With this running
A conversation started within two minutes of the contact existing, while you are still their most recent thought.
Step by step
What actually happens
- Your team
A form submission, an import or a walk-in creates a contact.
- Assistant
Wakes on the event, reads the contact and checks whether it has notes about them from before.
- Assistant
Opens a deal and sends a first message that references how they came in.
- Customer
Replies within the hour, because the message arrived while they were still looking.
01 / 02
The trigger is an event, not a schedule
A run that checks for new leads every fifteen minutes averages seven and a half minutes of delay and looks like a robot. This starts when the contact is created — the same moment, whatever produced it: a website form, a CSV import, a colleague adding someone from a business card.
02 / 02
It knows if you have met before
Long-term memory means a returning enquiry does not get a cold opener. If there is a note from a conversation eight months ago, the assistant has it, and the first message reflects that — which is the difference between an automation and something that feels like the business remembering you.
How this is put together
The same building blocks every assistant is made of. Nothing here is bespoke to this scenario.
What starts it
Something changing in your CRM — A new contact is added — however it arrived
Where it runs
What it can do
- Looked up the contact
- Read the contact's extra fields
- Checked the pipelines
- Created a deal
- Replied
- Tagged the contact
- Checked what it remembered
What it uses
Every action above is a real capability, and every run keeps a record of which ones it used. How the engine holds this together →
More like this
Other things it does
The deals nobody followed up
Found every Monday, chased with your approval
Nobody decides to abandon a deal. It just stops being the most urgent thing, fourteen times in a row, and then it is too late to message without it being strange.
Learn moreWhen a deal is won, the handover starts itself
The welcome, the note and the next step, on the drag
The gap between winning and onboarding is where new customers form their opinion, and it is almost always the least designed part of the process because the person who won them has moved to the next deal.
Learn moreThe pipeline review nobody has time for
A written summary, on your desk, every Monday
Every sales manager intends to review the pipeline weekly. What actually happens is a glance at the board in the meeting, which surfaces the deals that are visible rather than the ones that are stuck.
Learn moreWhere this runs
The channels this scenario works on, and the industry module it belongs to.
Would this work for how you actually operate?
Tell us the scenario you have in mind. If it needs a building block we do not have, we would rather say so than sell you a demo.
We reply in under an hourOr message us on WhatsApp