What does the Digital Recruiter agent do?

Screens and ranks applicants for an open order, then drafts bilingual outreach — you approve every step. Cuts time-to-fill and protects the 30-minute-callback promise without a coordinator glued to the ATS.

Does the Digital Recruiter agent act on its own?

It run on demand by a person; runs when an event arrives (webhook); runs its steps in order; every write waits for a person. In production every write to a connected system stops in an approval queue for a person to accept, modify or reject.

What can a Gmail (Google Workspace) domain agent actually do?

Once Google Workspace is connected, a domain agent can: search/list messages with the normal Gmail search syntax (e.g. "category:promotions newer_than:7d"), read a message, list labels, archive or label messages (single or up to 1000 at once), move a message to Trash, and send email. Archive means removing the INBOX label — the message stays searchable, it just leaves the inbox. These are grounded in the Gmail API, not simulated. Two notes: (1) it needs the gmail.modify scope, so if you connected Google Workspace before this was added, reconnect it (Tacit re-prompts consent). (2) To run automatically on incoming mail today, use a scheduled domain agent that searches recent messages and archives/labels them — a true "new email" push trigger is on the roadmap, not yet available.

How do I adapt a catalog agent to my work when I adopt it?

When you click Adopt, a short dialog opens with a “What should it do for you?” box. Describe your context in plain words — e.g. “Focus on enterprise renewals in North America, use our formal tone, flag any deal over $50k, and pull deal data from Salesforce.” We treat that as authoritative and build the agent around it (not a generic clone). If the agent works with interchangeable platforms, the same dialog asks which one you run. After you hit “Adopt & build”, we take you to the new agent so you can watch it build, then adapt → try it out → submit to IT for review. You can keep refining it any time by opening it or using “Ask for help with this”. (IT users who adopt see setup guidance instead: connect the tools, review, and approve.)

I adopted an agent from the catalog but it’s not in My agents — why?

Adopting builds the agent in the background (usually under a minute), so it appears shortly after, not instantly. While it’s building you’ll see a “Building…” banner on the My agents page, and you get a notification when it’s ready. If the build hit a temporary snag (e.g. the AI provider was briefly overloaded), that same page shows a “We hit a snag” message with a Retry button — one click rebuilds it. Nothing is lost in the meantime.

A catalog agent lists several platforms (Salesforce, SAP, Adobe Commerce, Shopify) — do I have to connect all of them?

No. Those show what the agent CAN work with — it adapts to whichever ONE your company runs (most companies have a single commerce/order platform). When you adopt it, a quick picker asks which platform you use and pre-selects the one we detect you’ve already connected; the agent is then built to use just that one. You never connect platforms you don’t use, and you can always tell it which to use in chat.

Digital Recruiter: AI agent for Staffing & workforce ops

What it does, step by step

Read the open job order and its role / shift / pay criteria
Pull and parse applicants from TempWorks
Screen for work-eligibility and certification gaps; honor screening holds
Rank candidates by fit (skill, availability, pay, reliability)
Propose a ranked shortlist with reasons — pause for your OK
Draft bilingual (EN/ES) outreach (SMS/email via TempWorks) — pause for your OK on first send
Answer applicant FAQs and book interviews / orientation
Log dispositions and next steps to TempWorks
Hand the placement to the Onboarding agent

Systems, trigger and oversight

Connects to: TempWorks
Trigger: run on demand by a person; runs when an event arrives (webhook)
How a person stays in control: Runs its steps in order; every write waits for a person. In production every write to a connected system stops in an approval queue for a person to accept, modify or reject; the corrected version is what executes.
Industry: Staffing & light industrial

Adopt it, then adapt it

A catalog agent is a working starting point, not a black box. When you adopt it, tacitrun stands up a draft in your workspace with these steps as its process, and you adapt the rules, the fields and the systems to how your team actually works. It is then tested against cases derived from that process, run in shadow beside your team, and approved by your IT before it can act. You choose your industry and what to adopt during onboarding; nothing is adopted for you.

Questions people ask

