Answers on Messenger
Bea replies from the branch’s real menu, prices and hours, in the customer’s own mix of Tagalog and English.
All case studies
Case study · Beauty studios · Philippines
An AI assistant, live on Messenger.It hands over instead of guessing.
Brow Code is a brow and beauty studio chain with six branches in the Philippines. We built Bea, an AI assistant that answers customers on Facebook Messenger and takes bookings.
Project facts and measured numbers
1 of 6 branches live for customers since Sept 29, 2026 The other 5 ran in shadow mode
259,735
customer messages studied before the build.
0
price mismatches across 320 services.
6.8sec
median reply time, first 32 live turns.
1,125
automated tests passing.
[01] The starting point
The inbox already showed where customers were waiting.
Each branch has its own Facebook Page, and staff answered every message by hand. Before building, we read the inboxes.
What else the inbox showed
- 1,172 customers waited an hour or more for a reply on one branch’s Page.
- 527 inquiries arrived around 8 PM, after that branch had closed.
[02] What we built
What Bea does.
The right branch every time
Prices, address and hours come from the Page the customer wrote to.
Instant answers
Opening hours, the address and the price list are answered by code, with no AI wait.
A form with real availability
The customer picks a service, an artist and an open time, then pays a deposit by QR code.
A clean handoff to staff
When Bea should not answer, she stops and alerts the team.
Built to be run
A health check, an off switch and a one-command rollback.
[03] Guardrails
A refusal costs one message. A wrong answer costs a customer.
Guardrail 01
Code decides the price. The AI never does.
Each price is looked up in that branch’s own records. 320 services were checked against 27 printed price lists, with 0 mismatches.
Guardrail 02
Bea only says what the system confirms.
She says a booking is made, moved or cancelled only when the booking system reports it.
Guardrail 03
Only staff can confirm a booking.
A booking is a hold until a staff member has seen the payment.
Guardrail 04
Health, money and complaints go to people.
Pregnancy, medication, refunds and complaints are handed to staff.
[04] Testing
Tested before any customer saw it.
- 134 test conversations about branch facts before launch.
- Shadow mode on all 6 Pages: Bea drafted, staff answered.
- 1,125 automated tests, up from 105 a month earlier.
- 5 deliberate bugs planted. The tests caught 5 of 5.
[05] Results so far
Results so far.
- Live at one branch since Sept 29, 2026.
- Median reply time: 6.8 seconds.
- First paid booking on launch day. The first with no manual step came the next day.
- Bea matched the customer’s language style 96% of the time.
[06] Tech used
What it runs on.
Claude (Anthropic API), Manychat, Meta Graph API, Cloudflare Pages Functions, D1, Postgres on Supabase, Slack.
Your inbox
Want an assistant that knows when to stop?
Show us your inbox and your price list. We will tell you what an assistant should answer and what it should hand to your team.
Or read how Bea works and the other case studies.