WordPress incident
Critical error, broken page, abnormal display or conflict visible after a recent change.
See interventions →
WPASSIST Support
Slow site?
Slow site?
Critical error?
Payment blocked?
Blank page after an update, visible slowness, critical error, blocked WooCommerce cart or checkout: describe the symptom, the business impact and the most recent change. WPASSIST directs you to the right audit, intervention, Care plan or partner scoping call.
✓Slow or unstable site
✓Critical error / blank page
✓Blocked cart or payment
✓Risky update
Choose the right path
No need to panic. Pin down the urgency.
We handle the technical side.
WooCommerce blocked
Cart, payment, shipping or checkout flow that's blocking an order.
WooCommerce package →Need to clarify
Imprecise symptom, slowness, instability or technical doubt before choosing an action.
Start with AuditWP →Care follow-up
Request related to a site already under our care: maintenance, monitoring or a scoped action.
See Care →Partner request
Agency, freelancer or reseller who wants to scope a client or a portfolio of sites.
Talk partnership →Support request
Open a request
Qualification form. It should never receive passwords, API keys or sensitive access. Those must go through an appropriate channel after scoping.
Before we act
Access should never be handed over just any way.
For a real incident, access may be necessary. It should only be shared after scoping, at the minimum useful level, with a plan to revoke it once the work is done.
WordPress access
Temporary account, matching role, removed after the intervention.
Hosting
Only if the problem requires files, logs, PHP, backups or DNS.
WooCommerce
Order context, payment, shipping, related extensions and screenshots.
Backup
To be planned before any sensitive action. Restore depends on the actual context.
Support FAQ
Frequently asked questions
Short answers to set expectations before sending a request.
It's a support page. It's meant to qualify the request and route it to the right offer or intervention, not to receive a vague message with no context.
No. Sensitive access should never be sent through the form. It can be requested afterward, through an appropriate channel, once scoping confirms it's actually needed.
Describe the problem and its real impact. If the need is unclear, it's better to start with an audit than to order an intervention at random.
No. Support is there to qualify, route and handle what's been scoped. Some cases require an audit, additional access, or a broader intervention.