Skip to content

Features

Everything a team needs to see, route and answer email together.

Bobby Inbox is an AI-assisted shared inbox, email-routing and communication-operations platform. Email is first; other channels come later.

View plansPrivacy approach

Shared inbox

Receive directly or by forwarding — and keep every message visible

Two ways in, one place to work. Whichever route a message takes, it stays visible inside its Bobby Inbox channel.

One shared inbox per channel

Every channel has its own message list, its own members and its own routing. Nothing lands in a personal mailbox where the rest of the team cannot see it.

Direct receipt

A channel can receive email at its own opaque Bobby inbound address, so mail arrives straight into Bobby Inbox with no intermediate mailbox.

Forwarding from an existing address

Keep the address your customers already know and forward it into a channel. The forwarded copy becomes the conversation the team works from.

Forwarded messages are retained

Forwarding never makes the original message disappear from Bobby Inbox. Outbound routing is an additional delivery, not a hand-off that empties the channel.

Compact conversation rows

Sender, subject, snippet, tags, assignee and state are readable in a single line so a long queue can be scanned quickly.

Threaded conversations

Replies, forwards and internal notes stay in one thread with the routing history attached to it.

Forwarding never makes the original message disappear from Bobby Inbox.

In the current pilot: Invited workspaces receive and archive inbound mail and read it in the shared console. Replying from Bobby Inbox is part of the full product and is not launched yet. Forwarding runs for the Support channel only, after the original is archived, under operational safety controls.

Collaboration

One clear place for team communication

Assignment, internal comments and shared drafts turn a queue into coordinated work.

Assignment

A conversation can be assigned to one teammate so ownership is never ambiguous. Unassigned and assigned-to-me are first-class views.

Internal comments

Discuss a message beside the message itself. Internal comments are visibly separated from customer-facing replies and are never sent outward.

Shared drafts

Prepare a reply together before it is sent, with the draft visible to the channel rather than trapped in one person's client.

Presence

See when a teammate is already looking at or replying to the same conversation, so two people do not answer once.

Mentions

Pull a specific person into a thread; mentions collect in their own view.

Tags and search

Tag by topic, customer or stage, then search across senders, subjects, bodies, tags and routing state.

In the current pilot: These collaboration tools describe the full product. Pilot workspaces read inbound conversations; outbound replies and workspace sending are not launched.

Routing and audit

Routing with accountability

Rules decide where messages go; the delivery timeline records what actually happened.

Routing rules

Conditions on sender, recipient address, subject or tag decide where a message goes and whether it is forwarded onward.

Delivery timeline

Each message carries an auditable record: received, matched rule, queued, sent, delivered, deferred or failed, with timestamps.

Failed delivery handling

Failures surface as their own inbox view with the provider reason attached, so a bounce is a visible task rather than a silent loss.

Accountable routing

Because the record stays with the conversation, anyone in the channel can answer what happened to a message and when.

In the current pilot: Routing and delivery records are kept for inbound mail and governed Support forwarding. Broader routing rules are part of the full product.

Bobby AI

Intelligent assistance without losing human control

AI assistance is optional, controlled by the workspace, and always reviewable. AI usage consumes Bobby AI Credits.

Optional and workspace-controlled

Bobby AI is off until a workspace turns it on, and it can stay limited to specific channels. It does not analyse all mail by default.

Summaries

A short summary of a long thread, shown beside it — never replacing the original message.

Priority and intent signals

Signals that lift the messages that need attention above ordinary inbox noise, while the human decides what happens next.

Suggested tags and assignment

Suggestions a teammate accepts or ignores. Nothing is applied silently.

Action items and suggested replies

Draft help and extracted tasks that a person reviews and edits before anything is sent.

Tone rewriting

Rewrite a drafted reply for tone or length while keeping the author in control of the final text.

Bobby AI Credits are consumed by workspace AI usage, including AI used through the API add-on. Credit pack pricing is not published yet.

In the current pilot: Bobby AI describes the full product. AI execution is not launched, so no AI processes pilot mail.

API and MCP

An optional API add-on, and MCP coming soon

API access is planned as an optional add-on at €99 per month per workspace. It is not launched during the pilot.

API add-on

Approved workspaces will be able to connect their own systems to their channels, messages and routing records.

AI through the API

AI used through the API consumes the same Bobby AI Credits as AI used in the interface.

Coming soon

MCP

MCP support is planned.

Roadmap

Email first, other channels later

Bobby Inbox begins with email because that is where team communication is hardest to keep visible. Additional channels will join the same channel, routing and audit model.

Email

The first channel: governed inbound receiving runs for invited pilot workspaces.

Additional channels

Planned. Nothing beyond email is implemented today.

Same routing model

Planned. Nothing beyond email is implemented today.

Same audit record

Planned. Nothing beyond email is implemented today.

Illustration

What the shared inbox looks like

Illustrative product view with sample data. Bobby Inbox is in a controlled, invitation-only inbound pilot. Accounts, sign-in, governed inbound receiving and a canonical archive are running for invited pilot workspaces. Support forwarding has been technically validated and stays under operational safety controls. Outbound replies, workspace sending, Forward All, AI execution, billing, the public API and MCP are not launched, and Bobby Inbox is not generally available.