Turn completed visits into review invitations.
Happy families are rarely asked for feedback.
Est. deploy 4–6 weeksSee the walkthrough
Marketing & Reputation · Fitness & Wellness
Draft community updates from approved events.
Studio posts require repeated rewriting.
For: Community managers and the team responsible for marketing & reputation in fitness & wellness.
01 · The outcome
What good looks like.
The team has a manager-approved community post, with source evidence and an explicit approval before any external action. Track approved events promoted before their cutoff against a baseline; do not assume automation improves it.
A connected workflow that uses event details, consent-cleared photos, and current membership information to draft a post without health guarantees, body claims, or unconsented member stories. It produces a manager-approved community post.
Where AI helps, and where a person decides.
AI can draft a post without health guarantees, body claims, or unconsented member stories. It drafts and organizes; it does not authorize spending, commitments, clinical decisions or customer communication. The community manager verifies the source facts and approves the final action.
Community manager is accountable. People approve customer-facing, sensitive, financial, and legally binding actions.
- Community manager: Capture the source and scope
- Community manager: Review the proposed outcome
- Community manager: Release only the approved version
- Community manager: Check the result and exceptions
A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
02 · The handoffs
How the work moves.
Every handoff has an owner. Select a step to open or close its detail.
Start when: A studio event is approved for promotion. Connect only event details, consent-cleared photos, and current membership information. The community manager confirms the request is authorized and in scope.
Ready when: The source reference, permissions and accountable owner are recorded.
Use the authorized records to draft a post without health guarantees, body claims, or unconsented member stories. Preserve the original language alongside the draft and label uncertain fields.
Ready when: Each proposed fact links back to a source, and missing information is visible.
Check a manager-approved community post against the original records and current policy. Correct errors and escalate exceptions to the qualified specialist; do not auto-approve.
Ready when: Community manager has recorded approval or a reason to hold the item.
After explicit approval, save a manager-approved community post in the system of record. Send only approved messages to verified recipients. Record the version and prevent duplicate delivery.
Ready when: The approved record is saved; any delivery is confirmed or placed in the retry queue.
Review approved events promoted before their cutoff each week, sample completed records for quality, and resolve held items. Change the rules only after reviewing actual errors and staff feedback.
Ready when: Exceptions have owners, the metric has a baseline, and corrective actions are assigned.
Sample record.
$ david run --workflow=fitness-community-posts
ILLUSTRATIVE RECORD / NOT LIVE CUSTOMER DATA
- Example
- Illustrative only — not a real client record
- Reference
- FITNESS-COMMUNITY-POSTS-DEMO-001
- Trigger
- A studio event is approved for promotion.
- Owner
- Community manager
- Prepared output
- a manager-approved community post
- Review status
- Awaiting human approval — no external action taken
- Missing information
- Owner to verify source completeness
- Measure
- Approved events promoted before their cutoff
Start with your tools.
Connect Mindbody, Stripe, Google Calendar through approved APIs or controlled exports. Map record identifiers first; test permissions and field updates in a sandbox. Vendor names describe possible connections, not a guarantee of an available integration or license.
When things go wrong.
- A named person approves customer-facing messages, spending, record changes and binding commitments before release. Pre-approved scripts are versioned; exceptions stop for review.
- Use only authorized sources and role-based access. Keep an audit trail of source records, drafts, approvals and delivery status; deduplicate retries.
- If an integration fails, a source is missing or confidence is low, pause the action and assign the original request to the accountable owner.
Try this week / no DAVID required
A useful first step.
This week, have your community manager time five examples of this work. Use redacted copies of event details, consent-cleared photos, and current membership information to make a manager-approved community post manually, then list which fields required judgment.
What to measure.
- Approved events promoted before their cutoff
- Minutes of human handling per completed item
- Drafts needing substantive correction
- Exceptions unresolved beyond the agreed review window
Estimate your time back.
20.8
$11,232
03 · More workflows to consider
Related workflows.
Draft practice posts without exposing patients.
Marketing drafts accidentally contain clinical details.
Est. deploy 4–6 weeksSee the walkthrough
Check practice articles before publication.
Draft articles can imply guarantees or reveal client facts.
Est. deploy 4–6 weeksSee the walkthrough
Want this running in your business in 2–4 weeks?
Free 30-minute call. We'll tell you honestly whether AI fits, and where.