Contact

Companion

Draft, assign, or send — per alias. Same mailbox as your team.

What Companion is

Companion lives in the mailbox. It reads the same threads, drafts replies, and can assign or send when you allow it.

Per-alias policy

Each sending alias has its own Companion policy. You decide how far the agent can go on that mailbox.

PolicyWhat Companion does
Draft onlyWrites replies. A human sends.
AssignDrafts and routes the thread to a teammate.
SendCan send from that alias when the draft is ready.

Set it per alias

https://app.humaner.io/dashboard/inbox/providers Open the connected inbox, pick the alias, then set draft, assign, or send.

Companion Intelligence

Companion runs on this framework. Native is Companion — including Hybrid RAG. Custom is your own agent on the same mailbox over MCP or REST; knowledge search there is full-text only, not Hybrid RAG.

  • Custom · The layer for your agent
  • Native · Companion only

Retrieval, memory, and the mailbox.

Companion Intelligence

  • Semantic vectors + BM25, fused and reranked. Companion retrieves automatically. Not exposed over MCP.

  • Postgres full-text search over the same workspace knowledge. What Custom agents get via `search_knowledge` on MCP — included, not Hybrid RAG, not Companion credits.

  • Memory sits on the mailbox so Companion and your team do not repeat themselves.

  • Returning contacts, purchase or account context — each person gets a stable id for retrieval.

  • Companion encodes acknowledgment, tone, and emotional judgment. Custom keeps voice on your own agent.

  • Companion learns from approved outcomes and how your team works the mailbox.

  • Answer gates, forbidden topics, and fallback messages. Configure what Companion — or your agent — can and cannot do.

    ! Advisory on Custom

  • Casual, Corporate, or Efficient tone on Companion. Custom integrations keep persona on your own agent.

Memory

Memory and Hybrid RAG sit with Companion on the mailbox. External agents share mailbox tools over MCP; their knowledge lookup is FTS via `search_knowledge`, not the hybrid stack.

Next