What is rolling out
OpenAI’s October 28 release notes announce a beta for texting your dot through iMessage or RCS. Its setup guide limits initial access to a subset of US ChatGPT Pro users; Business and Enterprise workspaces are excluded. An announcement does not establish that your account has the Texting control yet. [1][2]
Your dot can send proactive updates. Texts can use relevant ChatGPT conversation context and connected plugins. This is a one-to-one channel: enabling it does not give OpenAI or your dot access to your other text conversations. [1][3]
Follow the message path
OpenAI’s guide says third-party provider Linq processes messages in transit, so a user-to-dot conversation is not end-to-end encrypted, even over iMessage or RCS. OpenAI says Linq removes message contents after delivery but may keep delivery metadata, while OpenAI saves the texts in your dot’s ChatGPT conversations. Those are provider statements; we have not audited the system. [2]
Know the channel’s limits
Setup requires verifying your phone number. Plain SMS, group texts, and calls to the dot’s number are unsupported. Approval requests can link back to ChatGPT. Message or data rates may apply. Reply STOP to stop receiving texts. Turning off texting disconnects the number, without erasing earlier conversations or saved memories. [2][3]
Our take
A familiar messaging app can make an AI agent easier to reach. Start with an ordinary, low-stakes update and review which plugins and context the dot can use. Decide whether the message belongs in this third-party delivery path before sending private business material.
We checked public documentation, without connecting a phone or testing messages.