Who owns your info@ mailbox?

Direct answer

Usually nobody. The info@, office@, contact@ or service@ address is on the website, the truck and the invoice, so quotes, job requests and vendor questions land there all day. It belongs to the company rather than a person, which is exactly why it goes unread. The fix is to give it an owner without giving anyone a second full-time inbox: connect that one mailbox to a reviewed triage layer that reads it every 15 minutes, sorts it into what needs you now, what needs a reply and what is noise, drafts the replies in place, and hands one person a short list at 7:00 am. It never sends and never deletes. A person approves what goes out.

Why the shared mailbox is the worst inbox in the building

A personal inbox has a person attached to it. If the owner does not answer a message in their own inbox, they feel it. The shared address has no such pressure. It is checked when someone remembers, which in a three-person shop means Monday morning and whenever a customer calls to ask why nobody wrote back.

Three things make it worse than it looks:

• It gets the highest-value mail. The website form, the "request a quote" button and the Google Business Profile all point at the shared address, so new work arrives there before it arrives anywhere else.
• It gets the most noise. Every vendor, directory and newsletter that ever scraped the website sends to it, so the real requests sit between forty pieces of junk.
• Nobody is allowed to be wrong in it. Because it is shared, people hesitate to archive or reply, so nothing moves.

The result is a mailbox that is simultaneously the most important and the least read. That is a triage problem, not a staffing problem.

What adopting it looks like

Adoption means one mailbox, one owner of the approvals, and a machine doing the reading.

Day one is a read-only scan. Inbox Concierge connects to the shared mailbox on Gmail or Microsoft 365 and reads what is there. It writes nothing. You see what it would have sorted, flagged and drafted, and what it would have left alone.

Then one approval. A single plain-language screen shows the proposed sorting rules and the exact labels or folders it will create. On Gmail those are labels, applied in place. On Outlook they are flat TeamShift - folders, and because a folder move takes a message out of the inbox, every proposed move waits for your approval. Nothing is written until you say yes, and an approval left unanswered for 72 hours stops the run rather than acting on a stale plan.

Then it runs. Every 15 minutes it takes a bounded page of the most recent untriaged mail, up to 500 messages, and classifies each one on sender priority, topic and urgency. A real quote request gets an importance mark and a saved reply draft. A vendor statement gets filed, or proposed for filing on Outlook. A newsletter is marked as noise. Anything that looks like a payment, a legal or medical matter, or a message that tries to give the system instructions is held and listed, never acted on. An existing backlog is worked down gradually instead of all at once.

At 7:00 am one person gets the list. What came in, what was drafted, what was held, and what needs a human. That person is the mailbox's owner now. They spend ten minutes, not an hour.

Gmail or Microsoft 365, and shared mailboxes

On Microsoft 365 the shared mailbox is a first-class object. Connect the account that manages it, and the read-only scan shows which mailboxes that account can reach before anything is set up. Start with info@, watch a week of briefs, then add billing@ or service@ once the folders have proven themselves. Use the same folder names on every mailbox so the front desk only has to learn one scheme. The Outlook triage guide covers the folder and category rules in detail.

On Google Workspace the shared address is usually its own user account. Sign in as that mailbox and connect it directly; labels are applied in place and nothing leaves the inbox. The Gmail organization guide has the label scheme.

Either way the mailbox stays visible and removable in your workspace, and you can disconnect it at any time.

What it will not do

It will not send email. Every reply it writes is a draft, saved in the mailbox, waiting for a person to read it and press send. It will not delete email. It will not move a message out of an Outlook inbox without an approval. It will not act on uncertain, transactional or sensitive mail, and it will not follow instructions that arrive inside a message. Those rules are written down in the safety rules, and they are the reason a shared mailbox is the right place to start: the mistakes it refuses to make are the mistakes that made everyone afraid to touch info@ in the first place.

What it costs

3¢ per successfully sorted email, with a monthly cap you set so it cannot overspend. There is no seat price and no minimum. You can start Inbox Concierge on your info@ mailbox with the $5 trial credit; the first run is a read-only scan. If you already run rules or filters on that mailbox, the general shape of moving from rules to reviewed triage is in AI email triage for small business.

FAQ

Should the owner or the office manager own info@?

Whoever will read a short list at 7:00 am every day. Ownership here means approving replies and glancing at what was held, not reading every message. Ten minutes a day from one named person beats an hour a week from everyone.

Can it manage a shared mailbox on Microsoft 365?

Yes. Connect the account that manages the shared mailbox and the read-only scan shows which mailboxes it can reach. Each connected mailbox stays visible and removable.

Will it reply to customers on its own?

No. It drafts replies and saves them in the mailbox. A person reads the draft and sends it, or does not.

What happens to the backlog already sitting in info@?

It is worked down a page at a time on each 15-minute sweep, up to 500 messages per sweep, so a mailbox with months of unread mail is sorted over days rather than in one pass you have to babysit.

What if I stop it?

Disconnect the mailbox from your workspace. Labels and folders it created stay where they are; nothing was deleted, so there is nothing to recover.