Bullhorn phone system integration for UK recruitment agencies
Bullhorn is the CRM most UK staffing firms run their desks on — and the phone is still where the placements come from. Integrating the two properly means a consultant never types a number again, never writes a note from memory, and never argues with a manager about what activity actually happened. This page explains exactly how we connect a cloud phone system to Bullhorn, what is genuinely automatic, and what we confirm against your tenant before anyone signs anything.
- Candidate, contact, lead, job and list views — one click launches the call
- Click-to-dialfrom any Bullhorn recordCandidate, contact, lead, job and list views — one click launches the call
- Direction, number, duration, outcome and recording link written back to the record
- Auto-loggedDirection, number, duration, outcome and recording link written back to the record
- Inbound calls match to the candidate or client record before the consultant answers
- Screen-popInbound calls match to the candidate or client record before the consultant answers
- Outbound dialling launched directly from Bullhorn — no copy-paste, no misdials, no mobile-in-hand.
- Inbound screen-pop so a consultant knows who is calling, which job, and what was last said.
- Call activity written back automatically, so desk reporting reflects reality rather than memory.
- We validate the integration against your own Bullhorn tenant and edition before you commit.
What a Bullhorn telephony integration actually gives a recruitment desk
The value is not the technology, it is the removal of admin from a consultant’s day. Every one of the items below is a behaviour change on the desk, not a feature on a datasheet.
- One-click dialling from candidate, contact, lead, job order and tearsheet records — including from list views while a consultant works a longlist.
- Inbound matching on caller line identity, so the candidate or client record opens on screen as the phone rings.
- Automatic activity capture: date, time, direction, number dialled, ring time, talk duration and the user who made the call.
- Disposition and outcome capture, so “left voicemail”, “not interested”, “CV requested” and “interview booked” become reportable data rather than free text.
- A secure link to the call recording stored against the record, so a manager can review the actual conversation in context.
- Consistent outbound caller identity from softphone, desk phone and mobile app — the candidate sees the same business number every time.
- Optional AI call summaries and next actions written into the record via Atom Insight.
How the integration is built
Bullhorn publishes a REST API and supports computer-telephony integration from telephony clients. We use those published routes — there is nothing bespoke or fragile sitting in the middle that breaks when Bullhorn updates.
- Authentication against your Bullhorn tenant using credentials your administrator controls and can revoke.
- A CTI-capable softphone or browser connector on the consultant’s device for click-to-dial and screen-pop.
- Write-back of call activity against the correct entity, mapped to the note action types your business already reports on.
- Field mapping agreed with you first — we do not silently create new note types that pollute your existing reporting.
- A test plan run on a sandbox or a small pilot group of consultants before any wider rollout.
Bullhorn tenants differ by edition, configured entities, note action types and enabled API access. We confirm what is available in your specific tenant during the design session rather than assuming it.
Want Bullhorn integration confirmed against your own tenant?
A review is free, there is no obligation, and you keep the written summary either way.
Before and after, on a working desk
A practical comparison of the same consultant day with and without integrated telephony.
- Phone system not integrated
- Read the number, type it into a handset or mobile
- Integrated with Bullhorn
- One click from the Bullhorn record
- Phone system not integrated
- Answer blind, ask the caller to explain who they are
- Integrated with Bullhorn
- Record opens on screen with history before answering
- Phone system not integrated
- Typed manually later, if at all
- Integrated with Bullhorn
- Written back automatically with duration and outcome
- Phone system not integrated
- Inconsistent free text, hard to report on
- Integrated with Bullhorn
- Structured dispositions you can filter and report on
- Phone system not integrated
- Based on what the consultant recalls
- Integrated with Bullhorn
- Based on the recording and the activity data
- Phone system not integrated
- Varies by device — mobiles, deskphones, withheld
- Integrated with Bullhorn
- One consistent business identity across every device
Questions worth asking any provider selling you “Bullhorn integration”
Integration is a word that gets used very loosely in telecoms. These are the questions that separate a real integration from a browser plug-in that only dials.
- Does it write call activity back into Bullhorn, or does it only dial out? Dialling alone is the easy half.
- Does inbound screen-pop work, and what happens when a number matches two records?
- Which Bullhorn entities are supported — candidates only, or contacts, leads and job orders too?
- Are outcomes captured as structured dispositions, or typed into a free-text note?
- Where is the recording stored, who can access it, and how long is it retained?
- Does it work identically for a consultant on a laptop at home and a consultant on a desk phone in the office?
- What happens to the integration when a consultant leaves — how is access revoked?
What we need from you to scope a Bullhorn integration
- Number of consultant seats, split by desk or brand if relevant.
- Which Bullhorn entities your consultants work from day to day.
- The note action types your current desk reporting relies on.
- Whether call recording is required, and any retention rule you already apply.
- Your current phone provider, contract end date and notice period.
- Where consultants work from — office, home, or a mix.
Frequently asked questions
Do consultants need a new handset to get click-to-dial from Bullhorn?
No. Click-to-dial works from a desktop softphone, a browser connector or a mobile app. Desk phones are optional and are usually chosen for comfort and headset preference rather than because the integration requires them.
Will call notes overwrite the notes our consultants type themselves?
No. Automatic call activity is written as its own logged activity against the record. Anything a consultant types stays exactly as they typed it. We agree the mapping with you first so the automated entries sit alongside your existing reporting rather than distorting it.
What happens if an inbound number matches more than one Bullhorn record?
The connector presents the matches rather than guessing, and the consultant picks the right one. This is common where a candidate has also been a client contact, or where an office switchboard number is shared by several contacts.
Can we roll this out to one desk first?
Yes, and we recommend it. A pilot group proves the field mapping and the dialling behaviour on real calls before the rest of the business is moved across.
Does it work with Bullhorn on a Mac?
Yes. Softphone clients are available for Windows and macOS, and a browser-based option removes the desktop dependency entirely where your IT policy prefers that.
Who owns the call recordings?
You do. Recordings relate to your business and your data subjects. We configure storage, retention and role-based access to match the policy you set, and you can export them.
Related recruitment guides
See it running against a Bullhorn record
We will walk through click-to-dial, screen-pop and write-back on a live call, then tell you honestly what your specific Bullhorn tenant supports.
- Full audit of every line, number and contract you hold
- Honest view of what your CRM will and will not integrate with
- The call data you are not currently seeing, including missed inbound
- A written summary — yours to keep either way