Create a Zendesk Account
To create a Zendesk account takes four minutes. One of the fields you fill in during those four minutes is very hard to change afterwards, so read this first.
How to create a Zendesk account
Start a trial from the Zendesk website. You get a working account without a card, populated with sample data, and it becomes your real account if you buy rather than something you throw away. See trials and free options for what the trial covers.
Use a work email on a domain you control, and ideally a shared one such as helpdesk@yourcompany.com rather than a personal address. Whoever signs up becomes the account owner, and the owner holds billing and the deepest permissions. When that person leaves and nobody can reach the mailbox the signup used, transferring ownership becomes a support ticket instead of a setting. See changing the account owner.
Pick your data region during signup if your business needs one. It's not something you flip later on a whim.
The subdomain you can't easily undo
You choose a subdomain, and it becomes yourcompany.zendesk.com. That string then propagates everywhere.
It is in your agents' URLs. It's in your default support address. It is the address of your help centre, and therefore in every link customers have bookmarked and every page a search engine has indexed. It's in your API endpoints, your webhook targets, your SSO configuration and any embedded widget on your site.
Changing it later is possible in some circumstances, and it is a conversation with Zendesk rather than a settings toggle, and everything pointing at the old string needs updating. Treat it as permanent and you will be right often enough.
The first five settings that matter
Do these in order, before you invite anyone, because half of what you configure later reads from them.
1. Account name, time zone and business hours. Every SLA, report and automation you build afterwards is measured against these. Getting the time zone wrong quietly corrupts months of reporting.
2. Your own support address. The default Zendesk address works immediately and looks temporary to customers. Add support@yourcompany.com and publish the DNS records Zendesk gives you, so your replies authenticate and land in inboxes rather than junk. It is worth the hour: see SPF and DKIM.
3. Roles and one more admin. Exactly one other person gets admin, no matter how many ask. Everyone else is an agent. A single admin is a bus factor of one.
4. Groups. Two or three, named after how work is actually distributed. Not fourteen. Adding groups later is trivial, merging them back is not.
5. The acknowledgement trigger and your default views. Confirm that a customer writing in gets an immediate "we have got it" and that your agents open the product to a queue rather than a firehose. See views.
What to leave alone in week one
Chat, voice, WhatsApp, AI features, half the marketplace and twenty custom fields. Every channel you switch on is a queue somebody has to watch, and every field you invent is one an agent will skip.
Turn on security properly instead. Two-factor for admins at minimum, a sensible session length, and a note in your own docs of who holds the owner account. Then go read the Admin Center guide and start working real tickets. Configuration decisions made after you have handled a hundred tickets are dramatically better than the ones made before.
The clean-up nobody remembers
Trial accounts ship with sample tickets and sample users so the interface isn't empty on day one. They're helpful for about an hour, and then they're pollution.
Delete them before you go live. Otherwise your first month of reporting includes a handful of fictional customers, your user list has entries nobody can explain, and at some point an agent replies to one. It happens more than you'd think.
Two other things worth doing in the same sitting. Check that your default views don't reference anything from the sample data, since a view built around a demo tag is quietly broken. And send one real test ticket from an outside address, all the way through to a reply that lands in a real inbox, before you publish your support address anywhere.
That end-to-end test is the whole point of the first week. Everything else is decoration until a customer can reach you and get an answer back.
Frequently asked questions
What happens during Zendesk sign up?
You pick a subdomain and a region, and both are hard to change. To set up a Zendesk account properly, decide those two before you start, because a new Zendesk account inherits them permanently.
Can I change my Zendesk subdomain later?
It's possible in some circumstances and it is not a self-serve toggle. Everything referencing the old subdomain, including help centre links and integrations, needs updating. Choose carefully at signup.
Do I need a credit card to create a Zendesk account?
No, the trial starts without one. You are asked for payment details when you convert to a paid plan.
What happens to my trial data if I buy?
The trial account becomes your account, so anything you configured carries over. Delete the sample tickets and sample users before you go live.
Who should be the Zendesk account owner?
Someone permanent, on a mailbox your company controls. The owner holds billing and the deepest permissions, and transferring it after they leave is more painful than setting it up right.
Can I create a second Zendesk account for a different brand?
Usually you want multibrand inside one account instead, since separate accounts mean separate bills, separate agents and separate reporting.
Set it up clean, keep it clean
Duplicates start on day one, when the same customer emails and then fills in the form. Ticket Merger catches them from the first week.
Start free trial14-day free trial. No credit card required.