It is worth it when at least half an hour of your day goes into reading mail and writing replies that repeat. An assistant with access to the mailbox can summarise what arrived in one sentence, prepare a draft reply in the right thread and write your numbers into a new spreadsheet — but it does not send the draft; that stays with a person. It is not worth it where mail volume is low or every message is different: then reading it is faster than explaining what to do with it. Two things decide the choice — whether the tool really only prepares and never sends on its own, and whether account access can be revoked at any time.
What an assistant with inbox access actually does
Three things, and all three are reading or preparing. It finds messages from a plain-language brief (“unread from this morning”, “everything from this supplier over the past month”). It reads the full text of a specific message, not just the preview — only then can it be summarised properly. And it prepares a draft reply that lands in the same thread, with a “Re: …” subject and the company signature from the configured profile.
The gain is not that the assistant writes more elegantly. It is that between “15 messages arrived” and “I know which three I have to deal with today” there is work you redo every morning and that is never stored anywhere. That work can be handed over, because it can be checked in seconds — the summary either matches or it does not, and you see it immediately.
What it will not do: it has not sent anything, it will not send anything, and it has no way to. The draft waits in the mailbox exactly as if you had written it yourself and closed the window.
Why a draft and not sending straight away
Because the cost of a mistake is completely different in the two cases. A badly written draft costs thirty seconds and one rewrite. A badly sent e-mail costs a customer and cannot be taken back.
There is a second, less obvious reason. When a person reads the draft, they take responsibility for it — and that is the only way a company keeps its own tone in customer communication. A tool that sends by itself removes that check exactly when it is needed most: on a complaint.
The same rule applies to publishing. A reply to a shop review is public, so it should come about the same way — the assistant prepares it, a person reads it, and only a confirmation sends it out. In MitoOps this is split into two steps, preparation and publication, and the second step does not run without an explicit confirmation.
What else can be connected besides mail
A company Google account is more than a mailbox. The usefulness grows once a single sentence can join an answer from your data with the place to write it down.
- Calendar — events for the coming days, busy and free slots, creating a new event. Invitations are usually not sent to attendees automatically; a person sends them.
- Sheets — reading tabs and creating a new spreadsheet with rows already in it. This is where the practical gain is largest: the monthly overview that otherwise gets retyped from three screens.
- Docs — reading a document and creating a new one. Note that reading usually returns paragraph text only, not the tables and images inside it.
- Drive — finding a file by name and reading its content.
The limits you only find once you are using it
This is the part missing from capability lists, and it decides whether you still use the tool a week later.
- A draft reply is usually text only. An attachment — a return label, an invoice, a price list — has to be added by hand before sending.
- Overwriting an existing file on Drive is usually a full replacement of the content, not an append. For a document someone keeps adding to, that is the difference between help and loss.
- The link to the new spreadsheet arrives in the chat as text. It need not be clickable — in MitoOps today you select and copy it.
- There is one account and it is the company one. Whoever can use the assistant can reach that mailbox through it, so these tools belong to an administrator, not to everyone who signs in.
- Without a connected account the tools do not work, and they should not pretend otherwise. The right response is a plain sentence saying the account is not connected, not a raw API error.
What to ask when choosing
- Does the tool send e-mail itself, or does it always only prepare a draft? If it sends, can that be turned off?
- Where does the signature under the reply come from, and what happens when no profile is configured for it?
- Which roles can reach these tools — every user, or only an administrator?
- How is account access revoked, and what happens to drafts already in progress?
- Is an existing file replaced in full, or can it be appended to?
- Can I see which tools the assistant used for an answer, or do I only get the result?
When it makes no sense
At low mail volume. If ten messages arrive a day and each one is different, writing the brief takes longer than reading them. You can estimate the threshold: how many minutes a day do you spend sorting and answering repeating messages? Under fifteen minutes it will not pay off.
And for work where the answer is a decision, not text. A complaint handled as an exception, cancelling a large order, agreeing a price — a better draft does not help there, because the problem is not the writing.