/Services

FOR RECRUITING + STAFFING AGENCIES

Staffing agency workflow automation,
thoughtfully handled.

Rungbird sets up scoped automation for the repeatable work around recruiting — so your team can keep its attention on candidates, clients, and decisions.

Describe your workflow and systems without sharing credentials, passwords, API keys, or access tokens.

Describe your workflow — no credentials Back to the Rungbird home
ILLUSTRATIVE SCOPE Human-reviewed

A practical workflow, with clear edges.

This introductory pilot explores one recruiting workflow around Bullhorn ATS/CRM and Google Calendar, if supported account access is confirmed and the integration scope is agreed. Recruiters retain the decisions that matter.

Bullhorn + Google Calendar scope, pending access Human review at each decision Recruiters stay in control
INTRODUCTORY PAID PILOT$1,500 setup + $500/monthMonitoring, fixes, and defined small improvements.
Scope this pilot — no credentials RB / 01
SCOPED ADMIN AUTOMATIONPEOPLE-FIRST WORKFLOWS
THE OFFER

The recommended
first paid pilot.

The introductory pilot covers one recruiting workflow: candidate intake, human-reviewed résumé summaries, a recruiter-approved Bullhorn ATS/CRM record update, Google Calendar interview scheduling, and a weekly activity report. The workflow description is illustrative. Live connections depend on supported account access and confirmed integration limits; Bullhorn ATS/CRM and Google Calendar are not already connected or live, and this offer does not write records or book interviews.

INTRODUCTORY COMMERCIAL TERMS

A clear first commitment, with a clear boundary.

$1,500one-time setup
$500/monthmonitoring, fixes, and defined small improvements

Pricing is for the recommended first paid pilot. Checkout below uses the owner-confirmed hosted payment service after a free account is created.

APPROVED INTRODUCTORY PILOT

Ready to take the first
bounded step?

Checkout is a two-step hosted payment path: $1,500 one-time setup, followed by $500 per month for monitoring, fixes, and defined improvements. The server verifies the setup payment before it makes the monthly checkout available.

Bullhorn ATS/CRM and Google Calendar are illustrative scope boundaries only. No live connection to either system is included or active from checkout: live connections depend on confirming supported account access and agreeing scope and integration limits up front. Checkout does not write records or book interviews.

RUNGBIRD / PILOT 01SERVER-VERIFIED CHECKOUT
$1,500one-time setup
$500/monthmonitoring, fixes, and defined improvements

Checking your account…

THE FIVE PILOT STAGES

One bounded admin rhythm.

The first pilot targets Bullhorn ATS/CRM and Google Calendar only. The exact scope is agreed with your agency before any live connection is considered.

  1. 01

    Candidate intake

    Capture candidate and role details in a consistent starting point.

  2. 02

    Résumé summary

    Prepare a concise résumé summary for a human recruiter to review.

  3. 03

    Recruiter-approved Bullhorn CRM update

    After approval, update the agreed candidate record in Bullhorn ATS/CRM.

  4. 04

    Google Calendar scheduling

    After confirmation, prepare interview scheduling in Google Calendar.

  5. 05

    Weekly activity report

    Bring activity, handoffs, and open loops into a weekly team view.

Recruiters retain all candidate screening and hiring decisions. Supported account access and actual integration limits are confirmed before any live connection is considered.

ILLUSTRATIVE WALKTHROUGH / SAMPLE DATA

From intake to a clear next step.

Follow one sample candidate through the five handoffs in order. This is an illustrative walkthrough using sample data only. Bullhorn and Google Calendar are not live integrations on this page: it does not change Bullhorn records, book Google Calendar interviews, or send a live report.

Illustrative sample data only: this page does not demonstrate live Bullhorn or Google Calendar integrations, change Bullhorn records, book Google Calendar interviews, or send a live report. Any live automation depends on confirmed supported systems, account access, and actual integration limits.

Current stage: 1 of 5 — Candidate intake

STAGE 01 / SAMPLE DATA

Candidate intake

A consistent starting record gathers the information a recruiter needs first.

Candidate
Maya Chen
Role
Senior Product Recruiter
Source
Sample referral
Status
New — pending recruiter review

