When a shared support inbox is enough—and when to pay for a help desk

If your team can see who owns each support email and what remains unresolved, an existing shared inbox may be enough. Google Groups already supports assignment and resolution tracking. Consider Zoho Desk Free if you need basic ticket records; pay for a help desk only when a specific coordination problem justifies it. AI is optional, not a prerequisite for assigning responsibility.

This guide uses plans and documentation checked on November 14, 2026. The illustrative business is an online shop with three nontechnical staff, one support address and 100–300 after-sales conversations a month. It already has Google Workspace with Groups for Business permitted, and budgets US$0–90 a month for additional support software before tax. These are buying assumptions, not a customer case or a volume threshold for upgrading.

What does your support queue need to do?

Before comparing subscriptions, agree what a satisfactory working day looks like. A useful queue should let the team answer these questions:

• Who owns each request, who covers an absence, and which requests still need action?

• Can the next colleague see the conversation history and distinguish an internal note from a customer reply?

• Do simultaneous replies cause problems? How many support addresses, responding staff and reports do you actually need?

• Can you configure private access and the correct sending address, afford the full commitment, and retrieve usable records when you leave?

Treat a missing capability as the buying reason. A fourth colleague, a second support address or a recurring reply clash can matter more than the number of emails. A higher plan is useful only if it addresses that requirement.

When is Google Groups enough?

Keep it when named ownership and an unresolved queue meet the job, and staff will consistently use them. A group owner or manager can enable Collaborative Inbox features; conversation history must be on, and the administrator may need to enable Groups for Business. See Google’s setup instructions.

Authorized members can take or assign conversations, mark them complete and filter by assignee or resolution status. Assignment and completion require the appropriate metadata permission. Use the unresolved-conversation filter to keep outstanding work visible without deleting the completed history.

The important distinction is between a shared queue and three separate copies of an email. Do not assume that ordinary forwarding keeps ownership and resolution up to date. Agree where staff claim work and record completion. Google’s reviewed guidance does not establish help-desk-style reporting or concurrent-reply warnings, so do not budget on those capabilities being present.

What will all three people cost?

The table uses public USD list prices checked on November 14, 2026. Each responding employee gets an individual seat; the calculations do not use a shared login. Taxes, optional services, staff time and the existing Workspace bill are excluded. Confirm local currency, any seat minimum and order-specific terms at checkout: this is not a regional quotation.

An annual monthly equivalent is not a cancellable monthly instalment. A $252 or $684 yearly commitment is a different cash decision from paying $27 or $69 month to month. On a paid Zoho plan, budget all three users; the Free allowance is not three extra seats alongside the paid subscription.

Which paid feature would actually change your work?

Zoho Free includes email tickets, internal comments and ticket history. Express adds predefined reports, two direct-assignment rules and one ticket workflow rule. Those are limited automations, not evidence that Free cannot assign work manually. The edition matrix supplies the user and channel limits above; confirm your selected edition before checkout.

If colleagues frequently start answering the same request, Freshdesk documents collision indicators on Growth and above. They show that another agent is working on a ticket; they do not guarantee that duplicate or incorrect replies cannot happen. Retain an owner and handoff rule even when a warning is available. Growth also lists a shared inbox, ticketing, a knowledge base and basic reporting in its current offer.

Zoho’s collision detection starts at Professional, not Express. At the current Professional prices, three users cost 3 × $35 = $105 monthly, above this budget. Annual billing is 3 × $23 × 12 = $828, or $69 a month equivalent. That may fit an annualized budget, but it is not the same obligation as Freshdesk Growth’s $69 monthly bill.

Do you need AI drafts or automatic customer replies?

These are three different choices, with different costs and responsibilities:

• Approved wording: a person adapts a standard acknowledgement or information request. You can keep this in a staff-only document without buying AI. Zoho’s in-reply email-template feature is not included in Free or Express.

• AI-assisted drafting: software proposes wording or a summary; a person checks the order details, policy and promised next step before sending.

• Autonomous replies: software sends messages to customers. This needs approved information sources, clear escalation rules and control over what the system is allowed to promise.

Freshdesk’s AI add-on documentation gives new Growth, Pro and Enterprise customers 500 introductory AI Agent sessions once per account—not every month or per employee. Further packs cost $49 for 100 sessions. For email, a session groups AI replies within 72 hours of the customer’s first email. It is a billing window, not a guaranteed resolution.

A conditional cost example: after the introductory allowance runs out, three monthly Growth seats plus one purchased pack cost $69 + $49 = $118 before tax in that billing month. That exceeds the $90 budget. It does not predict usage: 100–300 customer conversations cannot simply be treated as the same number of billable AI sessions.

Purchased sessions have validity tied to the payment cycle; do not assume unused credits last indefinitely. Before activation, verify pack sizes, charges and automatic-recharge settings in your account rather than relying on a presumed default.

