Product · Booking receipts
Proof behind every booking
A booking receipt is the record Notaray will leave for every finished booking attempt: what was asked, what was checked, what the calendar returned and what the outcome was. So when someone asks “did that really get booked?”, the answer is on the receipt, not in someone’s memory.
- RequestedEstimate on Wednesday at 9:00 AM
- Calendar checkedSlot free at 9:12:02 AM
- WrittenEvent evt_7c21 created at 9:12:03 AM
- Read backEvent found, details match, 9:12:04 AM
- Caller toldConfirmed after the read-back
Nothing changes this record later; corrections add a new line.
Estimate, Wed 9:00 AM
evt_7c21Copy event ID
Read back after the write
Caller (510) •••-0333
Rules behind every receipt
Notaray is built so that every finished booking attempt leaves a receipt.
Notaray is built to confirm a booking after the calendar shows it, not before.
Notaray is built so that a retried request returns the original outcome instead of booking twice.
Everything on the record
- The request as it was understood
- The consent and business rules that applied
- The calendar that was checked and what it showed
- The write that was attempted and what the calendar returned
- The read-back and whether it matched
- Timestamps with the time zone
- Any human step that followed
A sample receipt
The third panel shows a sample receipt. The rest of the picture shows where it sits in the flow.
What the caller heard
“I’ve asked for Tuesday at 2:30 PM. I’ll confirm as soon as the calendar shows it.”
Requested
What the calendar shows
Tuesday
- 1:00 PM
- 2:30 PMService visit
- 4:00 PM
Verified in calendar
The receipt
- Requested
- Service visit, Tuesday 2:30 PM
- Calendar checked
- The slot was free
- Written
- Event ID returned by the calendar
- Read back
- Matches the request
Confirmed
Owner, if pending
Shown when the calendar does not confirm the booking.
- Owner
- Front desk
- Deadline
- Today, 4:00 PM
- Original request
- Service visit, Tuesday 2:30 PM
Needs follow-up
A record to check, not a celebration
A receipt is an audit record. It will say Confirmed when the calendar returned an identifier and the read-back matched, and not before. A reply from a server isn’t enough.
If verification isn’t available, the receipt will say so plainly instead of faking success.
What would you want to check?
Design partners tell us which facts belong on a receipt before they’d rely on it. Spots are limited.