MILabs
Integrations

Lead routing automation with Bullhorn for recruitment agencies

Route enquiries in Bullhorn to the right consultant or account owner, with a named fallback and a log of each routing decision for team leads.

Updated 2026-05-23

Lead routing automation with Bullhorn

Recruitment agencies receive enquiries from two directions: candidates asking about roles and clients asking for people. In Bullhorn, those contacts and job orders already sit in one database, so a routing rule can read the record itself rather than rely on memory. A web form submission or inbound email can be matched to a sector, a consultant and an open desk, then assigned before anyone opens the inbox. The rules should follow how your desks already divide work, such as by industry vertical, placement type or the team member who covers a client account. Start by writing those divisions down, then check which of them can be read from fields already held in Bullhorn. Routing can write the owner and assignment time back to the record, so the team can see the history. MILabs, a Sydney agency, works through this with owners and team leads, and delivers the same work remotely for agencies elsewhere.

How it works

  1. Capture each web form submission or inbound email and create or update the matching contact or lead record in Bullhorn through its API, within the permissions granted to the connecting user.

  2. Read the company, sector and region from the record, then match them against the routing rules your desks have agreed.

  3. Assign the record to a named consultant or account owner and write that owner and the assignment time back to Bullhorn.

  4. Send the enquirer an acknowledgement that names the person now handling their request.

  5. Log each decision with the rule matched and the owner chosen, so a team lead can review routing against the agreed rules.

  6. Route unmatched enquiries to a named fallback owner, and have a team lead check that queue before any rule is changed.

good questions, straight answers

Frequently asked questions

What does a lead routing automation read from Bullhorn?
It reads the fields that describe each contact and job order, such as company, sector, region, record owner and status, along with the enquiry details arriving from the web form or inbox. The connecting user's permissions decide which objects it can reach through Bullhorn's API. Fields that are empty or inconsistent should be listed during scoping, because routing depends on them being filled in.
Is a lead routing automation safe with Bullhorn data?
Yes, when access is scoped carefully. The connecting user should hold only the permissions the routing rules need, and the build should write owner and assignment fields rather than editing candidate details. Changes to records can carry into placements and timesheets, so a review step and a log of every write help a team trace an error back to its source.
What happens if Bullhorn changes?
The build depends on Bullhorn's API and on the field names it exposes, so a change to either can stop routing. Before launch, the set of fields and endpoints in use should be recorded, and the vendor's current API documentation should be checked against that list. Routing logs should alert a team lead when a write fails, so that leads do not go missing silently.
Who owns a lead routing automation built around Bullhorn?
Ownership should be settled before the build starts. The client should hold the Bullhorn subscription, the API credentials and the routing rules, so the business can change desk assignments without outside help. A named team lead should approve each rule change. MILabs, a Sydney agency, documents the connection and rules so that an internal owner can maintain them after delivery.
How does a lead routing automation hand work to a person in Bullhorn?
The routing step assigns the record to a named owner in Bullhorn and writes that owner to the record, so the consultant sees the lead in their usual view. The acknowledgement email tells the enquirer who will respond. Leads that match no rule go to a fallback owner, who is named in the rules. The person then works the lead in Bullhorn as they would any other record.
let's make something happen

Custom development: how we can help

Choose how you want to work on this with MILabs. Both options start with an enquiry.

Discovery is free, no obligation from the first chat.

Let us build it for you

We build it and look after it.

Build it yourself, we'll help

You build it with our direction, teaching and a weekly check-in.