Customer support: every agent gets every ticket

The setup

Mira runs support for a 40-seat SaaS helpdesk desk with four agents. The public address is support@, and the agents are mira@, theo@, june@ and sam@ — each with their own inbox and their own App Password in Sinka.

How the mail flows

1. A customer writes to support@. Gmail receives it like any normal mail.
2. Sinka files an identical copy into mira@, theo@, june@ and sam@ within minutes.
3. Whoever picks it up replies from their own inbox, so the customer always hears from a named human with a normal thread.
4. Nobody touches the support@ login; it stays an archive of everything that arrived.

Why Sinka fits here

• No forwarding rules to maintain when someone joins — add their address and App Password once.
• Attachments arrive byte-identical, so screenshots and logs survive the trip.
• If one agent's password is revoked, only their copies pause; the other three carry on.

Watch out for

• Agree on a claim convention (e.g. reply-all to an internal thread, or a label) so two agents don't answer twice — Sinka copies mail, it doesn't assign it.
• Auto-replies from customers (out-of-office) are skipped automatically, so nobody's inbox fills with loops.