Notaray · AI booking front doorEarly accessMissed calls are lost jobs. Not for long.
Notaray is the AI front door for service businesses, and it's almost here. It will pick up the requests your team can't, check your real calendar and confirm the booking once the calendar shows it. Anything uncertain goes straight to a named person with a deadline.
Early access is opening for design partners. Spots are limited, and a pilot place isn't guaranteed.
In development: the booking engine is in testing now, and phone answering is on the way.
Built by Agnotiq. Made for small service businesses in the United States and Canada that run on an appointment calendar: home services, clinics and wellness, salons and spas, and professional services. Notaray is the name of Agnotiq's AI front door for service businesses, in development in Toronto; it is not a notary, a notarization service or a document-signing tool.
We're putting Notaray through its paces on Agnotiq's own operations before we ask anyone to rely on it. Next up: a small group of outside design partners, on real workflows and real calendars.
Read the announcement: Notaray is opening early access: bookings your calendar confirmsFour parts of a booking you can check.
Receipts and the callback queue belong to the booking engine, in testing now. Phone and voice are on the way, and no integration is announced yet. Each is described the way notaray.com describes it, including what isn't built yet.
Booking receipts
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.
Explore booking receiptsCallback queue
Where every request Notaray can't confirm will land, with a named owner, a deadline and the original request.
Explore the callback queuePhone and voice
On the way. Browser voice comes next, then a limited phone pilot for missed, overflow and after-hours calls, subject to testing. None of it takes live calls today.
See where phone and voice standIntegrations
No integration is announced yet. Notaray will write each booking to a real destination calendar and read it back before confirming.
See where integrations standFour steps, no guessing.
Every request runs through four steps: understand it, check the real calendar, write the booking and read it back. The caller hears "confirmed" once your calendar shows the booking.
Understand the request
Capture the requested time, the service and the details needed to act, under the business's own rules.
Check the calendar
Look at the real destination calendar before promising anything. A suggested slot is not a reservation.
Write one booking
One bounded attempt with a stable key, so a repeated request finds the original result instead of booking twice.
Read it back
Ask the calendar what it now holds and compare it with the request. That comparison alone decides the outcome.
Confirmed
The calendar returned an identifier and the read-back matched the request. That's the moment the caller hears "confirmed", not a second earlier.
Pending
The result couldn't be verified. The request goes to a named person with a deadline and the original context, and the caller hears that it was requested.
Built so you stay in control.
The reliability contract: eight rules every Notaray confirmation has to pass. They are design rules, not measured results, and no reliability figures are published yet.
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.
“Answering the phone is easy. Landing the booking is the job.”
What it is built never to do.
These lines are design rules Notaray is being built to. It isn't live yet, so none of them is a measured result.
Never say "confirmed" before the calendar shows it
Notaray is built to confirm a booking after the calendar shows it, not before.
Never let an unknown result sound like a success
Notaray is built so that an uncertain result goes to a named person with a deadline.
Never book the same request twice
Notaray is built so that a retried request returns the original outcome instead of booking twice.
Never let a channel bypass the booking rules
Voice and phone will run on the same booking rules as every other channel. There's no path from audio straight to a calendar write.
What's next, in order.
Notaray doesn't take calls yet. There's no number to try today, but design partners get an early look.
The booking engine
Requests, calendar checks, read-back, receipts and follow-up.
Browser voice
A voice in front of the same booking rules, subject to testing.
A limited phone pilot
Overflow, missed and after-hours calls, subject to testing and to a review of call-recording consent where the pilot runs.
Who it is for.
Small service businesses that run on an appointment calendar and lose requests when the team is busy or closed.
Book the next job while you're on this one
Notaray will turn a homeowner's request for a visit into a booking on the right calendar, or into a follow-up a named person owns.
Home services on notaray.comDon't lose the after-hours appointment request
Notaray will turn an after-hours appointment request into a booking on the right practitioner's calendar, or into a follow-up a named person owns.
Clinics and wellness on notaray.comBook the next client while you're with this one
Notaray will turn a service request that arrives while the stylist is with a client into a booking on the right calendar, or into a follow-up a named person owns.
Salons and spas on notaray.comLand the consultation on the right calendar
Notaray will turn a consultation request into a booking on a specific person's calendar, or into a follow-up a named person owns.
Professional services on notaray.comPay for bookings, not minutes.
Notaray has no price yet. The plan is to charge for verified bookings, not minutes on the phone. Prices are not set, and no plan or trial goes up until the team knows what a verified booking costs to deliver.
What design partners get
Design partners are the service businesses that get in early and shape Notaray before launch. You tell the team how requests reach you and where bookings must land; your answers steer what ships.
- A say in how Notaray works for businesses like yours
- A direct line to the team building it
- An early look at workflow samples and test results
- A shot at a place in the limited external pilot
Early access is opening for design partners. Spots are limited, and a pilot place isn't guaranteed.
What the team needs from you
- 01A short call about how requests reach you today
- 02Which system holds your real calendar
- 03What happens now when a request can't be completed
- 04Honest feedback on workflow samples
The fine print. It's not a purchase, a trial or a commitment. Applying doesn't reserve a pilot place, and one isn't guaranteed. Nothing is live yet: no customers, no supported integrations, no price.
Guides from the Notaray team.
Each guide opens with a short answer, then gives the reasoning and the sources behind it. Written for owners and office managers in the United States and Canada.
How to tell whether an AI receptionist actually booked the appointment
A booking is real when the calendar shows it and the caller got the details. How to check an AI receptionist yourself, and what to make a vendor show you.
Read on notaray.com (opens in a new tab)The eight-scenario booking reliability test to run before you buy any AI phone agent
Eight test calls that show whether an AI phone agent books reliably: a taken slot, a calendar failure, a repeated request and more.
Read on notaray.com (opens in a new tab)Missed calls without lost customers: owning every callback with a deadline
A missed call becomes lost work when nobody owns the callback. How to give every missed or uncertain request an owner, a deadline and the details to act.
Read on notaray.com (opens in a new tab)Call recording consent for service businesses in the US and Canada
When a service business can record a call, AI-answered or not, in the US and Canada: one-party vs all-party consent and a safe default. Not legal advice.
Read on notaray.com (opens in a new tab)AI disclosure rules for phone agents in the US: what to tell callers
What to tell callers when an AI phone agent answers: the FCC ruling on AI voices, California's bot disclosure law and the FTC on AI claims. Not legal advice.
Read on notaray.com (opens in a new tab)When Google's AI calls your business: answering agentic callers about price and availability
Google Search can now place AI calls to local businesses about price and availability. What it means for you, where the settings live and how to handle it.
Read on notaray.com (opens in a new tab)Notaray questions, answered.
Notaray is an AI front door for service businesses, and it's almost here. It will pick up the requests your team can't, check the real calendar, save the booking, read it back and confirm once the calendar shows it.
Not yet. Notaray is in development at Agnotiq. The booking engine is in testing now, and early access is opening for design partners.
Small service businesses in the United States and Canada that run on an appointment calendar and lose requests when the team is busy or closed.
Not yet, and it's on the way. The booking engine is in testing now. Browser voice comes next, then overflow, missed and after-hours phone coverage, subject to testing. Design partners get an early look.
No integration is announced yet. Design partners help choose and validate the initial calendar, so tell the team which one runs your day.
That's the rule: nobody hears "confirmed" unless the calendar shows it. An uncertain result goes to a named person with a deadline and the context to follow up.
Answering is one job. Notaray is built around the other one: a booking that actually lands and can be checked. That's a design goal, not a performance guarantee.
The plan is to charge for verified bookings, not minutes. Prices are not set.
Design partners get in early. A limited number of spots are opening to walk through your booking workflow with the team. A pilot place isn't guaranteed.
The Notaray site is already in English, French and Spanish. Which languages the voice agent will speak on calls isn't announced yet and is subject to testing.
Notaray doesn't take calls yet, so it records nothing. No phone pilot starts without a review of recording-consent rules where it runs.
Get in early. Spots are limited.
Tell the Notaray team where requests arrive and where bookings need to land. They take it from there.
MarginTideWhat you chargeKnow every price. Protect every margin.
A sister product
LumtryWhat you give backRefunds decided by policy. Exceptions decided by you.
A sister productNotaray runs on the same patterns we build for clients: evals, guardrails and a person on every call that matters. A two-week Discovery scopes yours and ends with a fixed quote.
Book a fit call