What can a Gmail (Google Workspace) domain agent actually do?: Once Google Workspace is connected, a domain agent can: search/list messages with the normal Gmail search syntax (e.g. "category:promotions newer_than:7d"), read a message, list labels, archive or label messages (single or up to 1000 at once), move a message to Trash, and send email. Archive means removing the INBOX label — the message stays searchable, it just leaves the inbox. These are grounded in the Gmail API, not simulated. Two notes: (1) it needs the gmail.modify scope, so if you connected Google Workspace before this was added, reconnect it (Tacit re-prompts consent). (2) To run automatically on incoming mail today, use a scheduled domain agent that searches recent messages and archives/labels them — a true "new email" push trigger is on the roadmap, not yet available.
How do I adapt a catalog agent to my work when I adopt it?: When you click Adopt, a short dialog opens with a “What should it do for you?” box. Describe your context in plain words — e.g. “Focus on enterprise renewals in North America, use our formal tone, flag any deal over $50k, and pull deal data from Salesforce.” We treat that as authoritative and build the agent around it (not a generic clone). If the agent works with interchangeable platforms, the same dialog asks which one you run. After you hit “Adopt & build”, we take you to the new agent so you can watch it build, then adapt → try it out → submit to IT for review. You can keep refining it any time by opening it or using “Ask for help with this”. (IT users who adopt see setup guidance instead: connect the tools, review, and approve.)
I adopted an agent from the catalog but it’s not in My agents — why?: Adopting builds the agent in the background (usually under a minute), so it appears shortly after, not instantly. While it’s building you’ll see a “Building…” banner on the My agents page, and you get a notification when it’s ready. If the build hit a temporary snag (e.g. the AI provider was briefly overloaded), that same page shows a “We hit a snag” message with a Retry button — one click rebuilds it. Nothing is lost in the meantime.
A catalog agent lists several platforms (Salesforce, SAP, Adobe Commerce, Shopify) — do I have to connect all of them?: No. Those show what the agent CAN work with — it adapts to whichever ONE your company runs (most companies have a single commerce/order platform). When you adopt it, a quick picker asks which platform you use and pre-selects the one we detect you’ve already connected; the agent is then built to use just that one. You never connect platforms you don’t use, and you can always tell it which to use in chat.

Why offload this process to tacitrun’s AI operating layer

tacitrun is built for exactly this handoff: a business team describes the process it already runs, and the platform turns it into governed domain agents that work across the systems you have, under your IT’s approval, with every write waiting for a person.

Built from your procedure, not a vendor template: Describe the process in plain English or hand over the SOP. tacitrun compiles it into a process graph and composes one domain agent per step, so the agents carry your rules, your exceptions and your vocabulary.
Tested against the process before it can act: Evaluation cases are derived from the graph itself, so a passing agent is one that does what your process says. Then it runs in shadow beside your team on real work before anyone lets it act.
Every write stops for a person: The approval gate sits on the actual call to Salesforce, Shopify, SendGrid, SAP or any connected system. A person accepts, modifies or rejects; the corrected version is what executes; the trace keeps the record.
Runs across the systems you already have: Built-in connectors, your own REST APIs or MCP servers, and on the Enterprise plan your own cloud project and your own models. The systems of record stay where they are; the layer does the work between them.
IT approves, business leads: Business users build and prove; IT connects the credentials, binds the fields and approves before anything goes live. Neither side inherits the other’s risk.

Start free →Talk to us Book a demo

More agents for Staffing & workforce ops

Digital Scheduler / Dispatcher — Fills open and called-off shifts with eligible, compliant workers and confirms coverage with the client.
Onboarding Agent — Runs a new placement through a bilingual onboarding checklist and document collection.
Timecard & Payroll-Q&A Agent — Reconciles timecards against schedules pre-payroll and answers worker pay questions from tenant data.
HR Agent (bilingual) — Answers worker PTO / benefits / policy questions in English or Spanish, grounded in the tenant's handbook.
Safety & Compliance Agent — Tracks cert/training expiry and IL Day & Temp Labor Act obligations, and drafts required notices for sign-off.
All Staffing & workforce ops agents →