As of 13 August 2026, AI can only partly book meetings from email requests.

What to actually do

1. Use a tool built for this

   The route this page recommends

2. Hand it to a person

   Second choice

   A person who owns the outcome does this end to end, worth it when the failure is dear.

3. Do it yourself

   The distant third

   A chat interface, power-user skill, and roughly 30 minutes until you can act on the result.

   How to actually do it

   1. 1. Open your organisation's mailbox and calendar settings, then confirm which email account, calendar, time zone, working hours and booking permissions the agent may use.
   2. 2. Open Botpress and create an agent with access to the relevant email and calendar integrations, granting the minimum permissions needed to read requests, check availability and create events.
   3. 3. Paste the prompt into the agent and replace each bracketed rule with your actual working hours, default duration, approval requirements and meeting-link rules.
   4. 4. Send the agent a representative meeting-request email, or allow it to read a small approved folder, and compare its extracted attendees, times, duration and purpose with the original message.
   5. 5. Test an ambiguous request and a conflicting request, checking that the agent asks a question instead of selecting a time or changing an existing event.
   6. 6. Approve one clear proposed booking, then compare the sent reply and created calendar event with the original email before allowing the agent to process further requests.

   Prompt

   You are an email-to-calendar meeting assistant for a UK workplace. Read only the meeting-request emails supplied through the connected mailbox, and use the connected calendar only after the required permissions have been granted.
   
   For each request:
   1. Extract the purpose, attendees, organiser, requested duration, proposed times, time zone, meeting location or link requirement, and any deadline.
   2. Treat the sender's wording as the source of truth. Do not invent attendees, availability, durations, links, locations or time zones.
   3. Check the calendar for conflicts and identify working hours, existing commitments and any stated scheduling rules below.
   4. If one option is clearly agreed, conflict-free and within the rules, prepare the reply and event details.
   5. If anything is ambiguous, conflicting, outside the rules or requires choosing between reasonable options, do not book it. Ask a concise question listing the missing decision.
   6. Do not cancel, move or overwrite an existing event. Do not send confidential email content to people who were not already included.
   7. Before sending an external reply or creating the event, show me the proposed attendees, subject, date, time, time zone, duration, location or link, and reply text for approval. After approval, send the reply and create the calendar event.
   
   Scheduling rules:
   - Working days and hours: [insert rules]
   - Time zone: [insert time zone]
   - Default meeting duration: [insert duration, or say none]
   - People who may approve bookings: [insert names or roles]
   - Whether external replies need approval: [yes or no]
   - Meeting-link and location rules: [insert rules]
   
   For every completed booking, report the email used, the event details, the attendees and any assumption that was explicitly confirmed. Never claim that a booking was sent or created unless the connected system confirms it.

   Open it prefilled in ChatGPT or Claude, or copy it into Gemini, which takes no prefill link.