Why one parse beats one event at a time
Most calendar tools assume you're adding a single meeting. An executive assistant's reality is the opposite: a day's worth of requests arrives in one email, and each one is a separate block at a different time, place, and length. Building them one by one means re-reading the same message four times and switching between the inbox and the calendar with every line.
Text to Calendar reads the entire batch at once. Multi-event parsing means a numbered list of three or four requests becomes three or four distinct calendar events in a single pass - the board call, the lunch, and the airport pickup all land separately, with no copy-paste between them.
Built for batch scheduling
The parser finds every date and time in the text and treats each as its own event, so you can paste a forwarded thread, a list of holds, or a quick note from your principal without trimming it down. A lunch with a duration becomes a timed block; a hard start like a board call keeps its exact window; a pickup with a leave-by time becomes an event at the time you actually need to move.
Timezones and recurring blocks
Meeting times stay in the timezone you intend - the parser sets each event's timezone using a standard IANA zone (ctz), so a 9:00 AM ET board call doesn't drift on a traveling executive's calendar. For standing commitments, recurring patterns are supported via RRULE, so a weekly 1:1 or a monthly board prep can repeat instead of being re-entered.
Google, Outlook, or .ics
Every parsed event can go straight to Google Calendar or Outlook, or download as an .ics file you can forward or import onto a shared executive calendar. The Chrome extension's right-click flow works directly inside Gmail and Outlook on the web, and the web app's paste flow is there when you're working from a doc or a notes app.
The first five events are free, so you can run a full morning's inbox through it before deciding.