1. Trigger: the workflow starts the moment a job event is created in Google Calendar. New events only — editing an event never re-dispatches it. 2. The full event details are pulled and structured for assignment. The service address, service type and customer contact are read straight from the event description. 3. First run only: the agent creates its own "Cleaning — Cleaner CRM" spreadsheet in your Google Drive — a Teams roster and an Assignments log, seeded with sample data — and reuses it from then on. 4. Cleaner availability, skills, service areas and existing assignments are read from that spreadsheet. 5. Cleaners are filtered by hard rules: available status, availability window, service area, skills (when the booking names a service type), and no clash with existing assignments. Among everyone who fits, the least-loaded cleaner gets the job — so work rotates fairly. 6. Condition check ("Cleaner Found?"): If True: The assignment is logged as pending_cleaner_confirmation. The cleaner gets an email asking them to accept or decline — a real conversation, with automatic follow-ups if they stay silent (up to 3, roughly every 12 hours). Accept → the log flips to confirmed. Decline or no answer → the log flips to declined / no_response and your manager gets an email with the reason. If False: Your manager gets one email with the job and every cleaner listed next to the reason they were skipped.