Support
Support that reaches an engineer
Search the guides first — most answers are there and it is faster. When you need a person, a ticket goes to the engineers who run the platform, around the clock.
Search the knowledge base
Ways to reach us
Open a ticket
The main channel. Tickets reach the engineers on duty, not a first-line script, and the history stays in your client area.
Live chat
For quick questions before you buy. Click the chat button in the corner of any page.
[email protected] reaches the same queue as a ticket, without the account history attached.
Browse the guides
Open the knowledge baseGetting started
Domains and DNS
How to Register a Domain
OpenClaw hosting
First login: the gateway token and approving your devices
Connect Telegram, WhatsApp or Slack
Add or rotate a model provider key
Security advisories
Mitigating CVE-2026-31431 (Linux based systems)
Shared hosting
How can I order a shared hosting plan?
Before you write
What should I include in a ticket?
The domain or server, what you expected, what happened instead, and the exact error text or the time it happened. That is usually enough to skip a round trip.
My site is down — what happens now?
Open a ticket and say the site is down. Platform incidents are handled by the engineers on duty; if the cause is on our side, the ticket is updated as the fix progresses rather than after it.
Do you help with things that are not our fault?
Within reason, yes — a broken plugin, a DNS record pointing at the wrong place, a migration from another host. What we will not do is write your application code.
Is there a phone number?
No. Everything goes through tickets and chat so there is a written record of what was changed on your server, and by whom.