FACILITATOR EMAIL KIT · T-3 / T-1 / T+1
Facilitator email kit
three moments, ready to send
Three emails for the three moments around the workshop: T-3 days, T-1 day, and T+1 day. Subject line, body, attachments, and To/Cc/Bcc — ready to copy-paste.
3 emails
Copy-paste ready
No individual names
§1 How to use this
A workshop runs better when three quick emails set the tone — before, just-before, and after. This page holds those three emails as ready-to-send templates addressed to the executive group. Recipients, dates, venues, and follow-ups are shown as {{ }} placeholders; swap them in your mailer after pasting.
- Timing: T-3 → set expectations + ask for prep · T-1 → final reminder + checklist · T+1 → thanks + follow-up resources.
- How to paste: Copy the "Subject" line into the subject field and the "Body" block into the body. Line breaks survive both Gmail and Outlook.
- Variables:
{{ WORKSHOP_DATE }}/{{ START_TIME }}/{{ VENUE }}/{{ ANSWER_TO_Q1 }}/{{ NEXT_PILOT_DATE }}/{{ FACILITATOR_NAME }}/{{ URL_BASE }}— seven placeholders total. Full table in §5.
Privacy policy: The bodies contain no individual names. Salutations use generic forms ("Team", "Executive team"). If you personalize for a single recipient, add only their name — never list other executives' names.
§2 T-3 days · expectations email
Sets expectations and asks for three pieces of prep (laptop, plan, Wi-Fi) in the opening note. Frame it as "so the 90 minutes can run at full density" — not as homework.
Team,
This is {{ FACILITATOR_NAME }}. A quick note ahead of the MIXI Executive Claude Workshop (90 min), scheduled for {{ WORKSHOP_DATE }} at {{ START_TIME }}.
The workshop has a single goal:
After 90 minutes, you should be able to run the three latest Claude products — Code Desktop / Design / Cowork — on your own laptop the next morning.
To make that possible, three small items of prep, please:
1. Install Claude Desktop (instructions at {{ URL_BASE }} — takes about 10 minutes).
2. Sign in to the Claude Max plan (needed for Opus 4.7 and the 1M context).
3. Confirm you can connect to the venue Wi-Fi ({{ VENUE }} Wi-Fi details will be on the reception desk on the day).
Three optional 10-minute reads that meaningfully deepen the session if you have the time:
• Overview: {{ URL_BASE }}/index.html
• Code Desktop deep dive: {{ URL_BASE }}/deep-code.html
• API key hygiene guide: {{ URL_BASE }}/deep-api-keys.html
If anything is unclear, please reply to this email — happy to handle pre-workshop questions here.
See you on the day.
Best,
{{ FACILITATOR_NAME }}
MIXI Executive Workshop Facilitator
§3 T-1 day · final reminder
The evening-before reminder so nobody is scrambling in the morning. Five things to have done 15 minutes before start. Light tone.
Team,
Looking forward to the MIXI Executive Claude Workshop tomorrow.
• Date/time: {{ WORKSHOP_DATE }} — {{ START_TIME }} start (90 min)
• Location: {{ VENUE }}
Five quick checks, please, ideally 15 minutes before the start:
1. Laptop fully charged (the room has power, but just in case).
2. Claude Desktop already launched and signed in.
3. Connected to the venue Wi-Fi, with a working connection confirmed.
4. Notifications off (Slack / email / personal apps — we'll want focus).
5. Notepad ready — paper or digital, for catching anything you want to come back to.
During the session, "obvious" or "basic" questions are actively welcome. Interrupt freely. The goal of the 90 minutes is to experience the tools, not to listen to a presentation.
On the day, I'll share these URLs live:
• Driver View (live dashboard): {{ URL_BASE }}/driver.html
• AI Executive spec: {{ URL_BASE }}/deep-ai-executive.html
• 14-Day Learning Path: {{ URL_BASE }}/learning-path.html
See you tomorrow.
{{ FACILITATOR_NAME }}
§4 T+1 day · thank-you + follow-up
Sent the morning after. Thanks, answers to the Q&A topics you didn't fully close in the room, next steps (14-Day Path, Cowork pilot), and a feedback survey link.
Team,
Thank you for joining the MIXI Executive Claude Workshop yesterday despite busy schedules. Hopefully the 90 minutes gave you enough hands-on time with the latest Claude products to reproduce what we did on your own.
A quick recap and the next steps below.
■ Three products we covered (one-line reminder + deep-dive URL)
• Claude Code Desktop — a dev environment where you build business tools in natural language.
Deep dive: {{ URL_BASE }}/deep-code.html
• Claude Design — a Research Preview that generates pitch decks and one-pagers through conversation.
Deep dive: {{ URL_BASE }}/deep-design.html
• Claude Cowork — a desktop agent that completes multi-step knowledge work autonomously.
Deep dive: {{ URL_BASE }}/deep-cowork.html
■ Follow-up to Q&A topics from the room
Q1: {{ ANSWER_TO_Q1 }}
Q2: {{ ANSWER_TO_Q2 }}
Q3: {{ ANSWER_TO_Q3 }}
(Filling in here the points I couldn't fully address live, plus what I dug up afterwards.)
■ Next steps
1. 14-Day Learning Path — 30 minutes a day × 14 days, designed to get an executive to the "I can modify this myself" level. You can start today.
{{ URL_BASE }}/learning-path.html
2. Cowork pilot proposal — the plan is a 30-day pilot with 5 people from Corporate Strategy. A full proposal will be in your inbox by {{ NEXT_PILOT_DATE }}.
3. Three deep-dive courses — pick based on your interest area.
• Beginner (1 hour): {{ URL_BASE }}/course-beginner.html
• Intermediate (2 hours): {{ URL_BASE }}/course-intermediate.html
• Advanced (half day): {{ URL_BASE }}/course-advanced.html
■ Feedback request
To make the next round better, please take 5 minutes to fill out the survey:
{{ URL_BASE }}/feedback-survey.html
■ Office hours
If anything in your own work made you think "I wonder if Claude could do this" — reply to this email anytime. Happy to run a 30-minute online sparring session to explore it.
Thanks again for yesterday.
Best regards,
{{ FACILITATOR_NAME }}
MIXI Executive Workshop Facilitator
§5 Variable substitution list
Before sending, replace every {{ }} in the body according to the table. Seven placeholders total.
| Variable | Meaning | Example |
|---|---|---|
{{ WORKSHOP_DATE }} | Workshop date | 2026-05-12 |
{{ START_TIME }} | Start time | 14:00 |
{{ VENUE }} | Venue | HQ 8F executive meeting room |
{{ ANSWER_TO_Q1 }} | T+1 email — fill in per question (Q2/Q3 too) | Fill in individually |
{{ NEXT_PILOT_DATE }} | Next pilot proposal date | 2026-05-26 |
{{ FACILITATOR_NAME }} | Sender | Facilitator to fill |
{{ URL_BASE }} | Site URL | https://mixi-exec-ai-workshop.mocco.team |
§6 Pre-send checklist
Copy-pasting saves time. Visual proofing before send isn't optional — especially the "no individual names" line, which is a workshop-wide privacy policy.
- To / Cc / Bcc are correct
- No individual names in the body — use generic forms ("Team", "Executive team")
- Attachment filenames don't contain sensitive info
- URLs point at production (not a preview / staging domain)
- Signature has the right organization and role
- Cc / Bcc split matches intent (Corp strategy is typically Bcc, not Cc)
Last verified: 2026-04-23
Related:
- Facilitator script — full 90-min run-of-show
- Feedback survey — link goes in the T+1 email
- 14-Day Learning Path — recommended in the T+1 email