A lead comes in and what should happen next depends on the answer. Emergency or not. Big job or small. Ready this week, or someone who found you at midnight and is nine months out. This is the conditional logic, scoring and routing that makes the next step depend on the answer instead of on somebody being awake to read it.
Same business, same form, same three questions on it. What happens after someone hits send is where a workflow stops being a straight line. Pick an answer and follow it down.
Quote request submitted at 11:40pm
How soon do you need this?
Every lead leaves a trail before anyone speaks to them. What they picked, what they opened, how fast they came back, whether they went quiet for a month. Scoring is just deciding in advance what each of those is worth, so the list sorts itself instead of getting worked top to bottom.
The strongest signal on the form, because it is the one people only choose when it is true.
Anyone with a date in their head has already moved past whether and on to when.
One visit is curiosity. A return visit inside the week is somebody comparing you to two other names.
Reopening a number usually means it is being shown to somebody else in the house.
Even three words. A reply moves someone out of the pile and into a conversation.
Not a dead lead. Just one that should stop taking up room at the top of somebody's day.
Better to know at the form than after a call, and better to send them somewhere useful than to nowhere.
Stays in the slow lane. Gets useful email, costs no one any time, and keeps scoring quietly in the background.
Surfaces on the board with a booking link already sent. Worth a follow-up, not worth interrupting a job for.
Somebody's phone goes off. This is the one you want called back inside the hour, and the workflow is the thing that knows it.
The numbers are yours, not ours. We start with what your best jobs had in common, then move them once you have watched a few weeks of real leads land where they should have.
Most businesses do not have one system. They have six, bought at different times for different reasons, and a person in the middle retyping the same name into all of them. That person is the integration. This replaces the retyping.
Named, tagged, scored and assigned on arrival, so nobody opens a record and finds three fields and a first name.
The booking link points at the right person's real availability, and the booking writes itself back onto the record it came from.
Confirmation, reminder the day before, a nudge the morning of. Reschedules rewrite the whole chain instead of leaving a stale reminder to fire anyway.
Paid moves the record forward, stops the chase sequence, and lands in the books without a second entry by hand.
Goes out at the hour people are most likely to answer, and only to the customers whose job went well.
The thing with no integrations and no plans for any. If it can export a file or answer a request, it can be made to hand things over.
Not a diagram of what could be built. The logic itself, running, with the failure cases already thought through.
Every answer someone can give, and what happens after each one, written out plainly enough that you can say no to a path before it exists.
Built from what your good work had in common, not from a template, and adjustable once real leads have run through it for a few weeks.
By job type, area, value, language, whoever is on call tonight. Round-robin is one option among several, not the only one on the shelf.
What happens when the first message fails, the first person does not answer, or the other system is down. The quiet part that decides whether any of it survives a bad Tuesday.
When something goes to the wrong person, you can see which answer sent it there and change that one rule, instead of guessing at a black box.
Written in your words, not in software terms, so a new hire can follow what happens and why without booking a call to find out.
The building is the short part. Deciding what should happen, and what should happen when that fails, is the work.
We take a lead that came in last month and trace where it went, hand-off by hand-off. The gaps show up on their own, and they are never where anyone guessed.
Every answer, every path, every ending, on one page you can read before a line of it exists. This is where paths get cut, which is cheaper here than later.
Fake leads down every branch, including the awkward ones. Blank fields, two submissions in a row, an answer nobody expected, a tool that does not respond.
Real leads, real routing, scores adjusted where they were wrong. Something always needs moving once it meets the actual mix of people who fill in your form.
Automations is the straight line. Form goes here, email goes there, reminder fires at nine. It is what every business needs and can picture without a diagram. This page is what happens when the next step depends on the answer, when leads need sorting rather than serving, when two systems have to agree, or when the first attempt fails and something has to try again. Automations is the entry point. This is the ceiling.
Ask a different question. Does the right next step depend on the answer someone gives, and is a person currently reading every enquiry to decide that? If yes, the branching already exists. It is just running inside somebody's head, only during working hours, and only while they are paying attention.
It will. A tool goes down, a message bounces, someone answers in a way nobody planned for. That is why retries, escalation and fallbacks get built at the same time as the happy path, and why there is a log you can read. Workflows that assume nothing ever fails are the ones that fail quietly for weeks.
Yes for the parts you should touch. Message wording, timings, score values, who gets what. The branching structure is the part where a small change has consequences three steps away, so that one comes to us, and we would rather you ask than guess.
It replaces the reading and the retyping. Nobody's best hour is spent deciding which pile an enquiry goes in and then copying a name between two systems. The calls, the quoting and the judgment stay with people, who now get to spend the day on the leads worth spending it on.
Book a call and describe the hand-off that always goes wrong. We will tell you on the call whether it needs branching logic or just a straight line done properly.
Built to keep running on the days nobody is watching