How bookings work — A booking is a row

Everything else here follows from one fact: when somebody books time with you, RowFold writes a row in one of your tables. Not into a separate booking system you later have to reconcile. A row, in a table you can see, with columns you chose. That is why a booking arrives already useful. It is on your scheduler because it has a date. It is in your reports because it is a record. It can trigger an automation, appear in a filtered view, go out in a CSV, or be read through the API — and none of that had to be built for bookings. It works because a booking is not special.