Staffing and recruiting firms get the most from Salesforce when it runs the client side of the business. That means accounts, hiring managers, business development and job orders. The applicant tracking system usually keeps candidates, submittals and placements. A third path is a Salesforce-native ATS from the AgentExchange (formerly AppExchange), which puts both sides in one org. The right split depends on where recruiters already work and how tightly sales and delivery must connect.
Which work should Salesforce own, and which should stay in the ATS?
Give Salesforce the buyer relationship and give the ATS the candidate journey. Job orders sit on the boundary, so decide their home first.
Most agencies already run an ATS that recruiters live in all day. Replacing it is a large change for the people who generate revenue. Salesforce adds the most value where the ATS is usually weakest.
- Client accounts, divisions and work sites, with a parent company above them.
- Hiring managers, procurement contacts and the people who approve new suppliers.
- Business development: prospecting, meetings, rate negotiations and new-logo deals.
- Account management: renewals, expansion into new departments and service reviews.
- Marketing to buyers, and in some firms to candidates as well.
The ATS keeps candidate profiles, resumes, sourcing, submittals, interviews and placement records. Back-office systems keep timesheets, payroll and invoicing.
Some firms skip the split entirely. AgentExchange staffing apps build the ATS inside Salesforce, so candidates and clients share one database. That suits firms ready to retrain recruiters and wanting one reporting layer. It is a bigger migration, and the app vendor’s data model shapes everything you build later.
How should job orders, submittals and placements be modeled?
If Salesforce holds job orders, model each one as an opportunity or as a custom object related to the account. Submittals and placements belong in Salesforce only when the ATS runs there too.
An opportunity works when each job order is something a salesperson wins, such as a new requisition or a project bid. Stages can follow intake, sourcing, submitted, interviewing, offer and filled. A custom Job Order object fits better when one client agreement produces many requisitions. Then the opportunity represents the agreement, and job orders hang beneath it.
| Process | System of record | Integration need | Report it feeds |
|---|---|---|---|
| Client accounts and hiring managers | Salesforce | Push client and contact IDs to the ATS | Account coverage and revenue by client |
| Business development pipeline | Salesforce | None, or enrichment for new prospects | New-logo pipeline by stage and owner |
| Job orders and requisitions | Salesforce or ATS (pick one) | Sync status and openings both ways | Open orders, aging and fill rate |
| Candidates and resumes | ATS | Usually none into Salesforce | Kept in ATS reporting |
| Submittals and interviews | ATS | Counts or status rolled up to the job order | Submittal-to-interview ratio per order |
| Placements and assignments | ATS | Placement summary back to the account | Time to fill and active headcount by client |
| Timesheets, payroll and billing | Back-office system | Billed and paid totals to the account | Spread or margin by client |
When the ATS runs inside Salesforce, submittals become a junction between candidate and job order. Placements then carry dates, pay rate, bill rate and assignment status. Keep pay and bill rates behind field-level security, because few users need both.
How do we manage business development and MSP or VMS clients?
Run new-logo work as a standard pipeline and treat program clients as accounts with their own record type. Requisitions from those programs arrive differently, so track them separately from sales deals.
Large buyers often route contingent hiring through a managed service provider and a vendor management system. Orders appear in a portal, rates are set by the program, and suppliers are scored. Selling into the program is a business development deal. Working the orders that follow is fulfillment.
- Add a program record type on the account with fields for program terms, tier and review dates.
- Track supplier scorecard results as a related record so account managers see trends.
- Separate new-logo opportunities from renewals and program expansions with record types.
- Feed requisitions from the portal into the job order object only if your ATS cannot hold them.
Our account hierarchy guidance applies here. Roll work sites and divisions up to the parent so leaders see total revenue per client, not per location.
How should the ATS and back office connect to Salesforce?
Connect them on shared IDs and a short list of fields, not full copies of each record. Decide the owner of every field before choosing a connector.
Most agencies need three data flows. Client and contact records move from Salesforce to the ATS. Job order status and placement summaries come back. Billed revenue and gross profit per client arrive from the back office on a schedule.
Options include the ATS vendor’s own connector, an integration platform, or a custom API build. Each trades speed against control. Our integration options guide compares them, and the ERP integration guide covers sync timing and error handling.
How do recruiters and account managers log activity without double entry?
Capture email and calendar activity automatically, then log calls and meetings in whichever system the person already uses. Ask each role to log in one place only.
Account managers and business developers should work in Salesforce, with Outlook or Gmail connected so meetings and messages attach to contacts. Recruiters usually log in the ATS. Roll their client-facing touches, such as intake calls, into the job order rather than duplicating the full history.
High-volume outreach can hit Salesforce email sending limits. Plan prospecting volume, and route bulk sends through a marketing tool built for them. Your Salesforce account team can confirm the exact limits that apply to your org.
Which dashboards should a staffing firm build?
Build separate views for business development, account management and delivery. Define every metric in writing before building, because fill rate and time to fill have several common definitions.
- Business development: new meetings, proposals out and new-logo pipeline by owner, this week against last week.
- Account management: open job orders per client, order aging and accounts with no recent contact.
- Delivery: fill rate, time to fill and submittals per order, drawn from ATS data.
- Leadership: spread or gross margin by client and by business line, once back-office data is connected.
Agree what counts as filled, when the clock starts for time to fill, and whether spread is per hour or per placement. Write those definitions on the dashboard itself. Our leadership dashboards guide covers layout, ownership and review rhythm.
What did this look like for a staffing firm we supported?
A labor and marine-personnel staffing company came to us with broken activity reporting. Dashboards were inaccurate and blended every rep’s numbers together.
The firm ran Sales Cloud and had bought Marketing Cloud Account Engagement plus a lead-enrichment tool. Neither had been switched on after earlier attempts through Salesforce support. The team was also running into Salesforce email limits.
We rebuilt the dashboard components so calls, emails, tasks and events showed for this week and last week. Dynamic dashboards let each rep see only their own activity. We configured Account Engagement with a foundational structure and lead scoring. We also fixed the enrichment integration and added templated lead reports by geography.
The result was accurate activity visibility per rep and campaigns the firm could track. It also unlocked the enrichment automation the firm had originally bought Salesforce to get. That project covered sales dashboards and marketing setup.
How should we market to clients and candidates?
Market to hiring managers from Salesforce, where buyer data already lives. Candidate marketing usually works better from the ATS or a dedicated tool, unless candidates are stored in Salesforce.
Account Engagement suits business-to-business nurture: hiring trend updates, salary guides, event invitations and re-engagement of dormant clients. Lead scoring tells business developers which contacts are warming up. Our Account Engagement setup guide covers the foundational build.
Keep the audiences apart. A hiring manager and a job seeker need different consent, content and unsubscribe handling.
What should we know about compliance and candidate privacy?
Candidate records hold sensitive personal data, so limit who sees them and how long you keep them. Treat this section as a starting checklist, not legal advice; confirm obligations with counsel.
- Keep candidate data in one system of record and copy as little as possible elsewhere.
- Restrict pay rates, background check status and identity details to the roles that need them.
- Record consent and the lawful basis for contacting candidates in each region you recruit in.
- Set retention rules for inactive candidates and test the deletion process end to end.
- Log who exported candidate lists, and why.
Our data privacy guide explains how Salesforce features support access control, consent tracking and retention.
Where can AI help a staffing team?
AI can help with first drafts and summaries; matching help depends on clean, structured data. Treat early results as suggestions a recruiter checks.
- Summarize an account before a client review: open orders, recent placements, notes and complaints.
- Draft intake notes or a job description from a hiring manager call for the recruiter to edit.
- Suggest candidates for a job order, if your ATS or Salesforce app offers matching.
- Flag accounts where order volume has dropped compared with prior periods.
Feature availability depends on edition, add-ons and your ATS vendor. Confirm with your Salesforce account team and ATS provider. Avoid fully automated screening decisions, and review any tool that ranks people for bias.
What belongs in a staffing firm’s first phase?
Start with the client side: accounts, contacts, business development and activity reporting. Add ATS integration once the client data is clean and owned.
- Account hierarchy for parent clients, divisions and work sites.
- Contact roles for hiring managers, procurement and approvers.
- A business development pipeline with clear stages and required fields.
- Email and calendar capture for business developers and account managers.
- Per-rep activity dashboards with written metric definitions.
- A decision on where job orders live, documented before any integration work.
