Assigning the next response
How to route a new lead to the right person
By ByTomorrow · Published
Sending a notification to a group does not establish who will respond. A lead can sit untouched because everyone assumes somebody else has it, or receive competing replies from staff who all try to help.
Route the work to an accountable owner. This guide supplies a fillable routing table and a fictional example. It addresses assignment of an inquiry, separate from transferring a live phone call.
What needs attention
Where the process can go wrong
Several rules match at once
A request can be from an existing customer, concern a particular service and arrive outside normal hours. Without rule precedence, the workflow may assign conflicting owners.
Assignment is confused with acceptance
A field containing someone's name does not prove that person is available or has seen the request. Define what happens while work remains unacknowledged.
Practical worksheet
Use this with your own business details
Write one routing row per condition
Copy columns: rule order; matching facts; assigned role; named current responder; backup; expected acceptance window; escalation owner; evidence of acceptance. Use approved coverage information rather than a person's assumed availability.
Separate request types first
Example order for a fictional service business: existing-customer service request goes to the service team; a new in-scope inquiry goes to intake; an unclear request goes to the review queue. The actual order must reflect your business responsibilities.
Define a single owner
The assigned responder owns the next action until another person explicitly accepts it. Other staff may be notified without becoming competing owners. Record reassignment as an event with the reason and new owner.
Include a no-match path
If the required routing field is missing or contradictory, create a review task for a known queue. Do not choose a random salesperson or discard the inquiry because a branch did not match.
Make backup coverage explicit
For each normal owner, name the backup when absent and the person who maintains coverage. An escalation needs a trigger the business approves, such as an unaccepted task reaching its agreed review point. Do not invent a universal response deadline.
Use a fictional assignment example
An existing customer asks about an ongoing job through the general inquiry form. The existing-service rule takes precedence. The service coordinator accepts the task; the sales team receives no independent follow-up assignment. If the job cannot be identified, the coordinator asks for clarification.
Put it to work
Check the complete process
Inventory current intake routes
List the forms, phone requests and shared inboxes that can create the same kind of work.
Order the rules
Resolve overlapping conditions on paper. Include missing information and unavailable staff.
Test one example per branch
Have staff predict the owner before the workflow runs. Compare the actual task assignment with that prediction.
Test concurrent and repeat inquiries
Check whether the same person contacting twice creates duplicate ownership. Preserve new context while applying the agreed inquiry-matching rule.
Review unaccepted work
Use a visible queue with owner, age, last action and next step. Close the gap between notification and accepted responsibility.
Questions
Straight answers.
It distributes work by a rotation rule, but fairness and suitability depend on capacity, service expertise and current ownership. Define those priorities before choosing an assignment method.
HighLevel documents If/Else branches based on conditions. That supports conditional routing, but the particular rules, actions and coverage still need implementation and testing.
Use the documented backup rule and record the handover of open work. Changing future assignment alone may leave existing tasks with an unavailable person.
Sources and further reading
- HighLevel conditional workflow branches
HighLevel documents routing contacts through workflow branches according to defined conditions.
Checked .
Define the next action
Start with one intake route that loses ownership. Complete its routing row, then test the no-match and absent-owner cases.
Talk through your workflow