WordPress Hosting Support: 11 Real Tickets Inside Our Helpdesk

It is 20:12 on a Thursday in March. A customer called Bex submits a support ticket: a page on a WordPress site she manages renders fine when she is logged in as admin, but blank for visitors in incognito mode. Six minutes later, a reply lands. Four numbered diagnostic steps. Twenty-one minutes after that, Bex writes back: "Thanks for your quick help." The whole ticket is closed in thirty minutes.

This is what WordPress hosting support looks like inside a UK hosting company that is not WP Engine, is not Kinsta, and is not running a global call centre operation. We have been doing it this way since 2001. We are going to show you eleven recent tickets in detail, with timings, customer reactions, and some uncomfortable numbers about how small our entire helpdesk really is. The post that inspired this one was the marketing-overview piece WordPress Hosting That Actually Helps. This one is its evidence-led twin.

Most listicles will tell you the best WordPress hosting in 2026 is Bluehost or Hostinger or whoever paid the affiliate the most. We do not have an affiliate budget. What we have is the helpdesk, the tickets, and the reviews.

A Thursday Evening WordPress Hosting Support Ticket

Let's go back to Bex on that Thursday evening. Her ticket described a real WordPress problem with a clear cause hidden behind it: "this page views fine when I'm logged in as admin, but in an incognito window it shows a blank page." Most non-technical users would have spent an hour Googling and walked away frustrated. Bex submitted a ticket because she trusted us to know what to look at first.

The reply she got was four numbered steps:

1. Put your edge caching into development mode
2. If that fixes it, switch off all JavaScript optimisations first
3. If it still doesn't work, deactivate non-essential plugins
4. Stay in development mode the entire time you are testing

That is not a generic "have you tried turning it off and on again". That is a real diagnostic protocol. We sent it because we know what edge caching plus aggressive JavaScript optimisations plus a stack of plugins tends to do to a logged-out browser. Bex worked through the steps in 21 minutes. One plugin was injecting JavaScript that broke for non-logged-in visitors. Another was a casualty of the optimiser. She replied "Thanks for your quick help". The reply from us was three words: "Yay! Brilliant!"

That is not the response a global helpdesk would send. It is also not the response we would send to a stranger. Bex isn't a stranger. She left a 5-star review back in 2020 calling 365i support "insanely fast" and "above and beyond the call of duty". The review is still on Google. The recent ticket is the same support, six years later, with more evidence.

449 Tickets in Our Entire WordPress Hosting Helpdesk

The screenshot below is our helpdesk dashboard. The number in brackets next to "Support Tickets" is the lifetime total in this ticket system. Not last month. Not last year. Lifetime.

449 tickets.

WP Engine handles more than that on a Tuesday morning. Kinsta's support volume is measured in millions per year. Bluehost runs an international call centre that never sleeps. By any metric the hosting industry uses to measure itself, 449 is a low number, and our instinct was to hide it.

We are not going to. The 449 is the entire point.

A small ticket count says three things that no listicle ever considers:

• The platform mostly works. Customers do not constantly open tickets because things are not constantly breaking. Our autoscaling cloud platform with unlimited LVE resources, our server-level web optimisations, and our managed WordPress stack handle the day-to-day without intervention. The fewer "my site is down" tickets we get, the better the platform is doing its job.
• Tickets get the founder's attention. At 449 lifetime, we can plausibly remember most of them. The 8:18 PM reply to Bex came from Mark, the same Mark whose name is on the company. WP Engine support staff do not know who their customers are. We do.
• The customer base is selective. Three of the eleven tickets in this article came from the same agency owner. Two came from the same individual customer in different months. We know who these people are. We know what their sites look like. That is not a feature you can build into a global call centre.

We do not run a high-volume support shop. We never want to. If hosting at scale meant losing the ability to remember every ticket, we would scale slower.

What a 4-Minute WordPress Support Response Time Looks Like

What is a fast WordPress hosting support response time? A fast first-response time on WordPress hosting support is anything under one hour for general questions and under fifteen minutes for site-down emergencies. The industry average is far slower: free WordPress plugin support averages 1.3 days, premium plugin support targets 48 hours, and most managed WordPress hosting providers do not publish a number at all. A median first response under five minutes, like ours across this sample, is at the fast end of what is observable.

Across the eleven recent tickets sampled for this piece, the median time from "I need help" to "here is what to do" is under five minutes. The fastest reply was 2 minutes 13 seconds. The slowest weekday-hours reply was 17 minutes 50 seconds (a complex DNS and SPF diagnosis on a Friday afternoon, where the right answer required actually investigating before replying). The arithmetic mean sits at about four minutes.

