A mailbox is the most sensitive thing an agency owns
The Gmail integration for agencies is the connection everything else depends on, and it is the one worth being suspicious about. Mail is where the whole relationship lives: the brief, the complaint, the change of scope, the invoice nobody answered. Connecting it should not mean handing a model the run of your inbox, and here it does not.
What connecting it changes
Gmail, once it is connected
Client email stops being something you process and starts being something the client record already knows about. A message arrives, it is read against the client it belongs to, and what it implies — a change request, an approval, a question, an overdue invoice — turns up as a prepared action rather than as an unread bold line at 22:00.
Generated from the registry
Everything NeoAI can do with it
This list is not written by hand. It is the same catalogue of typed actions the operator executes through, so it cannot promise more than the product does — reads first, then the writes, each of which waits for a person.
Reads
Run unattended, scoped to what you designated for that client.
- Read recent mail from a clientThe latest messages from the addresses designated for this client, and from nobody else.
- Read one mail threadEvery message in one conversation, so a reply can answer what was actually said.
Writes
Every one waits for a named person to approve it.
- Send an emailOpens a new thread with a designated address. Never a new recipient.
- Reply in a mail threadAnswers a message where it was sent, so the reply keeps its quoting and sorts with the conversation.
- Save an email draftWrites the email into the mailbox without sending it — the safe half of every mail action.
What it cannot do
- It reads mail from the contacts you designate for a client, and no others. There is no whole-mailbox search and no setting that widens it.
- It cannot send to a new recipient. Every send and reply resolves its destination from the client’s designations rather than from an argument.
- External email can never run unattended. That ceiling is enforced where the autonomy settings are stored, so no plan and no workflow can lift it.
- It does not move your mail. Nothing is migrated, no address changes, and disconnecting removes the access immediately.
What this changes
Three specifics, rather than a feature list
Designated contacts only
Reads are built as a query restricted to the addresses you named for that client. What comes back is filtered again before anything is stored.
A thread, not a snippet
When context matters the whole conversation is read, so a drafted reply answers what was actually said rather than the last two lines of it.
A draft in your drafts folder
If you would rather send from Gmail yourself, it can leave the reply as a real draft where you expect to find it.
What "designated" means in practice
A client in Neoflow is not a name — it is a set of specific addresses, channels and accounts you have attached to them. Every read the operator performs is built from that set, and every write resolves its destination from it. The destination is never something a model chooses.
The practical consequence is worth stating plainly: your own internal mail, your other clients’ mail, the recruiter emailing you and everything else in the mailbox is outside the query. Not filtered out of a screen — outside the request.
What it does with what it reads
- Turns a message into what it implies: a change request, an approval, a question, a scheduling problem.
- Attaches it to the right client and project rather than leaving it in a thread.
- Drafts the reply, in the register you have used with that client before.
- Raises what follows — an invoice to send, a meeting to book, a file to chase.
Outlook, if that is what you run
The same surface, the same rules, the same actions. An agency on Microsoft 365 connects Outlook instead and nothing downstream changes: features ask for "mail" and get whichever mailbox this workspace connected.
How the connection is made
Through a connection broker, on Google’s own consent screen, with the access you approve there. Neoflow stores a connection reference rather than a password, revoking is immediate from either end, and the connection belongs to your workspace rather than to the person who set it up.
Questions people ask about this
Can NeoAI read my whole inbox?
No. Every read is scoped to the addresses you designated for a specific client, at the point the request is built. Widening it is not a setting that exists.
Will it email a client on its own?
No. External email is the one capability with a hard ceiling: it cannot be set to run unattended by any plan, any workflow or any admin. Sends and replies are drafted and wait for a person.
Does it work with a Google Workspace shared mailbox?
It connects the account that goes through the consent screen. A shared mailbox that account can access behaves like the rest of that account’s mail, which means the designation rule still decides what is read.
What happens if I disconnect it?
Access stops immediately and the operator loses the mail surface — actions that needed it stop being offered rather than failing silently. What was already read and stored stays on the client record until you delete it.
Last reviewed on . Something out of date or wrong? Tell us and it gets fixed.
اقرأ أيضاً
Point it at one client and see what it prepares.
Connect a mailbox, designate the contacts for a single client, and read what the operator has drafted by tomorrow morning. Free to start, and nothing leaves without you.