watsi and Inmuebles24

Exactly what happens when someone writes to you from Inmuebles24

The path is the same one any other prospect reaching your WhatsApp takes, and that is the point: Inmuebles24 puts a contact button on your listing, the prospect taps it, and their first message lands on your WhatsApp Business number. From that instant the conversation is yours, not the portal’s, and watsi sees it the way it sees any other.

The agent answers that first message without waiting for someone on the team to be free. That matters more on a portal than on any other source: whoever writes from a listing is usually writing to several listings the same afternoon, so the conversation is decided in the first few minutes and not in the next day’s follow-up.

From there the agent does what an advisor would do on that first contact: confirm which property caught their eye, ask about area and budget, understand how they plan to pay, and offer real time slots from your calendar to book the viewing. If the conversation goes beyond what the agent can resolve, it escalates to a person with the whole thread, not with a summary.

How it gets recorded that the contact came from Inmuebles24

Inmuebles24 is one of the contact sources watsi recognises out of the box, at the same level as WhatsApp, Instagram or Google Ads. It is not a free-text label somebody has to remember to add: it is a value of the contact’s own source field, so it counts in the reports without depending on anyone’s discipline.

On top of that, watsi ships a built-in rule that recognises the template text the portal prepends to the prospect’s message, and marks that contact as coming from Inmuebles24 even if nobody classified it by hand.

The rule governing that detection is deliberately conservative, and it is worth knowing before you trust the data: if the message does not match a known template, the contact is left untagged. Watsi never infers the source channel from arbitrary text. An untagged contact — which is visible, and fixable — is better than a report that splits leads across portals with a confidence it does not have.

What a correctly recorded source is for

The question this answers is not "how many leads did the portal give me" — the portal already tells you that — but "how many of my viewings came out of it". Those are different numbers and only the second one helps you decide whether to renew the portal plan. Since watsi is the one booking, it is the one that can join both ends: the contact carries its source and the appointment carries its contact.

The same field enables the opposite, which is just as useful: seeing which source produces conversations that die on the first message. A portal that sends volume but no intent shows up in that rate before it shows up on the invoice.