Requirements and responsibilities
Have the restaurants owner approve public copy, required staff roles and the exact sample journey. A restaurant needs accurate menus, opening hours and reservation choices.
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: Static menu photos and stale opening hours mislead visitors.
Illustrative situation
Illustrative scenario: a restaurant publishes its current menu and opening hours. A guest requests a table and staff accept or decline it from the reservation ledger before confirmation.
Choose the approach
Choose a reservation service only after checking capacity rules and confirmation delivery. 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 · Easy!Appointments hosting, setup and deployment requirements · Easy!Appointments official application settings
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
Collect menu versions, allergens owner, hours and table policy
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Collect menu versions, allergens owner, hours and table policy; named administrator and a harmless representative sample.
- Action
- Ask the manager to approve menu version, allergen contact, opening hours, holiday exceptions and whether reservations are required.
- Expected result
- The public promise matches today's operations.
- Verify
- The public promise matches today's operations. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If the kitchen cannot own menu updates, use a smaller stable menu and a direct inquiry path.
Sources: WordPress roles and capabilities · WordPress plugin administration · Easy!Appointments hosting, setup and deployment requirements · Easy!Appointments official application settings
Step 2 of 5
Publish accessible WordPress menu and location pages
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Publish accessible wordpress menu and location pages; named administrator and a harmless representative sample.
- Action
- Publish accessible WordPress menu text, address and contact actions rather than relying only on image menus; check mobile legibility.
- Expected result
- Guests can find food, hours and location.
- Verify
- Guests can find food, hours and location. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If a menu item or hour is wrong, correct the source page before advertising.
Sources: WordPress roles and capabilities · WordPress plugin administration · Easy!Appointments hosting, setup and deployment requirements · Easy!Appointments official application settings
Step 3 of 5
Publish staffed reservation requests
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Configure chosen reservation tool or clear phone route; named administrator and a harmless representative sample.
- Action
- Publish a reservation request form or staffed phone route with party size, date and contact fields approved by the manager. Confirmed table inventory remains in the restaurant’s own reservation book until a documented provider is selected.
- Expected result
- A request reaches staff without promising that the requested table is available.
- Verify
- A request reaches staff without promising that the requested table is available. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If the app cannot represent linked tables or walk-ins, adjust the public availability claim.
Sources: WordPress roles and capabilities · WordPress plugin administration · Easy!Appointments hosting, setup and deployment requirements · Easy!Appointments official application settings · Contact Form 7 getting started guide
Step 4 of 5
Test request approval and cancellation
- Where
- WordPress or selected application administrator and public test browser
- Permissions
- Named WordPress or selected application administrator; business owner accepts result.
- Inputs
- Test date, party size, confirmation and staff workflow; named administrator and a harmless representative sample.
- Action
- Send a synthetic request for a busy time and a cancellation message; ask staff to locate both and reply with an explicit accept or decline decision before any guest confirmation.
- Expected result
- Guests receive a decision from staff, and the public page does not call an unapproved request a booking.
- Verify
- Guests receive a decision from staff, and the public page does not call an unapproved request a booking. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If confirmation arrives without a calendar record, treat it as failed and contact the guest.
Sources: WordPress roles and capabilities · WordPress plugin administration · Easy!Appointments hosting, setup and deployment requirements · Easy!Appointments official application settings · Contact Form 7 getting started guide
Step 5 of 5
Assign holiday edits and recovery of reservation records
- 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 holiday edits and recovery of reservation records; named administrator and a harmless representative sample.
- Action
- Assign someone to update seasonal menus and holidays, and back up reservation records separately from WordPress pages.
- Expected result
- The next shift can manage changed hours.
- Verify
- The next shift can manage changed hours. Have the responsible business staff member record the sample identity and observed result.
- If it fails
- If a restore predates future bookings, reconcile them before reopening the calendar.
Sources: Site backups in xCloud · xCloud agent capability boundaries · Easy!Appointments hosting, setup and deployment requirements · Easy!Appointments official application settings · 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 guest sees today's menu and reservation state and staff receive the request. 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
For a request-only route, preserve the staffed mailbox or request log independently of WordPress. If the restaurant later chooses a reservation system, document its own backup, capacity and recovery process before making instant-confirmation claims.
Contact Form 7 getting started guide · Site backups in xCloud
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 a reservation request form or staffed phone route with party size, date and contact fields approved by the manager. Confirmed table inventory remains in the restaurant’s own reservation book until a documented provider is selected.
- The business owner compares the controlled sample with this observable result: Guests receive a decision from staff, and the public page does not call an unapproved request a booking.
- 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 guest sees today's menu and reservation state and staff receive the request. Test request approval and cancellation
- recovery (covered): Static menu photos and stale opening hours mislead visitors. Assign holiday edits and recovery of reservation records
Sources
- xCloud agent capability boundaries
- WordPress roles and capabilities
- WordPress plugin administration
- Site backups in xCloud
- WordPress hardening handbook
- xCloud MCP documentation and connection profiles
- Easy!Appointments hosting, setup and deployment requirements
- Easy!Appointments official application settings
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Contact Form 7 getting started guide