Example workflow: separating candidates from clients for a recruitment agency
This is not a customer story. It is an example of how we configure a deployment for this industry. There is no named company, no testimonial and no performance figures on this page, because there is no customer behind it.
This is an example of how we configure Boafo Agent for a recruitment agency, where the same enquiry channel carries two completely different conversations. It is a configuration walkthrough, not a customer result.
The problem
A recruitment website gets candidates and hiring managers through the same door, and they need opposite things. One wants to know about a role, the other wants to know whether you can fill one.
Consultants end up triaging that mix by hand, which is time spent sorting rather than placing.
Client enquiries are the ones you cannot afford to sit on. A hiring manager with an urgent vacancy is usually talking to more than one agency.
The solution
The agent opens by identifying itself as AI, then asks the one question that splits the conversation: are you looking for a role, or looking to hire.
Candidates get a straight answer about what you recruit for, and can leave their details and the kind of work they want. Nothing is promised on your behalf.
Client enquiries follow a qualification flow: role, seniority, location, working pattern and when they need someone in post. That arrives with you already structured.
For client enquiries the agent can offer a slot from a connected Google Calendar and book the call there and then, while the person is still on your site.
Every conversation is summarised and categorised as candidate or client, so your inbox is already sorted before you open it.
What this changes, and what we will not claim
There are no performance numbers on this page, because there is no customer behind it. What is concrete is the shape of the output: two clearly separated enquiry types, each with the fields your consultants need, delivered by email and into a Google Sheet.
Whether that is worth it for you depends on how much consultant time currently goes into triage. That is a number only you have.
Without the agent, and with it
| What happens | Without Boafo Agent | With Boafo Agent |
|---|---|---|
| Enquiry type | Mixed in one inbox | Split into candidate and client |
| Client enquiry detail | We are hiring, please call | Role, seniority, location, pattern, start date |
| Booking a call | Email back and forth | Booked into a connected Google Calendar |
| Triage | Done by a consultant | Categorised summary waiting for you |
| Phone calls | Rings out to voicemail | Not covered yet, voice is on the roadmap |
Implementation playbook
Step one is the content pass. We read your website, your service list and your pricing page, then train the agent on what you actually offer and how you describe it. You review the answers before anything goes live.
Step two is the enquiry pass. We agree what the agent needs to collect on every enquiry, and where it goes: your inbox, a Google Sheet you control, or both. On Growth we can post it into your CRM.
Step three is go live. We give you a single line of code for your site, or we add it for you. Most set ups are answering enquiries within 24 hours.
Step four is tuning. You read the conversation summaries in the first week, tell us what the agent got wrong, and we adjust the answers. That loop is included, not billed as extra work.
What is next
Voice and phone answering is on the roadmap and is not live today. Everything described on this page happens in website chat.
If you want to see this running on your own site, book a demo. We train the agent on your live website first, so you are looking at your own answers rather than a generic script.