This is an illustrative scenario, not a client story. It shows how a GCC real estate developer could use Salesforce Agentforce across the sales journey, based on capabilities Salesforce has announced. Each capability is labelled with the status Salesforce gives it today: GA (generally available), pilot, or beta.

Why the first hour matters

Picture a mid-sized developer in Riyadh or Dubai launching a new residential phase. Enquiries arrive from property portals, the project website, WhatsApp, and paid social ads. Some arrive at 11 pm. Some are from investors abroad. Some are the same person enquiring three times through three channels.

Most sales teams know the pattern. The enquiry sits in an inbox or a spreadsheet, a sales advisor calls back the next day, and by then the buyer has spoken to two other developers. The problem is rarely a lack of leads. It is speed, consistency and context.

This is where AI agents can help, as long as the data and the rules underneath them are right.

Stage 1: The enquiry arrives

In our scenario, every channel feeds one place: Salesforce. Portal leads come in through an integration. Website forms create leads directly. WhatsApp conversations and ad leads are captured the same way.

Two Salesforce agents are relevant at this stage:

• Piper, the inbound pipeline agent (GA). Salesforce describes Piper as working across websites and inboxes to engage, qualify and convert inbound leads into pipeline. Note that Salesforce positions Piper for B2B sales and marketing teams, so its fit for consumer property buyers is something to test, not assume.
• Casey, the help agent (GA). Casey resolves customer questions across voice, SMS, WhatsApp and web chat, with pre-built support for FAQs, account questions and human escalation. For a developer, that could mean answering first questions about a project on WhatsApp, day or night.

Salesforce says customers can tailor each agent to their business and even give it their own name, so buyers could meet "your" assistant rather than a generic bot.

Where the human steps in: your team decides what the agent may answer. Prices, payment plans, availability and anything contractual should come from approved records, not from the agent's general knowledge.

Stage 2: Qualification and routing

A good first conversation gathers what an advisor needs: budget range, unit type, preferred project, timeline, cash or mortgage, and whether the buyer is an end user or an investor.

The agent records these answers on the lead in Salesforce, and your existing assignment rules route it. A buyer asking about villas in one project goes to that project's team. An overseas investor might go to a specialist desk.

• Multi-Agent Orchestration (GA) lets specialised agents work together when a job crosses roles, systems or stages of the customer journey. In practice, a help agent can hand a qualified buyer on to the next step without the buyer repeating themselves.

Where the human steps in: you define what "qualified" means, and every high-value or unusual enquiry should reach a person quickly. The agent does the first sort. People decide.

Stage 3: Follow-up and nurture

Not every buyer is ready this week. Many are comparing projects, waiting for a launch, or checking financing.

In our scenario, follow-ups are driven by what the buyer told the agent: a reminder when a new phase opens, a floor plan for the unit type they asked about, or a check-in after a payment plan was sent. Each message is based on real data in Salesforce and follows your approved templates.

• Hunter, the outbound sales agent (pilot, GA planned for November 2026). Salesforce says Hunter works a pipeline from research to outreach, collaborating with sellers over weeks and months. It could one day help re-engage quiet leads, but it is in pilot today. We would not build a plan around it yet.

Where the human steps in: advisors review anything that makes an offer, a commitment or a price statement. Marketing owns the templates and the frequency.

Stage 4: Booking the site visit

The site visit is often where the sale is really decided, so this is the step to get right.

In our scenario, once a buyer says they want to visit, the agent offers available slots, confirms the booking, creates the event in Salesforce and sends a confirmation with the location. The day before, the buyer gets a reminder, and the advisor gets a summary of everything the buyer has asked so far.

This relies on an action your team builds, for example a Salesforce Flow that checks advisor or sales-centre availability. Agents take actions you define, so the quality of that booking step depends on how well it is designed and tested.

Where the human steps in: the advisor owns the visit. The agent books it and prepares the context.

Stage 5: Handover to the sales advisor

When the buyer walks into the sales centre, the advisor should already know:

• Which project and unit types they asked about
• Their budget range and timeline
• Every question they asked, and every answer they were given
• Which documents or payment plans were already sent

From here, the sale is human. Negotiation, reservation and contract steps stay with your team and your existing approval process. Salesforce says every agent operates within the customer's business rules, permissions and security, which is exactly why those rules need to be right before you start.

