Forwarded emails to Robin: what works and what doesn't
The NestBoard team · 2026-05-17
The ones that worked
Robin handles straightforward appointment confirmations beautifully. A dental reminder with "Tuesday, March 12 at 2:30 PM" becomes a calendar event in seconds. Same with restaurant reservations—OpenTable confirmations include the date, time, and location in a predictable format, and Robin pulls those details cleanly.
School announcements work well. Forward an email about an early dismissal day and Robin catches the date and creates "School early dismissal - 12:30 PM" without being asked, pulling the date and the dismissal time out of the announcement text.
Youth sports schedules work when they're formatted as lists. A league schedule in bullet points becomes six separate events with opponents and field locations, and an unresolved phrase like "rain date TBD" is left in the event's description rather than turned into a date of its own.
Doctor's office reminders are a solid yes. Those auto-generated "You have an upcoming appointment with Dr. Chen" emails have consistent structure, and Robin reads them the same way every time.
The ones that still need help
Conversational emails are Robin's weak spot. When a friend writes "Let's do coffee next Thursday if that works?" there's no confirmed plan yet. NestBoard will usually read that as a plan and put it on the calendar anyway. This is the case to watch: check the confirmation email that comes back and delete anything that was only a maybe.
Embedded images with schedule information don't work. If a swim team coach screenshots a meet schedule and pastes it into an email, Robin can't read it. The information lives in the image, not the text. You'll need to manually add those, or ask the sender for a text version.
Long newsletters with multiple events scattered throughout are hit or miss. Robin might catch the first date it sees, but a PTA digest with twelve upcoming dates buried in paragraphs isn't something it can reliably parse. Too much noise, not enough signal.
Anything that requires interpretation of house rules or family preferences won't work yet. An email that says "parent volunteers needed for the field trip" isn't an event for your calendar unless you've signed up for a specific slot.
Why it matters which emails work
We're not trying to make Robin read everything. Some messages are better left as messages—things to discuss, not things to auto-schedule. The goal is to catch the stuff that's already decided and formatted clearly enough that a machine can be confident it's reading correctly.
When we built forwarding, we looked at what Robin actually reads (and what it never will) and applied the same principles. Clear structure wins. Ambiguity needs a human.
If you forward something and Robin misses it, that's useful feedback. We're learning which formats matter most to families, and where the gaps are.