KICKHOST SUPPORT
Customer Service Policy
How KickHost supports customers, how to reach us, and what you can expect from our team.
01Purpose and scope
This policy explains how KickHost support works: the channels available, what is covered, how requests are prioritised and how to escalate a concern. It applies to hosting, domains, email and related services.
The specific response and resolution commitments for your plan are confirmed in your order or service description. This page explains the general approach; it does not create a service-level agreement where none is stated.
02Support channels
| Channel | Best for | How it works |
|---|---|---|
| Client area ticket | Account, billing, technical and domain issues | Creates a tracked record and keeps the history with your account. |
| Knowledgebase and guides | Self-service setup and common questions | Available at any time; no account needed. |
| Contact form | Sales, pre-sales and general enquiries | Routes your message to the right team. |
| Abuse and security contacts | Spam, phishing, malware, vulnerabilities | Handled under the abuse and disclosure policies. |
Telephone or account-management options, where offered, are confirmed with your service and market. Support is not provided by social media direct message or by contacting staff personally.
03Support hours and time zones
Support is delivered online. The hours that apply to your plan and market are shown in the client area or your service description. Critical security and abuse reports are monitored outside normal hours where the channel is designed for them.
We aim to answer within the published target for your plan, but a target is not a guarantee. Complex issues, third-party dependencies and requests that need information from you can take longer.
04What is covered
Support covers the operation of the service and our platform, including:
- Activation, provisioning and access problems.
- Faults in the hosting, email, DNS or control-panel service we provide.
- Domain registration, renewal, transfer and DNS issues we can act on.
- Billing, invoice and account questions.
- Guidance on using the features included in your plan.
- Migration assistance where it is included in your order.
05What is not covered
Unless it is part of your service, support does not include:
- Building, redesigning or debugging your website or application.
- Writing or fixing custom code, themes, plugins or third-party integrations.
- Administering your email users, mailing lists or DNS records for you.
- Recovering data that you did not back up.
- Support for a third-party product under someone else’s terms.
- Training on general web development or software not supplied by us.
We may offer help with some of these as a separate service. We will tell you if a request falls outside your plan.
06Prioritisation
We prioritise by impact and urgency, not by the order in which tickets arrive. A useful report helps us judge both.
| Priority | Typical situation | Approach |
|---|---|---|
| Critical | Service-wide outage, security incident, data loss risk | Investigated immediately, with updates as information becomes available. |
| High | A service is down or unusable for you, or a domain is at risk | Treated ahead of routine requests; may need verification or a fix from you. |
| Normal | A feature is not working as expected, or a configuration question | Handled in queue order within the plan target. |
| Low | How-to questions, advice, feature requests and feedback | Answered when capacity allows; may point to documentation. |
07Information we need
To investigate efficiently, include the affected domain or service, the time the issue started (with time zone), the exact error, what you have already tried, and what a good outcome looks like.
Never send passwords, one-time codes, full card numbers or private keys in a ticket. If we need a credential for diagnosis, we will ask for a temporary one through a secure method.
Keep the ticket updated if the situation changes. If you do not respond to a request for information, we may close the ticket and ask you to reopen it when you can continue.
08Escalation
If a ticket is not progressing, reply within the same ticket and ask for it to be escalated, explaining why the current response does not resolve the issue. We will review the handling and assign it to a more senior person where appropriate.
Escalation is not a way to jump the queue for a low-priority request. It is for a service-impacting issue, a repeated failure to resolve, or a disagreement about the outcome.
For a billing dispute, include the invoice number and the amount in question. For an abuse matter, use the abuse channel rather than opening a second support ticket.
09Complaints
If you are not satisfied with the outcome, ask for the complaint to be recorded. Include what happened, what you want us to do and any relevant ticket or invoice references.
We will review the handling, respond with our position and, where we got something wrong, explain what we will do to put it right. A complaint does not remove any statutory right you have.
For a domain dispute, use the applicable dispute process rather than the complaints route. For a data-protection concern, contact privacy@kickhost.com.
10Feedback and changes
We read feedback and use it to improve the service and the knowledgebase. We may update this policy when our channels, hours or processes change. The date at the top of this page shows the current version.
Contact support through the client area or our contact page.
