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 booking to check

Search

Search pages, clients and actions

Cedar Point · Lead S.P. · Yesterday 7:12 PM

Booking check
What the booking system's own record says
Needs a check

Fynso · where it stands

The booking system didn't answer in time. The agent didn't tell the lead they were booked; Fynso checks the booking system before anything else happens.

Request
One booking request, sent once
Answer
No answer in 30 seconds
Marked booked
No. Only once the booking system's record confirms it
Retried
Fynso doesn't retry a booking it can't see
Not in this case
Listed so the case never looks more complete than it is
  • The booking system's error details beyond the timeout
  • 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?
    Text replyThe lead chose Saturday at 9:00 AMTue, Oct 27, 7:11 PM
  2. Who acted?
    Cedar Point's local agentRunning under Luis Romero's authority since Aug 18
  3. Why was it allowed?
    Booking tours is on at Cedar PointConsent to tour texts recorded on the form, wording v1Consent wording v1
  4. What did it know?
    Cedar Point's calendar, 1 minute oldSaturday 9:00 AM was open
  5. What did it propose?
    Tour on Saturday at 9:00 AMOne booking request, sent once
  6. What happened?
    No answer in 30 secondsThe request may or may not have been saved. The agent told the lead it was confirming the time.Tue, Oct 27, 7:12 PM
  7. What changed?
    Not known yetFynso doesn't retry a booking it can't see
  8. What happened next?
    Check the booking systemRead the calendar back before booking again or texting