Scheduling workflow notes (detailed)

Scheduling workflow notes

• Overview

  • Sunday morning is the target window for the service job: typically scheduled at 7AM. This appears repeatedly as the standard slot for Sunday service.

  • Customer has already emailed requesting their next available date, so the agent must act on that request rather than asking again.

  • The process involves checking the service calendar, the local van's availability, the technician schedule, and then creating CRM records and calendar invites accordingly.

• Step-by-step workflow

  • Identify target date based on customer request and typical scheduling window

  • Target time: $7\text{AM}$ on Sunday

  • If the weekend is unavailable, note the weekend constraints and save a tentative date for later confirmation (e.g., “the next available Sunday”).

  • Check calendar availability in the Service calendar

  • Open browser session for Service and navigate to the calendar view

  • Access the calendar for the local van (e.g., “Texas” as the local van)

  • Confirm there is no pre-existing schedule for this weekend in the market

  • Review technician availability (e.g., Thomas currently has other jobs scheduled with two vans in use)

  • Create a tentative calendar entry

  • Schedule the tentative job for the next available Sunday (e.g., the 24th)

  • Copy the customer/lead name for the event title (e.g., format title using the customer name) and place it into the calendar event

  • Set up the event details

  • Ensure the event shows the correct local time and time zone for the customer account

  • Add the technician as a guest (e.g., Thomas) and grant him the ability to modify the event

  • Color-code the event (yellow/banana)

  • Ensure the event is saved with the correct duration: 5 hours (from 7AM to 12PM) and correct timezone

  • Update the account state in the CRM

  • Change the account stage to “scheduling penciling in” or similar pre-appointment status

  • Prepare and send the pencil-in email to the customer

  • Use the CRM’s scheduling email template

  • Body should acknowledge the customer’s email and explain we’re checking availability to provide accurate information

  • Calendar and data verification before sending final confirmation

  • Verify the van (Texas local van) and the time window: still showing 7AM–12PM (5 hours total) for the slot on the target Sunday

  • CRM/Salesforce entry for the opportunity and related notes

  • Create a new Opportunity for the account

  • Set the Close Date to the target date

  • Stage: “Confirming with the client”

  • Pre-op notes: include a calendar reference CAL and copy into CRM notes

  • Attach the not-to-exceed estimate

  • Attach the one-time service estimate as part of the email package

• Key concepts and conventions

  • Time and duration: Sunday service target is 7AM; duration is 5 hours; resulting end time is 12PM

  • Time zones: Customer time zone is Central; internal calendar uses Central Time (Chicago)

  • Customer time zone indicator: Central

  • Worldwide calendar default or “CBS” calendar uses Central Time for the nation-wide view

  • Roles and resources

  • Van: Local van (Texas) with no current weekend schedule in this market

  • Technician: Thomas (availability must be checked; two vans are already scheduled)

  • CRM states and workflow stages

  • Pre-app / pre-appointment state: “pre” stage while confirming details

  • Scheduling penciling in: intermediate stage indicating tentative scheduling while awaiting client confirmation

  • Communication conventions

  • Yellow color coding for scheduling notices (banana metaphor)

  • Email templates to preserve a professional tone and maintain accuracy: phrase “to ensure we provide you with accurate availability”

  • Documentation and attachments

  • Not-to-exceed estimate (POU)

  • One-time service estimate

  • Data integrity and consistency

  • Copying the event title/name from the CRM into the calendar to maintain consistency

  • Copying the calendar date into the CRM opportunity notes (cal, calendar, etc.)

  • Contingency and flexibility

  • If weekend confirmation is not obtained, move or adjust the technician assignment (e.g., shift Thomas if needed) and keep the weekend slot on hold until confirmation

  • Practical reminders

  • Keep multiple browser windows tidy; avoid excessive tab-switching during live data entry

  • Verify the correct account (e.g., Waxahachie) and proper market (Texas) before finalizing the event

  • Save milestones at each step to avoid losing progress

• Examples and real-world relevance

  • The sequence demonstrates how a service company coordinates field work using a CRM (Salesforce-style) and a calendar system

  • It shows how to handle customer requests quickly while balancing technician availability and vehicle scheduling

  • It illustrates how to document planning steps (target date, tentative schedule, CRM updates) to improve customer communication and avoid misalignment

• Numerical references and formulas (LaTeX)

  • Target start time: $7\text{\,AM}$

  • Duration: $5\text{\,hours}$

  • End time: $12\text{\,PM}$

  • Dates referenced: $08/24$ (next available Sunday) and the notion of a Sunday window

  • Time zones: $\text{Central}$ (customer) and $\text{Central}$ (calendar in Chicago)

• Ethical, philosophical, and practical implications

  • Ensuring accurate and timely communication respects the customer’s time and reduces back-and-forth

  • Transparency about availability helps manage expectations and maintain trust

  • Professional documentation and proper permissioning (modifying events by attendees) support accountability and clear responsibilities

• Quick-reference checklist (condensed)

  • [ ] Confirm customer’s requested date or next available Sunday

  • [ ] Check local van availability and technician schedule

  • [ ] Create tentative calendar event for the next available Sunday (e.g., 08/24) at 7AM, duration 5 hours

  • [ ] Set time zone to Central for customer and internal calendar

  • [ ] Invite Thomas with modify permissions; color-code event yellow

  • [ ] Update CRM status to Scheduling Penciling In

  • [ ] Create Salesforce Opportunity; set Close Date to 08/24; Stage to Confirming with Client; add pre-op notes

  • [ ] Attach not-to-exceed estimate and one-time service estimate

  • [ ] Send pencil-in email using the appropriate template; include the next available date

  • [ ] Copy calendar link and ensure consistency across records

  • [ ] If no confirmation by weekend, consider relocating technician or rescheduling

  • [ ] Send final customer communication with date, time, and attachments

• Notes on potential ambiguities encountered in transcripts

  • The exact year for the date is not specified; use the nearest upcoming Sunday and confirm the year in your system

  • The transcript references several windows and tabs; in practice, streamline by consolidating into a consistent workflow and documenting where each action is performed

  • The metaphor of “banana” for color-coding helps with quick visual cues but ensure all team members understand the coding convention