Skip to content
UnleashX
Login

Hire James.
Move candidates forward. Without the admin.

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.

Sign up

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

From candidate interest to recruiter-ready context.

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.

Worked example

The conversation

CUSTOMER REQUEST

I’m interested in the analyst position. What happens next?

JAMES

I can walk you through the role and collect the job-related screening details.

Conversation → structured context
James

James

Capture job-related screening answers

Autonomous · within your rules
ATS + calendar
People join only when needed

Candidate brief

WORK RECORD
  • Requisition · analyst
  • Screening · answers recorded
  • Availability · candidate supplied
SYSTEM ACTION

Capture job-related screening answers

Awaiting workflow steps

Step 1 of 4 · Screen

Example sequence only. Channels, integrations and permitted actions are configured and validated for your deployment.

SELF-SERVICE SETUP

You configure James.
James gets to work.

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

Define the job

YOUR ROLE BRIEF

Starts with
An application or eligible candidate record
Works toward
A complete screening handoff and verified interview or follow-up
First responsibility
Read the role brief
Human authority
Hiring decisions, candidate scoring policy and employment offers

A defined scope for James to work within.

Sign up

Create your account, then configure your employee in UnleashX. This preview does not save settings or connect systems.

THE JOB TO BE DONE

A clear responsibility.
A verifiable outcome.

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.

Work James executes autonomously

  • Read the role brief
  • Gather screening information
  • Clarify the process
  • Schedule the interview
  • Prepare recruiter review

Your team handles the exceptions

Hiring decisions, candidate scoring policy and employment offers stay with authorized people in the scope described here.

  • Use approved knowledge instead of guessing an answer.
  • Separate customer intent from a confirmed system result.
  • Assign unresolved work to a named team.
  • Test policy changes before expanding responsibility.

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

How James executes the work.

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.

  1. 01

    Read the role brief

    Work from the current requisition, job-related questions and approved candidate communication.

    Information needed
    Role requirements, process stage and recruiting ownership.
    What moves forward
    A candidate interaction aligned with the actual open role.
  2. 02

    Gather screening information

    Ask the agreed questions and record answers faithfully. Do not infer sensitive attributes or fill gaps with assumptions.

    Information needed
    Candidate record and structured screening guide.
    What moves forward
    An evidence-based summary with unanswered questions visible.
  3. 03

    Clarify the process

    Explain the published role and next steps, separating confirmed details from questions for the recruiter.

    Information needed
    Approved job information and recruitment timeline.
    What moves forward
    A candidate who knows what happens next.
  4. 04

    Schedule the interview

    Coordinate candidate and interviewer availability, including timezone and rescheduling rules.

    Information needed
    Calendar access, panel requirements and candidate preferences.
    What moves forward
    A verified interview event with the correct participants.
  5. 05

    Prepare recruiter review

    Attach the screening record, questions and scheduling outcome to the recruitment system.

    Information needed
    Candidate answers and confirmed system results.
    What moves forward
    A reviewable handoff to the recruiter or hiring team.

HUMAN HANDOFF

When an exception needs a person, send the full context.

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.

  • Customer and source-record references
  • The customer’s stated request or concern
  • Completed actions and verified results
  • Unresolved questions and exception reason
  • Relevant knowledge or policy version
  • Assigned team and the next decision needed

DESIGN THE DIFFICULT CASES

Exceptions need a path, not a success message.

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.

Candidate requests accommodation

Route to the designated recruiting contact without making assumptions about eligibility.

Review: 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.

Review: Original answer and reviewer task.

Interviewers are unavailable

Offer a permitted alternative or route scheduling assistance.

Review: Verified attendees and calendar outcome.

SYSTEMS & PERMISSIONS

Connect the work to the source of truth.

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.

Integration requirements for James
System categoryWorkflow useReview before connecting
Applicant tracking systemRead requisitions and candidate stage; record screening and next action.Field access, retention and candidate-record ownership.
CalendarsCoordinate panel availability and invitations.Timezone, cancellation and attendee confirmation.
Recruiting knowledgeExplain 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 requirements

PILOT EVIDENCE

Measure the result.
Inspect the failures.

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.

Screening fidelity

Reviewed summaries that match the candidate’s actual answers.

Scheduling correctness

Interviews with correct attendees, timezones and confirmed invitations.

Candidate follow-through

Open candidate cases with an explicit next step and responsible recruiter.

Workflow acceptance criteria
Test caseExpected behaviorEvidence to inspect
Candidate requests accommodationRoute to the designated recruiting contact without making assumptions about eligibility.Assigned request and privacy-appropriate handoff.
Answer does not fit the screening formPreserve the response and flag it for review instead of forcing an unsupported score.Original answer and reviewer task.
Interviewers are unavailableOffer 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 approach

IMPLEMENTATION GATES

Prepare the workflow before production.

Pre-built means the role is a starting point. It runs alongside knowledge review, integration mapping and your organization’s release decision.

01

Scope

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.
02

Connect

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.
03

Evaluate

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.
04

Release

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

Choose the right level of responsibility.

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.

Use simpler automation when…

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.

Consider James when…

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.

Keep a human in charge when…

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.

Build a custom workforce when…

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 path

BUYER & IMPLEMENTATION QUESTIONS

What to know before hiring James.

Does James need human approval at every step?

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.

Does James decide who gets hired?

No final hiring authority is included in this role. Recruiters and hiring managers review the evidence and make decisions under your recruitment process.

Can we use our screening questions?

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.

What happens if a candidate reschedules?

Define cancellation, panel availability and reminder behavior. Update the recruitment record and verify the replacement event so the candidate does not receive conflicting invitations.

What does James do?

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.

Can I set up James myself?

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.

Can we customize James for our business?

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.

Are the listed integrations available out of the box?

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.

How long will deployment take?

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.

What happens when a system fails?

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.

How do we measure the employee’s impact?

Agree the workflow’s baseline, eligible cases and measurement period. Track verified completion, unresolved work, human review and operating cost using your source records.

Make James part of
your workflow.

Configure James’s knowledge, connect your supported systems and test the journey. You decide the scope before live work begins.

Sign up
Hiring workflowsDeployment readinessAll AI employees
Aye Finance
Bajaj Capital
eMSME
Shyama Power
MedoPlus
Gullybaba
ICOFP
Sapio Analytics
Ostello
OnGrid
Black Kite Foundation
AAFM
Regus Automobiles
Karma Hyundai
Codestax
AksEdge
Tiger FinTech
Coneon
Xoxoday
Blu Parrot
Edgy Scribblers
NxG
V2C

CUSTOMER REVIEWS ON G2

From conversations to completed work.

4.9/ 5
  • End-to-end automation

    We’ve deployed UnleashX across a genuinely wide range of use cases, rather than relying on a single narrow bot.
    Nitin J.SVP, Head of EngineeringEnterprise (> 1,000 employees)
1 / 7