ChatGPT Dots Meets RCS Inside Google Messages
TL;DRChatGPT Dots, the persistent agents inside ChatGPT, can now hold a one-to-one conversation over RCS in Google Messages on Android. On iPhone, the same bridge runs through iMessage. It is a limited preview for ChatGPT Pro subscribers in the United States. The Texting option has to appear on the Dot, and the phone number has to be verified. There is no SMS fallback, no group chat, no calling, and no end-to-end encryption.
By Cameron Voss
Three pieces, one conversation
A Dot is a small worker you leave running inside ChatGPT. Dots arrived on September 29, 2026 as persistent agents with their own cloud computer. A Dot keeps a goal, keeps notes, and can keep working after you close the app.
RCS is the newer carrier messaging layer that runs over data. It adds typing indicators, read receipts, and larger media than SMS. Google Messages is the Android app that speaks RCS and shows whether the connection is live.
The integration joins them with a phone number. You open the Dot's profile, choose Texting, and verify a number. The setup attaches that number to the Dot. In Google Messages the Dot looks like a contact, and the thread travels over RCS. On iPhone, the same idea runs through iMessage.
The Dot is the agent you already configured in ChatGPT. Texting is another entrance to it, with the same task state and the same connected apps. Gemini in Google Messages is a separate product.
It fits one kind of user: a US Pro subscriber on Android who wants a task update without opening ChatGPT. It does not fit a team that needs a shared thread. The Dot has one assigned user and cannot join a group.
What works, and where the support stops
The channel carries text messages. The Dot can reply, ask a question, or send relevant updates proactively. For example, it might send an update about an ongoing task without waiting for you to open ChatGPT.
Context carries over. A Dot keeps its notes and can use the apps you connected in ChatGPT. If a task needs approval, the request may arrive as a link back into ChatGPT, because a text thread is not a place to grant permissions.
The limits are narrow and concrete. This is a US-only preview for ChatGPT Pro. Business and Enterprise workspaces are out. Android needs Google Messages with RCS on, and iPhone needs iMessage. Plain SMS does not work. There are no group threads and no calls to the Dot's number. Messages are not end-to-end encrypted, even over RCS. Delivery runs through a third-party provider, Linq. According to the Dot documentation, Linq does not keep message contents after delivery but may keep delivery data such as timestamps.
The documentation also says the conversation stays between you and the Dot. Enabling texting does not expose your other text conversations. The texts themselves are stored in the Dot's ChatGPT conversation, so the privacy model is closer to ChatGPT than to a carrier chat.
| Item | Status in the preview |
|---|---|
| Plan | ChatGPT Pro in the United States; Business and Enterprise are not included |
| Android | Google Messages with RCS showing Connected |
| iPhone | iMessage |
| Message types | Text; support for other media may vary |
| SMS | Not supported; an SMS may get an automatic reply pointing back to RCS or iMessage |
| Group chat | Not supported |
| Calls | Not supported; calls go through the ChatGPT app |
| Encryption | Not end-to-end; delivery runs through Linq |
| Region | United States only at launch |
Where setup usually gets stuck
The sequence has four checkpoints, and each one fails with a different symptom.
- RCS reads Connected in Google Messages. Open Settings, then RCS chats. Connected means the number is verified. Connecting means it is not.
- The Dot's profile shows Texting. If the option is missing, the account is not in the preview. Turning on RCS will not add it, and retrying will not either.
- The number is verified inside ChatGPT. Enter it, send the code, enter the code back, and keep that code private.
- The first message goes out from the new thread in Google Messages. A short hello is enough. If the thread falls back to SMS, the Dot will not answer.
The common stalls are not mysterious. Most of them come from the same handful of mistakes:
- Do not toggle RCS repeatedly to force a connection. Google warns that this can disturb group chats.
- A missing verification code is usually a number or carrier problem, not an RCS problem.
- The Dot's number is for texting only. Calls still go through the ChatGPT app.
- Approval links are part of the flow. A Dot cannot grant itself access to an app from inside a text thread.
- To stop messages, reply STOP or turn Texting off on the Dot's profile. That disconnects the number, but it does not delete past conversations or saved memories.
Does Dot texting work with ChatGPT Plus?
No. The texting preview is tied to ChatGPT Pro in the United States. Dots are not part of the Plus plan either, so there is no Texting option to enable.
Does it replace Gemini in Google Messages?
No. They are separate products. Turning on Gemini does not turn on Dot texting, and the Dot does not appear inside Gemini's thread.
Can I add the Dot to a group chat?
No. The Dot has one assigned user. Other people cannot text it, and it cannot join a group.
Are the messages encrypted?
Not end-to-end. The documentation says this path is not end-to-end encrypted, and delivery runs through Linq.
Dot access is not texting access. You can have a Dot in ChatGPT and still see no Texting option. The feature is rolling out to accounts, so the profile is the source of truth, not the RCS toggle.
If you are building chat-style workflows on standard chat-completion APIs and want to keep the model side predictable, our Coding Plan provides official DeepSeek keys and a direct connection, with stock-based availability. Current plans are listed on that page.