Fixed quote after a free call

Property viewing booking and showing feedback, handled automatically

Booking a viewing can take five messages, and getting feedback afterwards can take five more. We build a workflow that offers approved viewing or showing slots, confirms and reminds both sides with access notes, asks every visitor the same short feedback questions afterwards and turns the answers into a weekly update the agent edits before it goes to the seller or landlord. A typical build costs $1,000 to $2,500 and takes about three to four weeks.

The problem

Why viewings and showing feedback eat agent time

Viewings and showings are where agents earn their fee, yet much of the work around them is logistics: agreeing a time with the buyer, the seller or tenant in occupation and the agent, sending the address and access details, reminding everyone and rescheduling when someone cancels.

Feedback is the part most often dropped. Sellers want to know how the weekend went, and the honest answer is spread across texts and calls. Without a consistent showing feedback form, price conversations rest on impressions rather than what buyers actually said.

What we build

What our property viewing booking workflow includes

Self-booking from real slots

Applicants pick from slots the agent and the occupier have approved, synced with the agent's calendar.

Confirmations and access notes

Factual confirmations and reminders for the visitor, the occupier and the agent, including parking and key notes.

Cancel and rebook

One-tap rescheduling that frees the slot and tells everyone affected.

Same feedback questions for everyone

A short feedback form after each visit with the same questions for every visitor, plus a call option.

Weekly vendor or landlord update

Feedback, viewing numbers and portal activity summarised into a draft the agent edits and sends.

Second-viewing alerts

Visitors who ask for a second look or say they want to offer are flagged to the agent at once.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Slot chosen

    An applicant books an approved viewing slot from the reply or listing page.

  2. 02 Automated

    Everyone confirmed

    The visitor, occupier and agent get confirmations and reminders with access notes.

  3. 03 Automated

    Feedback collected

    After the visit the visitor gets the same short feedback questions as everyone else.

  4. 04 Negotiator or PM review

    Agent edits update

    The agent reviews the feedback summary, adds context and sends the vendor update.

  5. 05 Agent or broker decides

    Price and offers

    Advice on price, offers and next steps comes from the agent, not the workflow.

How it behaves

How viewing booking and feedback behave

What each person sees and what runs in the background, including what happens when something goes wrong.

What the applicant sees

  • Approved slots to pick from, with one-tap rebooking
  • A confirmation and reminder with address and access notes
  • A short feedback form after the visit

What agents see

  • Bookings in their calendar with occupier notes
  • Second-viewing and offer interest flagged straight away
  • A draft weekly vendor or landlord update to edit

What the automation does

  • Keeps calendars, occupiers and visitors in sync
  • Asks every visitor the same feedback questions
  • Summarises answers without adding opinions

Edge cases and fallbacks

Occupier cancels at short notice
Visitors are told at once and offered the next approved slots.
Visitor does not turn up
Logged as a no-show and the agent decides whether to rebook.
Feedback contains a complaint about the agent
Sent to the branch manager, not summarised for the seller.
Calendar sync fails
Booking switches to a request form and the agent confirms by hand.

Architecture

Viewing booking and feedback at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Applicant Booking link Agent calendar Approved slots n8n workflow Confirm and remind Feedback form Same questions Feedback summary Draft update Agent Edits and sends
  • Input
  • Logic and services
  • Output
  • AI step
  • People

How it flows

  1. 1 An applicant picks a viewing or showing slot that the agent and occupier approved.
  2. 2 n8n sends confirmations, reminders and access notes to everyone involved and handles rebooking.
  3. 3 After the visit every visitor gets the same short feedback questions.
  4. 4 Answers are summarised into a draft update that the agent edits before it reaches the seller or landlord.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Viewing & showing booking with feedback automation project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    How viewings are booked today, calendars, occupier rules, feedback habits and vendor update format.

  2. 02

    Design

    2 to 3 days

    Slot rules, message wording, feedback questions and the weekly update template.

  3. 03

    Build

    About 1 week

    Booking page, calendar sync, n8n messages, feedback form and summary.

  4. 04

    Shadow run

    About 1 week

    One branch books through the workflow while agents check every message.

  5. 05

    Launch

    1 to 2 days

    Roll out to all listings and walk agents through the vendor update.

  6. 06

    Support

    Ongoing

    Question changes, new branches and monitoring.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Google Calendar or Microsoft 365 calendars Your CRM (Follow Up Boss, Reapit, Street or Alto) Twilio SMS and email A form tool for feedback Claude or OpenAI for feedback summaries

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Slot rules, wording, feedback questions and update template.

    $200 – $400

  • Build

    Booking flow, reminders, feedback form and summary step.

    $500 – $1,300

  • Integrations

    Calendars, CRM and messaging.

    $150 – $400

  • Testing and shadow run

    QA and a branch shadow run.

    $100 – $250

  • Launch and training

    Roll-out and agent walkthrough.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Scheduling, messaging and n8n costs are billed to you directly. If you already use a showing service, we connect to it rather than replace it.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • AI model usage: Billed by the provider per use; summarising short feedback is usually a small monthly amount.

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: same process for every applicant

The Fair Housing Act prohibits discrimination in housing based on race, color, national origin, religion, sex, familial status and disability. Every applicant sees the same slots and questions.

Source: www.hud.gov

UK: keep reminders factual

Viewing confirmations stay purely factual; adding promotions turns them into marketing that needs consent or the soft opt-in under PECR.

Source: www.legislation.gov.uk

EU and UK: minimise visitor data

Visitor names, numbers and feedback are personal data, so the workflow collects only what the booking needs and keeps it with contracted processors.

Source: gdpr-info.eu

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Property viewing and showing feedback questions questions, answered.

Yes, from slots the agent and the occupier approved. Agents can block times, require approval for certain listings or keep some viewings accompanied only.

A few short ones: overall impression, price view, condition, location and whether they want a second viewing. Every visitor gets the same questions, and they can ask for a call instead.

No. The agent sees the summary, adds context and decides what to send and how. Nothing goes to a seller or landlord without the agent editing it.

Not necessarily. If you use a showing service in the US, we connect around it. If you book viewings by phone and calendar today, the workflow becomes your booking tool.

Occupiers get notice of each viewing in line with your tenancy terms and local rules, and can be asked to approve slots before they go live.

Viewings per listing, no-shows, feedback response rate, second viewings and how often sellers get an update each week.

Free 20-minute call

Want this for your estate & letting agent?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call