Track 1 — Virgin brows
No previous permanent makeup. The assistant answers questions, sends the Acuity link and address, and lets Acuity collect the normal intake details.
Client work · AI DM assistant
MUUVA Beauty: a DM assistant that knows who can be booked today
For a brow studio, not every enquiry can go straight to the calendar. Clients with previous brow tattoo work need a consultation before booking — and the studio needs photos first. We built the ManyChat AI flow that answers, screens, collects photos and only then sends the booking link.
Instagram + Messenger
Acuity booking
Photo intake built in
At a glance
- Client MUUVA Beauty — brow studio (ombre powder brows, nano combination).
- Channels Instagram DMs and Facebook Messenger.
- Goal Answer FAQs, screen brow history, collect photos, book to Acuity.
- Stack ManyChat + OpenAI, Acuity booking, no CRM or landing page required.
The client
A specialist studio with a two-track booking process
MUUVA Beauty's service is not one-size-fits-all. Virgin brows can usually be booked directly through Acuity, which handles the standard intake form. Clients with previous brow tattoo work need a different path: photos first, review by the artist, then booking.
Track 2 — Previous work
Existing brow tattoo work means the artist needs to see the canvas first. The assistant requests three specific photos before any booking link is sent.
Everyone else
Not sure, or asking detailed questions? The assistant answers from the studio's approved FAQ content and keeps the conversation moving to a decision.
The problem
High-intent DMs, managed one reply at a time
- The same FAQs — pricing, healing, aftercare, address, what a brow tattoo involves — answered manually, every day.
- Booking links sent without knowing whether the client was suitable for direct booking or needed a photo consultation first.
- Photo requests handled conversationally, so pictures arrived in inconsistent numbers, angles and lighting.
- Leads who received the booking link but never confirmed were not followed up systematically.
- Instagram and Messenger were handled as separate inboxes rather than one pipeline.
Why it happens
A DM inbox is a queue, and the queue wins. Nuanced steps — like knowing who needs photos first — get skipped when someone is answering twenty conversations between appointments.
This describes the workflow gap the build was scoped to close.
What we built
One flow with a real decision inside it
A ManyChat automation with an AI layer, custom fields and tags that track every lead's stage — so the same rules apply to every conversation, on both channels.
FAQ answering from approved content
Common questions are answered from the studio's own content: services, process, healing, aftercare, location. The assistant stays within approved answers rather than improvising.
Brow-history screening
Every lead is asked about previous brow tattoo work and sorted into virgin, previous work, or not sure. The answer decides which path the conversation takes.
Structured photo intake
Previous-work leads are asked for three specific photos in sequence: a center selfie, a right profile and a left profile. Each photo has its own status field, so the studio can see what has arrived and what is still missing.
Booking routing
Virgin-brow leads receive the Acuity booking link and the studio address directly. Previous-work leads move to photo review first. Either way, the conversation ends with a clear next step, not a dead end.
Follow-up on unconfirmed bookings
Leads who received the booking link but did not confirm get follow-up messages. Because Acuity and ManyChat are not directly linked, the flow tracks "booking link sent" and asks the client to confirm — with a webhook option documented for true booked detection later.
Lead state you can see
Custom fields and tags track stage, service interest, brow history, photo status and follow-up permission — so the artist opens any conversation and immediately knows where that lead stands.
Evidence
What the build record shows
The blueprint and the deployed ManyChat flow contain the full asset list. These are the structural facts of the build.
2
channels covered by one flow: Instagram DMs and Facebook Messenger
3
required photos in the previous-work intake: center, right profile, left profile
6
custom fields tracking brow history, stage, service, photo status, permission and source
9+
tags segmenting leads from first message to reported booking
Verified build facts
These figures come from the delivered blueprint and the workflow assets. No booking-volume, revenue or conversion claims are made — the studio's results are the studio's own.
ManyChatOpenAIAcuity SchedulingInstagram DMFacebook Messenger
How it works
From first message to a booked appointment
1
Enquiry
A DM or message arrives on Instagram or Messenger.
2
Answer
FAQs handled from approved studio content.
3
Screen
Previous brow tattoo work? The answer branches the flow.
4
Photos or book
Previous work: three photos collected. Virgin brows: booking link sent.
5
Confirm
Acuity handles the appointment; follow-ups chase unconfirmed links.
Honest limits
What this case study does not claim
No results claimed
This page describes the system that was delivered. It does not claim booking counts, revenue or conversion rates — those belong to the studio.
Booking detection is honest
Without a direct Acuity-to-ManyChat integration, the flow cannot see a completed booking by itself. It tracks the link and asks for confirmation, and the blueprint documents the webhook upgrade path if true detection is wanted.
Content is the client's
Every FAQ answer, policy and wording point comes from the studio's approved material. Where information was still needed, the blueprint marks it as a placeholder to confirm — not a guess.
FAQ
Questions about this build
Why does the flow ask for three specific photos?
Because previous brow tattoo work changes what is possible in a single session, and the artist needs consistent angles to judge the existing shape, pigment and coverage. A center selfie plus both profiles gives her a complete view before the client books — without a back-and-forth photo exchange.
Can it tell whether someone actually booked?
Not natively, and the build says so plainly. ManyChat tracks that the link was sent and follows up with the lead, who can confirm. If the studio wants automatic booked-detection later, the blueprint documents adding an Acuity webhook through an automation tool as a clean next step.
Does it replace a CRM?
No CRM was needed for this build. The lead's stage, history, photo status and service interest live in ManyChat's fields and tags, which is enough for a single-studio workflow. A CRM becomes worth adding when multiple artists or locations need shared reporting.
Get your plan
Drowning in the same DMs every day?
Tell us what your clients ask and how they book. On a free strategy call we will map the fastest DM automation for your business.
- A free 15-minute AI strategy call — no obligation.
- A scoped blueprint: the biggest leak in your DMs, and the first automation to fix it.
- Honest fit check — we will tell you if automation is not your fastest win.
The fastest way in: answer six short questions and we will map your lead journey, find the biggest leak and show the fastest automation win — before we ever get on a call.
Free strategy call · No commitment · We reply by email
Keep going
Related pages
More client work
Relevant AI services
Industry pages
Ready to answer every DM without typing a reply?
Book a free AI strategy call and we will walk your enquiry flow against this build.