Illustrative intake record — not a customer or candidate record.

RÉSUMÉ EVIDENCE EXCEPTION / FICTIONAL SAMPLE

An uncertain skill stays with the recruiter.

This static example shows how a résumé summary can surface an evidence gap without turning it into an automated candidate decision.

RÉSUMÉ SUMMARYFICTIONAL / SAMPLE DATA

Maya Chen — fictional candidate

Stated skill
Technical sourcing
Supporting evidence
Résumé summary does not contain clear supporting evidence for this skill.
REVIEW GATE

Held — recruiter review required

A human recruiter must review the résumé and decide what, if anything, should happen next.

The summary does not decide whether the candidate progresses. No live system is connected, and no candidate record is changed by this example.

CRM UPDATE EXCEPTION / FICTIONAL SAMPLE

A field mismatch holds the proposed update.

This static example surfaces a specific field issue instead of presenting a proposed Bullhorn update as successful or already applied.

PROPOSED CRM UPDATEFICTIONAL / SAMPLE DATA

Maya Chen — fictional candidate

Field
Employment type
Proposed value
Full-time
Field issue
Conflicts with the fictional résumé note: contract role.
Status
Held for correction
REVIEW GATE / HELD FOR CORRECTION

Recruiter approval is still required.

A human recruiter must verify the employment type, correct the proposed value, and approve the corrected update before anything could proceed.

Bullhorn — not connected. No real Bullhorn or CRM record was changed; this is a static fictional example only.

DECLINE BRANCH / FICTIONAL SAMPLE

A fictional recruiter can stop the sample path.

After reviewing the fictional candidate summary, a fictional recruiter decides not to advance the candidate. This static branch ends at that human decision.

  1. 01FICTIONAL SUMMARY / SAMPLE
    FICTIONAL / ILLUSTRATIVE

    Recruiter reviews the fictional candidate summary

    Candidate
    Maya Chen — fictional candidate
    Summary
    Sample résumé summary — illustrative only
    Reviewer
    Fictional recruiter — sample action
    Status
    Ready for fictional human review
  2. 02FICTIONAL DECISION / SAMPLE
    FICTIONAL / ILLUSTRATIVE

    Fictional recruiter decides not to advance

    Reviewer
    Fictional recruiter — sample action
    Decision
    Do not advance — fictional decision
    Reason
    Sample fit concern — illustrative rationale
    System state
    No live action taken — not live
  3. 03BRANCH ENDS / NOT LIVE
    FICTIONAL / ILLUSTRATIVE

    Decline branch stops here

    Bullhorn ATS/CRM
    No approved update — not live
    Interview
    Not scheduled — sample outcome
    Handoff
    None — illustrative stop state
    Persistence
    No write or integration — not live

Fictional, illustrative sample branch only: the recruiter decline is a static example. No approved Bullhorn ATS/CRM update is made, no interview is scheduled or handed off, and no live integration or persistent write occurs.

CANDIDATE WITHDRAWAL / FICTIONAL SAMPLE

A candidate withdrawal stops the sample path.

Before interview scheduling begins, a fictional candidate withdraws and a fictional recruiter confirms that the workflow should stop. This is a static illustrative branch.

  1. 01CANDIDATE WITHDRAWS / SAMPLE
    FICTIONAL / ILLUSTRATIVE

    Candidate withdraws before interview scheduling

    Candidate
    Avery Brooks — fictional candidate
    Action
    Candidate withdraws from consideration
    Timing
    Before any interview is scheduled
    Status
    Withdrawal received — sample event
  2. 02RECRUITER CONFIRMATION / SAMPLE
    FICTIONAL / ILLUSTRATIVE

    Recruiter confirms that the workflow should stop

    Reviewer
    Fictional recruiter — sample action
    Decision
    Stop the workflow
    Next step
    No interview handoff
    System state
    No live action taken — not live
  3. 03TERMINAL STATE / NOT LIVE
    FICTIONAL / ILLUSTRATIVE

    The withdrawal branch ends here

    Google Calendar
    No booking proposed or made
    Bullhorn ATS/CRM
    No update or CRM action
    Notifications
    None sent
    Persistence
    No record write or integration

