Collect booking requests while you’re with a client
The problem: People message to ask about services and availability at all hours. Staff are busy with customers, replies come late, and the enquiry goes to a competitor who answered first.
People type: BOOKAPPOINTMENTPRICES
The flow, step by step
What happens from first comment to captured lead
Every step is something you switch on, edit or remove in the builder, with a live preview of exactly what people will receive.
- Step 1 · Trigger
Someone comments or DMs “BOOK”
Works from a post comment, a DM or a story reply, so every way people reach out starts the same flow.
- Step 2 · DM
A friendly welcome and what happens next
Set expectations: “I’ll take a few details and our team will confirm your slot.”
- Step 3 · Question
Which service do they want?
A choice question (Haircut / Facial / Colour…) keeps answers clean and easy to act on.
- Step 4 · Question
Preferred date
A validated date question (DD/MM/YYYY) so you don’t have to decode “sometime next week”.
- Step 5 · Question
Phone number
Checked for a sensible length and country code, then saved on the contact.
- Step 6 · Tag
Tag as a booking request
Makes it easy to find everyone waiting for confirmation.
- Step 7 · Human
Hand over to the front desk
A person confirms the slot from the inbox, and the automation stays quiet so the customer never gets conflicting messages.
- Step 8 · Integration
Notify your calendar or sheet
A webhook can add the request to Google Sheets, a CRM or your calendar tool via Zapier/Make.
How it helps
What changes for you
Never miss an enquiry
Requests are captured even when the whole team is with customers or the studio is closed.
Staff handle only ready leads
Your team sees complete, validated requests — service, date and phone — instead of back-and-forth questions.
A full record of every request
Each conversation and answer is saved on the contact and can be sent on to your systems.
Getting set up
What you configure
- 1Pick the keyword (BOOK) and where it should work.
- 2List your services as the choices.
- 3Ask for date and phone, then tag and hand off.
- 4Tell your team to watch the “Needs a human” inbox.
Features this flow uses
Good to know. DynamicDM collects the request and routes it to your team. Confirming slots and managing the calendar stay with you.
Teams & accountability
Run by a team? Everything is accounted for
Front-desk staff, a marketing person and the owner all touch the same inbox. Each action is attributed, so the owner can always see who confirmed what.
An audit log of changes
Creating, editing or deleting an automation, connecting or disconnecting an account, changing integrations and resuming a paused conversation are recorded with who did it and when.
Every message on record
Each comment, reply and DM is logged with its status, the automation and message variant that sent it, and the reason if it failed. Searchable and exportable.
Replies carry a name
When a teammate replies from the inbox it shows “Sent by” their name, and automations pause for that person so only one voice speaks.
The right access for each person
Five roles from owner to read-only viewer decide who can edit, who can reply and who can only look.
Roles for every person on the team
- OwnerFull control of the workspace
- AdminAccounts, integrations, audit log
- EditorBuilds automations, replies to people
- AnalystReads insights and the message log
- ViewerRead-only, e.g. a client or stakeholder
Inviting teammates from inside the app is coming soon.
A mobile app is on the roadmap
Planned · not available yetSo every role can do their part from a phone: editors replying to people who need a human, analysts checking the numbers, and owners keeping an eye on activity.
Other ways teams use DynamicDM
Want this flow for your account?
Request early access and we’ll help you set it up.