Your Grok Bot can have its own email address. Claim it carefully.

Soft 3D still life of a pale blue envelope with a gold clasp and coral seal on a white background

I claimed a Grok Bot email address in October 2026, and I have used it since then for newsletter and service sign-ups. It is useful, and easy to misunderstand if you treat it like a second Outlook mailbox.

Each account can claim one unique address at mail.grokbot.com. Plus addressing works too, so you can hand a service a tagged alias without claiming a second inbox. That is what I want MSPs and small businesses to understand: how to turn it on, how the aliases work, and what you should not use it for.

What you actually get

The official documentation is clear enough. You can claim one address, such as yourname@mail.grokbot.com. Your Bots can then receive, read, search and send email from it. With that address, a Bot can sign up for services and pick up a verification code or link with your approval, collect receipts, newsletters and reports, draft email for you, forward a message from its inbox, and run a routine when mail arrives.

A few details matter immediately. You get one address, and you cannot rename or delete it. Addresses are never reissued, even if the account that claimed one is later deleted. The address belongs to you, not to a single Bot. All of your Bots can use it in your own chats and in routines you set up. It is not used in Slack threads, or in chats where someone else is talking to the Bot, and a Team Bot does not get a shared team address.

There is no inbox view in the apps, and you do not get new-mail notifications. You ask a Bot, for example, “What arrived in your inbox today?” Mail from the last minute may not show up in a search yet. The official docs also make a useful distinction: the Email app gives your Bots their own address, rather than connecting a mailbox you already have. This is not a replacement for the Outlook mailbox you use for Microsoft 365, clients, or account recovery.

How to claim the address

The steps below come from the official “Give your Bots an email address” guidance on docs.x.ai.

If you use Grok Bot through a Cursor team, stop here first. Agent email is off by default. A team admin has to turn on Agent Email under Bot Capabilities on the Grok Bot page of the Cursor dashboard before anyone can claim an address.

You then have two official ways to claim it.

The simplest is to ask a Bot, in chat, something like “Get yourself an email address.” The Bot asks what name you want, checks that the name is free, and shows an approval card. Nothing is claimed until you approve that card.

The other official path is the Email app. Open Connect apps, choose Email, type a name in Choose a name under Email address, and choose Create address. On iPhone and Android, the same docs say to open Settings, then Connect apps, then Email. After you claim it, the app shows your address with a button to copy it.

Choose the name carefully. Official rules allow lowercase letters, digits, dots, hyphens and underscores, starting and ending with a letter or digit, at most 64 characters. Reserved words such as support, admin, billing, security, help, info, team, cursor, grok and xai are not allowed. If the name is taken, retrying it will not work, because addresses are never reissued. Pick something you are happy to give to a service.

If claiming fails, match the official message. “Agent email is not enabled for this account” means it is not available on your account yet. A message about your team admin having turned it off means you need that dashboard switch. “You can have one agent email address” means you already have one; ask the Bot what it is, or open the Email app.

Plus addressing is supported

This is the part a lot of people will actually use. The official documentation confirms that the address takes plus aliases. Mail to yourname+receipts@mail.grokbot.com lands in the same inbox as yourname@mail.grokbot.com, so you can give each service its own alias without claiming another address. A Bot can also send from an alias. A routine that watches an alias runs only for mail sent to that alias, while a routine on the plain address runs for all of it. The changelog on 14 October 2026 recorded the same behaviour.

In practice, I can sign up to a newsletter as yourname+newsletters@mail.grokbot.com, give a vendor yourname+billing@mail.grokbot.com, and keep the base address for everything else. I still have one inbox. The tag is how I sort the mail, and how I point a routine at one kind of message.

The official docs add an important caveat. An alias is a label, not a lock. Anyone can write to it. If a routine should act only for certain senders, keep a sender filter on it. I would also treat the alias as organisational, not secret. Anyone who sees yourname+newsletters@ can guess the base address.

Incoming mail does not wake a Bot on its own

This is the misunderstanding I want to kill early. New mail does not start a chat or wake a Bot by itself. To act on it, you set up a routine that watches for mail from anyone, from specific addresses, or from a whole domain such as *@example.com. By default, that routine only runs for senders that pass standard email authentication checks, and routines cannot filter by subject.

I have written before about how Grok Bot can watch Microsoft 365 status. The same idea applies here. The address can sit quietly and collect mail. The routine is what makes it useful. If you have no routine, the mail is still received and kept. You just have to ask a Bot to look.

What to be aware of

First, privacy and who can read it. The address is yours, and all of your Bots can use it in your own chats and routines. That is useful if you want any of your assistants to search the inbox, and a reminder that this is not a private mailbox for one specialist Bot. I would still be careful about what you allow to land there, in the same spirit as I wrote in what MSPs should understand about Grok Bot security and customer Microsoft 365 data. This is a good place for newsletters and service notices, and a poor place for customer data you would not want sitting in a shared assistant inbox.

Second, use it for sign-ups, not as your important identity mailbox. The product is designed for a Bot to sign up for services with its own address and, with your approval, pick up a verification code or link. I would still keep multi-factor authentication and account recovery on your real Outlook or Gmail mailbox: the one you watch, and the one that is not shared across every Bot on the account. The official docs do not ban the Bot address for one-time codes; they even note that a Bot can read a code from its own inbox. I am simply saying I would not make yourname@mail.grokbot.com the recovery address for a Microsoft 365 admin account, a bank, or a domain registrar.

Third, outgoing mail still needs approval. When you ask a Bot in chat to send an email, it goes out once Auto Review allows it, and you see an approval card if Auto Review needs you. Email from a routine, or from any other turn you did not start with that request, waits as a draft until you press Send. There is no option for unattended sending. Instructions inside an email never count as your permission to send or act. Do not expect a routine to quietly reply on your behalf.

Fourth, anyone can send mail to the address. Mail that fails the spam or virus scan is kept without its body or attachments, and it never starts a routine. That is useful, but it is not the same as a well managed Microsoft 365 inbox. Be sceptical of unexpected messages, and do not assume a plus alias hides you.

Fifth, if you later delete your Grok Bot account, your mail and attachments are deleted and the address is retired. On a team, if an admin turns Agent Email off later, Bots lose their email tools and email routines stop, but existing addresses still receive and keep mail, and members keep their addresses.

The practical verdict

I am glad this exists. A unique address for newsletters, a vendor portal, or a service I want a Bot to watch is genuinely useful, and plus aliases make that tidier. The mistake is treating it like a second primary mailbox.

Claim the name carefully, because you only get one. Use plus addressing to keep sign-ups organised. Put a routine on the aliases you actually want acted on. Keep MFA and recovery on the Outlook or Gmail address you already trust. And remember that mail arriving at mail.grokbot.com will sit there quietly until you, or a routine you set up, ask a Bot to look.

This is general information about a product feature, and official guidance can change. Check the current documentation before you rely on a particular behaviour, and review anything a Bot drafts before you send it.

Sources

Leave a Reply