What Calendar isn't
Google Calendar is brilliant at one thing: putting time blocks on a grid with people invited. For meetings, that's exactly what you need.
For dispatch, the model starts to fail in small ways. There's no concept of a customer (just an invitee). There's no driver (just a calendar). There's no queue (just a "no time" feeling). There's no workload bar (just a wall of blocks).
Most small crews start in Calendar and stay there too long. The signals it doesn't fit are subtle: scrolling through a month to find Mrs Verlinden's last visit, copy-pasting addresses into events, sending SMS reminders by hand, asking "wait, where am I sending Tom Tuesday?".
When those frictions add up, the answer isn't a better Google Calendar setup. The answer is a tool that models the actual nouns: drivers, customers, appointments, queue.
Where Calendar wins
If you're solo and your scheduling is straightforward (1-2 visits a day, no recurring rounds, no SMS needed, no team), Google Calendar is free, fast, and works fine. There's nothing wrong with it for that shape.
It also wins for anything that's actually a meeting. Calendar invites, conference rooms, Zoom links, accept/decline flows. Jasning doesn't try to compete there.
Where Jasning wins
Three things, all small individually, all expensive in aggregate.
Customer memory. A customer in Jasning has an address, a phone, notes, key-codes, and a history. You enter that data once. Calendar makes you enter the same address into every event.
Workload at a glance. Open the dispatch board and you see the day for the whole crew in one screen, with workload bars per person. Calendar shows you one person's day at a time.
A queue. Unplanned requests sit in a list and wait. Calendar has no place to put "someone called, we should fit them in somewhere". You end up tracking these in WhatsApp or Notes app.
Plus the AI: ask Claude to plan the day, find a slot, reschedule the storm, or report workload. Calendar's AI story exists but isn't built around dispatch.
Migration path
If you're already in Calendar, your data is portable. Customers come over via CSV (or the Jasning import). Recurring appointments rebuild from your existing recurring events. You keep using Calendar for meetings; you move dispatch to Jasning.
A common pattern: 30 days of side-by-side, then drop the Calendar entries that were really dispatch and keep the ones that were really meetings.