Choosing customer support software

Match customer support software to the work your team handles, then check required capabilities in the plan you would actually buy. Start with channels, case ownership, customer context and reporting needs. A dependable way to receive, assign and reply to a request matters more than a long feature list.

Decide what the system must own

List where customers contact you and where those conversations are handled now. Include email, chat, phone or social messages only if your team supports them. For each channel, identify the receiving team, the reply path and the record an agent needs when a conversation continues later.

Separate support work from customer data. A helpdesk may handle enquiries while a CRM holds account records. If service decisions depend on contracts or entitlements, consider whether CRM case management should own the case. Decide which system is responsible for the next customer reply.

Write down the few requirements that could rule out a product: perhaps an essential channel, a required connection to another system, restricted-case access or a reporting field. Keep preferences separate from requirements so the decision remains clear.

Include privacy applicability in the shortlist

For Australian organisations, establish whether the Privacy Act 1988 applies to your organisation before setting privacy-related requirements for a support system. The OAIC says the Act covers organisations with an annual turnover of more than $3 million and some other organisations.

The Act includes 13 Australian Privacy Principles, which apply to some private sector organisations and most Australian Government agencies. Use that applicability check to inform your access and information-handling requirements.

Privacy considerations for Australian organisations

Compare the same work across products

Ask each vendor how its proposed plan would handle the same questions:

These are comparison questions, not features every product necessarily provides. Use the same workflow brief for each vendor so differences in their answers are visible.

Four starting points for a shortlist

Confirm current terms for the product and plan proposed to your organisation.

Zendesk: ticketing with a broader service suite

Zendesk is a candidate when a team wants a ticketing workspace and may need broader channel coverage. Its Support Team plan lists email ticketing, routing, automations and prebuilt analytics. Suite Team adds messaging, live chat and a knowledge base.

Freshdesk: email-first support or a separate multichannel product

Freshworks describes Freshdesk as email-first and Freshdesk Omni as a product that brings email, chat and social messages into one inbox. Both have Growth, Pro and Enterprise tiers, with capabilities that vary by product and tier. Ask for the feature list for the exact product offered; the Freshdesk name alone does not establish channel coverage.

Help Scout: shared conversations and knowledge content

Help Scout is a candidate for teams that want to work through shared inboxes, saved replies and knowledge content. Its plans differ in user and inbox allowances. Standard lists basic workflows, while Plus adds advanced workflows and round-robin routing.

Additional inboxes may carry a charge. AI Answers is a separate resolution-based add-on, so include it in a cost comparison only if the team intends to use it.

Intercom: conversations, tickets and in-app support

Intercom is a candidate when customers contact support through a website or app and the team wants conversations, tickets and help content together. Essential lists Messenger, a shared inbox, ticketing and a public help centre.

Advanced adds multiple team inboxes, a workflow builder and round-robin assignment; Expert adds service level agreements. Intercom charges for full seats and certain usage, including Fin outcomes and some messaging channels. Estimate the cost using the intended configuration and expected usage.

Key capabilities by platform

Use plan differences as shortlist gates

Check whether a proposed plan's capacity fits the team you expect to support. Help Scout lists up to 25 users and two inboxes on Standard, up to 50 users and five inboxes on Plus, and unlimited users with a minimum of 10 on Pro. Its listed inbox allowances are a practical way to screen out plans that do not match your expected team or workspace size.

Freshdesk Growth includes reporting, automation and a self-service knowledge base; Pro adds advanced routing, custom roles and stronger analytics; Enterprise adds multiple service level agreements and enterprise-grade controls.

For Freshdesk Omni, the listed highlights differ: Growth includes a knowledge base, automation and basic reporting, while Pro adds advanced routing, analytics dashboards and WhatsApp campaigns.

Plan capacity limits for team size and workspace needs

Decide on the complete setup

Request a proposal that names the edition, agent roles, channels, integrations, add-ons and billing units. For an Australian purchase, ask which currency is quoted and whether GST is included. Identify who will configure the system and maintain its rules.

Record the decision in plain language: the work the setup covers, the requirements it meets, the gaps you accept and who owns each gap.

Separate organisational obligations from vendor claims

Use the shortlist to identify evidence still needed from each provider. Distinguish requirements arising from your organisation's obligations from operational preferences.

Request product documentation for relevant data-handling capabilities and limitations of the exact plan under consideration. Record any assumptions that need verification.