FrontLine for Recruiting & Onboarding — one funnel from requisition to day-1 ready.
Recruiting and onboarding sit on the same data model. The candidate Recruiting closes never falls into a handoff gap; the hire HR builds the record around already has BGC, documents, and provisioning queued. Multi-client by default.
Recruiting dashboard
Acme BPO · 18 reqs · 4 clients
Open requisitions
18
Active candidates
142
Offers out
7
Day-1 ready
4
Funnel · this month
May 2026
Applied
142
Phone
38
Assessment
24
BGC
12
Offer
7
Recent recruiting activity
Offer sent · Jordan W. · RetailCo Sr. CSR
5m ago
BGC cleared · Tyler B. · Sterling
1h ago
Mass-hire event opened · RetailCo launch · 50 target
3h ago
Candidate accepted offer · Maya P. · day-1 May 25
Yesterday
Open requisitions
8 active
CSR · RetailCo
12 open
8d openBilingual Sup · Atlantic
4 open
14d openTeam Lead · FinTech
1 open
3d openSpanish · MedTech
6 open
19d openWhat's hard about hiring at a multi-client BPO
Generic ATS tools were built for one employer hiring for one funnel. Your BPO runs four funnels in parallel, with different rules each.
Four clients, four funnels, one ATS
Each client carries different role requirements, comp bands, BGC depth, assessment vendors. A generic ATS models one funnel; reality is 4–8 in parallel. Every Monday the recruiter who should be sourcing reconciles per-client exception lists instead.
Candidate communication scales linearly with hires
From application to day 1, a candidate sees 8–12 touchpoints. Manual recruiters drop one every few candidates; templated systems get silence back. The TA team finds out from the floor lead, not the ATS.
BGC and assessment sequencing across vendors and clients
Each client requires different BGC depth; each role uses different assessment vendors. Without strict sequencing, a candidate hits day 1 with an open BGC. The ungated hire on a regulated LOB is a contract conversation you don't want.
The handoff gap between recruiting and onboarding
Recruiting closes the offer Friday. Onboarding picks it up Wednesday. In the gap, the candidate fields counter-offers and questions the decision. By Wednesday, day 1 is a sprint of badge-and-laptop logistics, not a calm welcome.
Mass hiring doesn't fit a steady-state recruiting flow
Five hires a week is normal. Fifty in a week for a client launch is a different motion — bulk assessments, parallel BGC, group orientation. Generic ATS chokes; the team improvises in a spreadsheet and the new-hire experience pays.
Day-1 readiness depends on four systems firing in order
Identity, scheduling, training enrollment, badge, equipment — all need to fire before day 1. With no orchestrator, the agent waits half their first day while someone figures out what's missing. The first impression becomes the missing impression.
What FrontLine does for your hiring team
Seven recruiting-specific surfaces, each shipped with the multi-client guarantee built in. Onboarding sits as a cross-team feature with HR — same workflow, two role-tuned views.
Feature 01
Recruiting ops queue — every requisition, candidate, and offer in one queue
Your recruiter's home screen. All clients, all stages, all aging in one filterable list. The morning workflow that replaces switching between four ATS dashboards.
- Cross-client view. Every open req across every client visible in one queue. Filter by client, LOB, role family, or recruiter assignment. Same data model, same screen — no context-switch tax.
- Stage-aware filters. Applied / phone screen / assessment / BGC / offer / accepted / day-1 ready. Drop candidates into the right bucket; bulk advance N at once.
- Inline candidate notes + call logs. Every recruiter interaction logged against the candidate record. The notes don't live in Slack DMs and lost email threads.
- SLA + aging indicators. Candidates sitting at a stage past their SLA flag amber; past 2× SLA flag rose. The aging candidates surface themselves; nobody has to remember.
- Bulk actions. Send templated reminders to N candidates, advance stage on N at once, schedule N for the same orientation slot. Mass-hiring-grade workflows from the same queue.
Recruiting ops queue
Open reqs
18
across 4 clients
Active candidates
142
all stages
Offers out
7
awaiting signature
Hires this wk
5
day-1 ready
Queue · aging-sorted
Filter: all clients · all stagesJordan W.
Sr. CSR · RetailCo
2d at stage
Aisha O.
CSR · TelcoPro
7d · aging
Tyler B.
CSR · RetailCo
3d at stage
Maya P.
Sr. CSR · FinCo
1d at stage
Liam S.
Team Lead · TelcoPro
9d · stalled
Bulk: send reminders to 12 aging candidates · advance 5 to next stage
Feature 02
Candidate self-service portal — public, mobile-friendly, bilingual
Candidates apply, check status, upload documents, reschedule interviews — all without recruiter mediation. The recruiter coordinates, the candidate self-serves.
- Public-facing application flow. Per-client branding, per-role custom fields. The candidate sees RetailCo's logo on RetailCo reqs, not generic FrontLine chrome.
- Status visibility. Candidate sees "Application received → Assessment scheduled → BGC running → Offer extended → Onboarding" — without asking the recruiter where they stand.
- Self-upload of documents. Candidates upload IDs, licences, references directly into their record. No email back-and-forth, no PDFs lost in inbox queues.
- Self-reschedule interviews. Recruiter calendar synced; candidate picks a new slot if they need to move. Manual rescheduling typically eats 15 minutes per swap; this eats zero.
- Bilingual EN ↔ FR. Candidate's preferred language detected from their browser or chosen at apply; every screen, every email, every notification in their language.
Candidate self-service portal
RetailCo · Customer Service Representative
EN support · Full-time · Hybrid (Montreal)
Your application status
Application received
May 12 · acknowledged
Assessment scheduled
May 16, 10:00 · Wonderlic + Hogan
BGC running
Sterling · standard-grade · ~3 business days
Offer extended
Pending BGC clearance
Onboarding starts
Auto-triggered at signature
Documents
Upload your ID, references, and signed PIPEDA acknowledgement here. We'll let you know when each is verified.
Need to reschedule your assessment? Pick a new slot →
Available in English and French · changes apply to all future emails
Feature 03
Hiring-manager portal — feedback lives on the candidate record, not in email
Hiring managers see their candidate pipeline scoped to their LOB. Structured feedback, ratings, advance/reject decisions — all captured against the candidate, not in lost email threads.
- Per-manager dashboard. Only see the candidates assigned to their LOB. Cross-LOB candidates are invisible — same RLS pattern as the rest of the platform.
- Inline feedback forms. Structured rating (1–5 on competency dimensions) + free text + advance/reject. The form is the audit log; no "I sent feedback in Slack" excuses.
- Hiring-manager sign-off gate. Offer can't go out without the manager's explicit advance. The gate is configurable per client; for clients that delegate full hiring authority to TA, it can be skipped.
- Manager availability + slot picker. Managers set their interview availability in-product; candidates self-schedule into open slots from the portal. Calendar push to Google Calendar / Microsoft 365 (so the interview lands on the manager's day) is on the Atlas roadmap; today managers see scheduled interviews in their FrontLine dashboard.
- Audit log. Who advanced whom, when, with what reasoning. When a regulator asks "why was this candidate rejected," the answer is one screen.
Hiring-manager portal
Sam Chen · Hiring Manager · RetailCo / EN support
Your candidates · 8 in pipeline
Jordan W.
Sr. CSR
Aisha O.
CSR
Maya P.
Sr. CSR
Manager feedback · Jordan W.
Phone screen · 30 min · May 16, 14:00
Communication
Multi-client fit
Problem-solving
Bilingual EN ↔ FR
“Strong candidate; clear EN/FR fluency. Recommend advance to offer.”
Feature 04
Offer letter automation — templated, e-signed, approval-gated
Templated offers per role family and jurisdiction. Multi-step approval before send. E-signature in-product. Auto-triggers onboarding at signature. Bilingual.
- Templates per role family + jurisdiction. QC offers carry LNT-required clauses; ON offers carry ESA clauses; US offers carry state-specific items. The template knows; the recruiter doesn't have to remember.
- Compensation / start-date variables. Comp, role, start date, manager auto-fill from the requisition. The recruiter reviews; they don't draft from scratch.
- Multi-step approval before send. Manager → HR → finance, configurable per client. The whole chain audit-logged. No "the recruiter sent a $50k offer without approval" incidents.
- E-signature integration. Candidate signs in-product. The signature event is itself an audit record; no "DocuSign envelope expired" follow-ups.
- Auto-triggers onboarding at signature. The moment the candidate signs, the onboarding workflow spawns. Document collection, BGC gates, provisioning hooks all start firing. The handoff gap stops existing.
Offer letter · OFR-2891
Jordan Whitfield
Sr. CSR · RetailCo · EN support
Compensation
$22.50/hr · ~$46,800 annual
Start date
Jul 1, 2026
Approval chain
Step 2 of 3Manager · Sam Chen
Approved · May 17, 14:02
HR review · Pat Rivera
In review since May 17
Finance · Jordan O.
Pending
E-signature
Awaiting candidate signature · expires May 24
On signature: onboarding workflow auto-spawns · documents + BGC gates fire immediately.
Feature 05
Assessments + BGC orchestration — sequenced gates per client
Multiple vendors. Sequenced gates. BGC must clear before onboarding starts. Configurable per client requirement. Compliance-grade audit at every gate.
- Native assessment engine + BGC orchestration. FrontLine ships a built-in assessment engine (typed-response forms, scoring rules, per-role thresholds) so most BPOs can run assessments without a third-party vendor at all. For BGC and for clients that mandate a specific assessment provider, the BGC orchestration layer wraps any provider through a standard webhook contract — your design-partner kickoff covers wiring whichever providers your client roster requires.
- Sequenced gates. Assessment → BGC → onboarding; each gate must pass before the next opens. The recruiter can't "forget" to run a BGC — the candidate literally can't progress.
- Per-client BGC depth. Financial-grade for fintech clients, standard for retail, custom per requirement. The depth is part of the client profile; recruiters don't have to remember.
- Appeal workflow. If a candidate disputes a BGC finding, the appeal runs in-product: FCRA-compliant pre-adverse + adverse action workflow, candidate response, final decision.
- Compliance audit. Every gate pass / fail logged with timestamp, vendor reference ID, and reasoning. When a client asks "did this hire clear our BGC requirement," the answer is one query.
Sequenced gates · Jordan W.
Jordan Whitfield · Sr. CSR · RetailCo
Client requirement: RetailCo · BGC = standard-grade · assessments = Wonderlic + Hogan
Gate sequence · must pass in order
Phone screen · Internal
S. Chen · May 13, 14:00 · advanced
Cognitive assessment · Wonderlic
Score 28/50 · ≥ threshold 22
Behavioural (Hogan) · Hogan
Fit score 76 · ≥ threshold 65
Background check · Sterling
Submitted May 16 · ETA May 19
Onboarding starts · FrontLine
Waiting for BGC clearance
If BGC returns adverse: candidate sees pre-adverse notice, has 5 business days to respond. FCRA-compliant.
Feature 06
Mass hiring events — bulk-grade, not band-aid
Hiring 50+ for a client launch is a fundamentally different motion. Bulk assessments, parallel BGC, group orientation, mass document collection — first-class workflows, not workarounds.
- Event-level dashboard. Cohort tracking, drop-off analytics by stage, bottleneck detection. See in real time where the funnel is stuck.
- Bulk candidate import. Via CSV, referral system, or job-board scrape. The candidates land in the event-scoped queue, not the general one.
- Parallel BGC + assessment dispatch. Send 50 candidates to assessment vendor + BGC vendor at the same time, get results back in parallel. The serial-processing bottleneck of a generic ATS doesn't apply.
- Group orientation scheduling. Pick 5 orientation slots, assign N candidates each. The system handles the calendar invites, the materials, the day-1 plan.
- Mass document collection. Templated reminders that escalate over 3 / 5 / 7 days. The 95% of candidates who upload don't need a phone call; the 5% who don't get one.
Mass-hiring event · RetailCo launch
RetailCo · May 2026 cohort
Target 50 agents · go-live Jun 15 · day-1 ready by Jun 12
Applied
67
In assessment
42
BGC cleared
12
Offers out
8
Cohort funnel
Applied
67
100%
Assessment
42
63%
BGC
22
33%
Offer
12
18%
Accepted
8
12%
Group orientation slots
Jun 02, 9:00
Jun 05, 9:00
Jun 09, 9:00
Feature 07
Hiring funnel analytics — by client, by req, by source
Time-to-fill, cost-per-hire, drop-off by stage, source quality — segmentable by client, role family, and time period. The recruiting lead's monthly review pack.
- Funnel drop-off. See exactly where candidates fall out. "Applied → Assessment" with 60% drop is a different problem from "Offer → Accept" with 40% drop. The analytics tell you which to fix first.
- Time-to-fill per client. Client A averages 12 days, client B averages 21 — why? The analytics segment by client, role family, and recruiter so you can isolate the cause.
- Cost-per-hire by source. Agency vs. referral vs. job board. Referral hires that survive probation are worth 3× the job-board candidate; the analytics make that visible.
- Source quality. Which sources produce candidates who pass probation? Which produce wash-outs? The funnel doesn't end at hire — quality data feeds back into your spending allocation.
- Export-ready. Monthly business reviews ship in 10 minutes: PDF, CSV, scheduled email. No more recruiting analysts rebuilding the same chart every month.
Hiring funnel analytics
Q2 2026
Time to fill
12 days
Cost per hire
$1,840
Funnel drop-off
22%
Pass probation
84%
Top sources · by hires that passed probation
Employee referral
38%
24%
Indeed
18%
Agency
12%
Other
8%
Funnel · stage-by-stage conversion
Applied → Phone screen
14227%Phone → Assessment
3863%Assessment → BGC
2450%BGC → Offer
1258%Offer → Accepted
771%Onboarding — the workflow that catches what Recruiting closes
The moment Recruiting closes an offer, an onboarding workflow auto-spawns and runs document collection, BGC gating, system provisioning, and day-1 plan handoff. Same data model HR sees on the employee record — different role-tuned views. The handoff gap stops existing.
- Auto-spawned at offer signature. No manual "start onboarding" button. The signature event triggers the workflow instance creation; document collection and BGC tasks start firing immediately.
- Same workflow, two views. Recruiting sees the candidate progressing from "Hired" → "Day-1 ready." HR sees the document compliance side. The manager sees the day-1 readiness side. One workflow, three role-tuned dashboards.
- Document collection orchestration. PIPEDA acknowledgement, banking, emergency contact, T4 / W-4, sector-specific forms — all with templated reminders. Candidates upload; you don't chase.
- BGC gating. Onboarding can't progress past the BGC gate until the result clears. Protects compliance AND the manager's day-1 expectations.
- System provisioning hooks. Identity, scheduling, training enrollment, per-client tool access all fire off the same workflow. IT, Training, and HR each act on their slice without coordination overhead.
- Day-1 plan handoff. When onboarding completes, the manager receives a curated day-1 plan with system access confirmed, schedule synced, training enrollment, and a fresh-hire checklist for the first 30 days.
Jordan Whitfield
CSR · RetailCo · EN supportHire date May 20 · Day-1 in 4 days
Day-1 readiness
3 / 5 stepsWorkflow steps
Background check
Verified May 14
Document collection
7 of 7 forms received
PIPEDA acknowledgement
v4.2 · May 16
System provisioning
Identity · scheduling · KB
Day-1 plan handoff
Manager receives Mon 9:00 am
Cross-team handoff: Recruiting sees “Hired → Day-1 ready”; HR sees document compliance; Manager sees readiness.
Business outcomes for the people running the BPO
What this looks like in margin terms for the COO or owner.
Time-to-fill compresses — faster billing on new agents
Parallel assessment and BGC processing plus auto-spawned onboarding pull days out of the typical funnel. For a multi-client BPO hiring at any meaningful scale, that compression pulls revenue forward — magnitude depends on your current funnel length and seat economics.
No-show rate drops — candidates stay engaged
Self-service portal + automated multi-touch communication + an onboarding handoff that doesn't drop the candidate during the week between offer and day 1. The candidates who normally ghost stay engaged.
Every gate audit-logged
Every BGC clearance, every assessment score, every offer signed — fully audit-logged with vendor reference IDs and decision reasoning. When a regulator asks "did this hire clear the right background check," the answer is one screen with the gate-pass timestamps.
Mass hiring without breaking the team
50+ in a week for a client launch is a normal workflow, not an emergency project. Hiring events ship to the team with first-class tools — cohort dashboards, parallel dispatch, group orientation. The team doesn't burn out every quarter.
What Hiring actually gets back
Directional outcomes — real magnitude depends on your current funnel baseline, client mix, and onboarding rigor.
Days off the funnel
Parallel assessment + BGC dispatch plus auto-spawned onboarding compress the cycle. Magnitude depends on your prior cycle length.
Fewer no-shows and ghosting
Self-service status visibility + automated touchpoints + no handoff gap between offer and day 1.
Zero IT escalations (target state)
Provisioning hooks fire off the offer signature, not the manager's panic call Tuesday morning. Hook coverage depends on which IT systems your team wires up at onboarding.
Three systems → one workflow
ATS + BGC vendor portal + onboarding tracker collapsed into one workflow with one source of truth.
Regulatory posture
FrontLine Hiring vs. a generic ATS
Six things BPO recruiting teams notice in their first month away from Greenhouse / Workable / Lever / BambooHR ATS.
| FrontLine Hiring | Generic ATS | |
|---|---|---|
Multi-client requisition with client-scoped metadata Generic ATS treats client as a tag; you need it as a data-model dimension. | ||
Native onboarding workflow auto-spawns at offer signature Most ATS end at offer-accepted; onboarding is a separate product / spreadsheet. | ||
Sequenced BGC + assessment gates per client requirement Some ATS support gates; few enforce per-client sequencing with appeal workflows. | ||
Mass-hiring event workflows (50+ in a day) Generic ATS choke on bulk; you end up running the event in a spreadsheet. | ||
Bilingual EN ↔ FR candidate portal + per-client branding Platform UI is fully bilingual today. Per-template content translation (offer letters, custom notification copy) ships in the language your team authors; per-template EN ↔ FR pairing is on the roadmap. | ||
Cross-client recruiter view — same recruiter handles N clients Generic ATS makes you create separate workspaces per client; recruiters context-switch. |
In production today
Both Recruiting (Module 20) and Onboarding (Module 21) are shipped and running on customer tenants today. See the technical status, full feature list, and weekly progress on the Atlas.
Questions recruiting leads actually ask before signing
Pulled from real fit calls. Short, direct answers.
How do we migrate from our current ATS without losing pipeline state?+
Can a single recruiter handle multiple clients with proper data separation?+
What ATS and BGC integrations do you support?+
Can candidates apply in their preferred language?+
What about ban-the-box laws and FCRA-compliant BGC handling?+
Ready to see it in your environment?
Two ways to take the next step.
Other teams using FrontLine
Hiring doesn't end at day 1. Here's what the rest of FrontLine looks like from the team next door.