---
title: "Deploy recruiting with evidence. | afka"
description: "Set up the role, run a candidate conversation and deliver a reviewable handoff. Keep the hiring decision with the team."
url: "https://afka.ai/playbooks/recruiting"
lang: "en"
---

Deployment playbook / Recruiting

# Deploy recruiting with evidence.

Set up the role, run a candidate conversation and deliver a reviewable handoff. Keep the hiring decision with the team.

[← All playbooks](https://afka.ai/playbooks) afka resources · Practical guidance

**On this page**

01 · Agree the outcome 02 · Prepare knowledge and access 03 · Set the boundaries 04 · Run the first workflow together 05 · Check the result, including the exception 06 · Keep the next promise on track 07 · Extend to the places work happens 08 · Leave a process the team can run

## 01 · Agree the outcome

A hiring team handling repeated first conversations, scheduling and scattered candidate notes.

Choose one repeated workflow with the team. Write down the trigger, the result, who owns an exception and how the team will verify that the work is finished. Keep the first deployment narrow enough to inspect together.

## 02 · Prepare knowledge and access

- Role requirements and evaluation criteria approved by the hiring lead.
- An interview guide, candidate communication rules and the information candidates may see.
- The ATS and calendars needed for the agreed workflow, with the right people and permissions.

Keep role criteria and internal hiring guidance scoped to the hiring team. Only candidate-facing information belongs in the candidate conversation.

Add and maintain knowledge in the web app. Use company, group and personal scopes deliberately. Connect the client’s own accounts through the approved connection flow; do not collect their passwords.

## 03 · Set the boundaries

Name the people who can approve sensitive actions, maintain knowledge and review the audit record. Set the agent’s autonomy for this workflow and identify the actions that must wait for a person.

Harm detection and prevention hold actions that could hurt the company for the workspace owner or admin. A request in chat, Talk or a meeting does not remove permissions or approval gates.

## 04 · Run the first workflow together

Run a candidate voice interview against the role criteria. Review the transcript and cited evidence, then prepare the handoff and scheduling step in the connected tools.

What the client should see

The original request, the information used, the action taken or held, and the delivered result. Review the work in the connected system as well as the conversation.

## 05 · Check the result, including the exception

| Check | Acceptance condition |
| --- | --- |
| Evidence | Each assessment points to what the candidate actually said. Missing evidence is marked for review. |
| Candidate experience | The invitation, browser interview and next-step message are clear and consistent with the role. |
| Decision boundary | Rejection, offer and other consequential hiring decisions remain with the authorized person. |
| Handoff | The hiring lead receives the evidence and the next owner, without re-entering the interview notes. |

Also test missing information, an expired connection and a request outside the person’s access. The client should know what afka asks, what it declines and where a person takes over.

## 06 · Keep the next promise on track

A hiring manager promises feedback after the interview. afka reminds them privately before the deadline. If they move the date in advance, the new date is carried forward without a slip.

Enable Follow-through for the agreed sources and give members a clear notice. Reminders arrive in the tools people already use and in existing Notifications. Use Done, New date, Blocked and Not mine. A date moved in advance is never a slip.

After the grace period, the owner receives a slipped commitment with its evidence and the person’s response. The person sees the same information. There is no leaderboard, productivity score or activity surveillance.

## 07 · Extend to the places work happens

When the client has frontline operations, start with one site and one report type. Talk lets a worker speak or type, add a photo and confirm the important details. afka opens an owned case and routes urgent issues through the configured escalation path.

- [Transport](https://afka.ai/industries/transport) : A driver reports a breakdown or delivery problem in Talk.
- [Logistics](https://afka.ai/industries/logistics) : A warehouse worker reports damaged goods, equipment trouble or a receiving discrepancy.
- [Manufacturing](https://afka.ai/industries/manufacturing) : An operator reports a machine fault or material shortage.
- [Hospitality](https://afka.ai/industries/hospitality) : Housekeeping reports a room repair or missing amenities.
- [Restaurants](https://afka.ai/industries/restaurants) : A team member reports equipment failure, a supply issue or a guest incident.
- [Field services](https://afka.ai/industries/field-services) : A technician reports a completed job, a missing part or blocked access.

Use the site’s own instructions and escalation owners. Keep sensitive knowledge with staff, and let safety decisions stay with the responsible person.

## 08 · Leave a process the team can run

- Deliver the agreed workflow, connected accounts and knowledge sources.
- Record the approval owners, escalation route and the person responsible for updates.
- Leave one successful result and one correctly handled exception as examples.
- Show the team how to pause the agent, inspect the audit trail and reconnect an expired account.
- Agree a review rhythm for recurring exceptions, stale knowledge and work still awaiting a person.

Use what the team learns to improve approved knowledge and workflow instructions. afka carries useful context from previous work forward within the same access boundaries. This is not a promise to train a shared model on the client’s data.

Security questions deserve a precise answer.

Explain workspace isolation, scoped permissions, protected credentials and the audit trail. afka is not currently SOC 2 certified. Use the [security overview](https://afka.ai/security) for the controls and current limits.

[Explore the workflow](https://afka.ai/for/recruiting) [Partner program & terms ↗](https://afka.ai/deployers)

## Build a working deployment.

Start with one team, one process and clear approval rules.

[Start free](https://app.afka.ai/signup) [Book a demo](https://afka.ai/book-demo)
