Without a route
Waiting for Monday.
The request sits in a shared inbox until someone checks it.
Leads & Automation
Give each enquiry a clear next step.
Connect the tools you already use so your team can see what came in, who owns it and what happens next.
Renovation quote request
- Received
- Friday · 5:42 pm
- Source
- Website quote form
- Owner
- Estimates team
- Next action
- Review brief and call back
Ready for review
The handover
Where enquiries go missing.
The hardest part is often what happens between the tools your team already uses.
Nobody owns the request.
The enquiry reaches a shared inbox. Everyone can see it, but nobody knows who should pick it up.
The details don’t travel.
The customer’s message is in one tool, the quote in another and the latest update in a chat.
The next step relies on memory.
A proposal goes out. A busy week later, nobody is sure whether anyone followed up.
One enquiry. Two weekends.
Compare two ways the same Friday enquiry could reach Monday. These are fictional scenarios.
Friday · 5:42 pm A homeowner requests a renovation quote.
With an agreed route
Monday has a next step.
Log the scope and assign a discovery task to the estimates team.
Next: Review the brief before calling the homeowner.
LeadOS product preview
Make the handover visible.
Automation Studio shows how a rule can turn an enquiry into a task for the right team. This capture uses sample data.
A new enquiry starts this workflow.
Follow-up workflow
Give the proposal a next step, too.
When a stage changes, this sample rule checks for an open proposal, waits a day and creates an internal follow-up task. Otherwise, it records a stage review.
Connect what you already use.
We check what each tool supports before agreeing where information should go and who can see it.
- Where it startsForms and inboxes
- Agree which requests to capture and which details are needed.
- Where it livesContact and sales records
- Keep the enquiry, its owner and its current status together.
- Where it goes nextTasks and calendars
- Give someone a next action and a place to see it.
See how the enquiry starts.
Working concept demos for fictional businesses. Each illustrates a different way to collect a request.
Kestrel Build
A guided quote form collects details about a building project.
Wexley
A booking form asks for the job details and preferred timing.
Rankwell
An audit request gives the visitor a clear first step.
Start with one workflow.
Three steps from the first conversation to a handover your team can use.
Map one handover
Show us where enquiries arrive, what your team does with them and where things get stuck.
Agree the route
Choose where details go, who owns the next step and what should happen in unusual cases.
Test before handover
Walk through sample requests together, including duplicates, missing details and failed connections.
Before we start.
Can we keep our current tools?
Where they support a suitable connection, yes. We check access, limits and subscription requirements before agreeing the scope.
Can we start with one workflow?
Yes. A single handover, such as assigning new quote requests, is a practical starting point.
Does the preview send follow-ups?
The LeadOS preview shows rules for internal tasks and notifications using sample data. Customer messaging is a separate integration that needs its own scope and checks.
What affects the quote?
The number of tools and steps, the state of your data, and how exceptions need to be handled all affect the work.