Key takeaways
- Answer proposed times with one firm choice instead of opening new options.
- The assistant checks your Google Calendar; the other person's availability comes only from what they wrote.
- Creating, updating and responding to events follow the execution mode; deleting always asks.
- The confirmation reply restates the time and time zone and says what the meeting is for.
How do you schedule a meeting from email without the back and forth
Schedule from email without back and forth by answering the proposed times in one reply with a firm choice, instead of offering fresh options. Scheduling threads grow because each reply opens a new question.
Read the thread for every time and constraint the other person gave, such as their time zone or the days they cannot do, and pick one slot that fits. If none does, offer two specific alternatives rather than a vague 'sometime next week'.
How does AI meeting booking find a time
The assistant finds a time by reading the thread for constraints and checking your Google Calendar for a free slot that matches them. Connect Google Calendar in Settings, Connections; it is available on every plan, for every user, alongside your Gmail or Outlook inbox.
It can show a read-only view of your calendar in the chat, so you see the week before choosing. It checks your calendar, not the other person's, which is why reading the thread first matters.
How do you send a calendar invite from the email
Send the invite by asking the assistant to create the event with the people on the thread as guests. Give it a title the guest will recognise in their own calendar, such as both company names and the purpose, and add a line of agenda.
Creating, updating or responding to an event follows the execution mode: Manual asks for approval, Plan queues the action and Auto runs it. Deleting an event always asks, in every mode. If the guest comes back with another time, ask the assistant to update the existing event rather than create a second one.
What should the confirmation reply say
The confirmation reply should restate the time with its time zone, say who will join and say what the meeting will cover. The invite carries the details; the reply handles the human side, such as thanking them for the time and naming anything they should bring.
Ask the assistant to draft it in the same thread. In Gmail and Outlook, drafting needs no approval and sending is the action that follows your execution mode, so in Manual you read it before it goes.
How to book a meeting from an email thread, step by step
Connect your calendar and inbox once; after that each booking is a short chat.
- Connect Google Calendar and your Gmail or Outlook inbox in Settings, Connections.
- Ask the assistant to read the scheduling thread and list the times and constraints the other person gave.
- Ask it to find a free slot in your Google Calendar that fits those constraints.
- Have it create the event with the people on the thread as guests, approving the event if you work in Manual mode.
- Ask for a short confirmation reply in the same thread, check the draft and send it.
Where Pebbles Ai fits
- FoundationIntegrationsWith Google Calendar connected, on every plan, the assistants list events, find a free slot, create events with guests, update them and respond to invitations, each following your execution mode; deleting always asks.
- CapabilitySmartboxWrite or refine the confirmation with Write with AI in Smartbox, which works from the thread, the recipients and your brand voice.
Common questions
Which calendar does the assistant use?
Google Calendar. Your email can be in Gmail or Outlook, but the calendar the assistants check and write to is Google Calendar.
Can the assistant see the other person's calendar?
No. It checks your own Google Calendar and reads what the other person wrote in the thread.
When is a booking link better?
When the other person has not suggested any times yet. Once they have, booking from the thread saves them choosing again.
About this page. Written by the Pebbles Ai team for people who run sales, marketing and growth. Last updated .
