How to handle an abuse report about a client

An abuse report about one of your clients — spam, malware, harassment, copyright infringement, or something else entirely — is one of the less pleasant parts of running a hosting business, and it is also one where handling it badly causes far more damage than the original problem. The goal is a process you can follow calmly every time, not a decision made under pressure from whoever is most insistent.

Where reports come from

Reports may reach you directly from an affected third party, or come to us first and get passed to you, since you hold the client relationship for accounts on your reseller plan. Either way, treat it the same: as a claim that needs checking, not a verdict that needs enforcing immediately. Genuine abuse reports and mistaken or malicious ones both arrive looking equally urgent, and the only way to tell them apart is to actually look.

Investigate before you decide anything

Look at the actual account: the specific content, page or activity named in the report, not just the client's site in general. If the report concerns something technical — spam originating from the account, malware, a compromised script — check what is actually happening rather than assuming the report's description is complete or accurate. This step alone resolves a surprising number of reports, either by confirming the problem clearly or by revealing it does not match what was reported.

Check it against your own terms, not your own opinion

Your decision should be grounded in your written terms of service and acceptable use policy, not a judgement made fresh each time. If you do not have clear terms covering the kind of content or activity in question, that is a gap worth closing — what your hosting terms need to cover sets out what a proper policy needs to address, and having one in place before a dispute is far better than writing the rule after the fact to justify a decision you have already made.

Act proportionately

The right response depends entirely on what the investigation found:

• A misunderstanding or no actual breach. Reply to the reporter explaining that, and take no action against the client.
• A minor, fixable issue. Contact the client, explain what needs to change, and give a reasonable window to fix it before considering anything further.
• A clear, serious breach. Suspend the account while the situation is resolved — see how to suspend and unsuspend a client account — rather than jumping straight to permanent removal unless the severity genuinely warrants it.
• Illegal content or activity, or something posing an active risk to others — active malware distribution, for instance. This warrants immediate suspension while you work out the appropriate next step, which may include informing the relevant authorities depending on what is involved.

Write it down as you go

Keep a record of the report itself, what you found when you investigated, the decision you made and why, and the action taken. This is not bureaucracy for its own sake — if a client disputes the decision later, or the same issue resurfaces, you want an actual record rather than a memory of what happened and why.

Reply to the reporter

Whoever raised the report is generally owed a response confirming it has been looked into. You do not need to disclose the client's private details or the exact action taken against their account — a confirmation that the matter has been investigated and addressed appropriately is usually sufficient, and it closes the loop for someone who took the time to raise it.

Handled this way, an abuse report becomes a manageable, occasional part of running a hosting business rather than a genuine crisis every time one happens. If you receive a report you are genuinely unsure how to handle, our own abuse reporting process and our support team are there for exactly that kind of situation, and it is always worth asking rather than guessing.