Overtoom
NL
HomeResourcesReach leads looking for a second home on WhatsApp within five minutes

Guide

Reach leads looking for a second home on WhatsApp within five minutes

Real estate companies lose leads because emails go unread and calls go unanswered. This is how you follow the entire journey on WhatsApp, from first contact to viewing, without your sales rep typing a single message.

Jamal CederMeta Tech Provider · · 8 min read
Meta Tech Provider

Overtoom builds custom solutions on the official WhatsApp Business API for real estate companies selling investment property and second homes. The WhatsApp number is registered to the client. Overtoom is a Meta Tech Provider and builds a bespoke service for each client, connected to the CRM systems they already use.

The problem

A lead requests information through your website. It lands in your CRM. An automated email is sent. That email goes unread, or ends up in spam. Your sales rep calls. Once, twice, five times. Those who do not answer are left behind. Meanwhile, the lead buys elsewhere, or not at all.

Nobody buys a second home worth several hundred thousand euros after one conversation. Months pass between inquiry and purchase. During those months, little happens. Your sales rep wants as few actions as possible. Even opening WhatsApp and typing a message is too much.

  1. 1

    0 minutes

    Lead requests information on the website

  2. 2

    Immediately

    Email is sent and not read

  3. 3

    Hours later

    Sales calls, no one answers

  4. 4

    Days later

    Lead has gone cold or moved to competitor

  5. 5

    Months later

    No contact, no viewing, no sale

Why WhatsApp

Speed decides everything. The sooner after the request, the better the lead still remembers it. WhatsApp gets read. A message with a personal name and photo does not feel like marketing.

Immediate contact

Within five minutes, a message from the advisor assigned to that project. It is a business account, but the name and tone are Sanne's, with her photo. The lead immediately picks a time to call. That choice becomes a task in the CRM.

Visuals that stick

One day later, the promotional video of the project. The lead watches at home, shows it to whoever decides with them. The video sits in the chat, ready to view and share.

Proof not promise

A few days later, completed projects, construction progress, what owners say. With the question whether the lead wants a viewing or prefers to call first. No pressure, but a next step.

No actions for sales

One field changed in the CRM, for example to not reached, and the lead immediately receives the corresponding message. Zero actions in WhatsApp. The sales rep works in the system they know.

What the lead sees

This is an example from Zonneplaneet, a real customer of ours. The profile photo is on the left, with the names next to it on the right. This phone has saved the number. That is why you see the custom name the user entered at the top. Below that is the approved business name with Meta's blue checkmark. A fresh lead only sees that approved name. The checkmark is then not visible. Meta rejects a standalone personal name. Meta does approve a name that includes the company. Always set a profile photo. Without a photo, your message looks like spam.

WhatsApp chat header of Zonneplaneet with logo and blue verified badge
Property leadPaul→Zuiderkust Resorts

How the conversation looks

Paul has requested information about an apartment. He is in Tribe with name, number, project and advisor. This is what happens.

Scenario

Paul has requested information about an apartment on the Zuiderkust Resorts website. He is in Tribe CRM with name, phone number, project and advisor Sanne de Wit.

Z

Zuiderkust Resorts

last seen recently

24h service window closed

Messages are end-to-end encrypted.

This conversation proves you can make personal contact within five minutes, without your sales rep typing anything. The lead chooses their own next step.

Speed

Tribe reports the new lead. The first message leaves within five minutes.

Hello Paul, I am Sanne from Zuiderkust Resorts. I saw you are interested in our project. I would love to call you to explain everything. When suits you best?

This afternoon

Perfect, I will call you this afternoon between 2:00 and 3:00 PM. Speak then.

The choice becomes a task for Sanne in Tribe: call this afternoon.

That evening

Hello Paul, here is the video of the project you are interested in. Let me know if you have any questions.

Watch video

Four days later

Hello Paul, I wanted to send you some images of our completed projects. I have also included a link to owner reviews below. Would you like to schedule a viewing, or do you have questions first?

Schedule viewing

Thank you, I will send you some options for a viewing right away. You can choose a date that suits you directly.

