Customer support · checked 2026-10-14

Can I vibecode Zendesk?

KINDA· weekend project

For one person or a small team answering support mail, the core is a shared inbox: poll a mailbox over IMAP, thread replies into tickets, set status and tags, answer through SMTP and keep saved replies. An agent can build that in a weekend. The risks sit outside the code: replies must pass SPF, DKIM and DMARC to avoid spam folders, threading has edge cases, and the ticket store holds customer data you now secure yourself. Chat, phone and SLAs aren't worth building; Zammad covers them and FreeScout is the lighter option.

$25/moprice per seat

$300you'd save a year

weekendbuild time

—people replaced it

Before you start

What you need on hand.

DifficultyAdvanced · Real infrastructure or OAuth work.

TimeA weekend; mail delivery setup is the slow part

Claude Code, Codex or CursorAny of them can run the prompt.
Node.js 22better-sqlite3 compiles a native module, so build tools must be installed.
A mailbox with IMAP and SMTP accessUse an app password, not your main one.
DNS control over the sending domainSPF, DKIM and DMARC records decide whether replies reach inboxes.
A VPS (optional)Needed if the inbox should keep polling when your laptop sleeps.

Before you buildZendesk has no free plan, only a 14-day trial. For one person with little mail, a shared mailbox in your mail provider may already be enough.

1. Install one agent: Claude Code, Codex, Cursor.
2. Make an empty folder and open it in the agent.
3. Paste the prompt below, press enter, and answer its questions as it builds.

The prompt

Build me a shared support inbox to replace Zendesk. Requirements:

- Node.js 22 + TypeScript: a Fastify server and a React front end built with
  Vite. `npm start` serves the agent interface on http://localhost:5100.
