Turn conversations
into business action.

REDA AI. Your agentic workforce for Salesforce. Configure agents to support employees, serve customers, and automate business processes. From a WhatsApp inquiry to the right next step.

In this video, we follow an API agent working behind the scenes: understanding a prospect, finding property information, updating Salesforce, and moving the conversation forward. Watch how business data, communication and AI work together. We have a dedicated WhatsApp number connected

to this Salesforce org through REDA Connect. REDA One is our real-estate management ERP, providing the property and inquiry records. REDA Connect brings conversations from WhatsApp, SMS, Facebook Messenger and Instagram into Salesforce, with messaging and workflow automation.

REDA AI adds the agentic layer. Here, that agent is Mira Praxis. Now let’s see it happen. The prospect sends a simple hello to the connected WhatsApp number. We refresh the inquiry list, and the new record appears.

Opening it shows the incoming message inside REDA Connect. The messaging integration has brought the conversation into the same workspace as the business record. Mira introduces herself as an AI leasing assistant and asks for the person’s full name and preferred area.

This is the first connection to the procedure: establish who is asking and where they want to live. The available areas are presented as choices, and the prospect selects Chicago. An API agent is called by another system or workflow to carry out a job.

In this setup, an incoming WhatsApp message triggers Salesforce automation, which gives Mira the inquiry context. She can use her configured tools to read information, update records and send a response. The employee does not need to open a copilot chat to start each turn.

Next, Mira asks what type of home the prospect wants. Kunal provides his name and email, then selects three bedrooms. He uses ordinary conversation and available choices. Behind the exchange, Mira has tools to turn those answers into fields the leasing team can use.

We refresh the inquiry and inspect the details. The full name, email and Chicago preference have been saved. This matters to the team: useful information is becoming part of the business record as the conversation develops. It does not have to remain buried in the chat.

Mira then presents a three-bedroom option at nine Walton. The response includes the recorded rent, the lease term and the property details returned by the search. She also asks about the move-in date and intended lease length. Here, the procedure connects the customer’s question to current Salesforce

inventory, while continuing to gather the missing requirements. What gives that work direction? Mira has been configured with the leasing team’s operating procedures. Understand the prospect and their requirements. Search the recorded inventory.

Use the returned prices and listing details. Keep the inquiry updated, and offer the appropriate next step. Her context brings together the inquiry, recent messages and related activity. Her tools provide the actions. These parts work together around this business process.

The workflow also sends a welcome email. We open the activity in Salesforce and inspect the branded message associated with this inquiry. The conversation began on WhatsApp, but the configured agent can coordinate another useful action using the contact information collected.

The sent email is recorded alongside the inquiry, where the team can review it. The prospect asks for photos or videos of the three-bedroom unit. Mira replies that media is not available for that unit and offers to check viewing times.

That is a useful boundary in this exchange: communicate the information available and offer another way forward. Then the prospect changes direction: is there a one-bedroom option? Mira responds to the new requirement using another property search. She provides the one-bedroom listing, its three-thousand-dollar monthly rent,

and the available video and listing links. The same agent adapts the next step as the conversation changes. Now Kunal says he would like to see the unit. Mira uses the configured viewing tool and offers available times to choose from.

This recording stops at the offered slots; a viewing has not yet been booked. The procedure has moved the inquiry from an initial question towards a practical next step. The inquiry is now at the Contacted stage, with the captured contact details and current one-bedroom preference saved.

The WhatsApp exchange and sent emails remain associated with it. A colleague can pick up the conversation with useful context, rather than ask the prospect to start again. What have we connected? REDA One supplied the business records.

REDA Connect carried the messages. REDA AI used the configured context, procedures and tools to respond, save information, send email and offer viewing times. For the prospect, it is one conversation. For the leasing team, it creates a more

useful inquiry and a clearer next step. WhatsApp is one entry point into this pattern. The API and automation channel can also support incoming email, scheduled follow-ups and other business events, with the relevant integrations and tools configured.

Your data model and your procedures shape the work. That is the broader opportunity: an agentic workforce for Salesforce, built around how your business operates. Hey, tell us about your one problem! We’ll build and test your first agent in your Salesforce sandbox.

Free within an agreed scope, with no obligation to proceed. Let’s bring an agentic workforce to your business!