Begin with the problem and available evidence
A public URL can start the review. Source, backups, database material, logs, licenses, and credentials are requested later only through an approved controlled route when needed.
WordPress support services
Start WordPress support with a clear diagnosis—not an open-ended promise to fix anything.
Support begins by identifying the site, materials, WordPress stack, visible problem, production risk, and desired result. Accepted work is scoped against a controlled copy before a fix is previewed, approved, and verified.
Private Pilot: this is reviewed support for suitable existing-site requests. It is not 24/7 emergency response, security incident handling, production access, or an unlimited human support retainer.
Not every request is the same kind of support
A content fix, broken form, plugin conflict, migration, redesign, hacked site, and production outage have different permissions, evidence, cost, and stop conditions.
A successful fix needs more than a screenshot
The agreed route can include browser behavior, WordPress/PHP/database facts, stack checks, search output, warnings, and a known production handoff step.
What happens next
A visible path, with a stop at every meaningful decision.
- 01
Describe the symptom
Provide the affected URL, expected behavior, observed behavior, recent changes, business impact, and what materials you control.
- 02
Classify the route
Decide whether this is standard maintenance, Site Intake, plugin work, migration, redesign, an unsupported incident, or a separately quoted project.
- 03
Preview the fix
For accepted work, reproduce and change the issue in an isolated copy, then present a versioned preview and stated evidence.
- 04
Approve or stop
Approve the candidate for C-verified handoff, return it for revision, or stop when permissions, materials, risk, or scope do not support a safe result.
Included in this route
- A first-pass fit and route classification from a plain-language request and public URL
- A written distinction between standard support, major work, incident response, and stop conditions
- Controlled reproduction, versioned preview, and agreed verification for accepted pilot work
- Known limitations, missing materials, and customer next steps
- A handoff to Maintenance, Site Intake, or a separate project route when appropriate
Not assumed or promised
- 24/7 support, guaranteed response time, emergency outage response, or security incident response
- Access credentials, private keys, source archives, databases, or customer data through the public form
- Automatic repair of every plugin, theme, server, email, payment, membership, or custom-code problem
- Production changes without a separate approved access and rollback route
- Unlimited human investigation or an active Managed Care retainer
Frequently asked questions
Scope first. Promises second.
What WordPress support requests fit the private pilot?
Requests with an identifiable site, authorized materials, a reproducible problem, manageable production risk, and a result that can be scoped and verified are the best candidates.
Can WPbyAI fix any WordPress plugin or theme problem?
No. Compatibility, licenses, custom code, server dependencies, data risk, missing source, and unsupported stacks can require a separate project or a stop decision.
Do you provide emergency or 24/7 WordPress support?
No. The current pilot does not offer emergency outage response, security incident handling, guaranteed response times, or an unlimited human support retainer.
What should I submit for the first support review?
Submit the public URL, expected behavior, observed behavior, recent changes, business impact, and a plain-language list of materials you control. Do not submit credentials or private files through the public form.
Choose the right route
Different WordPress needs should not be forced into one vague plan.
Existing Site Intake
Use SOURCE/BACKUP or an authorized URL when the available material must be classified first.
View this route →WordPress Maintenance Services
Use maintenance when the requested change and acceptance boundary are already clear.
View this route →Pilot Pricing
See the current Free Check, Site Intake, Launch, Continue, and Done For You boundaries.
View this route →Limited private pilot
Describe the WordPress problem, expected result, and what you control.
Start with a public URL and a non-sensitive summary. We will confirm whether the request fits maintenance, support, Site Intake, a separate project, or a stop condition.