Messages your contacts and team may see
This page lists every fixed message the app puts in front of a contact, your team or a workflow builder, with where it appears and which page owns it. Text in {braces} is filled in: {agent} is the agent's display name, {frequency} the message frequency you chose, {email} the support email, {hours} the support hours. A message you edit in the setup guide shows your wording instead; the text below is the default. Wording that differs for an agent whose use case is Marketing has its own row. To find a message, search this page for its first few words.
Opt-in
Everything here is seen by the contact.
| Message | Where it appears | Editable in the setup guide? | More on |
|---|---|---|---|
| You're subscribed to receive {frequency} from {agent}. Reply STOP to cancel. Reply HELP for help. Msg & data rates may apply. | Sent after a contact opts in (JOIN keyword, JOIN link, or Yes, Subscribe). {frequency} defaults to "recurring messages" | Yes: Message frequency or Use custom text (must mention STOP and HELP) | Consent capture |
| Would you like to receive RCS messages from {agent}? Tap Yes to subscribe or No to decline. | Double opt-in prompt, with buttons Yes, Subscribe and No, Thanks. Also sent to an opted-out or unknown contact who texts something that is not a keyword | Yes (text and button labels) | Consent capture |
| Marketing form: Would you like to receive marketing messages from {agent}? Click Yes, Subscribe to agree to receive automated marketing msgs at this number. No purchase necessary. | Same prompt, default for a Marketing agent | Yes | Consent capture |
| Processing your opt-in request... | The JOIN entry state's own text; the state moves on to the opt-in confirmation at once | No | Consent capture |
| We couldn't process your request right now. Please reply JOIN again in a few minutes. | JOIN, or Yes, Subscribe in a chat, when the app could not record the opt-in | No | Consent capture |
Opt-out
Everything here is seen by the contact.
| Message | Where it appears | Editable in the setup guide? | More on |
|---|---|---|---|
| You've been unsubscribed from {agent}. You won't receive any further messages. | Sent after STOP, any opt-out keyword, No, Thanks, or a typed opt-out in an unrecognized message | Yes: STOP confirmation message | Consent capture |
| Processing your opt-out request... | The STOP entry state's own text; the state moves on to the confirmation at once | No | Consent capture |
| We couldn't process your request right now. Please reply STOP again in a few minutes. | STOP when the app could not record the opt-out | No | Consent capture |
| We couldn't process your request right now. If you want to stop receiving messages, please reply STOP again in a few minutes. | An unrecognized message when the app's keyword check gave no answer | No | Consent capture |
Help and unrecognized
Everything here is seen by the contact.
| Message | Where it appears | Editable in the setup guide? | More on |
|---|---|---|---|
| Here's how to reach us. Tap an option below. | HELP reply once it has a button (website, phone or Chat with agent). "Here's how to reach us." until then | Yes: HELP text, buttons and details | Consent capture |
| Email us at {email}. | Added to the end of the HELP reply when a support email is set. A placeholder address, [email protected], is written when nothing else is set, and the health check flags it | Yes: Support email | Consent capture |
| Looking up your subscription info... | The HELP entry state's own text; the state moves on to the HELP reply at once | No | Consent capture |
| Sorry, we didn't understand that. Reply HELP for help or STOP to opt out. | Unrecognized message when no inbox is connected and HELP has no real contact detail | No | Consent capture |
| Sorry, I can't respond right now. Please try again in a few minutes. To stop messages, reply STOP again. | A text in a live chat when the app could not run its check | No | Consent capture |
| Sorry, we can't process your message right now. Please try again later. | The reply to any text, including STOP, HELP and JOIN, once the clean-up after an uninstall has reached the agent | No | Uninstall |
Setup-guide health banners and tile titles are listed in the health checks section of the agent setup page.
Chat and inbox
| Message | Where it appears | Who sees it | Editable in the setup guide? | More on |
|---|---|---|---|---|
| Checking your subscription... | After the contact taps Chat with agent, while consent is checked | Contact | No | Inbox |
| To chat with an agent, you first need to opt in to recurring messages from {agent}. 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 for a contact who is not opted in, with buttons Yes, Subscribe and No, Thanks | Contact | Yes (text and button labels) | Inbox |
| Marketing form: To chat with an agent, you first need to opt in to marketing messages from {agent}. 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. | Same prompt, default for a Marketing agent | Contact | Yes | Inbox |
| Capturing your opt-in... | After Yes, Subscribe in the chat opt-in prompt | Contact | No | Inbox |
| Thanks for reaching out! A support agent will be with you shortly. Our team is available {hours}. If you would like to opt out of these messages at any time, please message STOP. | Chat confirmation. The hours sentence only when hours are set | Contact | Yes: Chat with agent message and support hours | Inbox |
| We 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. | After each text the contact sends during a live chat | Contact | No | Inbox |
| Sorry, we couldn't connect you to an agent right now. Please try again in a few minutes. | Chat with agent when the hand-off to the inbox failed | Contact | No | Inbox |
| Your chat has ended. Text us anytime to start a new conversation. | Sent when your team closes a conversation. Not sent when an opt-out closes it | Contact | Yes: End-of-chat message in the Inbox step | Inbox |
| Closed automatically: this contact opted out of RCS messages from this agent. | Internal note on the thread when an opt-out closes it | Your team | No | Inbox |
| Not delivered: this contact opted out of RCS messages from this agent. They must opt in again before you can message them. | Internal note on the thread when a reply to an opted-out contact is blocked | Your team | No | Inbox |
| Not delivered: consent could not be verified. Try again in a moment. | Internal note when the app could not check consent on a thread an opt-out closed | Your team | No | Inbox |
| Not delivered: the message could not be sent to RCS. Try again in a moment. | Internal note when the send to RCS Studio failed | Your team | No | Inbox |
| [Conversation escalated — no prior message history available.] | First line of a thread when no earlier messages could be copied in | Your team | No | Inbox |
Thread lines that start [RCS Agent] carry the message's name, never the message text. See Inbox.
Consent import
Everything here is seen by your team.
| Message | Where it appears | Editable in the setup guide? | More on |
|---|---|---|---|
| Unrecognized column: company_name. Allowed columns: phone, first_name, last_name, email, company, job_title. | The import window, when a file has a column it does not accept | No | Add your existing consent |
| Column email appears more than once. | The import window | No | Add your existing consent |
| Column 3 has no name. | The import window | No | Add your existing consent |
| The file needs a column named phone. | The import window | No | Add your existing consent |
| The file is empty. | The import window | No | Add your existing consent |
| Columns other than phone are not used when opting out. | The import window, on the Opt-out tab | No | Add your existing consent |
| N rows imported, but some details were not saved. | The finished import | No | Add your existing consent |
| +12345550100 opted in. The name could not be saved. | The Record Existing Consent tile | No | Add your existing consent |
Workflow results
Everything here is seen by the workflow builder.
The text is the Not Sent Reason output of Send RCS Message, shown in the workflow history next to the Send Status. See Workflows for the order of the checks and the fix for each.
| Message | Where it appears | Editable in the setup guide? | More on |
|---|---|---|---|
| Not sent: this contact has opted out of messages from this RCS agent. | SKIPPED_OPTED_OUT | No | Workflows |
| Not sent: this contact has no recorded opt-in for this RCS agent (the agent is not in the contact's RCS Consent — Opted In property). | SKIPPED_NO_CONSENT | No | Workflows |
| Not sent: this contact's consent could not be verified because HubSpot was unavailable. The send was not retried. | SKIPPED_CONSENT_UNVERIFIED | No | Workflows |
| Not sent: this RCS agent's STOP step is not set up, so a STOP reply could not be recorded. Open RCS Studio in HubSpot ({link}), open the agent and finish the setup guide. | FAILED. Without a link: "Open Marketplace › RCS Studio › Agents and finish the setup guide." | No | Workflows |
| Missing agentId — select an RCS agent in the workflow action configuration | FAILED | No | Workflows |
| Missing message template — select a template in the workflow action configuration | FAILED | No | Workflows |
| This message template is managed by the HubSpot integration and cannot be sent from a workflow. Choose another template. | FAILED | No | Workflows |
| Installation not configured | FAILED | No | Workflows |
| Contact has no Phone Number, or Contact has no Mobile Phone Number (the field in use, set in Settings) | FAILED | No | Workflows |
| Contact phone number is invalid or missing country code | FAILED | No | Workflows |
| A previous attempt of this action run may already have sent the message, so it was not sent again. | FAILED | No | Workflows |
| RCS Studio refused the send — the account may be suspended. Check the account in RCS Studio. | FAILED | No | Workflows |
| The RCS message could not be sent because of an unexpected error. Try again later or contact support. | FAILED | No | Workflows |
| The RCS message failed to send. Check the RCS Studio logs for details. | The action's own message on any FAILED run | No | Workflows |
Next
- Return to the overview for the path from install to your first message.
Updated 9 days ago