Reliability contract
Eight rules every confirmation must pass
The reliability contract is the eight rules every Notaray confirmation has to pass, so “confirmed” means the calendar really holds it. They are design rules, not measured results, and no reliability figures are published yet.
- Request understoodTime, service and details captured
- Calendar checkedThe real calendar, not a guess
- One booking writtenA single bounded attempt
- Read backCompared with the request
When the calendar shows it.
A named person, with a deadline.
The eight rules
Confirm after the calendar shows it
Notaray is built to confirm a booking after the calendar shows it, not before.
Retry without booking twice
Notaray is built so that a retried request returns the original outcome instead of booking twice.
Availability is not a reservation
A write conflict is a normal branch: offer another slot or hand the request to a person, instead of hiding it as an error.
Leave a receipt
Notaray is built so that every finished booking attempt leaves a receipt.
Unknown means owned
Notaray is built so that an uncertain result goes to a named person with a deadline.
Report every outcome
Every finished attempt, confirmed or not, sends a signed notice, so your other systems hear the same result the calendar holds.
Count the cost per outcome
What each attempt costs gets recorded, and cost is reported per verified booking, not per minute.
Channels cannot bypass the rules
Voice and phone go through the same booking rules as every other channel, with no path from audio straight to a calendar write.
Figures, when they’re real
Nothing on this page is a measurement. Notaray isn’t live yet, so there are no results to report.
No reliability figures are published yet. When there is evidence, this page will show the count and the period each figure covers.
Which rule matters most to you?
Design partners help us rank what a confirmation has to guarantee for a business like theirs.