Start with the requests your team handles, the channels customers use and the records you need to keep. Compare a working support process and its full cost, rather than treating every helpdesk feature as interchangeable.
Start with your support channels
An email-based support team has different needs from a contact centre handling voice, messaging and complex routing. Frappe Helpdesk documents email tickets, team assignment, customer access and a knowledge base. Zendesk offers different support and Suite plans with channel, automation and reporting differences. List the channels you actually use and demonstrate each one in the proposed setup. A telephony connection or an AI feature needs its own capability and cost check.
Compare the decisions that affect daily work
| Decision | Frappe Helpdesk | Zendesk |
|---|---|---|
| Software and hosting | AGPL-3.0 open-source software, with managed Frappe Cloud or a maintained self-hosted installation. | Vendor-hosted subscription service; compare the exact support or Suite plan. |
| Agents and capacity | No per-agent software licence fee. Hosting still needs enough processing and storage for the actual workload. | Base subscriptions are typically priced per agent; billing term and selected add-ons affect recurring cost. |
| Email and customer access | Email conversations become tickets; the customer portal can submit and track requests and search supplied help articles. | Ticketing is available; check which plan includes the channels, help centre and customer experience you require. |
| Response targets | Priority-based first-response and resolution timers use configured working hours, holidays and pause conditions. | Compare the plan-specific SLA and routing controls against the same response rules. |
| Additional channels and systems | Supported connections require configuration; provider fees, compatibility and extra implementation scope need review. | Check included channels, integrations, usage charges and any paid applications or add-ons. |
Run a small support exercise
- Email a realistic request, reply from the helpdesk and answer from the customer inbox. Check that the conversation stays together.
- Assign it to the right team, add an internal note, hand it to another agent and verify what the customer can see.
- Test an urgent request arriving after working hours and another waiting for a customer reply. Check the intended timers.
- Have a customer find a help article and submit a ticket through the portal. Test access using a second customer account.
Check history before planning a move
Ask which ticket records, comments, attachments, users and organizations must move, and which history can remain in an accessible archive. Zendesk’s standard CSV export excludes ticket comments and descriptions. Its file-export tools depend on plan and enabled access; the official API provides another export route. Review real samples before choosing a transfer method. An export file is not a ready-made Frappe import. Agree field mapping, identities, dates and a trial comparison before changing the live support address.
Keep the quote and service promises clear
Fullsend’s one-time Helpdesk setup covers one support email address, teams and routing, the customer portal, agreed ticket SLA rules, up to ten supplied knowledge-base articles and training. Hosting and optional ongoing support are separate. Ticket-history migration, article writing, additional inboxes, telephony and custom integrations need an agreed additional scope. Configuring an SLA timer tracks your team’s targets; it does not create a Fullsend response-time guarantee. Compare first-year setup and recurring costs, including storage, channel usage and maintenance responsibility.
Choose from the tested workflow
If Zendesk already supports essential channels or routing reliably, assess the disruption and retraining before moving. Frappe Helpdesk is worth evaluating when its tested workflow fits and you want an open-source system without agent licence charges. Name the person who will maintain hosting, updates and support rules, then agree what a successful pilot must demonstrate.
Related decisions
Official references: Frappe Helpdesk hosting, licensing and agent billing · Frappe Helpdesk email and team setup · Frappe Helpdesk customer portal · Frappe Helpdesk response targets and working hours · Zendesk plan features and billing structure · Zendesk export access and format limitations