Every message and every answer stands on the customer card in Tribe, with a task for Sanne.

Play the conversation

Software that works together

The WhatsApp conversation is automated. The sales rep works in their CRM. The integration makes it feel like one system.

What the sales rep does

The sales rep works in Tribe CRM. They see a lead, change a field, and the rest happens automatically. Every message and every reply comes back to the customer card. The full history is in one place.

  • Lead enters Tribe
  • Rep changes field in Tribe
  • WhatsApp sends automatically
  • Reply appears in Tribe

What we built

Tribe notifies us via webhooks when something changes. Those notifications are signed, so we know they really come from Tribe. We then fetch the lead via the API: name, phone number, project, advisor, even the photo. Writing back works the same way: every message arrives as an activity on the customer card. Tribe has no native WhatsApp function. That integration did not exist, we built it.

Tribe CRM
Name and phonePersonalizing the WhatsApp message
ProjectSelecting the right video and proof
AdvisorName and photo in the message
Appointment dateSending reminders automatically
Choice fieldSales rep triggers message without typing
Interaction historyWriting back as activity

This works with any system with a usable API, Tribe is the example because the integration is live there.

Your sales rep types no messages at all.

How we build it

No standard package. A bespoke service for each client, built on the systems they already use.

  1. 1

    Discovery

    We look at your CRM, your processes, your projects. What is there, what needs to come out, what needs to go in. We map the conversation your lead should receive.

  2. 2

    Integration

    We build the connection to your CRM. Tribe is the example, but any system with an API works. We test whether notifications arrive, whether fields match, whether photos come through correctly.

  3. 3

    Messaging

    We write the messages together. Your brand tone, the steps that fit your sales process. The video, the proof, the questions. Everything is approved in advance.

  4. 4

    Automation

    We set the triggers: after five minutes, after one day, after four days. The reminders that move with appointments. The follow up that automatically asks if there is still interest.

  5. 5

    Go live

    We go live with a test project. We check whether everything arrives, whether sales reps understand it, whether leads respond. Then we roll out to the rest.

What it costs

Meta charges per message sent, by country and category. Dutch rates from 1 October 2026: marketing 0.1323 euro, utility 0.0414 euro, service 0.0414 euro per message. The first thousand service messages per month are free.

On top comes Overtoom's monthly fee. That depends on the number of steps in your conversation, the number of systems we integrate, and volume. You hear it in a thirty minute conversation. No surprises afterwards.

The requirement

This works if your CRM has a usable API. Tribe is the example because we built and tested the integration there. Pipedrive, HubSpot, Salesforce, all possible. Without an API we cannot write back, and the sales rep loses oversight.

Systems that work

Tribe CRMPipedriveHubSpotSalesforceMicrosoft DynamicsCustom CRM with API

Frequently asked questions

Why does this work with Tribe and not other CRMs?

It works with any CRM that has a usable API. Tribe is the example because we built the integration there for a client. The webhook is signed, the fields match, the writeback works. For other systems we build the same.

What does Meta charge per message?

Meta charges per message sent. Marketing messages cost 0.1323 euro in the Netherlands. Utility and service cost 0.0414 euro. The first thousand service messages per month are free. After that you pay 0.0414 euro per service message, even if it is a reply to something from the customer.

Can the sales rep really type nothing in WhatsApp?

The sales rep works in their CRM. They change a field, we send the message. If they want to add something personal, they can. But the idea is that standard work happens automatically, and the sales rep has time for real conversation.

What if a lead does not respond?

Leads on follow up automatically receive a question after a few weeks whether they are still interested. Three buttons: yes, later, no. For no, the lead goes to lost in the CRM with reason. For later, a new date. For yes, a task for the advisor.

How quickly can this go live?

The Tribe integration is already built. Templates must be approved by Meta, usually within a day, sometimes a week. After that it depends on how clean your data is in the CRM. We schedule thirty minutes to discuss your situation.

Build this for you

Discuss your situation in a thirty minute conversation

We look at your CRM, your processes, your projects. You hear what is possible, what it costs, and how quickly we can start. No obligations.

Schedule a call