Help desk procurement checklist

A small help desk purchase can still become a long-lived operational commitment. The inbox will hold customer history, support promises and integrations that are difficult to move quickly. A procurement checklist protects the decision from a persuasive demo or a low entry price that does not include the required workflow.

The checklist below is intentionally proportionate. A two-person email team does not need an enterprise tender, but it does need evidence that messages will be owned, customers can reply, permissions are safe and the bill will be understood at the next hiring point.

1. Write the use cases before contacting sales

Choose five representative cases: a normal email, a handover, an overdue promise, an issue needing another team and a customer who replies after the case was marked solved. Add the channels you actually use, not every channel a vendor sells. Write the expected result for each case and mark must-have versus optional. The selection guide shows how to turn queue problems into requirements.

2. Verify plan and people fit

Confirm the exact edition that contains each must-have: shared inbox, private notes, collision warnings, automation, knowledge base, SLA and reporting. Count all paid agents, supervisors and occasional specialists. Ask whether a feature shown in a demo requires an add-on or higher tier. Save the written feature grid and note any contract-specific promise. Do not score an unavailable feature as present because it appears in a vendor's general marketing page.

3. Put costs on the same basis

Use the total-cost calculation for today, peak demand and the next team size. Ask for an itemised quote covering seats, billable tickets, AI, integrations, onboarding, tax, support and annual renewal. Record billing currency and what can change mid-term. A quote should say what happens if you add or remove users, exceed an allowance or move to a higher plan.

4. Check security, privacy and data location

Request the current security overview, data processing agreement, subprocessor list, hosting/residency detail and incident contact path. Use the security checklist and UK GDPR buyer questions to decide which answers are needed for your data. Test MFA, roles, an agent leaving, export and deletion in the intended plan. A trust certificate is useful evidence about defined controls, not proof that your own account is configured safely.

5. Pilot the real queue

Run the same safe test cases in each finalist and record pass, workaround or fail. Connect a test support address, send a customer reply and inspect the complete thread. Test migration of a small active case sample, not the entire archive. Check how the reporting definitions match the team's dashboard. Include a mobile or remote-agent check if that is how the team works.

6. Read the exit and renewal terms

Ask how to export tickets, contacts, attachments, notes and knowledge content; which format is available; and whether API or export access changes by plan. Confirm the termination notice, data deletion schedule and treatment of unused prepaid fees. An exit test is not pessimism—it tells you whether you can protect customers if the product stops fitting.

Decide with a short evidence record

If a must-have fails, either document an acceptable workaround with its cost and owner or remove the candidate. The demo-question guide helps get evidence before the pilot; the implementation checklist picks up after the decision.

Sources and product documents

• ICO: controller–processor contract guidance
• Freshdesk pricing and plan grid
• Zendesk UK pricing
• Zoho Desk pricing comparison

The sign-off structure is Support Sorted's editorial recommendation, not legal or procurement advice.