Messaging with REDA Connect
If you've spotted a REDA Connect app in your org and wondered how it relates to REDA, here's the short answer: it's the suite's messaging arm — a companion product for holding WhatsApp and SMS conversations with your customers, installed in the same org and running right beside REDA. It has its own app and its own documentation. This article's job is to place it for you and point you in the right direction; it deliberately does not walk through Connect's own features or setup, because those belong to Connect's own guides.
Access you'll need. REDA Connect has its own access model, separate from REDA's. If the app is installed but you can't open it, ask your administrator to grant you access.
What REDA Connect is
REDA Connect is a customer-messaging product: it lets your team have conversations with customers over WhatsApp and SMS from inside your Salesforce org. It's one of the packages in the REDA suite — installed alongside REDA's property-management core and the other suite components — so it shows up as its own app in the same org you already use.
Think of it as a sibling to REDA rather than a feature of it. Where REDA manages your properties, leases, and inquiries, Connect manages the messaging channels you use to talk to the people behind those records. The two live together in one org, but they're distinct products with distinct purposes.
How it relates to REDA
REDA Connect is installed in the same Salesforce org as REDA, so both sit over the same customer directory of accounts and contacts your org already keeps. But the connection stops there: REDA's own integrations don't depend on Connect, and Connect isn't wired into them. The links that carry REDA's data to REDA's accounting extension, to the resident portal, and to your website contain no messaging automation — they work identically whether or not Connect is installed.
Connect talks directly to the messaging providers that carry WhatsApp and SMS traffic. That's Connect's concern, not REDA's — REDA doesn't route messages, and none of REDA's integrations rely on those channels. In short: the two products share an org, but they run independently, and there's no messaging data flowing through REDA's own integration links.
Where to learn more
Because REDA Connect is a separate product, its features, channel setup, and configuration are covered in its own documentation rather than here. To set Connect up, learn what it can do, or get access, start with your administrator, who can point you to Connect's own guides and confirm how it's licensed for your organization.
Where to go next
- Suite Implementation Sequence — where Connect sits in the full REDA suite.
- Reading REDA Data via Salesforce APIs — the other "separate concern" article, on pulling REDA data out.
- Understanding Inquiries — where prospect conversations begin on the REDA side.
Frequently asked questions
It's a companion product in the same suite — installed alongside REDA, but a distinct product with its own app and its own documentation.
No. None of REDA's integrations depend on Connect — they behave the same whether or not it's installed.
Ask your administrator — they can point you to Connect's documentation and confirm how it's licensed and set up in your org.
Was this article helpful?