WordPress Support
WordPress Support
Every support request starts in ticketing so nothing is missed.
What To Include In The Request
Send the site URL, the page or screen involved, what you expected to happen, what happened instead, and whether the problem blocks sales, leads, staff, or visitors. Include the last change you remember, the time the issue started, and a screenshot when it makes the problem easier to see.
- Do not place passwords, payment keys, private customer records, or authentication codes in the first message.
- Say whether Help4 may work immediately or whether changes need approval before publishing.
- List any deadline, active campaign, checkout impact, or legal/compliance concern that changes the priority.
What Happens Next
Help4 records the request, confirms the affected site and business impact, then routes the work to the right support, design, commerce, security, or infrastructure lane. A complex request may be split into diagnosis, approval, implementation, and verification so the customer can see what is happening instead of receiving a vague answer.
Self-Managed Support
Self-managed plans use ticket-first support. The ticket keeps the request, site details, replies, and completion evidence together. Work outside the active plan may need a separate scope before implementation begins.
Fully Managed Support
Fully managed customers can use ticketing or contact their account rep directly. Routine requests still belong in the ticket so updates, page edits, plugin conflicts, forms, security checks, speed work, and follow-up testing are not lost between messages.
Open Ticket Contact Account Rep
Escalations
Calls can request escalation, but SMS usually escalates faster than the sales queue. Mark a request urgent when checkout is unavailable, a production page is broken, the site shows a security warning, customer data may be exposed, or a time-sensitive campaign cannot run. Urgent does not replace the ticket; it helps the team find the existing record faster.
Call (757) 528-6321 SMS (757) 528-6321 WhatsApp
Before The Request Is Closed
Verify the original problem on the public site, not only in the editor or server. Check the affected desktop and phone view, the important link or button, and any form, checkout, login, or account action involved. Confirm that caches were cleared when needed and that the final page does not show a private preview, maintenance screen, mixed-content warning, duplicate template, or horizontal clipping.
Reply on the same ticket if the result is incomplete. Include the exact URL and what still differs from the requested outcome so the team can continue from the existing evidence instead of starting the diagnosis again.