Two-Way Inbox

The two-way inbox lets your team chat with contacts from a HubSpot Conversations inbox, and a reply from your team reaches the contact as an RCS message from your agent. A thread opens only when a contact who has opted in taps Chat with agent, a button in your HELP reply. A contact's ordinary reply does not open a thread.

Access

  • Connecting, changing or disconnecting an inbox is limited to HubSpot super admins. Other users are refused, and no setting opens this to them. You do not need an RCS Studio account.
  • The inbox needs a HubSpot account on Sales Hub Enterprise or Service Hub Enterprise, with the two optional inbox permissions (conversations.custom_channels.read and conversations.custom_channels.write) approved for the app. Without them, RCS messages still send from workflows and consent works normally. Only the inbox is missing. If you declined the permissions at install, see If the Inbox step says it is unavailable.
  • A thread opens only for a contact who has opted in to the agent (Consent management). In Test Mode, the contact's phone must also be a test device (Create and set up your agent).

What connecting creates

InWhat
HubSpotOne RCS channel account on the inbox (the RCS channel HubSpot lists in the inbox's channel settings), named <Brand> — <Agent> (<agentId>) so you can tell agents apart
RCS StudioThe Inbox Reply flow (passes a contact's replies to your HubSpot inbox), the Chat with agent states in HELP Response, the full Unrecognized Message shape and, for the first agent, the HubSpot Escalation (account name) connector (hands a conversation to HubSpot)

The app adds the channel to the inbox. It does not rename the inbox or change its other channels, and inboxes you do not connect stay as they are.

An inbox can be connected to one agent, and an agent to one inbox. To move an agent, disconnect first, then connect the new inbox.

Connect an inbox

You can connect from the agent's setup guide or from HubSpot's channel settings. Both create the same connection. Connecting adds Chat with agent to your HELP response and changes nothing else for contacts.

Connect from the setup guide

  1. Open the agent's setup guide and go to the Inbox step.
  2. Click Connect inbox. The Connect HubSpot Inbox window opens.
  3. Under Select an existing inbox, choose an inbox. Inboxes already connected to another agent are not listed. If you have none, the window says "No available inboxes found."
  4. To use a new inbox, click Create new inbox in HubSpot, create it in HubSpot, then click the refresh icon in the window. "After creating it, click Refresh to see it in the list."
  5. Click Connect.

The inbox is connected at once. The step shows "Setting up your inbox…" while the app finishes the RCS Studio side in the background. If it runs long you see "Still setting up, this can take a minute or two. It keeps going in the background." with Check again. You can leave the page.

When setup finishes, the step shows Inbox name: and the End-of-chat message editor.

Connect from HubSpot's channel settings

  1. In HubSpot, open the inbox's channel settings and choose the RCS Studio channel.
  2. HubSpot opens a Connect to Inbox page: "Choose which agent will handle conversations for this inbox."
  3. Select an agent. Agents already connected to an inbox are greyed out and show "Already connected to this inbox" or "Connected to inbox name". If you have no agents, the page says "No agents found. Set up an RCS Studio agent before connecting an inbox."
  4. Click Connect Agent. HubSpot returns you to the inbox's channel settings.

The end-of-chat message

When your team closes a conversation in the inbox, the contact gets your End-of-chat message. It is on the Inbox step once the inbox is connected and setup has finished. The default is "Your chat has ended. Text us anytime to start a new conversation." Edit it and click Save. The message cannot be empty, and the preview shows how it looks to the contact. Close a conversation says when it is sent.

If the Inbox step says it is unavailable

When the app does not have the optional permissions, the Inbox step shows a notice instead of the form:

Two-way inbox needs Sales Hub or Service Hub Enterprise and the inbox permissions. Workflow sends and consent work normally.

If your account has one of those plans and you declined the inbox permissions when you installed, reconnect and approve them.

Reconnecting helps only if your account is Sales Hub or Service Hub Enterprise.

The notice has a Reconnect HubSpot link. The steps to switch the permissions on in HubSpot and then reconnect are in Install RCS Studio for HubSpot. Reconnecting keeps your RCS Studio connection. While the notice shows, the Chat with agent option and the inbox hours in the HELP setup are hidden.

How a conversation starts

A thread opens in your inbox only when a contact who has opted in taps Chat with agent in your HELP response. The button appears only when an inbox is connected.

  • A plain reply to a workflow message, a keyword or any other text does not open a thread.
  • Before a thread is open, an inbound message is logged by the app and not shown in the inbox. When the thread opens, the earlier messages are copied in. If the number belongs to a HubSpot contact, the message is recorded on the contact's timeline.
  • A number with no HubSpot contact gets no timeline entry until the person opts in, opts out by STOP or taps No, Thanks.

The sequence

  1. The contact texts HELP (or INFO) and gets your HELP response.
  2. The contact taps Chat with agent. The agent sends "Checking your subscription..." while it checks consent.
  3. The app looks up the contact by phone number. It opens the chat only if the contact is opted in to this agent and not opted out.
  4. A contact who is opted in goes straight to step 6.
  5. A contact who is not opted in, opted out, or unknown gets the chat opt-in prompt below. Yes, Subscribe records the opt-in (creating a HubSpot contact if none matches the number) and goes on to step 6. No, Thanks records an opt-out and sends your STOP confirmation.
  6. The app opens the thread in the connected inbox and copies in the earlier messages of the conversation. If the contact's earlier thread was closed, it is reopened first so the history stays in one thread.
  7. The contact gets the chat confirmation. From then on, each of their texts appears in the thread as [Customer], and your team can reply.

If the consent check cannot run, or the contact is not opted in when the request arrives, no thread is created.

What the contact sees

WhenMessage
Consent checkChecking your subscription...
Chat opt-in prompt, standard agentTo chat with an agent, you first need to opt in to recurring messages from agent name. Msg & data rates may apply. Reply STOP to cancel or HELP for help. Tap Yes, Subscribe to opt in and connect to an agent.
Chat opt-in prompt, marketing agentTo chat with an agent, you first need to opt in to marketing messages from agent name. Tap Yes, Subscribe to agree to receive automated marketing msgs at this number and connect to an agent. No purchase necessary. Msg & data rates may apply. Reply STOP to cancel or HELP for help.
Prompt buttonsYes, Subscribe and No, Thanks
Recording the opt-inCapturing your opt-in...
Chat confirmationThanks for reaching out! A support agent will be with you shortly. Our team is available (your hours). If you would like to opt out of these messages at any time, please message STOP.
After each text during the chatWe received your message and an agent will respond shortly. If you would like to opt out of these messages at any time, please message STOP.
The hand-off failedSorry, we couldn't connect you to an agent right now. Please try again in a few minutes.
Recording the opt-in failedWe couldn't process your request right now. Please reply JOIN again in a few minutes.
The chat check could not runSorry, I can't respond right now. Please try again in a few minutes. To stop messages, reply STOP again.

Edit the chat messages

You edit the chat confirmation, the support hours and the chat opt-in prompt in the Help part of the setup guide, on the Help Capture tile. See Collect future consent for the HELP reply itself.

  • Support hours. Chat with agent needs support hours. The default is Mon-Fri, 9 AM to 5 PM, CT, and you can set them per day. The app appends them to the confirmation as "Our team is available Mon–Fri, 9 AM–5 PM CT." The hours sentence is added only when hours are set. Without hours the health check finding is "Support hours for Chat with agent are missing".
  • Chat confirmation. The default text is "Thanks for reaching out! A support agent will be with you shortly." The app appends the hours and then the STOP line. The same STOP line ends every message in a live chat.
  • Chat opt-in prompt. The app re-checks the contact's consent on the server each time. You can edit the text and both button labels (up to 25 characters). The step shows the same Not legal advice notice as double opt-in, and for Marketing agents PEWC required for marketing programs. It is separate from the double opt-in prompt, so you can word it for chat.

Yes, Subscribe records the opt-in with the source "Double opt-in" and opens the conversation. No, Thanks records an opt-out with the source "Double opt-in declined".

What your team sees

The history copied in when the thread opens

The copy covers the messages the app logged for the contact's current conversation. A conversation starts when a workflow sends the contact an RCS message, and each new workflow send to a contact with no open thread starts a new one. So the history begins at the contact's most recent workflow send.

  • If the contact's earlier thread was closed, the thread is reopened first. Only messages after the close are copied, because the earlier ones are already in HubSpot.
  • Messages are copied in the order they were sent.
MessageHow it appears in the thread
A message from your agent (a workflow send, an automated reply, an earlier reply from your team)[RCS Agent] followed by the message's name. It is never the message text
What the contact typedThe contact's own text
A button the contact tappedTapped: "..." with the button's label
A contact message the app cannot read back[Customer message]

The app reads the contact's text back from the contact's HubSpot timeline, so a message shows as [Customer message] when the entry is missing or the number belongs to no HubSpot contact. If nothing can be copied in, for example because the contact was never sent a workflow message, the thread opens with this line:

[Conversation escalated — no prior message history available.]

Live messages after the thread opens

While the thread is open, each message is added as it happens:

MessageFormat
The contact types a message[Customer] "the text"
The contact taps a button[Customer] Tapped: "the button label"
Your agent answers automatically[RCS Agent] and the message's name
A workflow sends the contact a message[RCS Agent] and the message's name

A workflow send to a contact with no open thread does not touch the inbox. A contact's STOP or JOIN shows in the thread as their text, like any other message. A reply from your team is written in the thread by your rep, so it is not repeated as an agent message.

The app also records messages on the contact timeline, which is separate from the thread. See Send RCS messages from workflows.

What never shows up

  • Anything sent before the contact's most recent workflow send. A new send to a contact with no open thread starts the history over.
  • The text of your agent's messages. Only its name shows.
  • A contact's messages while no thread is open, or after the thread was closed or the inbox disconnected. They are logged and recorded on the timeline, and not shown in the inbox. They are copied in if the contact later opens a thread, within the window above.

Reply, close and reopen

Reply from the thread

Type in the thread's compose area and send. The reply reaches the contact as an RCS message from your agent. Only the text is delivered.

  • An attachment, image or other rich content is not delivered.
  • A reply with no text (an attachment on its own, or only spaces) is dropped. HubSpot shows it as sent and the thread gets no note.
  • A reply to a thread that has no conversation record in the app is dropped, with no note in the thread.
  • Each delivered reply is recorded on the contact's timeline as an Agent Response.

A reply can also be refused. The app then adds an internal note to the thread, listed in Not delivered notes.

Close a conversation

What the contact receives depends on how the thread is closed in HubSpot.

In HubSpotThe contact getsThe conversation
ClosedYour End-of-chat messageEnds. The contact's next text goes to your automated flows
ArchivedNothingEnds the same way
SpamNothingEnds the same way
Moved to trashYour End-of-chat message, sent without checking the contact's consentEnds the same way

The same applies when HubSpot reports the close as a status change: the end-of-chat message is sent without a consent check. It is not sent when the contact opted out.

After a conversation ends, the contact's next text gets the agent's automated replies, the same as a contact who never chatted.

Reopen a conversation

  • Reopening a thread in HubSpot does not resume live messages. The app still treats the conversation as ended, so the contact's texts are logged and not shown in the thread.
  • A reply from your team reopens the conversation. When you reply in a closed thread and the reply is delivered, the conversation is open again and the contact's texts show live.
  • A new Chat with agent also reopens it. The thread is reopened and only the messages since the close are copied in.

A reply to a contact who opted out is blocked, so it cannot reopen the conversation. A conversation closed by an opt-out stays closed.

What an opt-out does to a thread

Consent decides what your team can send. Every way a contact can opt out of an agent closes that contact's open thread for the agent. The ways are listed in Consent management. A contact who was never on an opt-in list closes the thread too: they asked to stop, so your team should not keep replying.

The thread gets this internal note and is closed:

Closed automatically: this contact opted out of RCS messages from this agent.

No end-of-chat message is sent. The contact gets only the confirmation of the opt-out, where the source sends one (for example your STOP confirmation).

A reply to a contact who has opted out is not delivered, whether or not the thread is still open. A thread closed by an opt-out stays closed, and a blocked reply cannot reopen it.

Not delivered notes

The thread gets one of these when a reply is refused. Notes are visible only to your team.

NoteCause
Not delivered: this contact opted out of RCS messages from this agent. They must opt in again before you can message them.The contact opted out of this agent
Not delivered: consent could not be verified. Try again in a moment.The app could not check consent, and the conversation was closed by an opt-out
Not delivered: the message could not be sent to RCS. Try again in a moment.The send to RCS Studio failed

When the app cannot check the contact's consent, the reply is held only if the conversation was closed by an opt-out. If the app cannot check and no opt-out is on record, the reply is sent.

Opting back in

Reopening a thread, or replying to one, does not opt the contact in. The contact is opted in again when they:

  • text JOIN, or tap Yes, Subscribe on the opt-in prompt they get when they next text the agent;
  • are opted in by the consent API, a CSV import, an admin, or an edit to the consent property.

Opting in clears the opt-out on the conversation, so replies are delivered again. A closed thread stays closed until a contact taps Chat with agent or your team replies.

A contact who texts JOIN while chatting gets the opt-in confirmation. The conversation is not closed and your team's thread stays open. A contact who texts STOP while chatting opts out, and the thread closes as above.

Change or disconnect an inbox

Disconnect an inbox

HubSpot has no API for disconnecting a custom channel, so the final step happens in HubSpot. The setup guide walks you there.

  1. Open the agent's setup guide and go to the Inbox step.
  2. Click Disconnect inbox. The guide explains what will happen and has an Open HubSpot channel settings button.
  3. In HubSpot, open the channel settings (Settings > Inbox & Help Desk > Channels, then RCS Studio), find this agent's instance and click Disconnect.
  4. Go back to the guide. It checks every few seconds and notices by itself, or click Check again.
  5. Once HubSpot no longer lists the instance, the guide says RCS Studio is removing the agent's inbox flows. This takes about half a minute and the guide finishes by itself. If a step fails, RCS Studio repeats it automatically. If it still cannot finish, the inbox stays connected in the guide and you can click Disconnect inbox again.

If you disconnect in HubSpot without opening the guide, HubSpot tells the app and the app cleans up the same way.

What happens when you disconnect

  • Past conversations stay in the HubSpot inbox, but you can no longer reply to them from HubSpot.
  • Contacts can still text the agent. If a conversation was open when you disconnected, its record stays open, so the contact's messages are logged and not shown in HubSpot.
  • If you connect an inbox again, a conversation that was still open is found open and its messages appear live again, without a new Chat with agent.
  • The app removes the agent's inbox flows in RCS Studio and forgets the inbox. The agent's default reply goes back to the version used when no inbox is connected, so Chat with agent is no longer offered in the HELP response.
  • The escalation connector (HubSpot Escalation, which hands a conversation to HubSpot) is shared by every agent in the RCS Studio account that has an inbox. It is removed only when the last connected agent disconnects.

Change to a different inbox or connect again

Disconnect the current inbox as above, then connect the new one in the same Inbox step. To reconnect the same inbox, follow the same steps. Uninstalling the app also ends the connection: see Uninstall RCS Studio.

Troubleshooting

If setup does not finish

The setup guide's health check shows one of these on the Inbox step. Click Fix to run the setup again.

MessageMeaning
Inbox setup did not finish. Use Fix to run it again, or contact [email protected].The background setup failed after its retries, or could not be started
Inbox setup timed out. Use Fix to run it again.The setup message was lost and the job never finished

If the connect call itself fails, the step shows "Failed to connect inbox. Please try again." Health checks and Fix are explained in Create and set up your agent.

If the HubSpot page shows an error

The page is valid only when HubSpot opens it, for the inbox it was opened for. An expired form shows "Link expired": go back to HubSpot and start again.

Page titleShown when
Inbox already connected"This inbox is already connected to a different agent. Disconnect it first before connecting a new one."
Agent already connected"This agent is already connected to an inbox. Disconnect it first before connecting to a new one."
Access denied"You do not have access to connect this channel." (you are not a super admin)
Inbox not available"The two-way inbox was not enabled for this HubSpot account when the app was authorized. Reauthorize the app and grant the inbox permissions to use it."
RCS Studio unavailable"RCS Studio is not reachable or its credentials are unavailable, so the inbox was not connected. Please try again."
Channel already in use"This agent's channel account is already used by another agent in your portal. Nothing was changed. Contact support so we can separate them."
Connection failed"Could not connect the agent to this inbox. Please try again or contact support if the problem persists."

Other pages you may see, such as "Link not valid" or "Setup incomplete", ask you to return to HubSpot and try again or to contact support.

If the guide does not let you disconnect

What you seeCauseFix
No Disconnect inbox controlThe agent's inbox is still being set upWait until setup finishes
"Your inbox is still being set up. Try again in a minute."The setup, or an earlier disconnect, is still runningWait a minute and try again
"This inbox is still connected in HubSpot. Disconnect it there, then check again."HubSpot still lists this agent's instanceDisconnect it in HubSpot's channel settings, then click Check again

Common problems

SymptomCauseFix
The inbox dropdown is emptyYour HubSpot account has no inbox yetCreate one in HubSpot Conversations, then return to the Inbox step
Connect inbox is missingThe step shows the unavailable notice, or you are not a super adminApprove the permissions, or ask a super admin. See Manage your team in HubSpot
A contact replied and nothing is in the inboxReplies do not open a threadThe contact must tap Chat with agent. Nothing is wrong
The contact got "Sorry, we couldn't connect you to an agent right now..."The inbox is not set up, the HubSpot connection is down, or the app has lost its escalation linkRun Fix in the setup guide
I reopened the thread and the contact's texts do not showReopening in HubSpot does not reopen the conversation in the appSend a reply from the thread
The contact opted back in and the thread is still closedOpting in does not reopen a threadThe contact taps Chat with agent, or your team replies
Replies or the thread seem to go nowhere for a test numberThe agent is in Test Mode and the device is not an accepted testerCreate and set up your agent

Next

Uninstall RCS Studio


Did this page help you?