Example workflow: handling routine client questions for an accounting firm
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 an accounting or professional services firm, where the same few questions arrive over and over and new enquiries need scoping before anyone speaks. It is a configuration walkthrough, not a customer result.
The problem
A large share of inbound questions at an accounting firm are the same handful: what the deadline is, what you need from me, what this service costs.
Those questions still land on a partner or a manager, which is expensive time spent on answers that never change.
New enquiries have the opposite problem. They arrive with too little detail to know which service line they belong to, so the first conversation is spent finding out.
The solution
The agent identifies itself as AI, and is trained on your published deadlines, service descriptions and document checklists, so routine questions get answered accurately in your own wording.
It is deliberately limited to published, non client specific information. It does not look up individual client records or discuss anyone's affairs.
New enquiries follow a qualification flow: entity type, services needed, current arrangement and when they want to move. That is enough for you to route it to the right person.
It can offer a scoping call slot from a connected Google Calendar so a qualified enquiry does not go cold while emails go back and forth.
Anything outside the published material is handed to a person with the conversation summary attached, rather than answered on a guess.
What this changes, and what we will not claim
There are no efficiency percentages on this page. We are not going to publish a number we cannot substantiate. What the set up does is answer published questions consistently and hand everything else to a person with context.
The value of that depends on how much of your inbound volume is genuinely routine, which is something you can see in your own inbox.
Without the agent, and with it
| What happens | Without Boafo Agent | With Boafo Agent |
|---|---|---|
| Routine questions | Answered by a manager | Answered from your published material |
| New enquiry detail | Looking for an accountant | Entity type, services, timing, current arrangement |
| Scoping call | Arranged over email | Booked into a connected Google Calendar |
| Client specific data | Not applicable | Out of scope by design, never accessed |
| 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.