A business workflow is a defined path that moves a piece of work from one person or team to the next, with a clear owner at every step and a time limit on each handoff. Most automation advice focuses on messages to customers. The costlier gaps in a 10 to 250 person firm are usually internal: the enquiry nobody picked up, the deal handed to the wrong person, the request that waited a week for a reply. This article answers how to build a business workflow that routes work between people, using the handoff of a qualified enquiry to a salesperson as the worked case on the levelpartner.ai platform.
Why internal handoffs are where work gets lost
When a customer message goes unanswered, someone usually notices. When a task sits between two colleagues, each assumes the other has it. The enquiry is logged, marked as qualified, and then nobody owns it. A week later the prospect has signed with someone else and nobody can say quite when the ball was dropped.
A business workflow fixes this by making three things explicit: who owns the work now, how long they have, and what happens if the time runs out. Those three rules do more for a stalled pipeline than another email sequence.
The parts of a handoff workflow
Every handoff has a trigger, the event that says the work is ready to move. It has an assignment rule, which decides who receives it. It has a deadline, the time by which the receiver must act. And it has an escalation, what happens if the deadline passes.
Get all four written before you build. "Qualified enquiries go to sales" is a wish. "Qualified enquiries go to the next available consultant in the region, who must call within four working hours, or the sales lead is alerted" is a business workflow.
Before you start
- Agree what makes an enquiry qualified and how that is recorded, such as a stage or a tag.
- List the people who can receive work, grouped by team, region or speciality.
- Decide the deadline for first contact and who is alerted if it is missed.
- Make sure each receiver has a staff user and has turned on notifications.
- Have a test contact you can move through the stages yourself.
How to set it up
- Go to Automation, click Workflows, then "+ Create Workflow" and "+ Start from scratch".
- Click "Add New Trigger" and select the stage change into your qualified stage.
- Click the "+" icon and select "If / Else" to branch by region or service line.
- Inside each branch, click the "+" icon and select "Assign To User".
- Enter an Action Name, then choose one or more users from the dropdown.
- Click "+" and select "Send Internal Notification" to alert the assigned user.
- Click "+", select "Wait", choose "A user to reply" and toggle Timeout on.
- Set the timeout to your first-contact deadline.
- On the timeout branch, add an internal notification to the team lead.
- Click "Test Workflow", select your test contact and click "Run Test".
- Click "Save", then switch the Draft/Publish toggle to Publish once every branch assigns correctly.
Choosing the assignment rule
Round-robin spreads work evenly and suits teams where anyone can take any enquiry. Routing by region or speciality suits firms where the right person matters more than speed, such as a consultancy with distinct practices. A mix is common: route by speciality first, then round-robin within the team.
Avoid assigning by whoever is fastest to click. It rewards the people who watch notifications, not the people who close, and it leaves quieter team members with nothing.
Say valuation requests arrive at about 80 a month across three branches. Each routes to its branch by postcode, then round-robin among that branch's valuers, with three working hours allowed for a first call. Now suppose 6 requests in a month escalate to the branch manager and all six belong to one valuer. That pattern points at one person's setup, such as notifications switched off, not at the workflow. The numbers are there for illustration.
What a business workflow is for in a stalled firm
When revenue has flattened, the instinct is to buy more leads. Before you do, check what happens to the ones you already get. A firm that loses a share of qualified enquiries between the marketing team and the sales team has a handoff problem, and more leads will fall through the same gap. The routing workflow closes it with no extra spend.
The same pattern applies beyond sales. A won deal handed from sales to delivery follows the same structure, which the guide to automating customer onboarding builds out in full. Customer-facing workflows, such as the first reply to an enquiry, are covered in setting up an automated text response.
What it replaces and the weekly time
It replaces the shared inbox where the team lead assigns enquiries by hand each morning, and the weekly meeting where people discover what was missed. The team lead's weekly time moves from assigning work to reviewing the escalations, which are the real exceptions. Expect around twenty minutes a week once the workflow is settled.
The mistake most people make
Setting a deadline the team cannot meet. If consultants spend whole days in client meetings, a one-hour deadline will escalate constantly and the alerts will be ignored within a fortnight. Set the deadline from how people actually work, then tighten it once the habit forms.
When not to use it
If one person handles every enquiry, routing adds nothing. Use a simple reminder instead. And if you have not agreed what qualified means, the trigger will fire on the wrong records. Settle the definition first.
For linking several handoffs into a longer chain, see workflow process automation. Drawing the handoffs before you build them, as described in the guide to mapping a visual workflow, often exposes the missing owner straight away.
Troubleshooting
Work goes to someone on holiday. Round-robin does not know who is away. Remove absent users from the distribution while they are off, or add a branch that checks an availability field.
Escalations fire after the work was done. The wait is listening on the wrong channel. If your consultants phone rather than text, the reply they send never reaches the step that is watching for it, so match the channel to how your team really makes first contact.
The same enquiry is assigned twice. The opportunity entered the qualified stage twice. Turn off re-entry, or add a condition that skips records already assigned.
One person gets most of the work. A routing branch catches more records than intended. Check the branch conditions and the order they run in.
Frequently asked questions
What is the difference between a business workflow and a business process?
The process is the agreed way work should be done. The workflow is the running version of it, with assignments, deadlines and escalations applied automatically.
Can the workflow reassign work automatically?
Yes, after an escalation. Many firms prefer the team lead to decide, so the workflow alerts them and they reassign by hand.
Should deadlines use working hours?
Yes, for internal handoffs. A deadline that runs overnight will escalate before anyone has had a fair chance to act.
How many handoff workflows does a firm need?
Usually one for each point where work changes team: marketing to sales, sales to delivery, delivery to account management.