Skip to main content
Menu

Notaray · Early access opening

Missed 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. No fake “you’re booked.”

Request early accessHow it works

The booking engine is in testing now. Phone answering is on the way. Partner spots are limited.

Inbound request

Requested

“Can I get Tuesday at 2:30 PM for a service visit?”

Booking check

  1. Calendar checkedThe slot was free
  2. Booking writtenThe calendar returned an event ID
  3. Read backMatches the request
ResultConfirmed
Tue 2:30 PM · Service visitVerified in calendar
Illustrative workflow

What a real booking looks like

Follow one request from the caller to your calendar. A suggested slot is not a booking, so the caller hears “confirmed” once the calendar shows it, not a second before.

  1. What the caller heard

    “I’ve asked for Tuesday at 2:30 PM. I’ll confirm as soon as the calendar shows it.”

    Requested

  2. What the calendar shows

    Tuesday

    • 1:00 PM
    • 2:30 PMService visit
    • 4:00 PM

    Verified in calendar

  3. 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

  4. 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

Illustrative workflow

The booking that never landed

A missed call is a job that goes to the next business on the list. A polite answer isn’t much better if nothing gets saved: a transcript, a callback note or a confident “you’re booked” while the calendar stays empty.

Notaray is built to close the gap between what was said and what was saved. This describes the problem. It is not a measured rate.

What was said

“You’re all set for Tuesday at 2:30.”

Sounds booked

What was saved

No event found

Not booked

Illustrative workflow

From request to booked in three steps

  1. Catch the request

    The time, the service and every detail needed to act, captured under your business’s own rules.

  2. Check the real calendar

    Look at the actual calendar, make one bounded booking attempt and verify what came back. A suggested slot is not a confirmed booking.

  3. Confirm or hand off

    Confirmed once the calendar holds it. If it can’t be verified, it’s marked pending and goes to a person with the details. An unknown result never sounds like a success.

A sneak peek at the workspace

Four screens from the workspace on the way, with sample data: what needs a person, every booking and its status, the receipt behind each confirmation, and the follow-ups your team owns.

Notaray workspaceSample data
Search bookings

Overview

Updated 9:41 AM

Needs a person

2

Oldest due 4:00 PM

Verified this week

18

Each with a receipt

Waiting for read-back

1

Waiting for the read-back

Needs a personView all

  • Service visit, Tue 2:30 PMSlot taken before the writeNeeds a person
    Front deskDue today 4:00 PM
  • Estimate, next weekAsked to talk to a personNeeds a person
    OwnerDue tomorrow 10:00 AM

Recently verifiedView all

  • Estimate, Wed 9:00 AMRead back after the write
  • Repair visit, Thu 11:30 AMEvent matches the calendar
Illustrative workflow

Why Notaray

Answering the phone is easy. Landing the booking is the job.

Explicit checks, retry control and an honest handoff, built into one booking flow. That’s a design goal, not a performance guarantee.

The rules behind every confirmation

  • Notaray is built to confirm a booking after the calendar shows it, not before.

  • Notaray is built so that an uncertain result goes to a named person with a deadline.

  • Notaray is built so that every finished booking attempt leaves a receipt.

Tested on our own bookings

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.

Spots are limited. The businesses that join now decide which calendars and workflows get validated.

  1. Our own operationsStarting with Agnotiq’s own bookings.
  2. A few design partnersReal workflows and real calendars.
  3. Wider launchOnce both hold up.

Sound like you?

You run a service business on an appointment calendar, and requests slip away when the team is busy or the doors are closed. Tell us how bookings reach you, where your real calendar lives and what happens when a request falls through.

Design partners shape the limited pilot. It’s not a sign-up for a released product, and a pilot place isn’t guaranteed, so apply early.

Straight answers

Does it answer calls yet?

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.

Which calendars will it work with?

No integration is announced yet. Design partners help choose and validate the initial calendar, so tell us which one runs your day.

What if a booking fails?

That’s the rule: nobody hears “confirmed” unless the calendar shows it. An uncertain result goes to a named person with the context to follow up.

How much will it cost?

We plan to charge for verified bookings, not minutes. Prices are not set.

Can I try it?

Design partners get in early. We’re opening a limited number of spots to walk through your booking workflow with us. A pilot place isn’t guaranteed.

Get in early. Spots are limited.

Tell us where requests arrive and where bookings need to land. We’ll take it from there.

Request early access