The conversation
I’m interested in the analyst position. What happens next?
I can walk you through the role and collect the job-related screening details.
James is UnleashX’s AI Recruiter. James autonomously screens candidates against your job-related criteria, answers recruitment questions, schedules interviews and updates candidate records. Routine actions run within your configured knowledge, permissions and business rules; exceptions and decisions outside that authority go to your team with context.
Autonomous execution within your rules. Human handoff when required, not at every step.
100+ system integrations · SOC 2 and ISO 27001 · Information security standards
JAMES AT WORK
James autonomously screens candidates against your job-related criteria, answers recruitment questions, schedules interviews and updates candidate records. Switch to an exception to see when, and why, your team steps in.
I’m interested in the analyst position. What happens next?
I can walk you through the role and collect the job-related screening details.

Capture job-related screening answers
Capture job-related screening answers
Step 1 of 4 · Screen
Example sequence only. Channels, integrations and permitted actions are configured and validated for your deployment.
SELF-SERVICE SETUP
Sign up and make this pre-built role your own. Prepare your approved knowledge, business rules, system access and escalation owner before launch.
ROLE CONFIGURATION
YOUR ROLE BRIEF
A defined scope for James to work within.
Create your account, then configure your employee in UnleashX. This preview does not save settings or connect systems.
THE JOB TO BE DONE
Hire James to own the routine work, not just recommend the next step. James screens candidates against your job-related criteria, answers recruitment questions, schedules interviews and updates candidate records, without step-by-step supervision. Your team sets the rules and handles hiring decisions, candidate scoring policy and employment offers.
Hiring decisions, candidate scoring policy and employment offers stay with authorized people in the scope described here.
Define James’s knowledge, system permissions and business rules before launch. James executes within that scope autonomously. The examples illustrate the workflow; they are not measured customer results.
FROM REQUEST TO RECORDED RESULT
Starting with an application or eligible candidate record, James runs these steps autonomously within your configured permissions and business rules. Routine work does not wait for manual approval. Exceptions and unverified outcomes follow the agreed recovery or human-handoff path.
Work from the current requisition, job-related questions and approved candidate communication.
Ask the agreed questions and record answers faithfully. Do not infer sensitive attributes or fill gaps with assumptions.
Explain the published role and next steps, separating confirmed details from questions for the recruiter.
Coordinate candidate and interviewer availability, including timezone and rescheduling rules.
Attach the screening record, questions and scheduling outcome to the recruitment system.
HUMAN HANDOFF
A handoff should explain the request, completed steps and unresolved decision. Do not make customers repeat information already captured, or leave a failed operation without an owner.
DESIGN THE DIFFICULT CASES
Use these role-specific cases when reviewing the workflow with business and technical owners. The expected behavior must be agreed before a pilot, not inferred after something fails.
Route to the designated recruiting contact without making assumptions about eligibility.
Review: Assigned request and privacy-appropriate handoff.Preserve the response and flag it for review instead of forcing an unsupported score.
Review: Original answer and reviewer task.Offer a permitted alternative or route scheduling assistance.
Review: Verified attendees and calendar outcome.SYSTEMS & PERMISSIONS
Agree the exact records, fields and operations needed for James’s role. Reading context and changing a record are different permissions. The categories below are the requirements map for this role. Scoping confirms the exact reads and writes against your systems.
| System category | Workflow use | Review before connecting |
|---|---|---|
| Applicant tracking system | Read requisitions and candidate stage; record screening and next action. | Field access, retention and candidate-record ownership. |
| Calendars | Coordinate panel availability and invitations. | Timezone, cancellation and attendee confirmation. |
| Recruiting knowledge | Explain role details and hiring steps. | Approved questions, versioned briefs and recruiter escalation. |
Bring system names, versions, API documentation and test-environment access. Review identity matching, retention, network boundaries, credential ownership and how an ambiguous write is reconciled.
Explore integration requirementsPILOT EVIDENCE
Choose an eligible cohort and record the current baseline. Keep successful conversations, verified outcomes and unresolved exceptions separate. Define a review sample that includes normal cases as well as failed tools and difficult customer requests.
Reviewed summaries that match the candidate’s actual answers.
Interviews with correct attendees, timezones and confirmed invitations.
Open candidate cases with an explicit next step and responsible recruiter.
| Test case | Expected behavior | Evidence to inspect |
|---|---|---|
| Candidate requests accommodation | Route to the designated recruiting contact without making assumptions about eligibility. | Assigned request and privacy-appropriate handoff. |
| Answer does not fit the screening form | Preserve the response and flag it for review instead of forcing an unsupported score. | Original answer and reviewer task. |
| Interviewers are unavailable | Offer a permitted alternative or route scheduling assistance. | Verified attendees and calendar outcome. |
Agree thresholds before testing, then measure verified outcomes, action accuracy and time saved against your baseline.
Review the evaluation approachIMPLEMENTATION GATES
Pre-built means the role is a starting point. It runs alongside knowledge review, integration mapping and your organization’s release decision.
Define eligible cases around this trigger: an application or eligible candidate record. Agree what counts as a complete screening handoff and verified interview or follow-up and which requests are excluded.
Output: approved role brief and named business owner.Map required fields and approved knowledge to the systems listed above. Separate read permissions from writes, test identity matching and document failure recovery.
Output: reviewed access and data-flow map.Exercise the normal journey and the exception cases on this page. Inspect responses, system actions and final records together, with a reviewer for unresolved results.
Output: acceptance record and documented open issues.Start with limited traffic, monitoring ownership and stop conditions. Review the first outcomes before expanding scope; keep a way to pause work and return it to people.
Output: rollout, support and recovery plan.Estimate the timeline from actual dependencies. Confirm privacy, contact requirements and decision authority with the relevant internal owners. Deployment design is not a substitute for their review.
BUYER GUIDANCE
Hire James to own the routine work, not just recommend the next step. James screens candidates against your job-related criteria, answers recruitment questions, schedules interviews and updates candidate records, without step-by-step supervision. Your team sets the rules and handles hiring decisions, candidate scoring policy and employment offers.
The input is structured, the action is fixed and there is no ambiguity to clarify. A form, notification or rule-based workflow can be the appropriate tool. Do not add a conversational role solely to perform a deterministic system update.
You want routine work executed end to end, without supervising each action. Keep the outcome explicit: a complete screening handoff and verified interview or follow-up. Validate that the configured role can meet that outcome under your constraints.
The case requires hiring decisions, candidate scoring policy and employment offers. The AI employee can prepare information and route the request without assuming decision authority.
The job spans several distinct responsibilities or the pre-built brief does not fit. Define separate roles only where the coordination adds value, and give each handoff a clear owner.
Explore the custom pathBUYER & IMPLEMENTATION QUESTIONS
No. Once knowledge, system access and business rules are configured, James autonomously screens candidates against your job-related criteria, answers recruitment questions, schedules interviews and updates candidate records. Human handoff is required for hiring decisions, candidate scoring policy and employment offers, or an unresolved case outside the configured rules. The handoff includes the request, completed actions and the decision needed.
No final hiring authority is included in this role. Recruiters and hiring managers review the evidence and make decisions under your recruitment process.
Yes, provide a reviewed, job-related question set and clear handling for incomplete or ambiguous answers. Do not treat inferred personal characteristics as screening evidence.
Define cancellation, panel availability and reminder behavior. Update the recruitment record and verify the replacement event so the candidate does not receive conflicting invitations.
James autonomously screens candidates against your job-related criteria, answers recruitment questions, schedules interviews and updates candidate records. Routine actions run within your configured knowledge, permissions and business rules; exceptions and decisions outside that authority go to your team with context. The workflow starts with an application or eligible candidate record and is designed around this outcome: a complete screening handoff and verified interview or follow-up. Agree the actual configuration and supported actions before release.
Yes. Sign up for UnleashX and configure James yourself. Prepare your approved knowledge, business rules, system access and exception owners. Test the configured workflow before using live traffic; supported connections and actions depend on your setup.
Use the role as a starting brief. Define your knowledge sources, required fields, permitted actions and escalation paths. Keep hiring decisions, candidate scoring policy and employment offers outside automatic authority unless a separately reviewed workflow explicitly defines the relevant permissions.
Connector availability depends on your systems and required operations. Confirm your vendors, versions, API operations and network requirements with the integration team. Document read and write access separately and test system failures before production.
Estimate the schedule after reviewing scope, data readiness, integration access and approval requirements. Agree milestone owners and dependencies. Configuration, security review and evaluation are part of every deployment.
Define bounded retries, result reconciliation and human recovery for every write. A timeout can leave the outcome uncertain: inspect the destination record before retrying an action that could create a duplicate. Keep unresolved work visible with an owner.
Agree the workflow’s baseline, eligible cases and measurement period. Track verified completion, unresolved work, human review and operating cost using your source records.
Configure James’s knowledge, connect your supported systems and test the journey. You decide the scope before live work begins.
Sign up

















CUSTOMER REVIEWS ON G2