Context in
Approved class, membership, booking, preparation, policy, and attendance context supplied by the operator and deployment connection.
Integration · Mindbody
Keep Mindbody as the record. Let Branch handle the follow-through.
Answer class-fit questions, help a trial member choose one next booking, prepare arrival, and create a specific second-visit path.
Status: assisted · confirm the current connection path before launch.
Connection boundary
Useful context in. Approved actions out.
Branch acts
Answer class-fit questions, help a trial member choose one next booking, prepare arrival, and create a specific second-visit path.
Operator boundary
Branch escalates ambiguous policy, billing, safety, and exception cases rather than inventing an answer.
Setup path
Start with one measurable workflow.
Begin with a reviewed first-visit or trial-conversion workflow and validate the current connection method before promising automation.
Questions operators ask
Clear answers before the next action.
Is the Mindbody integration live?
Current status: assisted. Confirm the exact connection path and supported actions during setup; this page does not imply an unverified public API integration.
What remains in the source platform?
Mindbody remains the source of truth for schedules, bookings, memberships, and payments unless explicitly configured otherwise.
What can Branch do around it?
Answer class-fit questions, help a trial member choose one next booking, prepare arrival, and create a specific second-visit path.
How should setup begin?
Begin with a reviewed first-visit or trial-conversion workflow and validate the current connection method before promising automation.
Private Branch preview
Show us where people get stuck.
Create a community and we’ll map one real attendance or conversion workflow around your context.
Create your community →No migration. No members contacted before review.