SMF·ZENDESK
Can a prompt replace Zendesk?
Customer support — enterprise support suite
Exhibit tracking slip
Verdict
For a small team, Zendesk Suite Team is ticketing, a help centre and a messaging channel — all of which are ordinary software, which is why this reads as kinda and not no. What the price is actually buying is everything that surrounds it at size: voice with a real carrier behind it, an app marketplace, and the audit, retention and residency controls a procurement review asks about. A personal build can match the day-to-day and cannot match the questionnaire.
Exhibit A — The prompt
Received on31.07.2026Build a help desk with a real customer portal, not just an inbox with a public form.
Stack: your choice, Postgres, Docker Compose. Inbound mail through a signed provider webhook, outbound through a transactional provider on a domain you own with SPF, DKIM and DMARC.
Agent side, kept conventional: tickets with status, priority, assignee, tags, threaded messages, internal notes stored separately from public replies, canned responses, and saved views with filters.
The customer portal is the part worth the week:
- Authentication by emailed magic link, no passwords. Links are single-use, expire in fifteen minutes, and are invalidated on use. Rate-limit requests per address.
- A signed-in customer sees every ticket they submitted, its status, and the full public thread — never internal notes. Write a test asserting an internal note can never appear in the portal response body.
- They can reply, which appends to the same ticket and notifies the assignee, and attach a file with a type allowlist and a size cap.
- Organisations: an email domain can be mapped to an organisation, and a designated member can see all tickets from that organisation. This is the feature that separates a portal from a form, and it is where authorisation bugs live — test that a member of organisation A can never load a ticket from organisation B, by direct URL as well as through the list.
- A public help centre: Markdown articles with categories, full-text search, and each article insertable into an agent reply.
Data handling, because it is the honest half of this entry: a configurable retention policy that deletes closed tickets and their attachments after N days, a per-customer export producing everything you hold about them as one JSON file, and a hard-delete that actually removes attachments from storage rather than orphaning them.
One report: tickets by status and priority per week, median time to first response, and reopen rate.
Write tests for magic-link single use and expiry, for cross-organisation access being refused, and for hard-delete removing files from disk.
Do not build a voice channel, mobile apps, or a marketplace.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the voice channel, which needs a carrier and number provisioning
- B.2 the app marketplace and its deep CRM and commerce integrations
- B.3 data residency, retention policies and the audit log an enterprise review asks for
- B.4 the mobile apps
- B.5 workforce management and quality-assurance add-ons
Prior art
Exhibit C — Why people still pay: compliance and channel breadth
Because Zendesk is the answer that survives a security review, and because once a company has built its reporting and its integrations around it, the switching cost is measured in quarters.
Questions
Why is the customer portal the hard part rather than the inbox?
Because it is the only part with an authorisation model. An inbox is yours; a portal decides which stranger may see which ticket, and the organisation feature turns one mistake into a data leak between two of your customers.
Are magic links safe enough for support tickets?
For this purpose, yes, and safer than passwords nobody will manage — provided they are single-use, short-lived, rate-limited and invalidated on use. Anything that emails a reusable link is a permanent back door in someone's mailbox.
Why build retention and export into a personal help desk?
Because support tickets accumulate personal data faster than anything else you run, and "delete everything you have about me" is a request you may be legally obliged to answer. Building it in on day one is a fraction of the cost of retrofitting it.
How hard is leaving Zendesk?
The data comes out — the API pages through tickets, users, organisations and help-centre articles, and there is a bulk export on request. The expensive part is the integrations and the reports other teams built on top, which is the real switching cost rather than the export itself.
Related tools
Receipt