Requirements and responsibilities
Have named ownership of the domain, selected xCloud team and site, and WordPress administrator access. For this scenario, agree who supplies the data and signs off: A consulting business wants qualified inquiries routed to a named person.
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 working form with failed email or integration delivery silently loses leads.
Illustrative situation
Illustrative scenario: a consulting business routes qualified inquiries to a named person. A marked form submission reaches the selected destination with source and consent details; any duplicate is handled by the selected system’s approved policy.
Choose the approach
Choose a form and CRM handoff only after agreeing required fields and consent copy. Verify the selected provider or plugin documentation and license against this requirement; xCloud hosting does not supply its business configuration. Contact Form 7 documents one WordPress form path; CRM handoff and delivery still need separate evidence.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · WordPress roles and capabilities · Contact Form 7 getting started guide
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 qualified lead and consent
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Owner, hostname, approved requirements, sample record and decision date. Define qualified lead and consent.
- Action
- Define each offer, qualification question, consent text and response owner. Distinguish contact intent from newsletter permission.
- Expected result
- The lead capture contract is approved.
- Verify
- The owner can identify how a sample inquiry should be routed and answered.
- If it fails
- If required personal data lacks a clear purpose, remove that field before building the form.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 2 of 5
Publish offer pages and contact route
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Target team/site, server or plugin version, license and documented prerequisites. Publish offer pages and contact route.
- Action
- On the approved existing WordPress site publish offer pages with a single visible next action. Confirm HTTPS and a contact alternative from a browser.
- Expected result
- Visitors can understand the offer and reach the inquiry path.
- Verify
- From mobile, open each offer and reach the form or direct contact route without login.
- If it fails
- If the action is hidden or ambiguous, revise navigation before paying for traffic.
Sources: WordPress roles and capabilities · WordPress plugin administration
Step 3 of 5
Connect form and lead destination
- Where
- WordPress administrator or the selected plugin/application
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Approved change scope, backup state, selected version and maintenance window. Connect form and lead destination.
- Action
- Configure the selected form plugin and, if required, CRM integration using their own instructions. Contact Form 7 does not store submissions by default; use a separately documented storage add-on if local retention is required. Map fields and source page; protect API credentials.
- Expected result
- The form accepts approved data and has a destination.
- Verify
- Submit a unique test lead and compare the selected destination, CRM record if connected and recipient notification; inspect local storage only when the selected tool provides it.
- If it fails
- If delivery fails, stop claiming the handoff is complete and use an alternate contact route.
Sources: WordPress roles and capabilities · WordPress plugin administration · Contact Form 7 getting started guide
Step 4 of 5
Test validation and duplicate behavior
- Where
- WordPress public pages, administrator and relevant external provider
- Permissions
- Named WordPress or selected app administrator; business owner approves results.
- Inputs
- Test accounts, sample content or transaction, expected result and provider access. Test validation and duplicate behavior.
- Action
- Define desired duplicate handling with the CRM owner if a CRM is selected. Submit an invalid form and a near-duplicate lead; compare the actual mailbox or provider destination, and inspect a CRM record only for a documented connected CRM. Repeat consent-declined submission where permitted.
- Expected result
- Validation and consent work; observed duplicate behavior matches the selected destination’s approved policy.
- Verify
- Validation and consent work; observed duplicate behavior matches the selected destination’s approved policy. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If duplicate or unconsented data moves unexpectedly, revise field mapping and retest.
Sources: WordPress roles and capabilities · Contact Form 7 getting started guide
Step 5 of 5
Monitor leads and recovery
- Where
- Selected mailbox, CRM or documented form storage and WordPress administrator
- Permissions
- Named lead owner and selected application administrator; inspect the actual record destination.
- Inputs
- Observed results, unresolved failures, backup point and owner contacts. Monitor leads and recovery.
- Action
- Assign daily ownership of form errors and unanswered leads. Have the owner retrieve a recent record from the selected mailbox, provider or documented form storage; include it in recovery decisions only if that system retains it.
- Expected result
- The owner can find and answer a recent lead in its actual system of record.
- Verify
- The owner can find and answer a recent lead in its actual system of record. Record the exact account or record tested, result, and time with the responsible owner.
- If it fails
- If delivery monitoring or recovery ownership is absent, retain a direct contact route.
Sources: Site backups in xCloud · xCloud agent capability boundaries · Contact Form 7 message persistence with Flamingo · Contact Form 7 getting started guide
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: The expected lead appears once in the destination with the correct source. 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
Before restoring, compare the chosen recovery point with newer business records. A working form with failed email or integration delivery silently loses leads. Use the xCloud dashboard for native restore only after the owner approves target and scope; reconcile or preserve newer data first.
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
- 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
- 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.
Copyable agent brief
Manual checkpoints
- The named WordPress, app, dashboard or provider administrator performs the guide’s actual configuration step: Configure the selected form plugin and, if required, CRM integration using their own instructions. Contact Form 7 does not store submissions by default; use a separately documented storage add-on if local retention is required. Map fields and source page; protect API credentials.
- The business owner compares the controlled sample with this observable result: Validation and consent work; observed duplicate behavior matches the selected destination’s approved policy.
- 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): The expected lead appears once in the destination with the correct source. Test validation and duplicate behavior
- recovery (covered): A working form with failed email or integration delivery silently loses leads. Monitor leads and recovery
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
- Contact Form 7 getting started guide
- Manage WordPress updates with Updates Manager
- Vulnerability Checker in xCloud
- Contact Form 7 message persistence with Flamingo