Skip to content

Automation · Sales and quoting

Show listings over WhatsApp and leave the viewing booked

How an AI agent shows Wasi listings over WhatsApp, registers the lead with approval and books a verifiable viewing slot.

How do I handle property enquiries over WhatsApp without a sales agent glued to their phone?

The Met on the channel works out what the person is looking for (property type, city, area and price range), queries Wasi and returns the records that match its publication filters in that query, with their links and photos when requested. Before sending personal data to Wasi it shows the exact fields and waits for approval. Once the person picks a slot, it rechecks the property, time and resource, presents the exact summary and books only after another explicit yes. It then verifies the booking and hands the written context to the human team.

Where it applies: Colombia. Wasi operates in several countries in the region; this automation is written on a Colombian operation, with its cities and areas.

What starts it

When the customer writes

It starts when somebody writes asking about a property, almost always from a listing or a campaign. The Met on the channel handles the conversation, and there is nothing to schedule.

Nothing to set up. The Met assigned to that channel picks up the conversation and runs the procedure inside it.

Who runs it

Met for real estate enquiries

Customer service team

It has no seeded name in the product: it is the channel Met with Wasi, scheduling and the CRM turned on. Its value is in the filtering, which is where a sales agent's time goes.

Channels: WhatsApp · Instagram · Website chat

What you need connected

6 steps · 19 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

  1. 1

    Narrow the search before searching

    Property types, the cities that actually hold published inventory and the areas inside those cities all come out of Wasi itself, so the Met offers options that exist instead of a generic list. The portfolio price range frames the conversation when the person does not know what to ask for: telling them the band the inventory moves in saves half an hour of empty searches.

  2. 2

    Show only what is published and live

    The search returns a short summary per property (price, bedrooms, area, location) and the detail brings the full record with its main image and public link. Before proposing a viewing, the Met reads the selected property again. That verifies the record at the last query; it does not prove access, keys or the owner's approval.

  3. 3

    Send photos when they are actually asked for

    The full gallery is requested separately, on purpose: sending twenty photos nobody asked for floods the conversation and the customer's phone. The Met also remembers the properties already reviewed in that session, so when the person says the one on Seventh Avenue it knows which one without searching again.

  4. 4

    Register the lead as a Wasi client

    The Met searches by email or phone and compares the exact value: zero matches may proceed to a proposed create, one means reading that id, and more than one stops for human review. Before a create or update it explains which data will leave Meteor for Wasi, shows the change and waits for explicit approval. After a create it requires one unambiguous id and reads that exact record. If the response is empty, non-JSON or lacks an id, it reconciles by email or phone: zero matches stays uncertain, one requires an exact readback and more than one goes to human review. It never treats an empty body as success or blindly retries the write.

  5. 5

    Book the viewing in a slot that exists

    Wasi does not book viewings; Meteor's native scheduling does. The Met lists the configured service with duration and modality, offers technical slots with their configured resource and rechecks the chosen one. It summarizes service, time zone, time and resource. It adds a venue only when explicitly stored, waits for an unequivocal yes, creates once and reads the booking back before confirming it.

  6. 6

    Hand the conversation to the sales agent

    The internal note writes down what they were looking for, which properties they saw and what they liked, in their own words. Transfer to a human leaves that note, marks the status and pulls the Met out in one step. The team receives the context, but the transfer does not prove that the same person named as the scheduling resource receives the case or already has access to the property.

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

They see the real listing: the property detail carries the public link, the same one anybody would open from the portal. The Met summarizes so the conversation flows, but the source is the published record.

It says so and offers the closest record found in the queried portfolio, using the price range and areas with inventory. It does not call a viewing available: the publication is rechecked before booking and the human team confirms access.

In both, each with its own job. In Wasi it is a client, where the sales team works; in Meteor it is the conversation with its notes and its history. A lead that lives only in the chat is the one that gets lost when the person handling it changes.

Yes. The search filters by deal type just as it filters by property type; what changes is the qualifying questions, which are adjusted in the Met.

Keep going

Other automations built on the same tools

Want this automation running on your own data?

We will show it to you with your accounts connected, not with a canned demo.