Held up against the rest of the WordPress support industry, those numbers look unusual:

WordPress hosting support response time comparison (first response, published targets)

Service type	Example	First response target	Source
Free WordPress plugin support	WordPress.org plugin forums	1.3 days (average)	CreativeMinds, 2023
Premium plugin support	Gravity Forms	48 hours (during support hours)	Gravity Forms (published)
Specialist WordPress maintenance	Maintenance-WP	1 hour (emergencies)	Maintenance-WP (published)
Specialist third-party WordPress support	Fixed.net	Sub-2 minutes (claimed average)	Fixed.net (published)
UK managed WordPress hosting (this article)	365i WordPress hosting	Under 5 minutes (median, 11 sampled)	365i helpdesk, 2026

We are a hosting company, and our first-response speed across the sample sits within the same range as the fastest specialist support shops on the internet. It is also faster than most managed-WordPress hosts admit to in their published SLAs.

The real headline is the floor, not the median. Our slowest reply across the sample was a Saturday-night ticket from a brand new customer ("I haent got a clue how to set up the domain as an email address") that landed at 23:21 and was answered at 06:15 the following Sunday morning. The reply included a custom-recorded screencast video walking the customer through their specific control panel. Most hosts would not have replied at all until Monday.

Another reply went out at 22:56 on a Thursday night to a customer asking about a PHP memory limit warning. The customer rated the ticket five stars after the issue was resolved. Stars on tickets are rare in our system because most customers just say thanks. Five stars on a 22:56 reply is the kind of detail that does not show up in a comparison table.

When WordPress Hosting Support Says No

The least talked-about part of WordPress hosting support is the part where you tell a customer the answer is not on your platform. Most hosts do not do it. We do. Here is one example. A ticket arrived at 16:51 on a Friday afternoon from Peter, who runs the website for a Northamptonshire signage business. WordPress could not connect to his SMTP host. He was getting "SMTP Error: Could not connect to SMTP host. Failed to connect to server. SMTP code: 101. Additional SMTP info: Network is unreachable". His ticket included four very specific technical questions about ports 465/587, internal SMTP relays, and IPv6/AAAA DNS records.

We replied 18 minutes later with a full diagnosis. The DNS records resolved fine. His SPF record was correct. The problem was that smtp.northamptonsigns.co.uk was not actually an SMTP host. It was just a webspace subdomain. WordPress was trying to send mail through a server that does not run a mail service, because at some point the original developer had assumed the subdomain would just work.

The right answer wasn't "we will fix this for you". The right answer was "this is not ours to fix".

We could have papered over it. We could have set up an SMTP relay on our platform, charged a few quid a month, and made the problem go away. Plenty of hosts do exactly that. But Peter's actual mail provider was not us, and the transactional mail he wanted to send needed a transactional email service. So our reply pointed him at MailerLite (or any equivalent transactional provider) and explained how to wire it into WP Mail SMTP.

That answer cost us a potential mailbox upsell. It also kept Peter's site honest. The decision was not agonised over. It happened in eighteen minutes, on a Friday afternoon, because the technically correct answer was clearer than the commercially convenient one. This pattern repeats. We say no on tickets where the request is outside what we cover, where a third-party tool is the better answer, or where the customer is asking us to do something we do not think is in their interest. The longer SMTP-and-email-deliverability story for WordPress sits in our companion piece Why Your WordPress Emails End Up in Spam, written for the same kind of customer Peter is.

If you are wondering why some hosts have suspiciously high ticket volumes for "simple" things, this is part of why. Saying no is part of the support model.

Bespoke Screencast Videos in WordPress Support

Late on a Saturday night, a customer called Christopher submitted a ticket. The text was four words long: "I haent got a clue how to set up the domain as an email address for myself and the team. Can i do it? How do i do it?"

The reply went out at 06:15 on Sunday morning. It contained one sentence and a link:

"I created a short screencast video for you that should be easy to follow."

The video showed Christopher exactly how to set up an email account on his account, on his control panel, with his settings. Not a generic tutorial. Not a knowledge-base article from 2019. A bespoke walkthrough recorded in fifteen minutes by Mark, with Christopher's specific situation in front of him.

This is not a one-off. The week before, we sent another customer (Gillian, also non-technical, also asking about email setup) a different bespoke screencast video. The reply went out 2 minutes 13 seconds after she opened the ticket. The week before that, two more videos went out to two more customers. The pattern is recurring.

When a customer is non-technical, or the explanation has a lot of "click here, then here, then here" steps, we record the video. It takes us about ten minutes. It saves the customer hours.

