Requirements and responsibilities
Have the fitness studios owner approve public copy, required staff roles and the exact sample journey. A fitness studio sells recurring classes with limited places.
xCloud agent capability boundaries · WordPress roles and capabilities
Use a compatible Nginx or OpenLiteSpeed stack for native WordPress. Verify current server resources, plan eligibility and each selected plugin or service license and requirements before installing; a Docker server does not host a new native WordPress site.
xCloud agent capability boundaries · WordPress plugin administration
Prepare a safe test identity and a completed, accessible backup before consequential changes. The important failure to plan around is: A checkout flow may succeed while class capacity is wrong.
Illustrative situation
Illustrative scenario: a fitness studio runs limited-seat classes. A visitor asks for a place in a full class and staff decline or waitlist the request under their written policy.
Choose the approach
Choose a class scheduler that supports waitlists and cancellation rules if required. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · WordPress plugin administration
Keep application setup, domain/DNS ownership, mail delivery and external integrations with their named administrators. Use a plain documented path when a proposed integration cannot be demonstrated end to end.
xCloud agent capability boundaries · WordPress plugin administration
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Map class types, instructors, capacity and membership rules
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Map class types, instructors, capacity and membership rules; named administrator and a harmless representative sample.
- Action
- Define class capacity, instructor, recurring timetable, membership eligibility, cancellation window and waitlist owner.
- Expected result
- The studio has a measurable class-booking policy.
- Verify
- The studio has a measurable class-booking policy. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If a class can exceed room capacity, reduce the online allocation.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 2 of 5
Build WordPress timetable and instructor pages
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Build wordpress timetable and instructor pages; named administrator and a harmless representative sample.
- Action
- Publish current class descriptions, instructors and timetable in WordPress; separate marketing copy from live slot counts.
- Expected result
- A visitor reaches the correct booking path from each class.
- Verify
- A visitor reaches the correct booking path from each class. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If timetable differs from the scheduler, mark WordPress copy as indicative and correct it.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 3 of 5
Publish a staffed class request route
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Configure scheduler and payment integration separately; named administrator and a harmless representative sample.
- Action
- Publish the class timetable and a staffed seat request path. Keep eligibility, waitlist and payment in the studio’s existing documented membership system until a class scheduler is chosen and verified.
- Expected result
- Visitors can request a place and staff can compare it with their authoritative class roster.
- Verify
- Visitors can request a place and staff can compare it with their authoritative class roster. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If a paid booking does not grant a seat, halt sales until records reconcile.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 4 of 5
Test full-class decisions
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Test full class, cancellation and member access; named administrator and a harmless representative sample.
- Action
- Send a request when a sample class is full, then ask staff to decline or offer a waitlist position under the written policy; test a cancellation and the response to the next person.
- Expected result
- Staff decisions match roster capacity; no automatic waitlist or entitlement is promised.
- Verify
- Staff decisions match roster capacity; no automatic waitlist or entitlement is promised. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If the extra booking is accepted beyond capacity, remove the public link until corrected.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 5 of 5
Monitor schedule edits and preserve bookings on recovery
- Where
- WordPress or selected application administrator and owner handoff
- Permissions
- Named WordPress/application administrator and business owner; inspect backup separately if recovery is in scope.
- Inputs
- Monitor schedule edits and preserve bookings on recovery; named administrator and a harmless representative sample.
- Action
- Assign schedule and instructor change owners; preserve bookings and member entitlements before a database restore.
- Expected result
- Staff can run a class even after a website update.
- Verify
- Staff can run a class even after a website update. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If newer bookings exist than the backup, export and reconcile them first.
Sources: Site backups in xCloud · xCloud agent capability boundaries · WordPress plugin administration · WordPress roles and capabilities
Maintenance
Assign a cadence for selected WordPress core, theme and plugin updates, review version-based findings and retest the path in this guide. In particular, repeat: A full class rejects or waitlists the next booking and staff see capacity. A chat prompt is not a scheduled task.
Manage WordPress updates with Updates Manager · Vulnerability Checker in xCloud
Record actual backup completion, storage access and responsible staff. Recheck connected application and provider behavior after changes rather than relying on a site health status alone.
Recovery decisions
Booking or reservation records in a separate scheduler need their own backup and reconciliation. A WordPress restore cannot recreate appointments held only in that app; compare both recovery points with bookings made since capture.
Validate the restored copy with representative content, authentication, HTTPS and this guide’s business acceptance test before moving traffic or closing the incident.
AI handoff
Connect xCloud MCP through the current documented profile and grant only the scopes needed for the selected team. Discover tool schemas first. Read resources to plan; require approval for any supported write. Use returned dashboard URLs for manual work. The packaged REST wrapper accepts GET requests only.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
- Review a WordPress business journey app · manual
Application data and observed transactions cannot be inferred from xCloud resource reads. Use authorized test accounts and the application or provider evidence.
Checkpoint: Record the test identity, timestamp, expected outcome, observed result and owner decision.
- Configure WordPress content, users and selected plugins app · manual
Requires a named WordPress administrator or suitable editor. Plugin behavior, commercial license, payment, email and external integration are verified in the chosen vendor documentation and application; xCloud hosting or MCP reads do not configure them.
Checkpoint: Open the actual WordPress or selected plugin interface, record the version and role, and have the business owner accept a real user journey.
WordPress roles and capabilities · WordPress plugin administration
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Publish the class timetable and a staffed seat request path. Keep eligibility, waitlist and payment in the studio’s existing documented membership system until a class scheduler is chosen and verified.
- The business owner compares the controlled sample with this observable result: Staff decisions match roster capacity; no automatic waitlist or entitlement is promised.
- Staging push/pull, native backup schedules, restores and cache-setting edits require the authorized xCloud dashboard operator; the packaged REST wrapper is GET-only.
Feature coverage
- business-acceptance (covered): A full class rejects or waitlists the next booking and staff see capacity. Test full-class decisions
- recovery (covered): A checkout flow may succeed while class capacity is wrong. Monitor schedule edits and preserve bookings on recovery