- Mail in: poll one IMAP mailbox every 60 seconds (`imapflow`, `mailparser`),
  one ticket per conversation. Thread replies by Message-ID, In-Reply-To and
  References, falling back to a [#123] token in the subject. Credentials in .env.
- Mail out: reply from the same address through nodemailer (SMTP from .env)
  with In-Reply-To and References set. Strip quoted history from inbound
  replies with `email-reply-parser`.
- Storage: better-sqlite3 in ./data/desk.db: tickets (subject, requester,
  status new/open/pending/solved, priority, tags), messages and internal notes;
  attachments in ./data/files/ (25 MB each). Sanitise HTML mail with
  `sanitize-html` and block remote images.
- Agent interface: a ticket list with filters (status, tag) and full-text
  search through SQLite FTS5; a ticket view with the thread, internal notes,
  status and tag changes, and saved replies ("macros") with {{requester.name}}
  placeholders that can also set status or tags.
- Rules: if the subject or sender matches X, set a tag or priority; one
  auto-reply per new ticket; a customer reply reopens a pending ticket; solved
  tickets close after 7 days. Auto-replies carry Auto-Submitted:
  auto-generated, skip no-reply and list addresses, max 3 a day per sender.
- Single agent, one password in .env (signed cookie). No accounts, no
  telemetry, local-first; the only connections are your IMAP and SMTP hosts.
- Out of scope: live chat, phone, social channels, SLA timers, a customer
  portal, several agents, AI replies.
- README: SPF, DKIM and DMARC records to set before sending, running it on a
  VPS, backing up ./data, and a note that stored customer email is personal
  data you are now responsible for.

Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.

Share on X

Max MiskowSponsoredAI agents, automations and MVPs, built for your company.Visit site ›

Then keep going

Next prompts, same folder.

The first prompt builds the core. Run these one at a time in the same folder to grow it into your own Zendesk.

Add multiple agents to the support inbox in this folder. Requirements:

- An agents table with name, email and bcrypt password hash; an admin page to add, disable and reset agents, replacing the single shared password.
- Assign a ticket to an agent or leave it unassigned; filters for mine, unassigned and all.
- @mention an agent in an internal note to email them a link.
- Record who made each status or assignment change in a ticket history list.
- Update the README.

Add a contact form endpoint to the support inbox in this folder. Requirements:

- POST /api/contact accepts name, email, message and an optional attachment up to 10 MB, and opens a ticket with the requester set.
- Hidden honeypot field, a 3-second minimum fill time, a rate limit per IP, and optional Cloudflare Turnstile through an env var.
- Send the requester a receipt email containing the ticket token so their reply threads onto the ticket.
- A small embeddable HTML snippet and CORS limited to an allow-list in .env.
- Update the README.

Add a knowledge base to the support inbox in this folder. Requirements:

- Articles written in Markdown with a title, category and published flag, stored in SQLite with FTS5 search.
- A public, read-only /help site rendered on the server, with category pages and search.
- In the reply box, a Suggest article button that searches the ticket subject and inserts a link to the chosen article.
- Update the README.

Add reply targets to the support inbox in this folder. Requirements:

- Settings for a first-reply target and a next-reply target in hours, plus business hours with a time zone and holidays.
- Compute due times with `luxon`, pause the clock while a ticket is pending, and show a countdown badge in the ticket list.
- A view of tickets due within 2 hours and breached tickets, and a daily summary email.
- Tests that cross a weekend and a daylight-saving change.
- Update the README.

What you lose

Live chat, messaging and phone channels (Suite plans)
AI agents, copilot and automated resolutions
Marketplace apps and connections to the rest of your stack
Skills-based routing and prebuilt analytics dashboards
Several agents working one queue with roles

Why people still pay

A help desk becomes the record of every customer conversation, and a missed email costs more than a seat. Teams pay for the channels, automations and reporting that grow around the inbox, and for a vendor that answers for uptime, security and data handling. Leaving is slow because ticket history, triggers and macros all live inside it.

Moatintegrations switching costs

Do the math

Zendesk or your own copy?

Seats

Over

Your usage

Count my time12h ×$/h

Zendesk, 1 yr$300

Your own copy, 1 yr$49running + build session

You keep$252pays for itself in the first month

Estimate · Runs on a laptop or a $5 VPS, on top of the mailbox you already pay for. The build is token usage on your agent plan.

Leaving Zendesk

Take your data, then cancel.

1 · Take your data out of Zendesk

1Data export is off by default: the account owner asks Zendesk Customer Support to turn it on, quoting the Support subdomain. It isn't available on Team plans, though every plan can read data through the REST API.
2In Admin Center open Account > Tools > Reports, then the Export tab. JSON (newline-delimited, tickets, users or organizations by date range), CSV (tickets only) and XML are offered; the file arrives as an emailed link valid for at least three days.
3CSV leaves out deleted tickets, comments and multi-line fields. JSON skips anything changed in the last 6 minutes, and tickets over 1 MB lose their comments. XML stops working above about 200,000 tickets and leaves out custom fields. AI agent tickets can't be exported.
4The JSON and CSV exports describe tickets, users and organizations. Read macros, triggers and views through the API or copy them by hand.

2 · Cancel Zendesk

1Only the account owner can cancel; billing admins can't. In Admin Center open Account > Billing > Subscription and click Manage.
2Choose Remove products or cancel account, click Cancel account, confirm, then pick a reason.
3The account keeps working until the end of the billing cycle. Sales-assisted accounts can't cancel online and must contact Zendesk Sales.

Export before the cycle ends. After cancelling you can't sign in, and the data is deleted under Zendesk's Service Data Deletion Policy; the owner can ask Support within 90 days for a temporary reactivation, billed for the period in between.
Products can't be cancelled one by one in a Suite account: ask Support to move you to a Support-only account.
Zendesk suggests pausing the account as an alternative to cancelling.
Contracts need at least 30 days' notice before the end of the term; cancelling self-service in Admin Center counts as that notice.

Checked 2026-10-14 against Zendesk's docs: 1, 2, 3, 4

The escape hatch

Don't feel like building it? These are already free.

ZammadOpen sourceAGPL-3.0 help desk for email, chat, phone and social channels, with SLAs and escalations; closest to Zendesk in scope among these.★ 6.0k · active Oct 2026 · docker to self-host
WebVisit ↗FreeScoutOpen sourceLightweight AGPL-3.0 help desk and shared inbox in PHP, billed as a Zendesk and Help Scout alternative, with mobile apps.★ 4.6k · active Oct 2026 · self-host, real ops
WebVisit ↗ChatwootOpen sourceSupport platform for live chat, email and social inboxes with an AI agent. Mostly MIT with an enterprise folder under a separate license.★ 38k · active Oct 2026 · docker to self-host
WebVisit ↗

All 5 free alternatives to Zendesk ›

The numbers

Zendesk pricing

Plan	Monthly	Annual, per month	What you get
Support Team	$25	$19	Email and ticketing, ticket routing, prebuilt analytics dashboards, pre-written responses, customer context, automations and triggers; 5 automated resolutions per agent a month.
Suite Team	$69	$55	Everything in Support Team plus AI agents, messaging and live chat, telephony, omnichannel routing and an AI knowledge base.
Suite Professional	$149	$115	Everything in Suite Team plus skills-based routing, IVR phone trees, AI writing tools and an admin copilot; 10 automated resolutions per agent a month.
Suite Enterprise + Copilot	custom	—	Everything in Suite Professional plus approval workflows, a sandbox, custom agent roles and AI triage.

Billing: Per agent per month. Annual billing is 20% cheaper; monthly, annual and multi-year terms exist. Pay by card, direct debit or PayPal. Plan changes can take effect at once or at renewal depending on your subscription. A 14-day trial is offered.
Hidden costs: AI agent resolutions beyond the included 5 per agent cost $1.50 each when committed or $2.00 pay-as-you-go. Copilot is $50 per agent a month on annual billing and light agents, sandboxes, extra storage, premier support and some voice features are add-ons. Chat and phone mean Suite from $69 per agent on monthly billing.
Source: www.zendesk.com

Also on the list

Intercom$39/mo · Customer supportKINDA

Help Scout$30/mo · Customer supportKINDA

Gorgias$10/mo · Customer supportKINDA

Questions

Zendesk, briefly

Not answered here? Tell us and we'll add it.

Ask a question ›

Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: Live chat, messaging and phone channels (Suite plans), AI agents, copilot and automated resolutions.

About $25 a month on the Support Team plan per seat, $300 a year (checked 2026-10-14).

Live chat, messaging and phone channels (Suite plans); AI agents, copilot and automated resolutions; Marketplace apps and connections to the rest of your stack; Skills-based routing and prebuilt analytics dashboards; Several agents working one queue with roles. If any of those matter to you, keep paying.