A buyer messages at 10 pm asking about a 3-bedroom unit near the metro. The team that replies first, with the right details, has the best shot at booking the site visit.
This guide shows how the Claudeforce MCP integration with RCS fits together. Claude reads approved CRM context through Salesforce, and an RCS messaging layer delivers the rich, tappable reply. One note on the name: “Claudeforce” isn’t an official product. It’s shorthand for connecting Claude to Salesforce Hosted MCP Servers.
Four Layers, Four Separate Jobs
The Claudeforce MCP integration with RCS is really four layers working in sequence. Keeping them apart avoids most confusion:
| Layer | What it does | Real estate example |
| Claude | Reads, summarises, and drafts | Summarises a buyer’s budget and location needs |
| MCP | Gives Claude a structured, permissioned way to reach Salesforce | Retrieves the lead record the rep is allowed to see |
| Salesforce | Stores leads, preferences, and sales activity | Budget, unit type, last site visit |
| RCS messaging layer | Delivers the customer-facing message | Sends a property carousel with a “Book a visit” button |
MCP is not an RCS API. Integrating Claude into Salesforce will not result in an RCS channel. An integration in Salesforce that supports RCS is required to have such conversations.
What Changes for a Property Sales Team
None of this replaces your reps. It removes the slow parts of their day:
- Quick context: A rep requests a lead summary from Claude instead of browsing through the notes.
- Appropriate responses: It depends on budget, location, and preference of the unit.
- Timely follow-ups: Follow up visits and emails are triggered by leads in Salesforce.
- Inquiries qualify more quickly: They get routed before even reaching the rep.
- Engagement can be tracked: Information about the delivery and response is logged in the lead record.
Setting Up the Claudeforce MCP Integration with RCS, Step by Step
The Salesforce steps below follow Salesforce’s developer guide to connecting Claude with Hosted MCP Servers. Menu labels can change, so check the current documentation before you start.
Part 1: Connect Claude to Salesforce
1. Activate a hosted MCP server – In Setup, search for MCP Servers, open the Salesforce Servers tab, pick a server, and click Activate. Standard servers are inactive by default. Copy the server URL, which differs for production and sandbox orgs.
2. External Client App Creation – This refers to application registration, which defines the capabilities and rights of the external client app to access Salesforce. This will be found in Setup on the External Client App Manager page.
3. OAuth Configuration – This enables Claude to authenticate without sending its password. It involves enabling OAuth, adding Claude’s callback URL (which differs depending on the Claude surface), and selecting the scope of access and Hosted MCP Servers. Enable PKCE and JWT-based access token as well, and then get the Consumer Key. Do not use JWT option, or sign-in will seem successful but subsequent requests will fail.
4. Add the server in Claude – Steps differ between Claude Desktop, the Claude connector flow, and Claude Code. Salesforce documents each in its Claude connection guide.
5. Test with a dummy lead – Ask Claude to pull one record. It works with the logged-in user’s Salesforce permissions, so field-level security decides what it can see. If sign-in fails right after setup, wait a few minutes and retry.
Part 2: Add the RCS layer
1. Set up RCS inside Salesforce – Through an RCS-enabled Salesforce messaging integration. Sender registration, templates, and consent rules belong here, not in MCP.
- Create the lead journey – Choose the Salesforce events that will trigger messages, such as a new enquiry or a scheduled visit, and how responses will be sent to the appropriate rep. An easy way to begin is by creating one trigger for new enquiries, one for visit reminders, and one for post-visit responses.
- Test the entire lead journey once – and then measure delivery and engagement.
Salesforce also enables the ability to make Flows and Apex actions available via custom hosted MCP servers. The presence of an RCS send action is dependent on the messaging layer that you use.
One 3-Bedroom Enquiry, From First Message to Site Visit
1. Buyer responds to launch message via RCS: The buyer is interested in a 3-bedroom apartment in a certain region, subject to a ceiling amount.
2. The lead is noted in the log, and the routing sends the lead to the representative.
3. The representative requests Claude to make a summary of the lead and list down the units which match the buyer’s requirements. Claude will be able to list the units if that data exists in Salesforce.
4. The rep checks the summary, then sends a carousel of matching units with a “Book a visit” button.
5. After the visit, an automated reminder and follow-up go out, and the rep sees whether the buyer opened them.
Claude supported the rep here. The rep decided what to send.
The speed gain comes from the first reply. Instead of asking the buyer to repeat their budget, the rep already has it, and the message arrives with options the buyer can tap.
RCS Messages Worth Building First
Rich messaging features like images, buttons, and carousels suit property sales well:
- Property carousels with photos, floor plans, and starting prices
- Site-visit confirmations and reminders with map buttons
- Availability and price updates for interested buyers
- Launch campaigns to segmented lists
- Post-visit follow-ups with brochure links
However, not all places offer RCS, nor is it supported by all phones used by customers. Create a contingency plan on how to deal with this situation in case someone misses your message.
Where AI Helps and Where Reps Stay in Charge
The advantages of AI include efficient research, summarizing the history of CRM, responding to customers, suggesting actions, and dealing with repetitive inquiries. Representatives need to be responsible for negotiations, exceptions in pricing, delicate conversations, and valuable clients. One useful rule is: If there will be any negative consequences from a mistake, send the message manually.
Useful prompts for a rep to try:
- “Summarise this lead’s budget, preferred area, and past enquiries.”
- “Which open 3-bedroom units fit this budget?”
- “Draft a short follow-up for a buyer who visited yesterday.”
A Checklist Before Going Live
- Permissions: allow Claude’s end users access only to the records and fields that they need.
- Data Quality: ensure the budget, location, and units fields are clean as the summary is as accurate as the record.
- Message Approval: employ approved templates, and have a representative check the drafts created by the AI.
- Consent: confirm that the user opted in before sending any marketing message.
- Routing: develop routing rules depending on the project, region, or language.
- Testing: start testing in sandbox, using sandbox server URL.
- Fallback and Monitoring: handle undelivered messages and monitor engagement once a week.
- Ownership: identify an administrator that will take charge of the connection in case of expiry or change in permission.
Conclusion
The Claudeforce MCP integration with RCS works best when each layer does its own job: Claude helps your reps think, Salesforce holds the facts, and RCS delivers a message buyers actually enjoy opening.
Pick one property project and one journey, from enquiry to site visit. Connect Claude in a sandbox, set up the RCS workflow, and measure response time before you scale. If you’re weighing an AI-connected CRM and RCS workflow, that single pilot will tell you more than any demo.
FAQs
Is Claudeforce an official Salesforce product?
No, it’s just a shortcut. Officially it should be called Salesforce Hosted MCP Servers with Claude as a connecting client.
Does the Claudeforce MCP integration with RCS provide me RCS messaging out of the box?
No, MCP provides a connection between Claude and Salesforce-approved data/actions. RCS messaging requires a separate messaging layer within Salesforce.
Can Claude send RCS messages to the buyers?
It cannot do it by default. This feature requires a specific sending action from your messaging layer and most often there is a representative who approves every message in Claudeforce RCS integration.
What is required on the Salesforce side?
An active Hosted MCP server, an External Client App with OAuth, and a Claude connection. Users should also have regular Salesforce permissions.
Can we personalize RCS messages using Salesforce data?
Yes, usually. The name, project, unit preference, and visiting dates can be used in a template, based on your messaging configuration. Test all fields using test data so that nobody gets a blank or incorrect value.
Will every buyer have access to RCS messages?
RCS will not be available to all buyers. It all depends on the type of phone, network operator, and the buyer’s location.
For more insights, updates, and expert tips, follow us on LinkedIn.