Outlook & Microsoft 365

Batohi works with the mailbox you already have. Connecting your Outlook or Microsoft 365 mailbox does two things, and only these two things:

• Sending. Tracked mail composed in Batohi is sent as you, from your own mailbox, through Microsoft's own API. The message lands in your Sent folder like any other mail you send — because it is mail you sent.
• Reply detection. When a prospect replies, Batohi matches the reply to your conversation using the message's routing headers and records that a reply happened, and when.

What Batohi can and cannot see

The Microsoft permission Batohi uses for reply detection is the narrowest one that exists for the job: it returns a message's headers and excludes the body, the preview text, and attachments. This is not a policy promise — it is how the permission itself is defined, enforced by Microsoft on every request.

Concretely, for mail arriving in your inbox Batohi reads:

• the routing headers (Message-ID, In-Reply-To, References) that say which conversation a reply belongs to,
• the sender address and subject line,
• the arrival time.

Mail that has nothing to do with a conversation you're tracking is discarded on sight. Nothing about it is stored.

Connecting

Open Setup in the dashboard and choose Connect your Microsoft mailbox. Microsoft shows you a consent screen listing exactly what Batohi asked for; approving it takes you straight back to the dashboard. Declining changes nothing — you stay signed in and every other feature keeps working.

Both Microsoft 365 (work) accounts and personal outlook.com accounts are supported.

Disconnecting

Disconnecting removes Batohi's authorization to your mailbox. Evidence already recorded about your own conversations — sends, opens, replies — remains yours in the dashboard; nothing new is observed after the moment you disconnect. You can also revoke Batohi's access at any time from your Microsoft account's app permissions page, with the same effect.