Uninstall RCS Studio

This page shows how to uninstall RCS Studio from your HubSpot portal, what is removed and what stays, and what happens to your data. It also covers reconnecting afterwards and moving your portal to a different RCS Studio account. You may see the words disconnect and uninstall. They mean the same thing here. There are two routes: the Uninstall RCS Studio button inside the app, and Uninstall in HubSpot's Connected Apps. Both end the same way: HubSpot removes the app's access, and RCS Studio cleans up what it set up for your portal.

Access

Only a HubSpot super admin can uninstall. The Uninstall RCS Studio button on the settings page is visible to everyone, but the app refuses anyone who is not a super admin. You do not need an RCS Studio account. To reconnect afterwards, see Reinstall and reconnect.

How to uninstall

Route 1: from inside the app

  1. In HubSpot, open the RCS Studio settings page.
  2. While RCS Studio is connected, select Uninstall RCS Studio.
  3. In the Uninstall RCS Studio from HubSpot window, read what will happen. Type UNINSTALL in the box labelled Type UNINSTALL to confirm, then select the red Uninstall button.

RCS Studio removes the app from your HubSpot account right away and starts the cleanup. HubSpot also emails your portal's super admins a link to reinstall the app.

Anyone else sees Not allowed: "Only a HubSpot super admin can uninstall RCS Studio." Nothing changes. Ask a super admin on your portal to do it.

If the uninstall does not go through, the window shows one of these and nothing is changed:

Window showsCauseFix
Reconnect needed: "RCS Studio needs a new HubSpot permission before you can uninstall. Reconnect HubSpot to grant it, then try again." with a Reconnect HubSpot linkThe app needs one extra HubSpot permission (settings.users.read) to check you are a super admin, and your connection has not accepted it yetSelect Reconnect HubSpot, approve the permission, then select Uninstall RCS Studio again
Something went wrong: "Could not uninstall right now. Nothing was changed. Please try again."HubSpot or RCS Studio could not complete the request, or the connection is not activeTry again in a moment. If the settings page shows a connection state other than Connected, see Install RCS Studio for HubSpot

Route 2: from HubSpot

  1. In your HubSpot portal, select the Settings gear icon in the top navigation bar.
  2. In the left sidebar, go to Integrations > Connected Apps.
  3. Under My Apps, select RCS Studio.
  4. On the app's page, select Actions, then Uninstall.
  5. In the dialog, type uninstall in the text field and select Uninstall.
The Connected Apps page with RCS Studio listed under My Apps

HubSpot reports an uninstall to RCS Studio through a notice that RCS Studio reads every two minutes, so the cleanup starts within about two minutes. If you want it to start right away, use route 1.

What happens during an uninstall

Both routes run the same steps, in this order.

  1. HubSpot removes the app. HubSpot ends RCS Studio's access to your portal and invalidates the app's HubSpot tokens. With route 1, RCS Studio asks HubSpot to do this for you.

  2. RCS Studio notices. Immediately with route 1, within about two minutes with route 2. From now on nothing is recorded in HubSpot and workflows stop sending.

  3. RCS Studio removes what it set up for each agent. It works in the background, one agent at a time, about half a minute to a minute each, and only on agents the app keeps a record for. An agent that only exists in RCS Studio is never touched. For each agent, in this order:

    • The default reply becomes one fixed message: "Sorry, we can't process your message right now. Please try again later." A default reply you built yourself is never replaced.
    • The inbox flows (Inbox Reply and the Chat with agent states), if an inbox was connected.
    • The JOIN link and the keywords that led to the app's flows.
    • The app's flows: JOIN Entry, STOP Opt-Out, STOP Confirmation, Opt-In Confirmation, HELP Response, Double Opt-In and the consent prompt.
    • The event forwarding, if it still points at the app. An address of your own is left alone. For an agent the app created nothing on (for example one you only imported consent for), this is the only step.

    After the last agent, RCS Studio deletes the HubSpot Consent and HubSpot Escalation connectors and their authentications.

  4. Final cleanup. RCS Studio withdraws the app's access to your RCS Studio account and deletes the stored credential. If the withdrawal fails (it is logged and nothing is shown to you), the app still deletes its stored copy, but the RCS Studio refresh token stays valid until it expires. It also deletes the agent and connector records, the conversation records and any consent imports, and marks your connection as disconnected. The settings page shows "HubSpot connection revoked".

While the cleanup runs, the settings page says "Disconnecting RCS Studio". Installing again is refused with "Please try again in a few minutes", and so is connecting the same RCS Studio account to a different portal. A portal with no agent records has no waiting period. The block lifts by itself after at most 30 minutes.

If a step keeps failing, RCS Studio repeats it up to three times and alerts the RCS Studio team. It still finishes the uninstall, but an agent it did not reach keeps its flows, connectors and event forwarding, and records nothing in HubSpot, until you remove them. See If something is left behind.

