Help Desk Software or a Shared Inbox? A Buying Guide for Australian Teams
If two people can read the support mailbox but neither knows who should reply, the problem is ownership. If a customer keeps repeating the same issue to different staff, the problem is continuity. Start by naming the support failures you want to fix before choosing between help desk software, a shared inbox and a broader service desk.
Those category names overlap across vendors. One product may use help desk to mean email assignment and tickets; another may include a knowledge base, phone routing or formal service management. Write down the capabilities you need and ask to see them. A category label alone is not evidence that every feature is included.
Map the support journey you actually run
Choose a representative request: a customer reports a delivery problem by email, the first agent needs advice from a colleague and the delivery team must investigate. Record who owns the customer reply at each point. Identify where notes belong, when the conversation is waiting and what counts as resolved.
Use a fictional or anonymised thread in the first demonstration. Include one useful complication, such as an absent assignee or a second email about the same issue. The goal is to discover whether the team can continue the conversation without losing the promise already made to the customer.
Assignment should produce a clear next owner
Ask one person to take responsibility for the conversation, then hand it to another. The next person should be able to identify the request and the reason for the handover. Also test the unassigned state: your operating process needs someone checking work that has not yet found an owner.
Do not treat access to the same email account as the same thing as assignment. A shared login can let everyone see a message while leaving responsibility ambiguous. Ask how intended staff access the mailbox, which permissions they need and how access changes when someone leaves. Verify these answers for your configuration rather than assuming the vendor's administrator demonstration represents a normal agent's permissions.
Define open, pending and resolved in plain language
A status is useful when the team agrees what it means. Open might mean the team needs to act. Pending might mean it is waiting for information. Resolved should mean the agreed support outcome has been reached, rather than someone having sent a reply. Decide what happens when the customer responds again.
Fulcrum's Inbox support desk includes open, pending and resolved conversation states. In a walkthrough, use the same test request to inspect assignment, state changes and the next action. Ask the demonstrator to show a handover that needs further investigation, not just a short question answered immediately.
Keep internal context separate from customer replies
Team notes can record what has been checked, who was consulted and what remains uncertain. They should be clearly distinguishable from an outgoing response. Ask the next agent to read the note and explain what the customer should hear next. If the note contains an unresolved hypothesis, it should not become a confident factual claim in the reply.
Fulcrum supports internal notes on support email threads. Confirm the visible distinction between those notes and customer messages in the actual screens. When testing, use harmless example text. There is no need to send a real customer an artificial message to discover whether a handover is understandable.
Link the conversation to the work behind it
A support email may concern an existing project or technical ticket. Ask how the support team finds that work and how the delivery team finds the customer's description. Fulcrum's Inbox can link an email conversation to an existing ticket. Check which record is the source of truth for ownership and how your staff will keep the support conversation current.
If your team also delivers client projects, evaluate the PM workflow and the project management buying checklist. Customer context starts earlier than support, so also inspect the CRM record that holds the sales relationship. A connected workflow should reduce re-explaining the same issue, but measure that in your own pilot rather than assuming a time-saving percentage.
List advanced requirements before committing
If you need contractual response-time reporting, asset management, a public knowledge base, phone queues or multiple messaging channels, add each as a separate requirement. Ask for a demonstration and the relevant commercial terms. This guide does not establish that Fulcrum Inbox provides every one of those capabilities.
For AI-assisted support, start with a draft based on approved information and a named reviewer. Define what should be escalated and who can authorise a promise, refund or account change. The Cortex task brief guide helps specify a bounded job. Do not assume that adding an assistant removes the need for support ownership or a reliable customer record.
Run a small pilot with an explicit review
Download the help desk evaluation worksheet. Mark the observed capabilities and the unanswered questions. During a pilot, record who handled each sample request, what was missed and how much effort the next person needed to understand it. If response-time measures matter to your team, agree the business-hours definition and verify how you will collect the data.
Before subscribing, confirm mailbox setup, access permissions, migration needs and availability for the intended configuration. See current Fulcrum pricing and request an Inbox walkthrough. Choose the setup that makes the next action clearer for both your team and the customer.
Writing about AI-powered CRM, sales automation, and the future of revenue teams at Fulcrum CRM.

