A shared mailbox like support@ looks simple until five agents reply to the same thread, the partner channel email pulls customer queries into the wrong queue, and a customer CCs three of your team on a follow-up. Freshdesk’s shared inbox model is robust but requires deliberate configuration.
Mailbox per audience, not per team
Map mailboxes to audience, not to internal team:
support@yourco.comfor customers.partners@yourco.comfor partners.internal-it@yourco.comfor employees (in Freshservice if you have it, otherwise a tagged group).
Tickets from each mailbox land in a separate group with separate SLA, separate routing, and often different auto-responses. Trying to use one mailbox for all three creates a tagging-and-filtering nightmare.
Auto-assignment that holds
Default behavior on a shared mailbox: ticket lands unassigned in the group queue. Use round robin or load-balanced assignment to push it to one agent. Without auto-assignment, tickets sit in the group queue until someone manually grabs them, which takes 11 minutes on average across teams I have measured.
Round robin honors the agent’s status; agents marked “Away” or “Offline” are skipped. Train agents to set status before logging off.
Observer access for cross-team visibility
When the customer success team needs to see support tickets without owning them, give them observer (read-only) access to the group, not full agent access. Observer counts against your agent license but is half-price on most plans. They can comment internally on tickets without claiming them.
Reply-all and email loop guardrails
Two configuration items prevent disaster:
- Admin, Email, “Skip ticket creation if from a no-reply address.” Saves you from looping with
noreply@vendor.com. - Admin, Email, “Detect and merge auto-replies.” Out-of-office responses get attached as notes, not as new tickets.
Without these, one out-of-office reply can spawn 50 new tickets in an afternoon.
Internal forward versus collaborator
When you need someone outside the agent pool to weigh in (engineering, legal), use the Collaborator feature, not email forward. Collaborators reply via a magic-link page; the reply attaches to the ticket as a note. Forward loses the thread.
Public vs private notes
Train every agent on the difference. Public reply emails the customer; private note stays internal. The button colors are intentionally different (blue for reply, yellow for note). Mistakes happen on the mobile app, where the buttons are smaller. Agent onboarding should include a deliberate “send yourself a private note” exercise.
Mailbox-level signatures and templates
Each mailbox can have its own outgoing signature. The partner mailbox should not sign with “Support Team.” Set the signature at the mailbox level under Admin, Email, Signature.
Spam and phishing routing
Set a spam-filter rule that auto-tags tickets containing common phishing patterns and routes them to a security review queue, not the support queue. This keeps phishing reports out of the SLA clock.
What to do this week
Audit each shared mailbox for auto-assignment configuration and the no-reply skip rule. Both should be on. Fix any that are off and watch your unassigned ticket queue length drop.
