1. Relevant meetings are selected first
Travel Time does not treat every calendar entry the same. It applies tenant defaults, selected calendars, categories and user settings to decide which appointments should affect travel planning.
That keeps internal appointments, private entries and non-relevant calendars separate from the external meetings where travel time matters.
- Per-user calendar selection
- Tenant-wide defaults for category, routing and title templates
- Support for active and blocked users
2. Microsoft 365 changes trigger the sync
Once a tenant is approved, Travel Time uses Microsoft Graph and webhook subscriptions to react to changes. That means no heavy constant polling is needed to keep calendars current.
A catch-up path stays in place as a safety net when a webhook is delayed or a subscription needs renewal, so the system remains practical in real operations.
3. Travel blocks are based on real locations
Travel Time uses routing services to calculate the gap between two appointments and turns that result into travel blocks that appear directly inside the calendar.
That matters most for people who spend the day moving between customers, sites or branches and need the calendar to reflect reality rather than wishful scheduling.
- Separate outbound and return blocks when needed
- Fallback minutes for incomplete location data
- Readable rounded values instead of awkward micro-adjustments
4. Status stays visible
Travel Time is designed to stay understandable in production. Users see account status, auto-sync health and recent runs. Admin views expose tenant state, subscriptions and failure patterns.
That transparency is what turns travel-time automation from a demo into a trustworthy tool.