Contact

Talk to us

There are two ways to reach us, and which one you use depends on whether you already have an account. Both are staffed around the clock.

Support available 24/7 Tickets tracked to resolution English

Two ways to reach us

Pick based on whether you're already a customer. Tickets are tied to your account, so we can see your services without asking you to prove who you are.

Already a customer? Open a ticket

Log in to your client area and submit a ticket. This is the right route for anything touching your account, and it's the fastest way to get a real answer.

  • We can see your services, invoices and server without asking
  • Every reply is logged, so nothing gets lost between shifts
  • Safe place to share account details, never over chat or social media
  • You can reopen it later if the same issue returns
Open a support ticket

Not a customer yet? Use live chat

Have a question before you buy? Start a live chat and ask. No account needed, and you won't be handed to a salesperson who can't answer technical questions.

  • Which plan fits what you're building
  • Whether we can host something specific
  • How migration from your current host would work
  • Pricing, billing cycles and payment methods
Start a live chat

Or email us

Two addresses, and sending to the right one gets you a faster answer. Email is slower than a ticket because we can't tie it to your account automatically.

Service and support

Anything to do with hosting, domains, billing, migrations, technical problems or pre-sales questions. If you're not sure where something belongs, send it here.

support@lucenthost.com

Report abuse

Phishing, spam, malware or other misuse of a site hosted on our network. Include the URL or IP address and any headers or logs you have, so the team can act on it without a round trip.

abuse@lucenthost.com

Worth checking first

Some questions have a faster answer than waiting for a reply from us.

What to include when you write

None of this is required, but a ticket with these details usually gets solved on the first reply instead of the third.