WORKFLOW DEMOS

See the work, step by step.

Choose an industry and follow one everyday task from the first message to a clear next action. Each video takes 72 seconds.

WORKFLOW DEMOS / 01Real estate

A new buyer. Two viewings. One clear plan.

Follow one buyer’s enquiry through a brief, a shortlist and proposed viewing times—then see the agent review them and the simulated confirmations arrive.

Buyer’s agent · Enquiries & viewings

1 min 12 secEnglish narration & on-screen captionsDownload video

A self-built demonstration using fictional buyers, listings, calendars and preset results. Messages, confirmations and calendar updates are simulated. No live AI, MLS, inbox or booking service is connected.

Read the video transcript

0:00 — A buyer inquiry starts a showing workflow. This fictional, preset demo connects the email, sample listings and calendar.
0:09 — Alex wants at least three bedrooms in Westboro, parking, and a budget ceiling of C$850,000, with showings on Saturday.
0:18 — The request becomes a buyer brief. Property type, move-in timing and must-haves are flagged for the agent to ask.
0:27 — Two fictional listings match the stated requirements. The third is excluded because it exceeds the buyer’s budget.
0:36 — Sample availability suggests two thirty-minute showings, with fifteen minutes between them. The agent still needs to check the route.
0:45 — Jamie checks the listings, times and route, then approves the proposal. This is a simulated review; no messages are sent.
0:54 — Preset buyer and listing-contact replies confirm the demo times. Two sample calendar events and Jamie’s follow-up are created.
1:03 — The agent has a buyer brief, two demo showings and an owned follow-up. Simulated confirmations; no real bookings.

THE JOB BEHIND THE DEMO

The work between a new lead and a Saturday of viewings.

A buyer sends their requirements by email. The agent still needs to check property details, coordinate times, get confirmations and keep the next action visible. This example follows one buyer all the way through.

The buyer’s request

A budget up to C$850,000, at least three bedrooms in Westboro, one parking space and Saturday availability from 2 to 4 pm.

What gets prepared

A buyer brief with missing details flagged, two matching fictional listings, proposed viewing times and a reply for the agent to review.

What the agent controls

The agent checks property facts, travel time and the schedule. Calendar entries are confirmed only after simulated buyer and individual listing-agent replies.

From the example to your own workflow

The sequence below uses the video’s preset results. The exception handling and preparation checklist describe decisions to make before building a live workflow.

How the example moves forward

Keep the enquiry with the brief
Carry the buyer’s budget, area, bedrooms, parking and available times into one record. Keep unanswered questions visible alongside the original request.
Prepare a shortlist and tentative times
The C$825,000 and C$849,000 fictional listings fit the price limit; the C$899,000 listing is excluded. The proposed 15-minute gap between viewings is an assumption for the agent to check.
Review before confirming
The agent reviews the plan. Separate simulated replies from the buyer and each listing side precede confirmed calendar entries; a follow-up task is prepared without inventing buyer feedback.

When something needs attention

Missing details or no suitable property: Ask the buyer to clarify the brief or have the agent review the search. Keep the buyer’s stated requirements unchanged until they agree otherwise.
A time changes or a reply is missing: Keep the affected viewing tentative and route it to the agent. Recheck availability and travel time before seeking a new confirmation.

Before a real rollout

List the inbox, listing source and calendar in use; confirm permitted access and any available export or integration options.
Agree which buyer fields are required and who verifies current property details.
Name the person who approves messages, handles missing replies and confirms appointments.
Prepare anonymized examples of a complete enquiry, missing information and a changed viewing time for a trial.

Does your team coordinate viewings like this?

Bring one example of how an enquiry becomes an appointment today. We can work out which steps are worth improving around your existing tools.

Discuss buyer follow-up Explore real estate enquiry services

WORKFLOW DEMOS / 02Restaurants

One dinner enquiry. A clear next step.

Follow a request for a 24-person team dinner, from the inbox to a clear brief, a reply reviewed by the manager and a follow-up with an owner.

Restaurant manager · Private dining

1 min 12 secEnglish narration & on-screen captionsDownload video

A self-built demonstration using fictional guests, venue notes and preset results. Email, approvals and follow-ups are simulated. No live AI, inbox or booking system is connected.

Read the restaurant video transcript

0:00 — A restaurant manager receives a private-dinner inquiry. This fictional, preset demo follows the workflow from email to a clear follow-up.
0:09 — Alex asks about dinner for 24 guests, with a private room, a C$85 per-person budget, and two vegetarian guests.
0:18 — The email becomes a structured brief, linked to its source so the manager can check the date, budget and guest requirements.
0:27 — The room fits, but availability needs review. Budget scope and end time are missing; vegetarian menu suitability needs kitchen confirmation.
0:36 — The reply draft asks for missing details. Room availability, pricing and menu suitability stay with the restaurant team to confirm.
0:45 — Jamie checks the draft and changes the reminder to 10 AM. Approval is simulated, and no real email is sent.
0:54 — The demo records approval and a simulated send, then assigns Jamie a follow-up. The inquiry remains open, with no booking.
1:03 — The manager has the original inquiry, a checked brief, a reviewed reply and an owned follow-up. Start with one business workflow.

THE JOB BEHIND THE DEMO

The questions behind a private-dining request.

A group-dinner email mixes clear requirements with details still to confirm. This example carries the original request, venue notes, reply draft and next action through one continuous record.

What the guest provides

24 guests on October 16 at 6:30 pm, a C$85-per-person budget, two vegetarian guests and a request for a private room.

What gets prepared

A brief linked to the source email, a capacity check, questions about budget scope and end time, and a reply draft for review.

What the manager controls

Capacity fit does not confirm availability. The manager checks the date, the kitchen reviews dietary needs, and final pricing remains unconfirmed. The record stays “Awaiting guest details · Not booked”.

From the example to your own workflow

The sequence below uses the video’s preset results. The exception handling and preparation checklist describe decisions to make before building a live workflow.

How the example moves forward

Keep the request and open questions together
Record the date, start time, headcount, budget and dietary request with the source email. Flag the missing end time and whether the budget includes drinks, tax and gratuity.
Compare the request with venue notes
The fictional Cedar Room has 28 seats and the example menu starts at C$75 before drinks, tax and gratuity. Those notes help prepare questions; they do not establish availability or a final quote.
Review the reply and assign follow-up
The manager reviews the questions before the simulated send and assigns an owner and follow-up time. The enquiry remains unbooked while guest details and venue checks are outstanding.

When something needs attention

Headcount, date or budget changes: Return the request to the manager for another capacity, availability and pricing check before preparing an updated reply.
Dietary needs or guest details remain unclear: Ask for the missing details and get kitchen confirmation for dietary arrangements. Keep the enquiry pending and give the next action an owner.

Before a real rollout

List where enquiries arrive and where the team records them; confirm available access, exports or integration options.
Gather current room limits, menu and budget terms, and identify who checks date availability and dietary requests.
Agree who approves replies, owns follow-ups and can change an enquiry to a confirmed booking.
Prepare anonymized examples of a complete enquiry, missing budget details and a changed group size for a trial.

Does your team handle group enquiries like this?

Bring one example of how a dinner enquiry moves through your team. We can work out where a focused workflow would help.

Discuss group enquiries Explore restaurant enquiry services