Before a customer call or team meeting, people spend ten to twenty minutes digging through mailboxes, folders and old minutes. An assistant already connected to calendar, mail and files can assemble the picture in seconds: who comes, what happened since last time, which documents matter, what is open. For most SMBs this is a feature switch in Microsoft 365 or Google Workspace, not a project.
Problem & value
- Today: scrolling through threads, opening folders, reading old minutes; context is often missed before external meetings.
- AI value: a consistent starting point, fewer forgotten commitments, better questions. Measure the time saved on your own meetings rather than trusting vendor claims.
- Limit: the assistant only sees what the user may see, so colleagues can get different briefs [1]. Meetings without earlier mail, files or notes yield thin output.
Variants
- Built-in button: Copilot in Outlook shows related emails, documents, tasks and a recap of the previous occurrence on the event [1].
- Chat-based: "prepare me for my 14:00 meeting" in Copilot Chat or Gemini; Google describes using Gemini with Drive documents for meeting preparation [2].
- Scheduled flow: a flow builds the brief 15-30 minutes before each meeting and mails it or saves a document (Workspace Studio, Power Automate, n8n) [3].
- Private use: appointments with authorities or doctors; see AUTO-024.
How it works
calendar event (button or trigger)
-> collect: attendees, agenda, previous occurrence
-> retrieve: mail threads, linked files, last minutes, open tasks (user's permissions)
-> LLM summarises: purpose, history, open points, suggested questions
-> brief in the event, by mail or as a document
-> user checks and adds notes
Retrieval must respect permissions; self-built flows must replicate this or they leak content. Nothing is sent to attendees automatically. Out of scope: the meeting itself (SPEECH-001) and scheduling (AGENT-012).
Data preparation
Which data: calendar entries with attendees and agenda, mail threads, earlier minutes, files in SharePoint, OneDrive, Drive or Nextcloud, optional CRM notes.
Typical gaps: meetings without agenda, minutes on personal drives, files spread over many places, and above all over-broad sharing ("anyone in the company") so the assistant surfaces documents a user should never see.
Preparation steps: 1. Review sharing on SharePoint, Teams and Drive sites before activation (half a day to a few days, using built-in sharing reports). 2. Agree meeting hygiene: agenda in the invite, minutes saved in one named place. 3. Archive obsolete folders; label confidential sites (Purview sensitivity labels, Drive labels). 4. For self-built flows: list allowed sources and test with 5-10 real meetings.
Rough share of effort: low, but the permissions clean-up is often underestimated. See GUIDE-003.
Implementation paths
Which path for whom
- SMB - A: built into suites most SMBs already run; standard process, no integration.
- Enterprise - B: CRM and ticket sources plus central governance favour an own flow on EU-region APIs.
- Developer - B: calendar API, mail search and an LLM with structured output on an EU-hosted API.
- Public - C: mail and files are sensitive and procurement favours sovereign hosting; a local model on HW2 suffices.
Path A - Buy (recommended for most SMBs)
- Microsoft 365 Copilot: Outlook "Prepare", Copilot Chat; admins steer meeting insights in the admin center [1]. Check the EU Data Boundary settings.
- Gemini in Google Workspace: Gemini in Gmail only answers about events on the primary calendar [2]; verify the feature in your edition.
- Meeting-assistant tools (Fireflies, Otter) focus on the meeting itself and are US-hosted; check AVV first.
- Licences are per user; check current prices.
Path B - Build on cloud APIs
n8n (self-hostable, EU) or Power Automate with a calendar trigger; EU-hosted models such as Mistral, Azure OpenAI in an EU region or Vertex AI in an EU location; Microsoft Graph or Gmail/Drive APIs with delegated (user) permissions, not admin rights. First flow in one to three days, production-ready in two to four weeks.
Path C - Self-host (open source)
n8n or a small Python service, a local model via Ollama or vLLM (7-30B class, e.g. Mistral Small, Qwen), Nextcloud calendar and files via CalDAV/WebDAV, mail via IMAP. HW1 works for short briefs, HW2 for a team. A few hours per month operations; sensible when mail may not leave the premises and the server also serves other AUTO use cases.
Path D - Custom training
Not needed; a general model with good retrieval is sufficient.
State of the art (2026)
Suite assistants use one permission-aware index across mail, chat, calendar and files; recurring meetings get a recap of the previous occurrence [1]. Agent-style flows trigger before each meeting [3]. Failure modes: missed or outdated context, guesses stated as facts, mixed-up people with the same name, and silent gaps (what was not retrievable is not mentioned).
Shared resources & combinations
Same stack as AUTO-002 (mail catch-up), AUTO-004 (chat catch-up), AUTO-024 (daily planning) and AUTO-028 (absence handover); one licence or one n8n server serves all. Natural chain: AUTO-003 before, SPEECH-001 during and after, AUTO-024 for follow-up tasks; AUTO-022 for a team "meeting coach".
Effort, cost & KPIs
- A: hours to activate, one to three days for permission clean-up and training; cost is licences.
- B: one to three days prototype, two to four weeks production.
- C: three to six days plus server and light operations.
- KPIs: share of meetings with a used brief, self-reported preparation time before/after, usefulness rating, reported errors.
People & change
Involve early: management, IT and IT security (permissions, labels), the DPO and data owners of shared sites (GUIDE-005, GUIDE-007).
Works council: yes in most cases. The BAG holds that objective suitability to monitor is enough under §87(1) no. 6 BetrVG, and assistants like Copilot log use. §90(1) no. 3 requires timely information on AI-supported work processes; §80(3) allows an AI expert. A works agreement (no individual performance evaluation) usually settles it (GUIDE-004). Public bodies involve the Personalrat.
Data protection: attendees' and correspondents' data are processed; AVV (Art. 28 GDPR) and DPO involvement are needed. A DPIA is usually not required for plain preparation, but check if the assistant reaches HR or health mailboxes.
AI literacy: Art. 4 AI Act requires measures that support staff's AI literacy; a one-hour session on what the assistant can see and how to verify summaries is a start (GUIDE-006).
Pilot: 10-20 volunteers (sales, project leads) for four weeks, one AI champion (GUIDE-008, GUIDE-009). Concerns: "will management read my prompts" (define log access), "will it show confidential files" (fix permissions first), "briefs are wrong" (always verify).
Humans in control: the user decides what to use; nothing goes out automatically.
Risks, regulation & compliance
- EU AI Act: minimal risk; Art. 4 literacy support applies; internal briefs do not trigger Art. 50 (GUIDE-014).
- GDPR: mail and calendar are personal data; AVV, EU hosting or EU Data Boundary, delete briefs after the meeting.
- Security: over-sharing is the main risk; prompt injection through incoming mail is another, so keep flows read-only (GUIDE-013).
Getting started
- Run a permissions review on your main sites (GUIDE-003).
- Inform works council and DPO, then activate for a pilot group with a one-page usage rule (GUIDE-004, GUIDE-007).
- Test 10 real meetings and note errors.
- Decide go/no-go on ratings; build an own flow only if the built-in one does not fit (GUIDE-002, GUIDE-009).
Sources
- Microsoft Support - Prepare for your meeting with Copilot - https://support.microsoft.com/en-us/outlook/prepare-for-your-meeting-with-copilot
- Google - Gemini at work: a practical guide - https://workspace.google.com/learning/report/content/geminiatworkapracticalguide
- n8n - Send daily meeting prep briefs from Google Calendar with Gemini and Gmail - https://n8n.io/workflows/17824-send-daily-meeting-prep-briefs-from-google-calendar-with-gemini-and-gmail
- Regulation (EU) 2024/1689 (AI Act) - https://eur-lex.europa.eu/eli/reg/2024/1689/oj