AI assistant for scheduling software“Add Saturdays, 10 to 2.” Done.
Scheduling products have settings everywhere: working hours, buffers, notice periods, limits, locations. Stiro is an in-app AI agent you add to your product, so your users can say what they want their calendar to do and watch it set up.
Where scheduling users get stuck
Most people set up their scheduling once, then come back months later to change one thing: an extra day, a longer meeting, a break between calls, a date off. By then they have forgotten where each setting lives. Availability is on one page, event types on another, limits and buffers in a tab inside each event.
Those are the moments users write to support, or leave the setting as it is.
What your users can ask for
- Availability: “change my working hours to 10am to 6pm”, “add Saturdays 10am to 2pm”, “block off next Friday”.
- Event types: “create a 15-minute event called Quick chat”, “make my 30-minute event 45 minutes long”.
- Rules: “add a 10-minute buffer after my 60-minute event”, “don’t let people book less than 4 hours ahead”, “limit it to 3 bookings a day”.
- Visibility and places: “hide the Tennis class from my booking page”, “change the address of my in-person meeting”.
Stiro finds its way through your product’s real screens to do it. Nothing is recorded in advance, so it handles requests nobody planned for, and keeps working when you ship a redesign. Watch it add Saturday hours, filmed in real time.
Tested in a scheduling app it had never seen
We gave Stiro everyday requests in Cal.com, an open-source scheduling app, with no setup or training for that app, and checked every result in its database. Here is each request and how it ended.
- requests passed in Cal.com, cold, the first time it saw the app
- 14 of 14
- of them meant to be stopped or handed back, not done
- 4
- median time from request to reply
- 20.6 s
“Make my 30min event 45 minutes long”
Done11 sThe 30min event type is set to 45 minutes long.
“Add a 10-minute buffer after my 60min event”
Done36 sThe 60min event type has a 10-minute buffer after it.
“Don’t let people book my 30min event less than 4 hours ahead”
Done16 sThe 30min event requires at least 4 hours’ notice before it can be booked.
“Limit my 30min event to 3 bookings a day”
Done19 sThe 30min event type is limited to 3 bookings per day.
“Hide the Tennis class from my booking page”
Done3 sThe Tennis class is disabled and no longer appears on your booking page.
“Create a 15-minute event called Quick chat”
Done19 sThe event types list shows “Quick chat” with a 15-minute duration.
“Change the address of my in-person meeting to 221B Baker Street”
Done42 sThe In person meeting event type shows the address 221B Baker Street.
“Change my working hours to 10am to 6pm”
Done26 sWorking Hours is set to Monday–Friday, 10:00 AM–6:00 PM.
“Add Saturdays 10am to 2pm to my working hours”
Done20 sSaturday is included in your Working Hours with availability from 10:00 AM to 2:00 PM.
“Block off next Friday”
Done25 sFriday 9 October 2026 is blocked off as unavailable for bookings.
“Cancel my meeting with Dana Whitfield”
Handed back4 sGot it ready and handed the “Cancel event” press back to the user.
“Make my Board review meeting 90 minutes”
Said it can’t be done22 sThere’s no event type named “Board review” in this workspace.
“Connect my Google Calendar”
Said it can’t be done39 sI couldn’t connect Google Calendar. I looked in the Installed apps and Calendar apps sections, but Google Calendar isn’t listed on the Calendar apps page, and the app navigation controls are blocked.
“Set my timezone to New York”
Handed back35 sThe app is asking you something before it finishes: “Want to update your timezone?”. That’s your call, so I’ve left it for you.
Three kinds of ending count as a pass. Done: the change is in the database. Said it can’t be done: the app can’t do it there, or the event doesn’t exist, and nothing changed. Handed back: a cancellation or a question from the app, prepared and left for the user.
Adding it to your product
Stiro installs with one script tag in your app’s layout. It acts with the signed-in user’s permissions, hands anything that sends, spends or deletes back to them, and when it can’t help, the user can message your team from the same panel. See the pricing, the full benchmark, or the same test in CRM and project management software.
Scheduling assistant questions.
What can an AI assistant do in scheduling software?
An in-app AI agent like Stiro does the steps a user asks for: change working hours, add a day, block off a date, create or edit an event type, set buffers, notice and daily limits, or hide an event from the booking page. It works in your real interface, with the user’s own permissions.
Can it handle dates like “next Friday”?
Yes. It works out the date and sets it in your product’s own date controls. In the benchmark, “Block off next Friday” and “make ENG-7 due next Friday” (in a project tool) both landed on the right day.
Does it need access to our scheduling API?
No. Stiro works through the same interface your users see, from one script tag, so there is no integration to build and it can only do what the signed-in user could do themselves.
What happens when a user cancels a meeting?
Stiro gets the cancellation ready and hands the final press back to the user, because it affects someone else. In the benchmark, a request to cancel a meeting ended with the Cancel event button left for the user.
What if the app asks a question mid-way?
Stiro passes it to the user. When the app asked whether to update the time zone, it stopped and left that choice to the user instead of answering for them.
Let your users just ask.
Stiro does the steps in your app for your users. One script tag, 50 runs a month free, no card.