The meeting is not the work. Arranging it is.
The Google Calendar integration for agencies exists because scheduling is the most reliably wasted half-hour in a client week. Three emails to find a slot, a link, a reschedule, and then the meeting itself begins with ten minutes of remembering what happened last time.
What connecting it changes
Google Calendar, once it is connected
A client asks for time and the operator finds a slot that is genuinely free, drafts the invitation, creates the event with a video link on it, and — before it starts — assembles what has happened since the last one. Rescheduling and cancelling are the same shape: prepared, then approved.
Generated from the registry
Everything NeoAI can do with it
This list is not written by hand. It is the same catalogue of typed actions the operator executes through, so it cannot promise more than the product does — reads first, then the writes, each of which waits for a person.
Reads
Run unattended, scoped to what you designated for that client.
- List upcoming meetingsEvents on the connected calendar in a window, filtered to this client.
- Find a free slotThe gaps on the connected calendar in a window, so a meeting lands somewhere real.
Writes
Every one waits for a named person to approve it.
- Create a meeting (with a Meet link)Books the event on the connected calendar, adds a Google Meet room, and invites the agency people named.
- Move or rename a meetingChanges the time, the title or the agenda of an event already on the calendar.
- Cancel a meeting— shown as destructive before you approve itTakes the event off the calendar and notifies everyone invited. There is no undoing it.
What it cannot do
- It reads and writes the calendar the connected account owns. It cannot see a colleague’s private calendar it has not been given.
- Free/busy is read over a window rather than continuously, so a slot booked by somebody else two seconds later is still a clash a human has to resolve.
- Creating, moving and cancelling an event are writes, and every write waits for approval. Cancelling is marked as destructive, which changes how it is shown before you approve it.
- It is not a booking page. If you want clients to self-serve a slot, connect Calendly — that is the other calendar app, and it has its own page on the Connections screen.
What this changes
Three specifics, rather than a feature list
A slot that is actually free
Availability is read from the calendar rather than inferred from a set of working hours somebody typed in once.
A meeting with a link on it
Events are created with a Google Meet link attached, so an invitation is complete when it is sent rather than after a follow-up.
A brief before you walk in
What they asked for, what was promised, what is outstanding and what has moved since the last meeting — assembled from the client record.
Scheduling, without a third tool in the middle
Most scheduling products solve the problem by moving it: the client goes to a page, picks from a grid, and the agency accepts whatever falls out. That works, and it is why Calendly is also a connected app here.
What this does instead is close the loop inside the conversation the client is already in. They asked for time in an email; the reply proposes times that are free, and booking one creates the event. Nobody is sent anywhere.
What happens around a meeting
- Before: a brief from the client record — open questions, promised deliverables, outstanding invoices, the last decision.
- After: a recap that becomes tasks and follow-ups rather than a note you meant to write up.
- Between: reschedules handled as an event to move rather than a thread to renegotiate.
Cancelling is treated as serious
A cancellation is the one calendar action that cannot be quietly undone — the invitation is gone from everybody’s calendar and the notification has already landed. It is flagged as destructive in the registry, which is why the approval screen shows it differently from creating one.
If you run on Outlook or Calendly
Features ask for a calendar and are answered by whichever one this workspace connected. Calendly covers the client-self-serve half and mirrors what has been booked; Google Calendar covers the agency’s own diary. Connecting both is common and they do not fight.
Questions people ask about this
Whose calendar does it read?
The one belonging to the account that went through the consent screen. It lists the calendars that account owns and reads events on them; it does not reach into a colleague’s calendar that has not been shared with it.
Can it book a meeting without asking me?
No. Creating, moving and cancelling events are writes and every write waits for approval. What it does unattended is the reading — finding the slot and preparing the invitation.
Does it double-book?
It reads free/busy over the window it is proposing into, so a slot it offers was free when it looked. Two people booking the same minute is a race no calendar integration can win, and a clash is surfaced rather than silently overwritten.
Do meetings get a video link automatically?
Events it creates carry a Google Meet link. If your agency runs on a different video product, the link goes in the invitation body instead — the event is still yours to edit before it is sent.
Last reviewed on . Something out of date or wrong? Tell us and it gets fixed.
À lire ensuite
Point it at one client and see what it prepares.
Connect a mailbox, designate the contacts for a single client, and read what the operator has drafted by tomorrow morning. Free to start, and nothing leaves without you.