Fynso
  • Start here
  • Overview
  • Network
    8
  • Marketing
  • Coaching
  • Financials
  • Brand
  • Trust
  • Connections
  • People & access
  • Settings

See it on your business

We'll map brand controls, owner approvals and results across your network.

  1. Trust
  3. Action case

A tour booked at Fairview

Search

Search pages, clients and actions

Open Fairview

Fairview · Lead T.W. · Mon, Oct 26 7:05 PM

Readback
What the booking system's own record says
Confirmed

Fynso · where it stands

The agent booked a Saturday tour, and the booking system's own record confirmed it before the lead got a confirmation.

Booking
FV-48213
Read back
Mon, Oct 26, 7:05 PM
Confirmation
Texted to the lead after the readback
Not in this case
Listed so the case never looks more complete than it is
  • Nothing Fynso recorded for this case is missing.
  • What staff do directly in the booking system, outside Fynso, isn't visible to Fynso.
What happened
Eight questions, each answered from a record rather than from what the agent said
  1. What triggered it?
    Web inquiryFairview's tour form, Oct 26 at 7:01 PMMon, Oct 26, 7:01 PM
  2. Who acted?
    Fairview's local agentRunning under Kevin Shah's authority since Sep 15
  3. Why was it allowed?
    Booking tours is on at FairviewConsent to tour texts recorded on the form, wording v1Consent wording v1
  4. What did it know?
    Fairview's calendar, 2 minutes oldFree first tour v2; Fairview's own hoursFree first tour v2
  5. What did it propose?
    Tour on Saturday at 10:00 AMThe lead picked it from three open times
  6. What happened?
    Booking createdThe booking system returned booking FV-48213FV-48213Mon, Oct 26, 7:04 PM
  7. What changed?
    One tour on Fairview's calendarSaturday 10:00 AM, with a coach
  8. What happened next?
    Confirmed by readbackFynso read the booking back, then texted the confirmation at 7:05 PMMon, Oct 26, 7:05 PM