Calendar Sync for Installers

Overview

Installers already run projects in Selora Connect — every job has steps, milestones, and scheduled visits. Today those plans live in one place and the installer’s day planner lives in another: they manually copy appointments into Google Calendar or Outlook, and keep the two in sync by hand. Missed a step? The calendar entry goes stale, the site visit surprises the customer, and the project record no longer matches reality.

Calendar Sync makes the two the same thing. All steps of a project, scheduled maintenance, and site visits are automatically mirrored in the installer’s Google Calendar or Microsoft Outlook. Changes flow both ways: reschedule a visit in Selora Connect and the calendar entry moves; drag the calendar event to a new time and the project updates. No more double-entry, no more stale plans.

Customer value

• One source of truth: The project plan and the day planner can never drift apart — every change is reflected in both immediately.
• No double-entry: Installers stop retyping appointments; a new project step or maintenance window shows up in the calendar automatically.
• Flexibility stays with the installer: Keep using Google or Outlook with the habits they already have, including drag-and-drop rescheduling; Selora picks up the change.
• Reliable customer communication: Visit times the customer sees come from the live project record, so no double-booked surprises.
• Lower administrative load: Site visits, maintenance, and project milestones are all planned, tracked, and visible in the tools the installer already opens all day.

Scope

• Project step sync: Every step and milestone of a project is mirrored as a calendar event with the property, customer, and step details.
• Scheduled maintenance: Recurring maintenance plans produce recurring calendar events; one-off service windows are synced as single events.
• Site visits: Scheduled site visits appear as calendar events with the job context; rescheduling flows both ways.
• Google Calendar integration: Connect via the installer’s Google account through standard OAuth; events are written into a dedicated folder so Selora entries are easy to spot.
• Microsoft Outlook integration: Connect via the installer’s Microsoft account; same event mapping and dedicated folder behavior.
• Conflict handling: When the same time is already occupied, Selora surfaces the conflict and the installer decides (reschedule, keep both, or ignore) — no silent overwrites.

Architecture

1. Calendar account connection: The installer authorizes Selora to read and write a dedicated calendar (Google OAuth / Microsoft Graph), one account per installer; tokens are stored and refreshed by Selora Connect.
2. Event mapping: Project steps, maintenance windows, and site visits are mapped to calendar events with a stable reference back to the source record, so updates and deletions are matched, not duplicated.
3. Sync engine: Changes on either side are detected and reconciled — Selora-side changes push to the calendar, calendar-side changes pull back into the project record.
4. Conflict detection: Overlapping events are detected before applying a change and surfaced to the installer for a decision.
5. Audit trail: Every sync action (what changed, where it came from) is logged per property and per project.

Open questions

• Recurrence rules: How faithfully should complex recurring maintenance schedules (e.g., “2nd and 4th Friday”) be mirrored across calendar providers with different recurrence semantics?
• Multi-calendar support: Should installers be able to sync into more than one calendar, or select a primary calendar per device?
• Shared team calendars: Should a whole team’s calendar be synced, so the office can see everyone’s visits, or is this installer-only at first?