Bullhorn CRM SMS Integration: Texting the Field and Capturing Leads

Your recruiters are texting candidates. That’s a fact. The real question is whether that communication is happening on their personal phones—a black hole of lost data and compliance risk—or within a system that enriches your single source of truth: Bullhorn. A proper Bullhorn CRM SMS integration does more than just let you send texts; it turns every message into a structured data point, automatically logged and actioned within your database.

Most SMS platforms offer a "Bullhorn integration" that is little more than a Chrome extension or a surface-level connector. This is different. We're showing you how a truly native integration works under the hood. It’s about mapping recruiter numbers, automatically creating candidate records from inbound texts, logging every conversation, and handling compliance without manual effort. This is the blueprint for turning SMS from a liability into your most valuable data acquisition channel.

For firms serious about leveraging their existing data, this level of connection is non-negotiable. A deep Bullhorn SMS integration doesn’t just add a feature; it fundamentally changes how you capture leads and manage relationships.

The Problem: Your Bullhorn Data is Incomplete Without SMS

If your team uses personal cell phones for texting, your Bullhorn data has a massive blind spot. Every text conversation—a candidate screen, a referral check-in, a negotiation—exists only on that recruiter's device.

This creates four immediate problems:

1. No Visibility: As a manager, you can't see the activity. You don't know if follow-ups are happening, what's being promised, or how candidates are responding. Reporting on recruiter activity is fundamentally inaccurate.
2. Lost Leads: A candidate texts a recruiter about a new role or sends a referral. That lead lives and dies in a single text thread. If the recruiter is busy or misses it, the opportunity vanishes. It never becomes a Candidate or Lead record in Bullhorn.
3. Compliance Risk: When a candidate replies "STOP" to a recruiter's personal phone, there is no system to honor that request across the company. The next recruiter who pulls their name from a tearsheet might text them, creating a TCPA violation risk.
4. Turnover Chaos: When a recruiter leaves, they take their entire SMS history—and the relationships within it—with them. Candidates are left texting a dead number, creating a jarring experience that reflects poorly on your firm.

Without an integrated SMS system, your Bullhorn instance is only telling part of the story. You're missing the most immediate and impactful conversations your team is having.

How a Native Integration Maps Recruiter Numbers to Bullhorn Users

Getting recruiters off their personal phones starts with giving them a better, integrated alternative. A true integration doesn't use shared company numbers or clunky web apps. It assigns a unique, dedicated business number to each recruiter and maps it directly to their Bullhorn user account.

Here’s the process:

1. Provision Numbers: First, we provision a dedicated phone number for each recruiter on your team through a carrier platform like Twilio. These can be local numbers to create a familiar presence for candidates.
2. User Sync via API: The integration platform uses the Bullhorn API to pull a list of all your active Bullhorn CorporateUser records.
3. Map User ID to Phone Number: In the backend, we map each newly provisioned phone number to a specific Bullhorn UserID. For example, recruiter Jane Doe's Bullhorn ID (12345) is permanently associated with the phone number (212) 555-0182.

The result is seamless. When Jane logs into the SMS platform, she is automatically authenticated as her Bullhorn user and all texts she sends will come from her dedicated business number. There’s no need to choose a number or specify a user. The system already knows who she is and what number belongs to her. This foundational step is critical for ensuring all subsequent activity is logged to the right owner in Bullhorn.

From Inbound Text to New Candidate: Parsing and Record Creation

What happens when someone you don't know texts your firm? This is where a native integration proves its worth over a simple texting tool. Instead of becoming a random notification, an inbound text from an unknown number can automatically create a clean, assigned record in Bullhorn.

Consider this workflow, which runs in seconds:

1. An un-recognized number texts a recruiter’s provisioned line: "Hi, my friend Sarah Jones said you were looking for DevOps engineers. Here's my resume."
2. The SMS platform receives the text and instantly makes an API call to your Bullhorn instance, searching for that phone number across all existing Candidate and Contact records.
3. No match is found. The platform's logic identifies it as a new lead.
4. The integration automatically creates a new Candidate record in Bullhorn.
5. It populates the record with the candidate's phone number and assigns the record's owner to the recruiter whose number received the text.
6. Finally, it posts the original text message as the very first Note on the new candidate's activity feed.

Your recruiter now has a new, fully-sourced candidate in their pipeline without lifting a finger. This is especially powerful for capturing leads from word-of-mouth or referral programs. By tying this into Bullhorn referral software, you ensure that every inbound referral text immediately becomes an actionable record in your database, not a forgotten message.

Logging Outbound and Inbound SMS to the Correct Bullhorn Record

For numbers already in your database, the goal is to create a complete, chronological audit trail of communication. A native integration makes this automatic.

Whether a recruiter sends a text or receives a reply, the system logs the entire conversation directly onto the appropriate Bullhorn record.

Here’s how:

