Why one razčleni beats one dogodek at čas
Most koledar orodja assume vi're adding single srečanje. vodstveni asistent's reality is opposite: dan's worth od requests arrives v one e-pošta, v each one is separate block at different čas, place, v length. Building them one z one means re-reading same message four časi v switching between inbox v koledar z every line.
Text to Calendar reads entire batch at once. Multi-dogodek razčlenjevanje means numbered list od three ali four requests becomes three ali four distinct koledarske dogodke v single pass - board call, lunch, v airport pickup all land separately, z ne kopiraj-prilepi between them.
Built za batch scheduling
Parser finds every datum v čas v besedilo v treats each as its own dogodek, so vi can prilepi forwarded thread, list od holds, ali hitro note iz vaš principal without trimming to down. lunch z duration becomes timed block; hard start like board call keeps its exact window; pickup z leave-z čas becomes dogodek at čas vi actually need v move.
Timezones v ponavljajoči blocks
Srečanje časi stay v timezone vi intend - parser sets each dogodek's timezone uporaba standard IANA zone (ctz), so 9:00 AM ET board call doesn't drift na traveling vodstveni's koledar. za standing commitments, ponavljajoči patterns are supported via RRULE, so tedensko 1:1 ali mesečne board prep can repeat instead od being re-entered.
Google, Outlook, ali .ics
Every parsed dogodek can go straight v Google Calendar ali Outlook, ali prenesi as .ics datoteka vi can forward ali uvoz onto deljen vodstveni koledar. Chrome razširitev's kliknite z desno tipko flow deluje directly inside Gmail v Outlook na splet, v splet aplikacija's prilepi flow is there when vi're working iz doc ali notes aplikacija.
Prvi five dogodki are brezplačne, so vi can run full morning's inbox through to before deciding.