Treat email as a column, not a mailbox you live in
Operational GTM: inbound mail becomes a row you classify, enrich, and answer. Forwarding is how messages enter the table.
Discuss this post in AI
Send a pre-filled prompt to ChatGPT, Claude, Gemini, or Perplexity — get a summary, ask follow-ups, or compare ideas from this guide.
People treat email as a room they sit in. Operational GTM should treat it as a column on a row. The message is evidence attached to a company, a person, a campaign, or a deal. Living in the mailbox produces heroics. Living in the table produces a queue.
Agent Inbox gives each role an address that can receive, thread, and draft. Forwarding is how mail that still arrives at sales@ or a personal inbox enters that table. Neuro OS runs the role that classifies, enriches, and answers — with Ask before send and Ask before CRM writes.
The row, not the unread badge
Define a schema before you automate. A useful inbound row has: received time, inbox id, thread id, message id, from, company guess, intent, language, attachments present, owner, status, and a link back to the raw thread. Status is a state machine: new, classified, waiting on human, drafted, sent, closed, spam.
The agent fills what it can. It must not invent a company match when the domain is generic. It must not mark closed because the model is confident. Ambiguity is a status, not a vibe.
Create the mailbox that owns the column:
from agentinbox import AgentInbox
client = AgentInbox()
inbox = client.inboxes.create(username="gtm-inbound", domain="agentinbox.space")
One inbox per queue beats one inbox for the whole company. Partner mail, product-qualified mail, and billing mail are different rows with different owners.
Classify, enrich, answer — as separate steps
Classification is cheap and should be boring: routing labels, language, and whether a human is required. Enrichment is a second step that may call your own HTTP APIs or a GTM workbook. If you write to Clay or another table, do it after Ask with an explicit payload. That is a write you control, not a claimed native email column inside someone else’s product.
Answering is a third step. Load the thread, draft in-reply, and wait. Do not enrich and send in one tool call. A bad enrichment should not leave the building as a wrong first name in a live thread.
Forwarding is the ingest
You will not migrate every stakeholder off their current client on Monday. Teach people to forward into the role address, or set a server-side forward from the shared alias. The forwarded message should preserve the original From when the platform allows it; if not, parse the forwarded block carefully and store both envelopes.
When a person must re-enter, forward the other direction: from Agent Inbox into Neuro OS so the human sees the same thread the agent saw. Screenshots are not a handoff.
Operate it like a queue
Staff the Ask queue. Report on time-to-classify, time-to-approved-send, and rows stuck in “waiting on human.” If the table grows and nobody owns exceptions, you have rebuilt a neglected inbox with extra JSON.
Keep sends on Ask even when the template is stable. Templates drift; buyers do not. CRM writes stay drafted next to the source message id so a reviewer can see why a field changed.
Email as a column is an operating choice. The mailbox is still real — people reply to it — but the company works the rows. Agent Inbox is the mailbox layer. The table is yours. Neuro OS is where the role and the gates live.
Agent Inbox gives each role a mailbox people can reply to, with forwarding into Neuro OS when a human must see the thread. Outbound mail defaults to Ask. Run the role on Neuro OS. To scope the first inbox, get started.