Grok Bot Adds Support for Plus Alias Feature
Grok Bot now supports plus aliases. Users can send and receive emails using dedicated aliases or set up routine tasks that trigger only when emails are received at specific aliases.
This feature was announced by Sam Sokolin from SpaceXAI. The basic email format is name@mail.grokbot.com, and users can create aliases by adding + followed by any text before the @ symbol, such as name+travel@mail.grokbot.com or name+newsletters@mail.grokbot.com. Previous user tests showed that the plus symbol is functional, while underscores and dots did not pass testing.
Grok Bot launched its standalone email on October 9, with addresses under the mail.grokbot.com domain. The Bot can use this email to register for services, contact businesses, and schedule appointments. Users can request the address from the Bot or tag @bot on X to receive it. The team plans for administrators to enable this feature first.
Aliases allow routing of emails on different topics to the same Bot and configuring targeted routine tasks. For example, a restaurant management Bot can use +customer-feedback and +food-deliveries aliases to handle feedback and deliveries separately. Routine tasks can be awakened only when specific aliases receive emails, avoiding irrelevant emails from triggering them.
Users can input emails into the Bot workflow by forwarding or directly using the alias. Resources and attention shift from manual classification to automatic routing by alias. Bot developers and everyday users gain finer control over triggers, reducing the burden of handling irrelevant emails.
Source: Public Information
ABAB AI Insight
After launching the standalone @mail.grokbot.com email on October 9, Grok Bot expanded support for plus aliases within a few days. Sam Sokolin announced this feature, and users had previously tested the plus format and reported its usability. This move continues xAI's path of integrating proxy tools with existing email infrastructure.
The alias mechanism allows a single Bot address to support multiple topics for sending and receiving, binding routine tasks to specific aliases. Resources shift from general inbox processing to purpose-based routing. Users can set up automations that trigger only for +travel or +receipts, while other emails remain silent.
Similar plus address technology has long existed in traditional email systems for filtering and classification. In the current AI agent phase, this feature combines email triggering with agent execution, allowing workflows to complete routing before messages arrive.
This essentially represents a restructuring of the industry chain. Email, as an input layer for agents, expands from a single address to routable aliases, changing the interface structure for agent communication with the outside. The mechanism leverages existing plus address standards to achieve topic-level triggering, allowing agent routine tasks to shift from time or general conditions to address-level precise matching, thereby reducing the occupation of irrelevant inputs on agent resources.
ABAB News · Cognitive Laws
Alias routing precedes content processing, and workflows are determined upon arrival
A single address with topic tags equals multiple entry points but a single agent
Routine tasks triggered by aliases, irrelevant emails no longer awaken the system