A portal lead goes cold in minutes
People browsing listing portals click "I'm interested" on five or six listings in the same evening. The agencies that reply first, and on WhatsApp, win the conversation. Whoever sends an email the next morning is talking to someone who has already booked a viewing elsewhere.
The bottleneck is rarely the agent. It's the path to them: the lead lands in a shared inbox, the manager forwards it by hand, the agent is out on a viewing and only sees it hours later. A real estate CRM that removes that path becomes a selling point for your product in the first meeting.
Lead routing: round-robin leaves the agents' group chat
Many agencies still distribute leads in a WhatsApp group, where the first agent to reply "mine" takes it. Your software can do it better, with rules and a record:
- The lead arrives from the portal through your system's integration, with the listing code.
- The system picks the agent by the agency's rule: round-robin, neighborhood specialty or listing agent.
- Within seconds, the first message goes out to the prospect from that agent's number, with their name and the property of interest.
- The agent gets a notice on their own WhatsApp with the lead details.
- If the agent doesn't respond within a set time, the lead moves to the next in line, with a record of who missed it.
The WhatsApp API handles sending and returns replies via webhook; the routing rule belongs to your software, and that is what sets one real estate CRM apart from another.
Example: property photos as an album
Sending twenty loose photos floods the chat and the client loses the thread. The album route groups images and videos into a single message, the way WhatsApp shows a gallery:
curl -X POST https://api.d-api.cloud/api/v1/messages/send/album \
-H "Authorization: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"sessionId": "realty-alpha-agent-joanna",
"to": "14155550123",
"caption": "2-bed apartment, Mission District, 730 sq ft. Ref. AP-4471",
"media": [
{ "type": "image", "url": "https://cdn.yourrealty.com/ap-4471/living-room.jpg" },
{ "type": "image", "url": "https://cdn.yourrealty.com/ap-4471/kitchen.jpg" },
{ "type": "image", "url": "https://cdn.yourrealty.com/ap-4471/bedroom.jpg" },
{ "type": "video", "url": "https://cdn.yourrealty.com/ap-4471/tour.mp4" }
]
}'The URLs must be public at send time, and the album accepts 2 to 100 items. Send photos already resized by your CDN so the client can open them quickly on mobile data. Each item also accepts its own caption. Other formats are in send images, audio and files.
Booking viewings without the back and forth
Scheduling a viewing is where agents lose the most time in chat: "does Saturday work?", "morning?", "what's the address?". The real estate system can shorten that:
- Open slots as a list: a list message with the available times on the agent's calendar; the client picks one and the viewing goes on the calendar.
- Native location: on the day, the property location arrives as a WhatsApp pin, not a typed address.
- Day-before confirmation: fewer missed viewings and fewer agents crossing town for nothing.
- After the viewing: a short question about what they thought, logged on the lead for the next contact.
Multiple agents: one number per person or one central number?
| Number per agent | Central agency number | |
|---|---|---|
| What the client sees | The agent's name | The agency's name |
| Connections on the account | One per active agent | One or a few |
| When the agent leaves | Disconnect their number; the history stays in the system | Nothing changes for the client |
| Best fit for | Agencies of independent agents and partners | Agencies with a first-contact team |
Your software should support both models, because the market uses both. On D-API each number is an isolated connection with a dedicated IP, created via API. If the agent who sent too many messages gets their number restricted, their colleagues are not affected. More on the topic in multiple WhatsApp numbers.
Roadmap for your real estate CRM
- A connection per agency or per agent, with the QR code in each one's dashboard.
- Automatic first message to portal leads, with the routing rule.
- Sending the property album from the listing page.
- Viewing calendar with a list of time slots and the location.
- Conversation history on the lead record, fed by the webhook.
History on the lead follows the same logic described in WhatsApp API for CRM. The commercial model, billed per connection and not per message, is in WhatsApp API for SaaS. If you want to validate it with a few agencies from your base, the 14-day free trial available through sales includes implementation support.