Scheduling and Dispatch

The problem

The schedule lives in one person’s head and a shared Outlook calendar nobody trusts. Two technicians get sent to the same site on Tuesday because the second booking went in by text message. A customer waits at 8am for an engineer whose day actually starts at 9. Somebody asks “who is free Thursday afternoon?” and the answer takes four messages and a guess.

What Solidlio does about it

Every scheduled block is an event with an owner, a type, attendees and a status, linked to the ticket, change, project or client it exists for. A drag-and-drop board puts technicians on rows and hours on columns, so reassigning a job is one gesture and the capacity bar beside each name is drawn to the length of that person’s real working day. Before a booking is made, Solidlio checks whether the people invited are actually free and can propose slots that fit all of them inside your configured business hours and around the holidays you observe. Technician calendars sync bidirectionally with Microsoft 365, in real time via Graph webhooks or on a schedule you choose.

Capabilities

Built for MSPs and their clients

An MSP and its clients are separate accounts. Each side keeps its own calendar; the MSP additionally gets a view across every client it services.

Scheduling into a managed client account is validated against the accounts the MSP actually services: an organization, ticket, project or contact outside that set is rejected, and rejected identically to one that does not exist.

How it works

1. Create the event — title, type, start and end, in the event’s own timezone. The organizer is your session; it is not a field a caller can set.
2. Invite who is needed — staff by name, anyone else by email address, each marked required or optional.
3. Check before you commit — “Check this time” names the invitees who are already booked; “Suggest times” proposes slots that fit everyone inside business hours.
4. Set reminders — one or more lead times, delivered in-app or by email. Invitees are notified the moment they are added.
5. Dispatch it — on the board, drag the block to another technician or another hour. The change saves on drop and the affected attendees are told.
6. Track it through — SCHEDULED → CONFIRMED → IN_PROGRESS → COMPLETED, with CANCELLED and NO_SHOW available throughout. Cancelling notifies everyone on the invite list.
7. Keep Outlook honest — with Microsoft 365 connected, the event flows both ways, and any single event can be pushed on demand.

Security and tenancy

• Visibility is ownership-based, not role-based: you see an event if you organize it, attend it, or it belongs to your account and is not private.
• Every client-supplied link on an event — organization, contact, ticket, change request, project, project task — is resolved inside your tenant before it is persisted. A foreign identifier and a non-existent one produce the same reply, so the API cannot be used to probe another tenant’s ids.
• Free/busy requests silently drop user ids outside your tenant. Colleagues’ event titles are never returned; their time reads as “Busy”.
• The Microsoft 365 OAuth state is signed and expires after 30 minutes, so a callback cannot be replayed or forged against another user’s connection.
• OAuth tokens are stored encrypted.

Editions

Scheduling and Dispatch carries no plan gate. There is no entitlement or tier check anywhere in it; every paying tier gets the full feature. Differences in what a person sees come from portal and role:

Integrations

Microsoft 365 / Outlook Calendar — per-user OAuth (offline_access, Calendars.ReadWrite), bidirectional sync with configurable direction and frequency, Microsoft Graph webhook subscriptions for real-time change notifications, a per-run history showing events created, updated and deleted, and on-demand push of a single event.