Fictional, illustrative sample branch only: after the withdrawal, no Google Calendar booking or interview-scheduling handoff is proposed, no Bullhorn ATS/CRM update or other CRM action occurs, no notification is sent, and no record is written.

REFERRAL ORIGIN / ILLUSTRATIVE SAMPLE

A referral follows the same human-reviewed path.

Every candidate detail below is fictional sample data. The path moves from referral intake to résumé review, recruiter approval, and proposed next steps.

  1. 01REFERRAL INTAKE
    FICTIONAL / SAMPLE DATA

    Referral enters intake

    Candidate
    Avery Brooks — fictional sample
    Source
    Employee referral — sample origin
    Role
    Operations Recruiter — sample role
    Status
    Intake complete — review proposed
  2. 02RÉSUMÉ REVIEW
    FICTIONAL / SAMPLE DATA

    Résumé is prepared for review

    Résumé
    Fictional résumé summary
    Signal
    Sample sourcing experience
    Question
    Recruiter to verify details
    Status
    Human review — not submitted
  3. 03RECRUITER APPROVAL
    FICTIONAL / SAMPLE DATA

    Recruiter approves the next step

    Reviewer
    Fictional sample recruiter
    Decision
    Proposed to advance
    Gate
    Approval required first
    Record
    No live update made
  4. 04PROPOSED NEXT STEPS
    FICTIONAL / SAMPLE DATA

    Handoffs stay proposed

    Bullhorn
    Not connected — update proposed only
    Google Calendar
    Not connected — event proposed only
    Notification
    Not sent — sample next step
    Outcome
    Not scheduled or completed

Fictional sample data only: Bullhorn is not connected and Google Calendar is not connected. Any record update, calendar event, notification, or scheduling outcome shown here is proposed only — not live or completed.

WEEKLY REPORT / ILLUSTRATIVE PREVIEW

A quick read on movement and open loops.

SAMPLE DATA
WEEK OF / SAMPLEAug 12–16NOT CONNECTED
  • Candidate handoffs preparedREVIEW
    1 sample handoff

    Résumé summary queued for recruiter review.

  • Interview windows surfacedREADY TO REVIEW
    2 sample options

    Next step is ready for recruiter confirmation.

  • Open recruiter decisionsPENDING
    1 sample decision

    Candidate advancement remains with the recruiter.

  • Exceptions to resolveEXCEPTION
    1 sample conflict

    Calendar conflict needs a human check before any change.

Illustrative sample data only. These example outcomes and exceptions are not customer results. Live reporting depends on confirmed systems and appropriate account access.

CANDIDATE-INTAKE EXCEPTION / ILLUSTRATIVE SAMPLE

Missing information pauses the handoff.

When required candidate information is missing, the sample case is held for recruiter review before any Bullhorn candidate-record update is considered.

  1. 01INFORMATION MISSING

    Required information is missing

    Candidate
    Maya Chen
    Missing
    Work authorization status
    Status
    Held — recruiter review required
  2. 02RECRUITER REVIEW

    Recruiter reviews and approves

    Reviewer
    Human recruiter
    Decision
    Approved to proceed
    Gate
    Approval comes first
  3. 03APPROVED NEXT STEP

    Bullhorn update follows approval

    System
    Bullhorn ATS/CRM
    Action
    Proposed candidate-record update
    Connection
    Not connected or written

Illustrative sample data only: recruiter review and approval come first; this page demonstrates no automatic decision, live Bullhorn integration, or live record change.

THE HUMAN-REVIEW BOUNDARY

Rungbird prepares the handoff. Recruiters decide.

Résumé summaries are prepared for human recruiter review, and the agreed Bullhorn ATS/CRM candidate-record update follows recruiter approval. Recruiters remain responsible for screening, advancement, and hiring decisions; automated outputs do not make those decisions.

01 / REVIEW

Résumé summary for recruiter review

Rungbird prepares a concise résumé summary for a human recruiter to review. Automation does not make candidate-screening, advancement, or hiring decisions.

02 / APPROVAL

Bullhorn ATS/CRM update after approval

