Requirements and responsibilities
Have the hotels and guesthouses owner approve public copy, required staff roles and the exact sample journey. A guesthouse has room descriptions and booking availability across channels.
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 manual WordPress page cannot guarantee live availability.
Illustrative situation
Illustrative scenario: a guesthouse advertises rooms on WordPress and other channels. The website collects a request; the inventory owner decides whether the last room can be confirmed.
Choose the approach
Use a booking engine only after verifying inventory synchronization with external channels. 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
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
Define room inventory, policies, tax and channel owner
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Define room inventory, policies, tax and channel owner; named administrator and a harmless representative sample.
- Action
- List room types, availability owner, cancellation terms and all channels that can sell the same room.
- Expected result
- The manager identifies the inventory source of truth.
- Verify
- The manager identifies the inventory source of truth. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If two systems can confirm the last room independently, resolve synchronization first.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 2 of 5
Publish property pages and a clear booking entry point
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Publish property pages and a clear booking entry point; named administrator and a harmless representative sample.
- Action
- Publish room descriptions, images, accessibility details, location and policies in WordPress with a clear booking entry point.
- Expected result
- A guest can compare rooms before entering the booking engine.
- Verify
- A guest can compare rooms before entering the booking engine. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If a room page advertises unavailable amenities, correct it before taking bookings.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 3 of 5
Link to staffed inventory inquiry
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Configure chosen booking service and channel settings; named administrator and a harmless representative sample.
- Action
- Link each WordPress room page to the property’s selected staffed inquiry channel. A channel-manager or booking engine requires a separate vendor review for rates, inventory and cancellation behavior before instant confirmation is offered.
- Expected result
- A guest reaches an owned inquiry route; the site does not claim live inventory sync without a selected provider.
- Verify
- A guest reaches an owned inquiry route; the site does not claim live inventory sync without a selected provider. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If the vendor cannot document a channel connection, do not promise live synchronization.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 4 of 5
Reconcile last-room requests
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Test availability, cancellation and confirmation messages; named administrator and a harmless representative sample.
- Action
- Submit a synthetic last-room inquiry from two channels and ask the inventory owner to decide which request can be accepted. Record response and cancellation handling in the reservation ledger.
- Expected result
- Only staff-confirmed inventory is offered to guests, with no unverified automatic double-booking prevention claim.
- Verify
- Only staff-confirmed inventory is offered to guests, with no unverified automatic double-booking prevention claim. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If both accept it, stop instant confirmation and use manual review until inventory is fixed.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 5 of 5
Assign rate review and reconcile bookings before restore
- 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
- Assign rate review and reconcile bookings before restore; named administrator and a harmless representative sample.
- Action
- Review rates and channel sync after changes; keep booking records and guest messages outside an old WordPress restore plan.
- Expected result
- The manager can reconcile a disputed reservation.
- Verify
- The manager can reconcile a disputed reservation. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If restoring would roll availability backward, reconcile from the booking engine first.
Sources: Site backups in xCloud · xCloud agent capability boundaries · 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: One sample room cannot be sold twice across the tested channels. 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: Link each WordPress room page to the property’s selected staffed inquiry channel. A channel-manager or booking engine requires a separate vendor review for rates, inventory and cancellation behavior before instant confirmation is offered.
- The business owner compares the controlled sample with this observable result: Only staff-confirmed inventory is offered to guests, with no unverified automatic double-booking prevention claim.
- 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): One sample room cannot be sold twice across the tested channels. Reconcile last-room requests
- recovery (covered): A manual WordPress page cannot guarantee live availability. Assign rate review and reconcile bookings before restore