Questions to ask in a help desk demo

A help desk demo should answer whether the product can run your support operation. Vendors naturally show polished features; buyers need to see the awkward everyday case: a message arrives at the wrong time, needs another team, waits for an answer, is reopened and must still appear correctly in a report. A buyer-led script makes the call comparable across providers.

Send the script in advance and ask for the exact plan being quoted. If the vendor cannot demonstrate a feature live, record whether it is unavailable, plan-dependent, needs configuration or is on a roadmap. None of those is automatically a rejection, but they are different from “included today.”

Start with one complete ticket

Ask: “Can you create a customer email in the demo account, show who owns it, add a private note, reassign it, reply as the customer and reopen it?” Watch the whole journey. Can two agents see each other's work? Is the customer history intact after the handover? What happens if an email reply arrives after the ticket was solved? Ask to see the same journey on mobile if the team uses it.

Then ask for the failure path. What if the incoming address stops forwarding, a rule misroutes the case or an integration cannot find the order? How does a lead discover unassigned or ageing work? The pilot guide turns these questions into independent tests.

Ask about the working plan and bill

“Which edition, add-ons and paid roles are enabled in this demo?” is essential. Ask whether the shown knowledge base, SLA, custom report, channel and permission control are included in the proposed quote. Ask how the bill changes when another agent joins, tickets double for one month or AI usage exceeds an allowance. Request the unit definitions in writing. The total-cost model gives you comparable scenarios to send to every vendor.

Do not accept “we can do that” without asking how. A custom integration, marketplace app or manual workaround can be entirely reasonable, but it has an owner, price and maintenance burden.

Ask for the report, not a reporting promise

Show the vendor your desired weekly report: new work, closing backlog, first human response, full resolution, reopens and customer feedback. Can they reproduce it with the current edition? What is the underlying event definition and data refresh interval? Ask to open the oldest tickets from the chart and export a sample. A dashboard that cannot be reconciled to real cases will be difficult to trust.

If your team relies on ecommerce context, ask the vendor to find an order from the ticket and explain what happens when the customer email differs from the order email. If the buyer is a SaaS team, use an account or incident scenario instead. The demo should reflect your risk, not a generic prospect story.

Cover security, privacy and exit

Ask how MFA, agent roles, departing-user access, audit records and data export work on the quoted plan. Request the current DPA and subprocessor list for review rather than asking a salesperson to declare “GDPR compliance.” Ask where tickets, attachments, backups and AI prompts may be processed. The security checklist and UK GDPR questions give a fuller review path.

Finally ask: “If we leave in two years, what can we export, in what format, and what happens to the remaining account data?” A vendor willing to show the exit route is giving you useful buying evidence.

Finish with a decision log

Use the same script for HelpDesk, Freshdesk, Zendesk, Zoho Desk or any other finalist. The procurement checklist keeps those findings alongside cost and contract review. A good demo narrows the shortlist; a good pilot proves the choice.

Sources and provider starting points

• HelpDesk pricing and feature overview
• Freshdesk pricing and feature overview
• Zendesk UK pricing and plans
• Zoho Desk plan comparison

The demo script and decision log are Support Sorted's editorial guidance.