Only after recruiter approval is the agreed update prepared or applied to Bullhorn ATS/CRM. This illustrative sample does not change a live Bullhorn record.

Illustrative sample workflow only. No live Bullhorn integration is demonstrated here.

CALENDAR-CONFLICT EXCEPTION / ILLUSTRATIVE SAMPLE

A calendar conflict pauses scheduling.

A proposed interview time is flagged as conflicting and held while the recruiter reviews alternatives, approves one, and only then lets the schedule proceed.

  1. 01CALENDAR CONFLICT

    Proposed time is held for review

    Candidate
    Maya Chen
    Proposed time
    Tue 10:00
    Calendar check
    Conflict flagged
    Status
    Held — recruiter review
  2. 02RECRUITER REVIEW

    Recruiter reviews alternative times

    Reviewer
    Jordan Lee
    Alternatives
    Wed 14:30 · Thu 09:00
    Decision
    Wed 14:30 approved
    Gate
    Recruiter approval first
  3. 03APPROVED NEXT TIME

    Approved time proceeds to scheduling

    Interview
    Wed 14:30
    Google Calendar
    Not connected or live
    Booking
    Not made
    Notification
    Not sent

Illustrative sample data only: Google Calendar is not connected or live here. No booking, notification, or record change occurs; recruiter approval is the gate before any real scheduling is considered.

SERVICE SCOPE

Setup once. Support monthly.

Every pilot starts with fit confirmation and one-time workflow setup, then moves into an ongoing monthly service for the agreed scope.

  1. 01

    Scope the workflow

    We map the repeatable process, handoffs, decision points, and boundaries for the agency.

    SCOPE FIRST
  2. 02

    Confirm supported systems and appropriate access

    Before a live connection is considered, we confirm supported systems, required account access, and actual integration limits up front.

    FIT CHECK
  3. 03

    One-time workflow setup

    The one-time setup covers configuring the agreed administrative handoffs with clear human-review points.

    ONE-TIME SETUP
  4. 04

    Ongoing monthly service

    The monthly service covers monitoring, fixes, and defined improvements within the agreed scope—not unlimited changes or unconfirmed integrations.

    MONTHLY SERVICE

Live automation starts only after supported systems and appropriate access are confirmed. Until then, the scope is illustrative and not live.

Recruiters retain human judgment over candidate screening, hiring, and other consequential decisions. Rungbird supports the agreed administrative handoffs around those decisions.

PILOT FAQ

A few clear answers before we scope.

The boundaries matter as much as the workflow. Here is what to expect before anything moves toward a live setup.

The pilot has a $1,500 one-time setup fee and $500 per month for monitoring. It covers one agreed recruiting or staffing workflow, scoped with your agency before setup; it is not a promise to automate every process.

BEFORE ANYTHING GOES LIVE

Fit comes before automation.

Recruiters retain all candidate screening and hiring decisions. Any live Bullhorn or Google Calendar connection depends on confirming supported account access and actual integration limits; if the fit is not clear, the scope is not ready to run.

WORKFLOW SCOPING INTAKE

Start with the process,
not the credentials.

Tell us what repeats between Bullhorn and Google Calendar. Credentials are not required. Rungbird first confirms supported systems, confirmed account access, and actual integration limits for this workflow; only then can a live connection be considered.

A scoping request is not a live automation request, checkout, or payment action.

RUNGBIRD / SCOPE 01DISCUSSION + SCOPING ONLY

What would you like to make lighter?

This is a workflow-scoping intake, not a live connection request. Share the repeatable work between Bullhorn and Google Calendar; credentials are not required. Please do not send passwords, API keys, access tokens, or other secrets. Live automation depends on confirming supported systems, account access, and integration limits first.

A rough count or range is enough; exact numbers are not required.

Can access to the supported accounts be confirmed? (optional)

Optional. Leave this unanswered if you do not know yet. This only indicates whether access can be confirmed during scoping; it is not a request for passwords, API keys, access tokens, or other credentials. Live automation is considered only after supported systems and account access are confirmed.

START WITH ONE WORKFLOW

Bring us the handoff
that keeps repeating.

Tell us where the admin gets stuck. We’ll start with the process, then the tools.

Describe your workflow — no credentials