• On Outbound: A recruiter uses the SMS platform to text a candidate about a new Governance, Risk, and Compliance (GRC) Analyst SOW project. The platform sends the text and simultaneously makes an API call to Bullhorn. It finds the Candidate record associated with that phone number and adds a Note with the full message content, a timestamp, and "Direction: Outbound."
• On Inbound: The candidate replies, "Sounds interesting, can we talk tomorrow at 10 AM?" The platform receives the reply, finds the matching Candidate record again, and adds a new Note with the reply's content, timestamp, and "Direction: Inbound."

Every touchpoint is captured in real-time on the Candidate's activity feed. Any manager, team member, or account executive can look at that record and see the entire communication history without having to ask the recruiter to forward them a screenshot from their phone. This is crucial for team-based recruiting and for building a complete institutional memory of your talent relationships. For specialized agencies, a dedicated referral integration for IT staffing firms relies on this exact mechanism to track and validate referral conversations.

Automating TCPA Compliance (STOP/START) Inside Bullhorn

Managing opt-outs manually is a recipe for disaster. A native integration automates TCPA compliance and makes the candidate's consent status a visible, queryable data point within Bullhorn.

When a candidate texts STOP, two things happen instantly:

1. Carrier-Level Block: The underlying SMS provider (e.g., Twilio) immediately blocks that number from receiving any more messages from that specific phone line. This is the instant, technical enforcement.
2. Bullhorn Record Update: The integration platform sends an API call to Bullhorn to update the candidate's record. This typically involves:
   • Checking a custom checkbox field, like SMS_Opt_Out.
   • Adding a Note to the activity feed stating: "Candidate opted out of SMS via STOP command on [Date] at [Time]."

Now, their opt-out status is not just an invisible block on a third-party platform; it's a permanent, searchable part of their Bullhorn record. Your team can build lists that automatically exclude anyone with SMS_Opt_Out checked, preventing accidental contact and ensuring firm-wide compliance. If the candidate ever texts START to re-subscribe, the entire process runs in reverse, un-checking the box and logging the re-subscription.

Workflow in Action: Bulk Texting a Tearsheet

Let's put it all together in a common recruiting workflow: reaching out to a list of qualified candidates for a new job.

1. Create Tearsheet: An IT recruiter creates a Tearsheet in Bullhorn named "Available Python Devs - Remote C2H" containing 50 qualified candidates.
2. Select Audience: In the SMS platform, the recruiter selects the "Available Python Devs - Remote C2H" Tearsheet as their audience. The platform automatically pulls in the candidates and filters out anyone who has previously opted out.
3. Compose Message: The recruiter writes one message using personalization tokens. Hi {Candidate.FirstName}, quick question. I have a new 12-month C2H Python/Django role that just opened up. Are you open to a chat this week?
4. Send Campaign: They hit send. The platform sends the message as 50 individual 1-to-1 texts from the recruiter's dedicated number. It's a bulk action on the recruiter's end but a personal message on the candidate's end.
5. Log and Manage Replies: Every outbound text is automatically logged to the corresponding 50 Candidate records in Bullhorn. As replies flow in—"Yes," "No, thanks," "Tell me more"—they appear in the recruiter's unified inbox and are also logged automatically on the correct candidate's activity feed.

The entire campaign, from outreach to response, is executed and documented in minutes, all within a compliant framework and captured permanently in your system of record.

Choosing a Partner: Questions to Ask About Their Bullhorn Integration

Not all "integrations" are created equal. When evaluating an SMS provider, you need to look past the marketing slicks and ask pointed questions about how their technology actually interacts with Bullhorn.

• Is it a native API integration or just a Chrome Extension? An API integration works server-to-server. It’s robust, runs in the background, and doesn't depend on a user having a browser tab open. A Chrome extension overlays on the Bullhorn UI and can be brittle, breaking with Bullhorn updates.
• How do you handle inbound texts from unknown numbers? Ask if it can automatically create a new Candidate or Lead record and assign it to the correct owner. If the answer is "it creates a task" or "sends an email notification," it's not a true automation integration.
• Where is SMS activity logged? The only right answer is "directly to the Notes/Activity feed on the relevant Candidate/Contact record in real-time." Anything less creates more work.
• How is TCPA compliance reflected inside Bullhorn? Does an opt-out update a field on the candidate record? Can you run a report in Bullhorn of all opted-out candidates? If the opt-out list only lives in their application, it’s not truly integrated.
• What Bullhorn objects do you interact with? A deep integration should be able to read Tearsheets, Candidates, and Contacts, and write back to Notes and custom fields on those records.
• Are you building on a platform like Twilio? Understanding the foundation of their tech can help you decide between the build vs. buy for a Bullhorn Twilio SMS integration and evaluate the provider's long-term stability.

A genuine integration makes Bullhorn better. A superficial one just adds another tab for your recruiters to manage.

How Earshot helps

At Earshot, we built our platform around a deep, native Bullhorn integration because we believe your CRM should be your single source of truth. We handle the complexities of number provisioning, user mapping, automated record creation, and real-time activity logging so your team can focus on what they do best: building relationships. Our system is designed to make every text message a valuable, reportable data point inside the system you already use every day.

If you're ready to see how a truly native SMS integration can transform your Bullhorn data and capture more leads, schedule a demo with our team.