OpenAI has begun a preview that lets eligible US Pro users communicate with a Dot agent through their ordinary phone messaging app. The addition supports iMessage on iPhone and RCS on Android, turning the agent from something accessed inside ChatGPT into a contact that can receive instructions by text, photo or voice memo.
The feature also gives Dots a way to send their users updates about assigned work. That distinction matters: this is not simply a shortcut that opens a ChatGPT chat from a Messages thread. It is designed as a two-way messaging channel for a personal agent, including proactive status updates on tasks a person has already assigned.
The rollout is a preview, is limited to Pro users in the US, and does not extend to ChatGPT’s Plus tier at present. Those boundaries are important for anyone seeing the feature discussed elsewhere: iMessage or RCS compatibility alone does not mean every ChatGPT user can activate it.
What changes when a Dot can be texted?
Texting is a familiar interface, but it changes the rhythm of how an assistant can fit into someone’s day. Instead of opening an app, navigating to an agent and typing a request into a dedicated conversation, a user can send an instruction from the same place they communicate with other people. A photo and voice memo can be sent through that same channel.
For task-oriented software, reduced friction can be more meaningful than it first sounds. An agent may be useful precisely when a person is away from a computer, moving between appointments, or has a quick instruction to capture before they forget it. The new option potentially makes those short interactions easier to start.
There is also a clear difference between a normal chatbot reply and an update initiated by an agent. In the first case, the user returns to the app to ask what happened. In the second, the agent can surface a task update in the messaging thread. That is the “agent” part of the design: the system is intended to remain connected to work that has been assigned rather than only reacting in the moment to a prompt.
None of this establishes how well Dots complete particular tasks, how frequently they will send updates, or exactly what types of workflows will benefit most. Those details are not part of the preview description. But the messaging feature makes the intended direction plain: Dots are being positioned as ongoing personal assistants with a place in everyday communications.
iMessage, RCS and the practical setup
OpenAI’s stated setup path begins inside ChatGPT. Users open a Dot’s profile and select Texting. On the phone side, iPhone users need iMessage enabled, while Android users need RCS enabled.
iMessage is Apple’s internet-based messaging service for Apple devices. RCS, short for Rich Communication Services, is a modern messaging standard used on Android devices that supports richer features than legacy SMS. The key practical point is that OpenAI is using the messaging systems people already encounter on their phones rather than asking users to install a separate communications client just to reach a Dot.
The feature is provided with messaging support from Linq. That is useful context because sending and receiving messages through mobile ecosystems requires an underlying messaging connection; it is more involved than merely adding another conversation layout inside ChatGPT.
For users, the immediate checklist is short:
- Be a US ChatGPT Pro user included in the preview.
- Open the relevant Dot’s profile in ChatGPT.
- Select the Texting option.
- Confirm iMessage is enabled on iPhone or RCS is enabled on Android.
Users should not infer wider platform availability from this list. The supplied details describe iPhone and Android messaging support, not a promise that every device, carrier, region or account tier can use the feature immediately.
Memory follows the conversation across ChatGPT and texts
Perhaps the most consequential detail is that information a Dot stores in its memory is shared across ChatGPT and text messages. In plain terms, a conversation does not have to become a separate, contextless exchange merely because it moves from the ChatGPT interface to a phone message thread.
That continuity can reduce the need to repeat background information. A user might begin a task in ChatGPT and later send a text related to it; the Dot can use relevant context that is held in its memory across those two surfaces. Conversely, information the Dot writes to memory after a text interaction can carry into the ChatGPT conversation.
It is worth separating two related concepts. Conversation history is the record of messages in a particular chat. Memory, as described here, is information the Dot writes for use across ChatGPT and texting. The announcement confirms that the latter is shared between these modes, but it does not spell out the precise rules for what a Dot will retain, how long it retains it, or every control available to the user. Those are questions people should consider before placing sensitive or highly personal material in any persistent assistant workflow.
The convenience and privacy implications arrive together. Cross-channel context is valuable because it avoids starting over. Yet it also means texting should not be treated as a completely isolated conversation just because it appears in a phone’s Messages app. The stated design intentionally links the two environments.
Security claim focuses on a closed messaging relationship
OpenAI says it conducted extensive penetration testing for the feature. Penetration testing is a security exercise in which testers try to identify weaknesses by attempting to breach or misuse a system under controlled conditions. It is a meaningful part of security work, though it is not the same thing as a guarantee that a service will never face a vulnerability or abuse attempt.
The company also says the messaging relationship is limited: only the user can text their Dot, and the Dot can text only that user. This restriction is a straightforward safeguard. It aims to prevent the agent contact from becoming a general-purpose texting endpoint that strangers could reach, or a system that could message arbitrary phone numbers.
That design is especially relevant for proactive updates. An agent capable of contacting a user can be helpful when a task changes state, but limiting who it can contact narrows the potential for unwanted or misdirected communication. It also provides a clearer mental model: the Dot is a private assistant contact, not a new broadcast tool.
Still, practical caution remains sensible. Users should review which Dot they are configuring, understand that memory spans text and ChatGPT, and take care with photos or voice memos containing private information. The feature description supports a user-to-Dot closed loop, but it does not remove the broader responsibility of deciding what information is appropriate to give an AI assistant.
A more crowded personal-agent field
The release lands as competition around personal AI agents increases. Anthropic recently introduced Claude Duet, another entry in the category. Its current access is through a US-only waitlist, and Anthropic has said it plans to offer it to subscribers of a $20-per-month Pro plan.
Dots, meanwhile, are available in the described preview to US Pro users but not to Plus users. The two products should not be treated as direct like-for-like offerings simply because both are framed as personal agents; the supplied information describes different access paths and does not provide a complete feature-by-feature comparison.
What can be said is that messaging is becoming a differentiator. A personal agent that lives solely in a browser or dedicated app asks the user to remember to visit it. A personal agent that can receive a quick text, interpret a sent photo or voice memo, and later report back has a more immediate route into daily routines.
That does not automatically make messaging the best interface for every job. Detailed work may still be easier to inspect in ChatGPT, where longer prompts and responses have more room. Texting is likely most compelling for quick instructions, additions to an existing task, and notices that someone needs to see while away from their main workspace.
OpenAI’s decision to connect that channel with persistent memory is therefore the bigger strategic move. It is not just placing the same assistant in another inbox. It is linking the assistant’s working context across app-based and phone-based conversations, while restricting the messaging connection to the owner and their Dot.
For now, the relevant caveats are clear: this is a US Pro preview, Plus users do not currently have access, and setup relies on iMessage for iPhone or RCS for Android. As AI companies push further into personal-agent tools, the test will be whether this lower-friction contact method proves genuinely useful without making users lose track of what their assistant remembers and where that context travels.
For more on the broader friction between AI services and online publishers, see the ongoing debate around website-scraping language and business terms.
