Ready scenarios
The property automations that come with Squaremeters, their triggers and steps, and how to read a scenario.
3 min read
Your automations aren't designed from scratch; they come as ready scenarios proven in estate agencies. During setup our team adapts them to your calendars, agents and tone of voice. This article lists the scenarios and explains how to read one on screen.
Scenario catalogue
| Scenario | Trigger | What it does |
|---|---|---|
| Appointment confirmation | Appointment booked (assistant, bot or team) | WhatsApp confirmation with date, time and address; task for the agent |
| Appointment reminder | 1 day and 2 hours before the appointment | Reminder, request to confirm, location link |
| Hot lead follow-up | hot-lead tag added | Task + alert for the agent; "we'll be in touch" message to the contact |
| Information request | Call outcome: information request | Requested listing or info on WhatsApp; a short check-in a few days later |
| No answer | no-answer tag added | Wait → WhatsApp → retry task if no reply |
| Lead routing | New lead (ad form, bot, assistant) | Assign an agent by enquiry type and area; create a task |
| Long-term nurture | Warm/cold lead, consented contact | Occasional, useful messages over weeks |
| After a viewing | Viewing done | Feedback question; follow-up task for the agent |
Which ones are switched on is agreed with you at setup. You may not need them all; a lettings-only agency, for example, won't have seller scenarios.
Note
Scenarios run on what the AI voice assistant and Conversation AI write to the CRM: call outcomes, tags, appointments and opportunity stages. When the assistant and bot tag correctly, automations run correctly. See CRM updates after a call.
Reading a scenario
When you open a scenario from Automation → Workflows, the Builder tab lists its steps from top to bottom:
- Trigger: the event that starts the scenario. Here, the
no-answertag being added to a contact. - Wait: the delay before the next step. Here, 3 hours, so a busy contact isn't disturbed.
- Send WhatsApp: a message using an approved template: "We tried to call but couldn't reach you…"
- If / Else: the flow splits. If the contact replied, the scenario ends and the agent carries on in the conversation.
- Add Task: if there's no reply, the agent gets a "call again" task.
Click a step to see its details. Some, like message text and wait time, you can change with care; see Turn on, off and edit.
Heads up
Adding or deleting steps, changing a condition or editing the trigger in the Builder changes the scenario's logic. For these, contact your consultant. If the scenario is published, a saved change applies to real contacts immediately.
Asking for a new scenario
If a flow you need isn't listed, send your consultant:
- When should it start? (e.g. "When an opportunity moves to Offer")
- What should go to whom? (e.g. "A task for the agent, a thank-you message to the buyer")
- When should it stop? (e.g. "When the contact replies or books an appointment")
Example request: "When a contact in the Sellers pipeline moves to Valuation done, send a reminder about the instruction 3 days later and create a task for Burak."
Related articles
Didn't solve your problem?
Ask the assistant or message our support team.