I see this as a cautionary tale for companies adopting AI in customer support. A quick, polished answer can be useful. It can also be dangerously reassuring when the advice rests on the wrong facts. When a customer points out conflicting instructions that could affect a live business, someone with the authority to check the facts and take responsibility needs to step in.

Twice, an automated warning from Hostinger suggested I might need to pay for more resources. The first time, I upgraded and found myself dealing with a server move and a change to my IP address. The second time, I used ChatGPT to compare Hostinger’s replies. The advice kept changing on three things I needed to know before agreeing to a move: whether my IP address would change, what would happen to orders placed during the move, and whether we could switch back if something went wrong. In the end, Hostinger told me I didn’t need to move at all.

The first incident: I followed the upgrade advice

I received an automated email suggesting that I optimize my websites or pay for more resources. I went ahead with an upgrade. I hadn’t realized it would move my hosting, change the server’s IP address, and leave me needing to update DNS records managed outside Hostinger. I was worried about keeping my store and business email running.

One support reply laid out a plan to put the store into maintenance mode, make a final copy of the database, and then update DNS. Later, a technical specialist told me the files and database had already been moved and that the old address was temporarily forwarding traffic. Hostinger said my website and email had remained online. I was glad to hear it. The problem was that I’d spent days trying to establish what had already happened, what I still needed to do, and how much time I had to do it.

The incident lasted well over a week and, by my estimate, involved 30 or more emails. Late in the process, Mathias, a Hostinger manager, reviewed the case and called me. By then I’d spent days trying to untangle problems that Hostinger’s conflicting instructions had created for me. Hearing directly from Mathias gave me more confidence that Hostinger would sort them out. Hostinger acknowledged that the advice had been inconsistent and said it was adding a clearer warning about IP address changes and external DNS to the upgrade process. It also said it had updated guidance for both its staff and its AI agent.

The second incident: I asked for the evidence

When another resource warning arrived, I asked Hostinger to establish what was driving the readings before I paid for an upgrade or approved another move.

Hostinger explained that the warning was an automated usage notice with a standard upgrade suggestion. The notice flagged high usage without establishing what caused it. Support later pointed to repeated interruptions in the database service on the shared server and told me that paying for more CPU or memory would not address the problem it had identified. It recommended moving my sites to a server with a better recent stability record.

That gave me a reason to consider a move. I still needed to know what I was being asked to approve. The written advice changed on three points that mattered to my business:

• IP address and DNS. I was first told my IP address would stay the same. A later reply said it would change and that I wouldn’t need to do anything because Hostinger managed my DNS. It didn’t. I was then told the IP address would stay the same again.
• Orders placed during the move. I was initially told there would be a final database sync before the switch. Later, Hostinger said there would be no second sync and that orders placed after the initial copy could be left on the old server. It recommended putting the store in maintenance mode and said I’d have to reconcile any missed orders myself.
• A way back if something went wrong. Support initially said the old setup would remain available so we could roll back. Later, Hostinger said rollback wouldn’t be possible after the switch. It could provide a copy of the old database, but that would not put the store back on the old server.

A database backup can help you recover data. It doesn’t automatically put a customer’s order into the live store. Had I relied on the earlier assurance and left checkout open, an order could have been left behind. I never approved the move, so that scenario never played out.

Escalation should give the customer someone to speak to

A senior support representative told me she’d been assigned to own the case. I heard from her again the next day, but then went about two weeks without a direct reply from her despite repeatedly asking for her involvement. Other support staff replied in the meantime. Hostinger later said the case had senior oversight and explained that staff worked different schedules.

The second incident lasted a couple of weeks and involved more than 30 emails. In roughly 20 of them, I asked for Mathias to get in touch. Other people at Hostinger replied, but I didn’t hear directly from Mathias until the very last email I received from Hostinger, when the case was effectively closed. By then, the decisions I’d wanted to discuss with him had already been made.

I can’t tell from the outside what decisions were made inside Hostinger. I can say what the process looked like to me. I was told my complaint had been escalated, yet I was still the one comparing different answers about the IP address, checkout, and what would happen if the move went wrong. In the first incident, Mathias’s call gave me a chance to talk through what had happened. In the second, I wanted that conversation while the move was still under consideration.

AI helped me question the advice

I used ChatGPT to go back through the emails, line up the promises, and turn the contradictions into specific questions. Hostinger explicitly labeled at least one response in the first incident as AI-generated. When I questioned whether a particular reply in the second incident was written by AI, the agent told me it wasn’t. I can’t say which other replies involved AI or whether AI caused any of the errors.

The irony is that I used AI to help me do the work I expected the support process to do. It helped me spot when an answer depended on the wrong DNS setup and when a promised final sync disappeared from the migration plan. It also helped me ask whether the unusual traffic Hostinger reported had actually been directed at my websites before I accepted that my sites needed to move.

In my view, the risk grows when a company relies more on automation while giving customers less access to someone who can check the advice and own the outcome. A routine question can be answered quickly. A recommendation that could affect live orders or take a business offline deserves a person who can check the details, give one coherent plan, and explain what changed if earlier advice was wrong.

Where things stand

Hostinger eventually told me it no longer saw a reason to move my sites. It said it had mitigated the database restart issue, that the unusual traffic hadn’t targeted my websites, and that no changes to my hosting or DNS were needed. Hostinger apologized and applied a free hosting extension. I appreciate that gesture. It doesn’t change how much time I spent trying to get a dependable answer.

If you’re considering Hostinger for a live business, I’d ask what happens when an automated alert recommends an upgrade and the support advice starts to conflict. Who can review the underlying evidence? Who is responsible for the technical plan? Can you speak with that person before you’re asked to approve a change that affects your store?

I’d welcome Hostinger’s response on what it has changed since these incidents, particularly how it distinguishes a resource warning from a recommendation to pay for more capacity and how customers can reach someone accountable when the advice they receive changes.