An AI voice agent knowledge base for recruitment should contain approved answers the agent is allowed to give, the source behind each answer, its scope and the point when it must be checked again. Keep general agency information separate from vacancy conditions. When a fact is missing, disputed or out of date, the call should produce a specific recruiter question instead of a guessed answer.
For a staffing agency, this is an editorial responsibility as much as a technical setup. A fluent answer about an old shift pattern can create more repair work than a straightforward admission that the recruiter needs to confirm it. The process below helps an operations manager prepare and maintain content for candidate calls. The controls are requirements to agree with an implementer, not features assumed to exist in every system.
Start with questions candidates actually ask
Ask recruiters to list recurring questions from ordinary desk work. Remove personal details before using examples. Group the questions by subject: contacting the agency, completing registration, understanding a specific vacancy and checking an individual application.
Choose a small first scope. General opening hours and how to request a callback are easier to maintain than constantly changing availability of jobs or accommodation. Include a question only when a named person can approve an answer and keep it current.
A knowledge base is not the entire recruitment database. CVs, private client notes and another candidate's application history do not belong in a shared answer collection. Candidate-specific questions need the agreed identity checks and access controls, or a recruiter handoff, rather than a broader search through documents.
Give every answer a usable source record
Write each entry as a compact answer card. It should contain the candidate's likely question, an approved spoken answer, its source, the relevant vacancy or branch, the content owner and its review date. Also record what the answer does not establish.
For example, an approved description of a shift's hours does not establish that there is still an open place on that shift. A description of the agency's registration process does not establish that a particular candidate has completed registration. Write these boundaries beside the answer so reviewers can spot misleading implications.
Use a clear publication state: draft, approved or withdrawn. A review date creates work for the owner; it should not silently extend the answer's validity. If the configured system cannot exclude withdrawn content, resolve that limitation before relying on it for changing vacancy facts.
Separate stable guidance from changing vacancy facts
Agency information
Keep approved contact routes, office details and general process explanations together. They still need an owner, especially around planned office closures or changes to the registration journey. Avoid embedding the same phone number in many unrelated answers where it becomes hard to update consistently.
Vacancy information
Tie every job-specific answer to the correct vacancy and location. A night shift at one warehouse must not become the default answer for another role with a similar title. If the caller cannot identify the vacancy, ask a clarifying question or collect the enquiry for a recruiter.
Individual commitments
Do not turn general job information into an offer, guaranteed start or guaranteed accommodation. Questions about the caller's agreed arrangements need a confirmed, appropriate source or human follow-up. Distinguish “this vacancy lists an evening shift” from “you are booked for the evening shift.”
Write for a conversation, then review each language
An answer that reads well on a page may be awkward on the phone. Start with the direct answer, add one necessary condition and offer the next step. Break complicated information into a short exchange rather than asking the caller to remember a long paragraph.
For a Dutch logistics enquiry, use the site's actual terms for shifts and locations. For Polish-speaking candidates, distinguish a general description of zakwaterowanie from confirmation that accommodation has been arranged for them. Spanish content needs its own fluent reviewer if Spanish calls are in scope; an English approval is not sufficient.
Keep all language variants attached to the same underlying fact. A vacancy change should mark affected translations for review. If one language is not ready, use an approved uncertainty response in that language rather than continuing to read an older promise.
Handle a changed answer from source to phone call
Consider a fictional vacancy where the client changes the reporting location. The account manager confirms the new site. The content owner identifies all answer cards that mention the previous site, including directions and translated location descriptions.
Withdraw those answers until the replacements are approved. Then publish the revised content and make a controlled call in each affected language. Ask about the old location as well as the new one. Inspect which answer is actually available to the agent, rather than assuming that editing the source document instantly updates the live system.
Record the publication time and responsible reviewer. If callers may have received the old instructions during the change, give a recruiter the affected enquiries to review through the agency's agreed process. The broader vacancy change workflow covers the staffing response; this step controls the answers available on the phone.
Make uncertainty useful to the recruiter
An appropriate fallback might be: “I do not have a confirmed answer about transport for that vacancy. I can pass the question to the recruitment team.” Use wording that matches the actual handoff, without promising a booking or response time the setup cannot support.
The handoff should preserve the question, the vacancy reference if known, the language and the missing or conflicting fact. “Candidate needs help” is too vague. “Asks whether transport reaches the new evening-shift location; no approved answer available” gives the recruiter a concrete next action.
Review repeated unanswered questions. Add an approved entry when the answer is sufficiently stable and useful. Some questions should remain with recruiters because they depend on individual circumstances; repeated frequency alone is not a reason to automate them.
Common mistakes and a maintenance checklist
Uploading the whole website without checking outdated pages can introduce competing answers. Copying client emails directly can mix tentative requests with approved conditions. Leaving translated answers unreviewed creates different promises across languages. Treating the newest document as automatically authoritative bypasses the person responsible for confirming the facts.
Use this short checklist before an answer is made available:
- A named owner has approved the answer and its source.
- Its branch, vacancy and language scope are explicit.
- Review dates and withdrawal behaviour are agreed.
- General information cannot be mistaken for an individual commitment.
- Each launched language has a fluent reviewer.
- A missing answer creates a specific, owned recruiter question.
AI JOB AGENCY's candidate intake service starts from the call and the next recruiter action. Bring a sample set of recurring questions to a workflow discussion to agree which answers belong in the initial scope and who maintains them.
FAQ
How many answers should we prepare before launch?
Prepare enough to cover the chosen call scope reliably. A small approved collection is more useful than a large collection with uncertain sources. Expand from observed questions after launch.
Can the agent use our website as its source?
Potentially, if the relevant content is current, approved and correctly scoped. Discuss how changes reach the agent and how conflicting pages are handled before relying on website content alone.
Who should own the knowledge base?
An operations owner should coordinate it, with vacancy facts confirmed by the responsible desk or account manager. The implementer manages technical publication; that does not make them the authority on client conditions.
How often should answers be reviewed?
Use a cadence that matches how quickly each fact changes, plus immediate review when its source changes. Opening hours and a live vacancy's start details may need different treatment.
Should we store a full call script here?
Keep approved factual answers distinct from conversation instructions and routing rules. They can work together, but changing a fact should not require rewriting every part of the call flow.