Make recurring work easier to run and easier to review.
For gyms, studios and coaching teams, automation starts with a clear process: clients book in the app, reminders support daily routines and billing follows the settings you configure. FITsociety MCP adds a separate layer for asking questions, preparing follow-up and carrying out selected approved actions.
Configured platform processes and AI-assisted requests serve different purposes. A scheduled reminder follows its setup. An MCP assistant uses the tools approved for a request. Connecting an assistant does not, by itself, schedule it to run in the background.
Scroll the table horizontally on smaller screens.
| Workflow | Configured platform process | AI-assisted review |
|---|---|---|
| Habit reminders | Configure reminders around the client’s routine. | Use recorded habit history to prepare a review when the relevant access is approved. |
| Session bookings | Let clients use the configured schedule and booking flow. | Review a named client’s attendance and cancellations for a defined period. |
| Recurring billing | Use subscription and payment settings to handle configured billing periods. | Review invoice records and outstanding amounts; MCP invoice access is read-only. |
| Coach follow-up | Keep the client record and team notes in the platform. | Draft a note, review it, and save only with the approved note-writing tool. |
This turns a recurring manual review into a consistent team procedure. It does not infer why a client cancelled or send a message just because attendance changed.
Review this client’s FITsociety bookings for the last 30 days. Show attended, cancelled and absent sessions separately, include the booking references, and draft a short follow-up for the coach to review. Do not save or send anything.
The booking adherence workflow explains the read tools. Saving a private coach note additionally requires the notes module, private-communication consent and the approved note-writing tool.
Choose one person to own each process and review its output. For billing, distinguish an invoice, a submitted payment attempt and a settled payment. AI invoice summaries help find records to inspect; they cannot collect money or change invoice status through the current MCP invoice module.
If you need an unattended integration, plan its trigger, credentials, monitoring and failure handling separately. The FITsociety API documentation and MCP tool catalog describe different integration surfaces. A REST endpoint being available does not mean the same action exists as an MCP tool.
Start with configured bookings, recurring billing and habit reminders, then consider AI-assisted attendance reviews, invoice summaries and follow-up drafts. Each workflow has its own settings and access requirements.
No. A connection gives a compatible assistant permissioned access to tools. A scheduled, unattended workflow requires a separate runner or integration with its own trigger and operating arrangements.
The current FITsociety MCP invoice module is read-only. It can help inspect invoices and prepare an administrator’s follow-up. Payment execution and settlement are separate platform and payment-provider processes.
Yes, when the company feature is enabled and the grant includes the notes module, private-communication consent, write access and the specific note-creation tool. Start with drafting and agree a review step before saving.
Record the time spent before and after, the number of corrections and whether the source records support the result. Review a small set of cases before expanding the workflow across the team.
Choose one frequent, bounded task with an obvious source record. A read-only attendance summary is a practical first step. Bring that example to a demo before enabling write actions.
Connect the daily work to the right product and integration guide.
Use these worksheets and examples to prepare your next coaching or operational review.
Bring a recurring admin task to the demo. We will help distinguish the configured platform process, the information an assistant can review and any action that needs separate approval.