No knowledge base ever built can do this. AI chatbots cannot do this. Pre-recorded tutorials do not help when the customer's panel looks different from the recording. What works is a real person, recording a real video, on the customer's actual setup. Our free 1-to-1 WordPress assistance page is the formal name for what is actually just "we will record you a video if it helps".

Mathew Patterson, Customer Educator at Help Scout, summarised the same idea in an interview with Authority Magazine in 2023:

"There are times when just having someone listen and respond to you, person to person, is like magic."

Mathew Patterson, Help Scout, Authority Magazine, July 2023

It is the part of our support model that competitors cannot replicate easily. WP Engine could do it in theory. They do not, because the maths does not work at their scale. At our scale, it is just how Tuesday afternoon goes.

Re-Registering a Customer's Domain at Our Cost

The strangest support interaction in our recent history was not technical at all.

Yasmin had registered a domain through us. The next day she opened a ticket: "I chose wrong site. I meant to choose the dot com. Can this be adjusted?"

The honest answer was no. Once a domain registration goes through, the registry has it, and the registrar (us) cannot unwind it without paying for a transfer or starting again. We could have left the conversation there. Yasmin would have been out a year's registration fee, paid for the wrong TLD.

We did not. The reply read:

"I'm afraid it cannot be undone once registered. However we would like to help you, if you can confirm the domain you want we will register it for you free of charge."

Yasmin came back with the correct domain. We registered it for her. We paid for it. It went onto her account at no charge. Total cost to us: roughly £15.

That was not a marketing decision or a "delight the customer" play out of a corporate playbook. It was just the right thing to do. Yasmin had made a real mistake. She apologised. The reply she got was: "These things happen, I've even done that myself in the past. No worries."

This is the kind of moment that does not show up on a feature comparison sheet. It also does not happen at hosting companies that measure their support team on cost-per-ticket. We do not. Most of the same logic applies on every domain transfer we handle, and on every free site migration where we end up doing more than just moving files.

What 365i WordPress Hosting Support Is and Is Not

We have made a few claims in this post. They are worth tightening up.

What our support is

• 7 days a week. Including evenings, weekends, and bank holidays. Most replies come from Mark, with help from Mike and Pippa during busier periods.
• Fast in practice. The eleven-ticket sample shows around 4-minute median first response, with two sub-three-minute replies and three out-of-hours staff replies.
• Personally handled. No chatbot triage. No Tier 1/Tier 2/Tier 3 escalation tree. Every ticket goes to a human who can solve it or knows who can.
• Includes bespoke screencast videos when they help. Two went out the fortnight before this article was written.
• Willing to absorb cost when it is the right thing to do. Yasmin's domain re-registration. Sometimes a free SSL setup. Occasionally a free site migration that turns into a free site rebuild.
• The same team for all customers, whether you are on WordPress hosting, web hosting, agency hosting, or you have just registered a domain. The same humans answer all the tickets.

What our support is not

• Not 24/7. We do not man phones overnight. We are not pretending to. The data centre infrastructure runs 24/7 with on-site technicians. Our human support is 7 days a week with extended hours.
• Not transactional email setup. If you need WordPress to send a thousand newsletters, that is what services like MailerLite and Resend exist for. We will point you at the right tool. We will not fake-fix it.
• Not WordPress development. We can fix things on our hosting platform. We do not build custom themes, write plugins for clients, or do site redesigns. For that we would refer you to our sister site 365iwebdesign.co.uk.
• Not enterprise SLA territory. We do not sign 99.99% uptime contracts with penalty clauses. The platform delivers it. We just do not paper it.

We have been around since 2001. We have 65 five-star Google reviews at the time of writing and zero negatives. One of the recent reviewers said it best:

"Mark on ticket chat, live chat, customer service top notch so easy to get in contact and so super helpful! THanks guys!"

Callum Wilson, Google review for 365i

Callum has had three of the eleven tickets in this article. The recent ones are not different in shape from the review he left a year ago. The support has not changed. The platform has not changed. We have just added more receipts.

If you want managed WordPress hosting that runs almost everything itself, with a tiny UK team that picks up the messy edges quickly when it does not, that is what we are. If you want a global call centre and a CRM telling you which tier of agent you have reached, we are the wrong fit. That is the honest scope. If you are still on the fence about moving to a smaller UK WordPress hosting helpdesk, the companion piece Scared to Switch WordPress Hosting? walks through what the actual switch feels like, ticket by ticket. For deeper WordPress build, plugin, and maintenance work that sits outside hosting, our sister site Press Forge handles the development side.

Frequently Asked Questions