Service dates
Keep cleaning dates separate from invoice dates
A single invoice can mention the day of a visit, the invoice date and the payment deadline. Those dates do different jobs. Keeping their meaning clear avoids a cluttered schedule.
Assistant inbox workflows are in testing and require a compatible doorledge TestFlight build. They are not yet part of the current App Store release. Provider access and source permissions vary.
Ask for dates with their meaning
Use a message with explicit dates and years. Ask for planned visits, completed work, invoice dates and payment deadlines to be labeled separately. When the year or purpose is unclear, clarify it instead of guessing.
Select and copy this prompt
Collect the explicit cleaning and maintenance dates from these messages and send them to doorledge for review. Keep planned visits, completed service, invoice dates and payment due dates distinct. Ask me about ambiguous dates. Do not infer recurring visits or work hours.
Choose what belongs on the schedule
Open the incoming draft, then Review service dates. Only a planned visit offers the next step to choose the team member and property and add it to Schedule. Nothing is sent to the team member by reviewing a date.
Invoice and payment dates stay with the record. They do not become expenses, hours or visits. These are day-level suggestions, not time-of-day synchronization with Apple or Google Calendar.
Handle a change as a change
A reschedule needs the original appointment identity and the actual source modification time. An assistant must not invent either. Without that evidence, edit the existing visit in Schedule instead of adding a replacement.
Persistent assistants may support monitoring with separate authorization, but doorledge-specific persistent workflows remain unverified. Connecting an assistant does not start monitoring your inbox or calendar. Each proposed change still needs host review.