Skip to content

Home Topics Inbox Management Shared inboxes

Inbox Management · Shared inboxes

Shared inbox management not working? Troubleshooting guide

Short answer

When shared inbox management fails, check in this order: the DNS or platform configuration is published and resolves; the sending system is actually using it; the domain in headers aligns with what you published; and the receiver's verdict in Authentication-Results or bounce messages.

Symptoms#

  • Messages landing in spam despite previously good placement
  • Bounces mentioning policy, authentication, or reputation
  • Provider dashboards showing a drop in reputation or authentication pass rate

Diagnosis steps#

  1. Confirm the configuration is live: query DNS from an external resolver and check the sending platform's settings page.
  2. Send to a seed mailbox and read the full headers, especially Authentication-Results.
  3. Compare the domains in From, Return-Path, and DKIM d= for alignment.
  4. Check provider dashboards (Google Postmaster Tools, Microsoft SNDS) for reputation and error rates.
  5. Review recent changes: new vendors, DNS edits, list imports, volume spikes.

Likely causes#

  • Sharing one login instead of using delegated access.
  • No visibility into who replied.

Fix and re-verify#

  1. Assign an owner to every incoming thread automatically or by rule.
  2. Track status: open, waiting, resolved.
  3. Set response-time targets and alert on breaches.
  4. Draft replies with AI using the team's past answers as style reference.

Frequently asked questions#

Should we use a shared mailbox or a helpdesk?

Under a few hundred messages a week, a well-managed shared inbox works. Beyond that, ticketing adds needed structure.

Keep reading on Shared inboxes