Team inbox: what it is and how it differs from your email

An inbox is the place where the messages you receive arrive; in email, it is the received folder. A team inbox gathers into one list the messages your organization receives by email, WhatsApp or forms, and every conversation has an owner everyone can see. Only you read your personal email. In a team inbox, anyone with permission sees what came in, who is handling it and what is still unanswered.

Picture a five-person consultancy with a single support address, the kind that starts with "info". Three people have the password and open it from their phone or computer. On a Monday a client asks about an invoice. The partner reads it on her phone and plans to answer later; the email now shows as read, so the accountant assumes someone handled it. On Thursday the client writes again, this time copying the manager.

What an inbox is and what changes when it belongs to the team

In a normal email program, the inbox has one owner. Read or unread is all the status a message keeps, and what happens next lives in that person's memory: whether they plan to reply, whether they forwarded it, whether they already called the client.

In a team inbox, each conversation carries what the team needs to split the work: who it is assigned to, which client it belongs to and what was said back. Opening an email does not resolve it: it stays on someone's list until that person answers or archives it.

Sharing the password of one address looks like a team inbox, but it keeps the problems of personal email. Everyone sees the same thing and nobody knows what the others did. When someone leaves the company, the password has to change and everyone has to be told, and if someone replied from their personal address, that reply leaves with their mailbox.

Your email and the team inbox: five differences

• Who reads it: you read your personal mailbox; in the team inbox each person sees their own part, and anyone with permission sees every conversation.
• Who answers: in your email, whoever opens it first, if they remember; in the team inbox, the person the conversation is assigned to.
• Where the history stays: in your email, in your folders; in the team inbox, next to the client who wrote, where the next person to handle them finds it.
• What happens when someone leaves: their mailbox closes and what they answered goes with it; in the team inbox, conversations belong to the organization and stay.
• Which channels come in: your email receives email; the team inbox also receives WhatsApp Business and the forms on your website.

Your personal email still works for what is yours, like a conversation with a supplier or an internal matter that involves no client. The team inbox is for what a client writes and any of you might have to handle.

How the inbox works in AgentticCRM

In Inbox and WhatsApp you connect the email account with its address, server and password, and a test button checks that it can receive and send before you save it. The password is stored encrypted and is never shown again. New mail comes in on its own, in the background, and the new-message notice reaches you even when nobody has the inbox open.

What you do there happens in your real mailbox. If you reply, forward, archive or move an email to the trash, it looks the same on your phone and in the email program you already used, and what you delete can be recovered from any of them. The team does not have to drop its email program overnight.

New messages land in Unassigned. Whoever is going to handle one clicks Claim and the conversation moves to their name; if it belongs to someone else, it can be handed over. Email tries to recognize the sender by their address, and from then on the conversation lives in the client's record. In the consultancy's case, the invoice question would have sat in Unassigned, in view, until someone took it, and the accountant would not have had to guess whether it was handled.

The same list receives messages to the organization's WhatsApp Business number and whatever arrives through your forms. Anything that needs formal follow-up, with priority and history, is handled as a support ticket.

What stays with each person

Each person creates their signatures and picks one for new emails and another for replies; the signature sent stays in the conversation, so the team sees what the client received. A half-written reply is saved as a draft and comes back when you return to the thread, and saving is not sending: the message goes out only when you click Send.

Pinning a conversation to the top, marking it as a priority or archiving it changes your list, not anyone else's. You can also snooze a conversation to handle it later and sort senders, starting with the ones writing for the first time. Email templates can be personal or shared, with CRM fields, blanks to fill in and attachments.

If your organization has AI set up, you can ask for a draft, rewrite, correct or translate your text, or summarize a long conversation before answering. You review the result and decide whether to send it.

If the next step is sorting out the team's WhatsApp, the article on when the WhatsApp group is no longer enough explains the 24-hour rule and templates. And if you serve clients from several offices, see how to work with several branches and a single inbox.

Frequently asked questions

Do I have to stop using my email program?

No. What you read, answer or delete in the inbox looks the same on your phone and in the program you already used, because it is the same mailbox.

Is a distribution list the same as a team inbox?

No. A list forwards each email to several people, and each one gets it in their own mailbox without knowing whether someone else already replied. In a team inbox the conversation exists once and has a visible owner.

Does the inbox answer clients on its own?

No. AI prepares a draft with the context of the conversation, and you edit, accept or discard it. A person always decides when it is sent.

Which address do proposals and invoices go out from?

That is set in Organization email: there you choose which address sends proposals, which sends invoices and which mailbox your client replies to.