Contact support
How to reach the Zyan team, what to put in a message so it can be answered on the first reply, and what happens after you send it.
If the documentation has not solved it, write to us. A good message is answered once. A vague one costs a day in back-and-forth, so the checklist below is worth sixty seconds of your time.
Before you write
Two pages resolve most reports faster than a ticket can:
- Common issues — the symptoms people report most, with the cause and the fix.
- What to expect — whether the thing you are chasing is gated by your plan, owner-only, waiting on Zyan to arm it, or not built yet.
How to reach us
Use the contact links on the Zyan website. Write from the email address on your Zyan account where you can — it lets us find your workspace without asking.
There is no support ticket page inside Zyan
Nothing in the admin portal raises a ticket with us, so do not go looking for one. The requests and approvals inboxes are your clients writing to you, and the portal Help page is written for them, not for you. The website contact route is the door.
What to include
What you were trying to do
In one sentence, in your own words. “Publish a lead form” is enough.
The page you were on
Paste the URL. It identifies the workspace, the surface and often the exact record.
What you expected to happen
What actually happened
Quote the on-screen message exactly if there was one. The wording maps straight to a cause, and a paraphrase usually does not.
When it started
First time ever, or working until a particular day? Tell us what changed around then — a plan change, a new teammate, a reconnected integration.
A screenshot if anything is visual
A status pill, a greyed-out button or a readiness chip is worth a paragraph of description.
Never send credentials
Do not paste API keys, capture tokens, webhook URLs, passwords or client data into a support message. We never need them. If you think a secret has been exposed, say so plainly and rotate it — do not include the value.
What happens next
You will get a reply to the address you wrote from, on the same thread. If the cause is something you can change, the reply names the exact setting. If it is something only Zyan can arm for your workspace, we will tell you that plainly rather than sending you looking for a switch that is not there.
Urgent and blocking? Say so in the first line, and say what it is blocking — a client launch reads differently from a preference.