The prerequisites nobody puts in the demo

An agent is only as good as the data and access behind it. Before switching anything on, we would check four things:

• Clean lead and unit data. Projects, phases, unit types, availability and price lists must be accurate and current in Salesforce. If the agent reads an outdated price list, it will share an outdated price.
• Duplicate rules. The same buyer enquiring through a portal, WhatsApp and the website should end up as one person, not three leads with three advisors.
• Permissions. Agents work within the permissions they are given. Review what each agent user and integration can see and change, and give it the least access it needs.
• Consent for WhatsApp. WhatsApp business messaging has opt-in rules, and KSA and UAE both have personal data protection laws. Capture and store consent properly, and check your approach with your legal team.

Two things to confirm with Salesforce first

We have not been able to verify these in Salesforce's public announcements, so we recommend confirming them for your org before you plan:

• Arabic language support for the agents described above.
• Saudi data residency. Salesforce has announced plans to bring Hyperforce to Saudi Arabia, but we have not confirmed that an in-Kingdom region is live today. If data residency matters to your compliance team, ask your Salesforce account team directly.

Salesforce also notes that availability may vary by region, so check what is live for your region and edition.

Where to start

You don't need all five stages on day one. Most developers would get the fastest value from one step: answering first enquiries quickly and consistently, or making sure every site visit starts with full context.

Pick one step. Fix the data behind it. Decide where your people step in. Then measure.

If you are exploring how Agentforce could fit your sales journey, the Cloudastick team would be happy to talk it through with you. Contact us through our website or send us a message on LinkedIn.

Your Flow Is Flawless… But Would You Send This Email?

As Salesforce professionals, we spend hours designing Flows, building automations, and making sure every record reaches the right place.

But here's a question we don't ask often enough:

What does the person receiving the email actually experience?

Let's look at a real-life scenario.

Your Flow runs every evening and automatically sends your Project Manager a summary of today's support cases.

Email #1

Subject: Daily Support Cases Update

Hi,

Today's open cases: Case #10451 for Company X has been assigned to Ahmed. Priority is High and the current status is Waiting for Customer Response. Case #10452 for Fabrikam has been assigned to Sarah. Priority is Medium and the current status is New. Case #10453 for Adventure Works has been assigned to Karim. Priority is Low and the case has been Closed. Case #10454 for Tailspin Toys has been assigned to Mariam. This is a High Priority case and it is currently Waiting for Internal Review. Case #10455 for Alpine Ski House has been assigned to Omar. Priority is Medium and the case has been Escalated. Please review and take the necessary actions.

Regards,

The information is all there...

But imagine opening an email like this every single morning.

Finding all the high-priority cases. Comparing owners. Spotting escalations.

It takes effort.

Now look at the exact same information presented differently.

Email #2

Which email would you rather receive every day?

Exactly.

Same Flow. Same records. Same recipients.

The only difference is how the information is presented and that can completely change the user experience.

Did You Know?

One feature that often goes unnoticed is that the core Send Email action in Salesforce Flow allows you to use a Rich Text Template as the email body.

Even better...

Rich Text Templates support HTML.

That means you're not limited to plain text, bold formatting, or colors.

You can create:

• Professional tables
• Clickable record links
• Styled headers
• Formatted sections
• Dynamic layouts

...all without writing a single line of Apex.

Why HTML Tables?

HTML tables are one of the simplest and most effective ways to organize information.

At the heart of every table are four basic HTML elements:

• <table> – Creates the table.
• <tr> – Defines each row.
• <th> – Creates the column headers.
• <td> – Displays the data.

Using these elements together, Salesforce Flow can generate dynamic tables directly from your record collection, making emails much easier to read and navigate.

Instead of reading through a long list of text, recipients can compare information across columns and instantly identify what's important.

Final Thoughts

Automation isn't just about making processes work.

It's about delivering information in a way that's clear, actionable, and easy to understand.

The next time you're adding a Send Email action to your Flow, don't stop once the automation is complete.

Ask yourself one simple question:

"If I were receiving this email every morning, would I enjoy reading it?"

A few lines of HTML can transform a basic notification into a professional report helping your users find the information they need faster while showcasing the quality of the solution you've built.

At Cloudastick, we believe great Salesforce solutions aren't just functional they're designed with the end user in mind.