Freddy Copilot, the staff-assistance add-on, is separate from AI Agent. The current pricing cards offer it on Pro and Enterprise, not Growth. Three Pro seats alone cost 3 × $66 = $198 monthly, or 3 × $55 × 12 = $1,980 annually ($165 monthly equivalent), before Copilot licenses. Giving Copilot to just one employee does not remove that base-plan expense.

Zoho Express generative AI is listed as BYOK—bring your own key, meaning a separately connected provider, not an established all-inclusive AI allowance. Its pricing summary and detailed prebuilt-agent row also differ. Do not choose Express on an unconfirmed promise of prebuilt AI agents; verify account eligibility, provider charges and data terms first.

Start with approved wording if repeated writing is the only problem. Consider AI drafting when staff can check its output against reliable order information. Automatic replies require a stronger case: decide which questions can be answered safely, when a person takes over and how spending stops. None of the subscription prices establishes time savings or answer quality.

Who should be able to read customer messages?

Customers should be able to contact the shop without gaining access to its conversation archive. Google provides separate viewing, posting and reply permissions, subject to organizational sharing settings. Restrict archive access to authorized staff, allow the necessary incoming customer messages and check who can reply as the group.

For any tool, review staff access and remove it when responsibilities change. Limit copied customer details to what the task needs. Zoho’s privacy policy distinguishes entrusted service data from account information and explains that enabled integrations can share data with another provider. A connected AI service therefore needs its own data-handling review; a help-desk privacy statement is not a blanket no-training or immediate-deletion guarantee.

Who owns a request after the acknowledgement?

Every open request needs one named owner and a backup for absences. The owner checks what is outstanding, records the next action and hands over explicitly when necessary. Set a routine for reviewing unassigned and unresolved requests.

An acknowledgement confirms receipt; it does not resolve a missing delivery or authorize a refund. Agree wording for receipt, requests for missing information and the next promised update. Keep refunds, policy exceptions and delivery commitments with a designated human. This is an operating rule, not a claim that the cheapest plans include a formal approval workflow.

How can you try a new queue without confusing customers?

Name the person responsible for mailbox configuration before signing up. Zoho documents forwarding and sender verification; Freshdesk documents mailbox access, administrator permissions and email configuration. Receiving a message and sending from the right business identity are separate checks. A nontechnical team may need its email administrator’s help.

Before switching live traffic, use invented customer and order details for these checks:

1. Send a message from an outside address. Confirm that authorized staff can see it and an outsider cannot browse other conversations.

2. Assign an owner, add a follow-up and hand the request to the backup. Confirm that the shared history remains understandable.

3. Where internal notes are supported, check that they stay internal. Verify the sender name, address and destination of the customer-facing reply.

4. Leave one request unresolved and find it again. If the selected plan includes collision indicators, check them with two staff sessions.

5. Inspect a sample export outside the service. Then choose a clear cutover point so the old inbox and new help desk do not both send replies.

These are proposed adoption checks, not reported test results. Avoid importing the full archive or choosing an annual term until the team can carry out its normal handoff and understand what happens when a colleague is away.

Can you leave with usable records?

An export button is not enough. Check whether the file preserves the conversation, dates and attachments you need, and whether someone can read or import it without the original service.

• Google Groups: Google lists archived threads and labels among exports for groups you own, with work-account availability caveats. An archive is not proof of a successful help-desk import.

• Zoho Desk: Free and Express allow 1,000 records per module-export batch. That is an export limit, not a ticket-storage cap. Module CSV exports and full backups preserve different information; the latter includes email threads and attachments. Report export is another capability, and full monthly backup starts at Standard.

• Freshdesk: its account-export guide describes an administrator-generated XML archive of tickets, solutions, forums and customers. Making it readily usable can require technical help; inspect a representative conversation and attachment before relying on it.

Trial expiry also matters. Zoho advertises a 15-day trial followed by Free; do not build the workflow around temporary paid features. Freshdesk’s 14-day Enterprise trial is not an ongoing free plan for this purchase: its page says the account is suspended if you do not select and pay for a plan.

Freshworks’ terms effective April 1, 2026 default to automatic renewal unless written non-renewal or downgrade notice is given at least 30 days before term end. Check the conditions attached to your order, including purchases through a reseller. Set a reminder while signing up, not when the next invoice arrives.

Those terms require trial data to be exported before expiry and describe a conditional 14-day post-closure export period for paid accounts, dependent on retained, exportable data and payment obligations. Export before cancelling, and keep the original archive accessible until the destination has been checked.

What should this shop choose first?

Start by running the ownership routine in the existing inbox. If it works, keep it. If the team needs a clearer ticket record, assess Zoho Free. Move to Express for a specific routing or reporting need, or consider Freshdesk Growth when its documented collaboration features justify the larger bill. Buy AI separately only after defining the task, review responsibility and spending limit.

If the problem is collecting the first enquiry rather than managing an ongoing support conversation, the separate Tally, Typeform and Google Forms comparison addresses that decision. For after-sales support, the immediate goal is simpler: every customer request should have a responsible person and a visible next step.