What is removed and what stays

Uninstalling stops the app: it no longer records consent in HubSpot, workflows can no longer send RCS messages, and connected inboxes stop receiving them. RCS Studio removes the credential it used for your portal, its records for your portal, and what it set up for your agents. Remove the Send RCS Message action from your workflows, or add it again after you reconnect.

These stay:

  • Your RCS Studio account, with its agents, brands and consent lists. The agent stays live. Team members who joined through HubSpot keep their RCS Studio accounts.
  • The consent properties on your HubSpot contacts (rcs_consent_opted_in, rcs_consent_opted_out, and the deprecated rcs_opted_in_agents and rcs_opted_out_agents), no longer updated.
  • Timeline entries already recorded on contact records, including consent entries.
  • Which of your team can use each feature (the switches on the Settings page). They apply again after you reinstall.
  • Your HubSpot Conversations inbox connections and past conversations, which stop receiving RCS messages.

What happens to your data

Your HubSpot data stays as it is, and RCS Studio can no longer access it. For questions about data handling, contact [email protected]. The Privacy Policy and the Terms of Service apply.

What the app reads and writes in HubSpot

The app reads data in real time and does not store it, except where the storage table says so. It does not read company, deal or ticket records. Company values in a workflow message come from HubSpot's own token picker, which HubSpot resolves before the message reaches RCS Studio.

  • Reads: a contact's phone number, the two consent properties and their history (to decide which change is newest when you edit consent by hand), contact lists (to keep an agent's opt-in list up to date), the app's own timeline entries (to show a customer's text in a handed-over conversation, with the business-intelligence permission), Conversations inboxes (to list them), files (to pick media) and your HubSpot user (user ID, email, whether you are a super admin), checked when you open the app to decide what you may do and to match an invitation to your email.
  • Writes consent: two custom contact properties, rcs_consent_opted_in ("RCS Consent — Opted In") and rcs_consent_opted_out ("RCS Consent — Opted Out"). They are multiple checkboxes, one per agent, in the "RCS Studio" property group, created the first time an agent is set up and shown on the RCS Consent card.
  • Writes timeline entries: message entries (agent name, the contact's phone number, the reply text or button tapped, and the reason a message failed) and consent entries (granted or revoked, and how).
  • Creates contacts: a contact holding only the phone number, when a number with no matching contact opts in (the JOIN keyword, the JOIN link, Yes, Subscribe, Record Existing Consent, a CSV opt-in row or the consent API). A STOP or No, Thanks from such a number also creates one. Chat with agent alone, or an ordinary message from an unknown number, does not.
  • Writes to Conversations: an inbox, if you connect an agent to a new one during setup, and inbound messages in a thread once a contact taps Chat with agent and is opted in. Before that, inbound messages are logged and not routed to the inbox.

What the app stores

The app stores this data in its own systems, not in HubSpot. It does not keep a copy of your HubSpot contact database. A customer's replies exist only in HubSpot, on the contact's timeline and in the inbox conversation.

DataWhat it holdsKept for
HubSpot connectionOAuth tokens for your portal, encrypted in AWS Secrets Manager, with your portal ID and installation metadataUntil you uninstall. The revoked token is kept until a reinstall replaces it
RCS Studio connectionThe RCS Studio refresh token the app uses in your RCS Studio accountUntil you uninstall, when the app withdraws and deletes it
Consent API keyOnly a hash. The key is shown once when you generate itUntil you generate a new key. Removed at uninstall
Agent configurationEach agent's setup, its connected inbox, and the list IDs linking your HubSpot lists to agentsRemoved at uninstall
Feature settings and phone field choiceThe switches on the Settings page, and whether the app reads Phone Number or Mobile Phone Number, with the user ID of the super admin who last changed each and whenKept after an uninstall and apply again after you reinstall
Consent importsThe uploaded phone numbers and the rows that failed, with the reason30 days, or removed at uninstall
Conversation recordsPer contact and agent: phone number, HubSpot contact ID, conversation status and thread IDAbout a year. Removed at uninstall
Workflow send recordsExecution ID, whether the message was sent and its message ID, so a retried run does not send twice. No phone number or text7 days
Message logsMessage IDs, timestamps, direction and template IDs. No message text and no delivery status90 days
Invitation audit linesIn the app's logs, not your HubSpot account: the inviter's email and user ID, the invitee's email and the roleIn the app's logs
Session tokensA signed token, carrying your user ID and role but not your email2 hours. Not stored

While RCS Studio is uninstalled

Your agents stay live in RCS Studio, so contacts can still text them. Once the cleanup has reached an agent, it answers any text, including STOP, HELP, JOIN and the buttons of an earlier double opt-in prompt, with "Sorry, we can't process your message right now. Please try again later." So:

  • Nothing is recorded in HubSpot. A STOP is not recorded, a JOIN does not opt the contact in, and nothing is queued for later. The contact is not told they were unsubscribed.
  • Messages still reach RCS Studio. RCS Studio handles them, but HubSpot gets no timeline entry for them.
  • Google's Block. A contact can still block your agent in Google Messages, and Google then stops delivering your agent's messages to them. The app does not record the block while you are uninstalled. See Consent management.

For the first minute or so, an agent the cleanup has not reached may still reply with its old failure message, such as "We couldn't process your request right now. Please reply STOP again in a few minutes." After a route 2 uninstall, a JOIN may still be recorded for up to two minutes.

If you keep messaging from RCS Studio directly, keep your own opt-out records and honor any STOP your contacts send: RCS Studio does not record it for you while the agent is uninstalled. If you do not plan to use the agent with HubSpot again, stop sending from it.

Reinstall and reconnect

  1. Go through the installation flow at hubspot-app.rcsstudio.ai/hubspot/install. See Install RCS Studio for HubSpot. If the settings page still says "Disconnecting RCS Studio", wait a few minutes. You approve the HubSpot and RCS Studio permissions again, because the old RCS Studio connection was withdrawn and is never reused.
  2. Same RCS Studio account: your agents are still there, but the flows the app created were removed. Open each agent and set it up again in its setup guide, which creates the flows and connectors again. The app does not restore the agent's opt-in list link, its inbox connection or its double opt-in setting, so choose those again, and add the Send RCS Message action again to affected workflows. Until you do, the action does not send from that agent, the agent shows "(setup needed)" in the action's agent list, and the agent keeps giving the "can't process your message" reply. Opt-outs sent while you were uninstalled, or while a reconnect is in progress, are not recorded.
  3. A different RCS Studio account: see the next section.

Change your RCS Studio account

A HubSpot portal is connected to one RCS Studio account at a time. To move to a different account, uninstall and install again (recommended): the uninstall cleans up the old account first, then you sign in to the account you want.

The other way is to reconnect after the connection is lost. When the settings page shows Connection lost or HubSpot connection revoked, Reconnect RCS Studio and Reconnect HubSpot work like a reinstall: the app forgets its RCS Studio account, asks for fresh approval, and connects whichever account you sign in to, so sign in to the account you mean. Reconnecting while the connection still works keeps the account you have.

Either way, sign in to the account on the RCS Studio connection page during the install, or create it there. It must not be connected to another HubSpot portal. When the new account is connected:

  • The app drops its records of the old account's agents, so nothing keeps routing into the old account.
  • The new account's agents appear in the app. Open each agent and work through its setup guide, as for any agent you add.
  • After Connection lost the app could not reach the old account, so its flows, connectors and event forwarding stay there and its agents stop working with HubSpot. Remove them as in If something is left behind, signed in to the old account.
  • Consent already recorded in HubSpot stays on your contacts. It is not linked to the new account's agents.

One account per portal

An RCS Studio account can be connected to only one HubSpot portal at a time, whoever signs in. This applies to a first install, a reinstall and a change of account. If you sign in to an account that is connected to a different portal, the install stops with this message:

This RCS Studio account is already connected to a different HubSpot portal. Contact your RCS Studio administrator to disconnect from the current portal before connecting here.

Nothing changes on the other portal. Your portal is left without an RCS Studio connection and the sign-in is discarded, so start again from the Install button. Either sign in to a different account, or have a super admin of the other portal uninstall RCS Studio from it first. The account is free once that portal's connection shows as disconnected: immediately with route 1, within about two minutes with route 2, plus about a minute per agent. Until then the install stops with "This RCS Studio account is still being disconnected from another HubSpot portal. Try again in a few minutes."

If something is left behind

If you find the app's flows or connectors on an agent in your RCS Studio account after an uninstall (for example an agent the cleanup did not reach after repeated failures, or from an earlier version of the app), you can remove them yourself. Sign in to app.rcsstudio.ai:

  1. For each agent, delete the flows the app created (only the ones that exist): JOIN Entry, STOP Opt-Out, STOP Confirmation, Opt-In Confirmation, HELP Response, Unrecognized Message, Inbox Reply and Double Opt-In: agent name.
  2. Delete the connectors HubSpot Consent (account name) and HubSpot Escalation (account name) (only the ones you set up), and each connector's authentication. If there are several with the same name, delete the copies no flow uses.
  3. For each agent, open its settings, clear the event forward URL and save (it points at the app, at /hubspot/events/ followed by a token or, in older versions, just /hubspot/events; leave it alone if it is your own address).

Before you delete the STOP flows, make sure your agent still answers STOP some other way, or a contact who texts STOP gets no reply.

Need help?

See Help and support on Open and navigate the app, or contact [email protected].

Next


Did this page help you?