Reads what was asked
A half hour this week, a call with three people, a slot that works from Berlin - it takes the constraint from the message rather than offering the same window to everyone.
GmailGoogle CalendarOutlook Calendar
Use case
Scheduling replies with times that are actually free.
Someone asks when you are free. Faber reads the request, checks the calendars you name, and drafts the reply offering real slots - the answer you would have written after opening your calendar, rather than a link asking them to go and find one.
How it helps
The reply people actually want back.
Checks the real calendars
It looks at the calendars you name, so the times it offers are open on all of them, including the one you keep separately.
Offers times, not a link
The draft is a normal reply with two or three specific slots in it, which is what most people answer immediately.
What happened
You see the slots before they are offered.
After every run, Faber leaves a plain-English record of the request it read and the times it proposed.
What happenedScheduling replies
- Read a request for 30 minutes this week from a customer in Berlin.
- Checked both calendars across the next 5 working days.
- Found 3 slots open in both, inside their working hours.
- Drafted the reply offering all three.
Good fit when
Booking links get ignored. Back and forth costs days.
Scheduling arrives by email rather than through a tool everyone uses.
More than one calendar has to be true at once.
The people you meet are customers, so the reply should read like a person wrote it.
You want to see the times before they are promised to anyone.
Answer scheduling mail without opening your calendar.
Describe which calendars count, how much notice you need, and how the reply should read.