AI Scheduling Assistant in Slack: What to Hand Off Before You Hire One to Run Your Calendar

Hand off the reading and proposing of meeting times first, booking second, and keep the exceptions with a person. The line that matters is the invite that reaches an outsider: let any assistant read and rearrange your own calendar, and keep your approval on anything that emails a client or prospect. Before you hire an executive assistant or a virtual assistant (VA), log your scheduling exceptions for two weeks. If the log is long, hire the person. If it is short, a booking page and an agent in Slack cover most of the job.

You run a 5 to 100 person firm out of Slack and still book your own meetings. You answer "does Thursday work", check the calendar, propose two times, move something, confirm, and do it again an hour later.

Scheduling is five jobs with different risk

A human assistant is good at the last row and acceptable at the rest. A booking tool such as Calendly or Cal.com covers propose and book for people who follow a link. An agent in Slack covers read, propose and book for you, inside the thread where the request came up, and waits for your Approve before anything changes. None of them removes your judgment from the meetings that carry a relationship, a contract or money.

Exceptions are where a person earns the pay

Finding a free slot is the easy part. The failure comes when a tool sees an empty hour and treats it as a good one. Boldly, which sells human executive assistants, argues that a tool can see you are free at 2 PM without knowing that 2 PM is a terrible time to call a client whose contract is hanging by a thread. It says AI tools are still hit or miss on tone and urgency, and that edge cases such as daylight saving changes and travel still need a human. Boldly benefits when you hire a person, so read that as a vendor's view. It also concedes that an AI tool could do the job when your calendar is simple, which tells you where the line is.

Early AI schedulers have been wrong in public. In a Show HN thread for an iOS scheduling assistant called Kali, one commenter asked for a simple lunch appointment and the app added a later event to book it. Another said only one of three suggested events reached his calendar, and not the one he was actually doing. A third noticed the app's own screenshot showed next Thursday's sales meeting on a Tuesday. These are commenters' reports from a launch thread, not a measured error rate, and the app is not the Kipwise agent. They show what a wrong date looks like when nobody checks it before it lands.

A scheduling decision has a fact part (is the time free, which time zone, which day) and a judgment part (is this the right time, for this person, now). Software is fast and cheap at the fact part and uneven at the judgment part. A new human assistant is slower at the fact part and also lacks your judgment for the first months. A person's real value is the judgment part, and it costs accordingly: Gamut, an AI vendor, quotes $75,000 to $150,000 fully loaded for a senior executive assistant in a major metro, against $15 to $200 a month for an individual AI executive assistant plan. Those are vendor figures and they compare a senior full-time hire with a tool, which is the wrong comparison for a founder who needs a few hours of help a week. Gamut's own conclusion is hybrid: let the software take the repeatable work and keep a person for the part that needs discretion and relationships.

So count the judgment part before you hire. For two weeks, write down every meeting you had to move twice, every outsider you had to chase, and every clash where you had to decide whose meeting wins. If that list is long, scheduling is mostly exceptions, and exceptions are the part that tools do worst, so you need a person. If it is short, a booking page and an agent can take the rest and you may not need to hire yet.

A booking page decides who can reach you

A booking page answers one question well: when can this outsider meet me. Google's help page says an appointment schedule does not show times when you are busy, requires a 4-hour minimum lead time by default, collects the booker's first name, last name and email, and cannot be created in the Calendar mobile app. Some features need an eligible Google Workspace or Google One subscription.

What a booking page does not do is judge. It offers every free slot you allowed to anyone who has the link, so if your most important client gets the same 4 PM Friday slot as a stranger who found your link, the tool worked and the outcome is still wrong. Treat the link as an access decision and make it before you automate anything else. Google's page lets you limit the hours, set the minimum lead time, add buffer time between appointments and cap the bookings per day, so set those tightly for the link a stranger gets and keep the roomier hours for a second link that only clients receive.

Another class of tool joins your email thread and negotiates a time with the other side. The maker of one says in a Show HN post for Carrie that he spent too many hours scheduling and following up on people's availabilities, and built an assistant you cc on email to sort out times across time zones. The maker of another says in a Show HN post for LIAM that he missed a meeting, spent most of a day sending about 35 emails, and that the tool sends nothing without approval. Both are launch posts, so they show the pain and the trust condition and say nothing about whether the tools work.

An agent in Slack

The Kipwise agent works in the thread where the request came up. It is not an email-negotiation tool, and you should not buy it as one. What it does, from the product pages:

• On Google Calendar, it reads your own primary calendar with times in your timezone. It can create, move or delete an event on that calendar when you ask. Events have no other attendees unless you explicitly ask it to invite someone, and only then does Google email them an invitation. Every change waits for your Approve.
• On Calendly, it reads your free times, you pick one, and the card says who is booked, when, and that Calendly will email them. It can also list tomorrow's meetings, and a cancel card names the meeting before you approve it.
• On Cal.com, it finds bookings and free times, and books, reschedules or cancels a booking after you approve the change.

Each card can be pressed only by the person who asked, and it expires after 30 minutes. If you deny it or let it expire, nothing runs.

It also has limits. Its documentation does not say it can read other people's calendars, so it cannot compare your free time with a client's. It does not say it can negotiate a time by email with an outsider, so a reply chain that needs three rounds of "how about Wednesday" stays with you, a person or a tool built for that. If you need either, say so before you buy.

Where the hand-off stops: the invite that reaches an outsider

Reading your own calendar harms nobody if the answer is wrong. You notice, you correct, you move on. An invite that reaches a client lands in someone else's inbox with your name on it, and taking it back means sending a second message. So let any assistant read and rearrange your own calendar freely, and keep a named person's approval on anything that emails a client or prospect. That is our recommendation, not a rule from a source, and it holds whether the assistant is a person, a booking tool or an agent.

For a human assistant it means they can see and rearrange your calendar but ask you before sending to a client you have not worked with. For a booking tool it means you decide which people get the link. For the Slack agent it is already built in: the Google Calendar card for an event with a guest says an email invitation goes to that guest, and the Calendly and Cal.com cards say the tool will email the person. You press Approve, and nobody else can.

On Outlook, the agent never invites other people to an event and leaves an event that already has attendees alone, so a guest event there is yours to handle by hand.

One booking, start to finish

Here is one thread, written as a made-up example and not a customer story.

1. You write to the agent in a DM: "what is on my calendar Thursday".
2. It lists your Thursday events from your own Google Calendar, with times in your timezone, and names the source.
3. You write: "book a call with Priya next Tuesday". The agent reads the free times in Calendly and replies with three.
4. You pick 14:30. The agent posts a card: book "Intro call" with Priya Nair on Tuesday at 14:30 in Calendly, and Calendly will email Priya.
5. You press Approve. Only you can. The booking is made.
6. Later you write: "cancel the renewal review". The card names the meeting and the guest before anything is cancelled.

You chose the time, pressed the button, and decided this call deserved that slot. The agent did the lookup and the confirmation.

For a daily agenda, you can ask the agent to run a request on a schedule. Creating the scheduled task needs your approval once, and its later runs do not ask again. A scheduled agenda only reads, so it fits that rule. The agent posts the result in the channel, so ask for it in a direct message if your calendar has titles you do not want a channel to see. That advice is a recommendation, not a documented default.

Read the date and the guest on every card before you press Approve. Daylight saving changes and travel are the two places where Boldly says human oversight is still needed, and the Kali thread shows a date landing on the wrong day. Treat a card you did not read as a booking you did not make.

What it costs

The Kipwise agent costs $10 per user per month, with a minimum of three users. Each user gets $5 of personal credit a month for their own requests, and a shared team credit of $2 per user sits behind it. Installing starts a trial: $2 of credit for 7 days with no card, or $10 for 14 days if you save a card or are on a paid Slack plan. See the pricing page for the current terms. The agent also needs the tools it works through: your own Google account, and a paid Calendly plan if you want Calendly booking. The Calendly page says booking from Slack and meeting automations need a paid Calendly plan, Standard or higher.

The agent takes over the typing and the lookups, which are the cheap hours. A person still owns the exceptions, which are the expensive hours.

Try it for two weeks

Week one: read only. Start with read-only questions about your own calendar, because a wrong answer there costs nothing, while the first booking card tests the one step where a mistake reaches someone else. Ask what is on your calendar tomorrow, whether Thursday afternoon is free, and which two meetings overlap. Count how often the answer matches what you see in the calendar. If it is wrong more than once, stop and find out why before you go further.

Week two: book with approval. Connect Calendly or Cal.com, or use the Google Calendar path, and make three real bookings with colleagues first. Read every card. Note any card that names the wrong person, date or time. Then book with two outsiders you know well, and ask them whether anything looked odd.

Keep the exception log running the whole time, and add the cards you denied and the meetings that still needed a person. If that count is large, your scheduling is mostly exceptions, and a human assistant is the right hire. If it is small, you may not need one yet.

Install the agent from the Google Calendar page, connect your own Google account, and ask "what is on my calendar tomorrow" in a direct message. Do that for a week before you book anything. If you are still weighing a hire after that, read Before you hire a virtual assistant, and look at the same one-hire format for an AI chief of staff and an AI operations manager. For the approval pattern behind the cards, see human approval in AI agent workflows, and for open loops that a meeting leaves behind, see keeping follow-ups from falling through the cracks.