Guide · Helpdesk
How to turn a shared mailbox into support tickets
In short
A shared mailbox such as support@ works until two people answer the same email, or nobody does. Turning each email into a ticket gives every request one owner, a status and a deadline, while customers keep writing to the same address and getting replies from it.
Reviewed 9 November 2026. Terms used: Shared inbox vs helpdesk, Ticketing system, SLA (service level agreement).
Seven steps from a shared mailbox to tickets
Do them in this order: the first three decide whether customers notice anything changed. They shouldn’t.
Connect the mailbox, or forward it
Connecting lets the help desk read the mailbox and send from it, so replies come from support@ and a copy sits in your Sent folder. Forwarding to the help desk’s own address is quicker to set up, but check what address replies come from.
Use a team mailbox and a proper login
Use a mailbox that belongs to the team, not a person who might leave. For Gmail, iCloud, Yahoo or Zoho that usually means an app password; for Microsoft 365 or Google Workspace, an admin-approved connection.
Thread replies onto the same ticket
A customer’s reply should land on their ticket, not open a new one. Good threading reads the email’s headers first and falls back to a ticket number in the subject. Decide what a reply to a closed ticket does: reopen it, or open a follow-up.
A subject that threads Re: My sofa arrived with a torn cushion [TKT-1284]
Keep the noise out
Bounces, out-of-office replies, newsletters and mail loops shouldn’t become tickets. Filter them by their headers before anyone has to read them.
Match the sender to a customer
Look the sender’s address up in your contacts. A known customer’s email lands on their record; a new sender becomes a contact or a lead, so their history starts with the first message.
Give each ticket a category, an owner and a target
Sort by category and send each to a team. Give each priority a first-reply and a resolution target, and pause the clock while you wait on the customer.
Reply from the mailbox, inside the thread
Customers trust replies from the address they wrote to, in the same email thread. Copy colleagues with Cc, bring in a supplier without showing them the whole ticket, and keep internal notes out of the email.
How it works in Axonave
Your own mailboxes, read every minute, answered from the same address.
Axonave connects Gmail, Zoho, Yahoo, iCloud or any IMAP and SMTP server with an app password, Microsoft 365 through your own Entra app or by signing in with Microsoft, and Google Workspace through your service account. Mail is read about once a minute and never marked read or moved. Each new email becomes a ticket on that mailbox, matched to the sender’s contact or lead. Replies thread by the email’s headers, or by the [TKT-…] token when they come from the requester, and a reply to a closed ticket opens a follow-up. Bounces, auto-replies, bulk mail and loops are dropped. Your replies go out from your mailbox, inside the customer’s thread, with a copy in your Sent folder.
- Reply, reply all and forward, with To, Cc and Bcc
- Replies written in Outlook or Gmail are synced in from Sent
- Mailbox health checked daily; a lapsed login shows Needs reconnect
Tickets in our demo workspace: the Source column shows the ones that came in by email, beside WhatsApp, live chat and the support form.
Common questions
What if we’d rather not connect the mailbox?
Forward it. Each Axonave workspace has a forwarding address, and forwarded mail becomes tickets the same way.
Can several mailboxes feed one helpdesk?
Yes. Basic includes one mailbox and Pro five. Agents pick the From address, and each ticket remembers the mailbox it came in on.
Does a customer’s reply reopen a resolved ticket?
Yes. A reply reopens a resolved ticket and moves one waiting on the customer back to in progress, and the SLA follows. A reply to a closed ticket opens a follow-up ticket instead.
See it working with your own customers.
We reply within one business day by email or WhatsApp.