Faster database search
Recruiters can express the target candidate profile in normal language and get to a Boolean search faster.
August 2026 AI workflows
AI Boolean Search and MCP Record Updates
ATZ CRM added natural-language AI Boolean Search and expanded MCP actions so connected AI assistants can create and update approved CRM records.
Search the candidate database with natural-language prompts
Generate and run Boolean searches without writing the full string manually
Use MCP-compatible AI clients to create supported records
Update approved ATZ CRM records through connected AI assistants
Give recruiters a faster path from intent to structured CRM action
Quick answer
What changed for recruiters?
AI Boolean Search lets recruiters describe the candidate they want in plain language and have ATZ CRM generate and run the matching Boolean search. MCP record updates let connected AI assistants create and update CRM records through supported MCP-compatible clients, with recruiter and admin control still guiding the workflow.
What changed
What this update changes
AI Boolean Search gives recruiters a new way to search the candidate database. Instead of building a Boolean query from scratch, the recruiter can describe the target profile in natural language and let ATZ CRM generate the search.
This is useful when a recruiter knows the profile they want but does not want to spend time translating that need into operators, synonyms, exclusions, and field logic.
MCP support also expanded. Connected AI assistants can now create and update ATZ CRM records through supported MCP-compatible clients such as Claude, Codex, and other tools that follow the protocol.
The shared theme is natural-language control. Recruiters can move from a plain request to a search or record action more quickly, while teams still need permissions, review habits, and data-quality rules around AI-assisted work.
Why it matters
Why it matters to recruiters
Recruiters are often measured on speed, quality, and follow-through. This update is designed to reduce manual work, protect useful context, and help teams keep hiring activity moving with fewer handoffs.
Less Boolean syntax friction
AI assistance helps recruiters who understand the role but do not want to manually compose every operator and variation.
More useful AI assistants
MCP record actions let approved AI clients help with CRM work rather than only summarizing information outside the system.
Better bridge between conversation and action
A recruiter can ask for help in natural language and turn that request into structured search or record maintenance work.
Before and after
How the workflow changes
Before
Recruiters wrote Boolean strings manually or reused old searches that only partly matched the new role.
After
Recruiters can describe the desired profile and let AI create a search that can be reviewed and refined.
Before
AI assistant work often stopped at summaries or recommendations outside the CRM.
After
Supported MCP clients can help create or update records when the action is allowed and reviewed.
Before
Finding candidates and maintaining records required more switching between thinking, searching, and data entry.
After
Natural-language requests can move closer to the actual CRM workflow.
How recruiters use it
How the workflow works
The exact setup depends on your workspace and permissions, but the core workflow is built to keep recruiters closer to the record, the next action, and the right team context.
1
Describe the ideal candidate
Use role requirements, seniority, skills, companies, locations, exclusions, and background signals in plain language.
2
Review the generated search
Check whether the AI-created Boolean logic reflects the hiring need before relying on the results.
3
Run and refine results
Inspect candidates, adjust terms, and save useful search patterns for similar roles when appropriate.
4
Use MCP for supported actions
Ask a connected AI client to create or update records only when the task fits team permissions and data rules.
5
Confirm important changes
Review AI-assisted record updates so candidate, client, job, and activity data stays accurate.
Feature-specific details
Extra context for this update
Some releases affect more than one recruiting workflow. These notes explain the practical details recruiters, admins, or managers may want to review before rolling the update out to the team.
AI control
Where recruiter judgment still matters
Natural-language workflows are helpful because they reduce setup work, but they should not turn into blind automation.
- Review Boolean logic for missing synonyms, over-tight requirements, and risky exclusions.
- Check candidate results before contacting, shortlisting, or submitting anyone.
- Use MCP record actions for clear maintenance tasks rather than vague open-ended changes.
- Keep admin permissions and team rules aligned with what AI assistants are allowed to do.
Best fit
Teams that benefit most
Recruiters who source from large candidate databases
Teams that use Boolean search but want faster setup
Admins piloting natural-language CRM operations
Recruiters using MCP-compatible AI assistants
Managers who want AI assistance without losing review control
Helpful next steps
Related ATZ CRM pages
Boolean Search help article Review the search logic that AI Boolean Search helps recruiters create faster. Saved Boolean search views Compare natural-language search with the June update for deeper Boolean and saved search workflows. ATZ CRM MCP Server help article Review the admin setup path for MCP-compatible assistants. MCP Server actions Review which MCP actions are available for search, reading, creation, and updates. MCP Server product update Read the earlier launch note for AI-client connectivity with ATZ CRM. AI MCP Server feature See how MCP support fits into AI-assisted recruiter workflows.
Quick answers
Common questions
What is AI Boolean Search?
It lets recruiters describe the candidate they want in plain language, then ATZ CRM generates and runs the Boolean search.
Should recruiters inspect the generated Boolean search?
Yes. Recruiters should review the search logic, especially for must-have skills, seniority, location, synonyms, and exclusions.
Which AI assistants can connect through MCP?
MCP-compatible clients can include Claude, Codex, and other AI tools that support MCP connections configured for ATZ CRM.
What changed with MCP record actions?
Connected AI assistants can now create and update supported ATZ CRM records through approved MCP actions.
Does MCP remove the need for CRM permissions?
No. MCP usage should still follow workspace permissions, admin controls, and internal data policies.
How should teams start using these AI workflows?
Start with clear search prompts or simple record updates, review the results, and expand usage once the team trusts the workflow.
See it in context
Review this update inside your recruiting workflow
Book a walkthrough with the ATZ CRM team to see how this update supports your jobs, candidates, and shortlist process.