Skip to content

Automation · Customer service and scheduling

Book a meeting with Meet in Google Calendar from your Met's chat

Ask your Met for a meeting with a CRM contact: it checks your Google Calendar, creates the event with Meet after your yes, emails the invite and logs it.

How do I book a Google Calendar meeting with a customer without leaving my AI assistant's chat?

You write to your Met something like "book a call with Laura Gómez on Thursday at ten, with Meet". Your Met finds Laura in Meteor's CRM and takes her email from the record; it lists the events in your Google Calendar for that range so the call does not clash with another meeting; it shows you the title, date, start and end time, guests and whether it has Meet, and waits for your yes. With your confirmation it creates the event, Google emails the invitation to the customer and your Met returns the event link and the Meet link. Then it leaves a note on the customer's record with the date and the link. If the meeting has to move or be cancelled, it does so on the same event and Google notifies the guests.

What starts it

When someone asks for it

It starts when someone on the team asks the Met, from the Meteor chat, for a meeting with a CRM contact. It is not a booking a customer makes over WhatsApp: Meteor Scheduling handles that and it lands on the same calendar by itself, without going through these steps.

A manual task: someone on the team runs it with a button, or asks the Met for it in chat.

Who runs it

Team scheduling Met with Google Calendar

Sales team

This is not a named, seeded Met. It is the Met your team talks to inside Meteor, with the Google Calendar skill turned on and access to the CRM. Its work ends when the meeting is on the calendar with the customer invited and logged on their record, or when it was moved or cancelled with notice.

Run by the scheduling Met

What you need connected

6 steps · 7 tools

The procedure, step by step

Each step shows the tool that runs. They belong to the real connector: if one of them stopped existing, this page would not build.

  1. 1

    Find the customer in the CRM

    Your Met searches by the name, phone or email you gave it. Search returns up to 50 contacts; if two Laura Gómez show up, it asks you which one instead of picking one. Then it opens the record and takes the email for the invitation. If the record has no email, it asks you for it: it does not guess it from the name or the company.

  2. 2

    Look at what is already busy

    Before proposing or accepting a time, your Met lists the calendar events in the range you asked for and answers with the free slots. That way it does not drop a call on top of another meeting. The list brings up to 50 events per page and moves to the next page if the range is long.

  3. 3

    Show the meeting and create it with your yes

    Your Met shows you the title, date, start and end time, guests and whether it has Meet, and waits for your confirmation. With it, it creates the event with the time in ISO 8601 and your time zone; Google emails the invitation to the customer and attaches Meet if you asked for it. Your Met answers with the event link and the Meet link Google returned, never with one it wrote itself.

  4. 4

    Log the meeting on the record

    Once the event exists, your Met adds an internal note on the customer's record with the date, the time and the event link. Whoever opens the conversation later knows there is a meeting coming up without looking into someone else's calendar.

  5. 5

    Move it without duplicating it

    If the customer asks for another time, your Met finds the event in the calendar, shows you which one it is and what will change, and with your yes updates that same event. If only the start changes, it keeps the duration. Google notifies the guests of the change and no second meeting is left behind.

  6. 6

    Cancel it with notice to the guests

    If the meeting falls through, your Met shows you the event and, with your yes, deletes it. Google sends the cancellation to the guests; on a recurring event it deletes only that occurrence. If the calendar does not confirm the result, your Met checks the list before trying again.

Before you start

What you need ready

The Met solves none of these for you. If one is missing, the automation stops there.

The limits

What this automation does NOT solve

Better said here than discovered halfway through the rollout.

FAQ

Questions about this automation

It should not. Its instruction is to show you the title, date, times, guests and whether it has Meet, and wait for your yes before creating, moving or deleting. If a detail is missing, it asks instead of making it up.

On yours if you connected your Google Calendar account; if not, on the team account's. The account's main calendar is used by default; to write to another one, the account has to be able to edit it.

That is what Meteor Scheduling is for: it offers the free slots of your services, creates the booking and, with Google Calendar connected, the event shows up on the calendar without anyone copying it. This procedure is for the meetings your team asks for.

Your Met does not retry blindly. It first lists the events in the range to see whether the meeting was created, because repeating the creation without checking is the most common way to end up with a duplicate meeting.

Keep going

Other automations built on the same tools

Last updated

Want this automation running on your own data?

Create your account: a 7-day trial with US$5 of Energy, no card needed. If you would rather see it with your accounts connected, write to us.