Recruitment administration now has one governed route across records, research and outreach, with voice automation staged behind explicit launch gates.

Care Networks needed relief from clinic research, record work and follow-up, but healthcare recruitment is not a place for a vague promise of autonomous calling. RECAST built the administrative operating layer, made each provider's authority explicit and separated the working recruitment lanes from a staged clinic-outreach pilot.

Evidence at publication: JobAdder helper paths and separated provider routes were built and checked; the client supplied an approved quote; the voice lane remains conditional on its phone, caller ID, script, pilot list and webhook decisions.

The company

Jane Benjamin operates Care Networks in healthcare recruitment. Her team works across clinics, doctors, locums, radiologists, practice managers and recruitment contacts. The daily system includes JobAdder, Gmail, Search Console, Calendly, calendars, spreadsheets and internal follow-up.

The work is high-context by nature. A useful outreach action may require knowing whether a clinic already exists in the recruitment system, who the relevant contact is, what was learned in prior research and whether a human should review the next message or call.

The constraint

Clinic research, record creation, recruitment outreach, JobAdder updates and email follow-up could all be performed manually. Growth made the handoffs between them the bottleneck.

The dangerous failure was false certainty. JobAdder required native API/OAuth helpers, not browser improvisation. Gmail and Search Console used separate tool routes. Voice could not be treated as live simply because an ElevenLabs agent existed. If the system checked the wrong connection or skipped a launch dependency, it would create more supervision work rather than less.

Why existing tools were not enough

The tools did not agree on a single route. A generic assistant could say JobAdder was disconnected because it looked in the wrong provider, overwrite one account route while configuring another, or prepare a call without the approved caller identity and post-call record.

The missing operating layer had to encode which system was authoritative, give each provider connection an independent route, preserve distilled recruitment context and make the voice pathway conditional. In this case, control is part of the product.

Transformation map

Before

Clinic research | JobAdder | Gmail | Calendly | Sheets -> manual cross-check -> outreach -> manual follow-up

After - live and supervised lanes

Research request -> authoritative provider route -> JobAdder confirmation -> outreach preparation -> Jane/team review -> record and follow-up

Staged voice lane

Approved phone + caller ID + script + pilot list + webhook policy -> limited clinic pilot -> structured call record -> human recruitment follow-up

The second route is intentionally shown as staged. It is not described as normal production calling.

One workflow, end to end

1. Input: A clinic or recruitment-contact research task enters the Care Networks workspace.
2. Authority check: The assistant uses the native JobAdder helper for recruitment records and the dedicated Tool Router for the relevant Google or scheduling account.
3. Context assembly: Existing records, clinic research and prior follow-up are brought into one working context.
4. Preparation: The system prepares the outreach material, record update or calling-agent script required for the next step.
5. Human gate: Jane or her team reviews the consequential outreach action. Voice cannot launch broadly until the pilot's phone number, caller ID, script, list and webhook decisions are approved.
6. Output: The approved administrative action is coordinated through the correct provider route; a future pilot call would return a structured result rather than an untracked conversation.
7. Record: JobAdder/Discord follow-up and distilled memory preserve what happened for the next recruiter.

What changed

• Built: Recruitment-operation helpers, provider-status tools, an ElevenLabs clinic recruitment agent, pilot scripts, dry-run commands and a structured voice-bridge pattern.
• Connected: JobAdder's native OAuth path, dedicated Gmail/Search Console routing, Calendly, calendar and spreadsheet routes, plus ElevenLabs configuration.
• Tested: JobAdder status behavior, separated account routes, agent and voice status tools, pilot-script preparation and outbound dry-run paths.
• Verified live: Recruitment administration and integration coordination are the evidenced working lanes. This case does not label broad outbound voice as verified live.
• Actively used: The retained source supports live administrative capability, not a quantified volume of routine recruiter usage.
• Provider or client dependency remaining: The clinic-calling lane still requires approved phone-number, caller-ID, script, pilot-list and webhook decisions before normal operation.
• Financial result reported by client: None retained.

Proof

• Authoritative record path: JobAdder native OAuth helpers were connected and documented.
• Account isolation: Separate provider routes were created for Gmail/Search Console, Calendly, an additional Gmail account, Calendar and Sheets.
• Voice readiness: An Australian-toned ElevenLabs recruitment agent, structured data fields and dry-run tools were created.
• State clarity: Live recruitment administration is separated publicly from the gated voice pilot.
• Client corroboration: Jane's exact approved remark is retained in the claims ledger.

Technology - revealed last

The system runs on a Mac mini with OpenClaw, Discord, gbrain, JobAdder native OAuth helpers and separated Composio Tool Router sessions for Gmail, Search Console, Calendly, Calendar and Sheets. ElevenLabs hosts the staged clinic recruitment agent with its configured voice, privacy settings and structured data fields. The provider routes remain separate so connecting one account does not silently overwrite another.

Client quote

“It’s brilliant. Like a game changer.”

• Jane Benjamin, Care Networks. Exact wording and publication approval are recorded in the claims ledger; “game changer” is the client's wording, not RECAST narration.

Next transformation

See how Linda's Care put a production voice bridge between new leads and a human closer. It shows the later-stage calling architecture without implying that two healthcare businesses share the same data model or qualification rules.

Get your AI blueprint

If growth is turning recruitment administration into a chain of manual checks, start by identifying the authoritative record, the human decision and the evidence every action must leave behind. Book a free AI audit to map it.

Source record

• OPENCLAW-DEEP-CLIENT-CASE-STUDIES.pdf, page 9.
• RECAST_CASE_STUDIES_2026_UPDATED.pdf, page 5, document RA-CASES-001, version 2.0.
• RECAST_WEBSITE_MASTER_BLUEPRINT.md, sections 6.5, 10.4, 11 and 58.