User Guide: Appointment Status Automation
Last updated: January 15, 2026
Overview
The Appointment Status Automation feature triggers automated actions when inspection appointment statuses change. This enables real-time notifications, record updates, and workflow progression without manual intervention.
Key Capabilities
- Automatic Notifications - Send emails when appointments are scheduled, completed, or cancelled
- Record Updates - Update permit records based on inspection outcomes
- Workflow Triggers - Advance permit status based on inspection results
- Integration Actions - Trigger external system updates
Understanding Appointment Status Changes
Standard Appointment Statuses
| Status | Meaning | Triggers When |
|---|---|---|
| Scheduled | Inspection is booked | Citizen or staff books appointment |
| Confirmed | Inspector confirmed | Inspector acknowledges assignment |
| In Progress | Inspector en route/on site | Inspector starts inspection |
| Completed | Inspection finished | Inspector submits results |
| Passed | Inspection approved | Inspector marks as passed |
| Failed | Inspection not approved | Inspector marks as failed |
| Requires Reinspection | Follow-up needed | Inspector requests re-inspection |
| Cancelled | Appointment cancelled | Citizen or staff cancels |
| Rescheduled | Time changed | Appointment moved to new slot |
| No Show | Citizen not present | Inspector marks no show |
Status Flow
| Step | Status | Possible Transitions |
|---|---|---|
| 1 | Scheduled | → Confirmed, → Cancelled |
| 2 | Confirmed | → In Progress, → Cancelled |
| 3 | In Progress | → Completed |
| 4 | Completed | → Passed, → Failed, → Requires Reinspection |
Configuring Status Automations
For Administrators
Navigate to: Automation Builder → Create New Automation
Step 1: Select Trigger
- Choose "Appointment Status Change" trigger
- Select which calendar/inspection type to monitor
- Define the specific status change to trigger on
Trigger Configuration:
| Field | Value |
|---|---|
| When | Appointment Status Changes |
| Calendar | Building Inspections |
| From Status | Any (or specific status) |
| To Status | Completed |
Step 2: Add Conditions (Optional)
Filter which appointments trigger the automation:
Example Conditions:
- Inspection Type = "Foundation Inspection"
- Priority = "Normal" (exclude emergency)
- Inspector = Specific inspector
- Time = Within business hours
Step 3: Define Actions
Add one or more actions to execute:
Available Action Types:
| Action | Description |
|---|---|
| Send Email | Send notification to applicant, staff, or inspector |
| Update Record | Change permit field values |
| Change Status | Update permit workflow status |
| Create Task | Generate follow-up task |
| Wait | Delay next action by specified time |
| Webhook | Call external API |
Common Automation Examples
Example 1: Inspection Scheduled Confirmation
Trigger: Appointment Status → Scheduled
Actions:
- Send email to applicant with:
- Inspection type
- Scheduled date and time
- Property address
- Inspector name
- Preparation instructions
- Cancellation/reschedule policy
Example 2: Inspection Passed - Update Permit
Trigger: Appointment Status → Passed
Actions:
-
Update permit record:
- Set "[Inspection Type] Complete" = Yes
- Update "Last Inspection Date" = Today
- Update "Inspection Status" = Passed
-
If all required inspections passed:
- Change permit status to "Ready for Final Review"
-
Send email to applicant:
"Great news! Your [Inspection Type] inspection passed. Next steps: [instructions]"
Example 3: Inspection Failed - Request Corrections
Trigger: Appointment Status → Failed
Actions:
-
Update permit record:
- Set "Inspection Status" = Failed
- Add "Correction Required" flag
-
Create task for permit reviewer:
- "Review failed inspection for [Permit Number]"
- Assign to department supervisor
-
Send email to applicant:
"Your [Inspection Type] inspection was not approved. Please review the inspector's comments and schedule a re-inspection after corrections are made."
-
Attach inspector notes and photos to permit record
Example 4: Reminder Before Inspection
Trigger: Scheduled → (Wait until 24 hours before appointment)
Actions:
- Send reminder email:
"Reminder: Your [Inspection Type] inspection is tomorrow at [Time]."
Example 5: No Show Follow-up
Trigger: Appointment Status → No Show
Actions:
-
Send email to applicant:
"Our inspector arrived but was unable to perform the scheduled inspection. Please reschedule at your earliest convenience."
-
Update permit record:
- Add "No Show" flag
- Increment "No Show Count"
-
If No Show Count > 2:
- Notify supervisor
- Add permit to review queue
Viewing Active Automations
Automation List
Navigate to: Automation Builder → Automations
View all active appointment status automations:
- Automation name
- Trigger description
- Status (Active/Inactive)
- Last triggered
- Run count
Testing Automations
Before activating:
- Set automation to Test Mode
- Trigger a test appointment status change
- Review the Run History to verify actions
- Check that notifications were sent correctly
- Verify record updates were applied
- Activate for production use
For Staff: Understanding Automated Actions
Recognizing Automated Updates
When viewing permit records, you may see:
- Status changes with "System" as the modifier
- Notes added with "Automation" tag
- Timestamps indicating automated actions
Manual Override
If automation produces incorrect results:
- Document the issue
- Make manual corrections to the record
- Report to administrator for automation adjustment
- Automation will continue for future appointments
For Citizens: What Happens Automatically
Notifications You May Receive
Based on your inspection appointments:
| Event | You May Receive |
|---|---|
| Inspection Scheduled | Email confirmation |
| 24 Hours Before | Reminder email |
| Inspection Complete | Result notification |
| Inspection Passed | Next steps email |
| Inspection Failed | Correction requirements |
| Appointment Cancelled | Cancellation confirmation |
Opting Out of Notifications
To manage your notification preferences:
- Log in to the Citizen Portal
- Go to Profile → Notification Preferences
- Toggle email preferences
- Save changes
Note: Some critical notifications may always be sent for compliance.
Troubleshooting
For Administrators
Q: Automation didn't trigger when status changed. A: Check:
- Automation is set to "Active"
- Trigger conditions match the status change
- No condition filters excluded this appointment
- Review Run History for errors
Q: Notifications are being sent to wrong recipients. A: Verify:
- Email/phone fields in the action configuration
- Applicant contact information in the permit
- Dynamic field references are correct
Q: Record wasn't updated as expected. A: Check:
- Field names match exactly
- User has permission for the update
- Record wasn't locked
- Field type compatibility
For Staff
Q: I see a status change I didn't make. Was it automated? A: Yes, check the activity log for "System" as the modifier, indicating an automated action.
Q: Can I prevent automation from running for a specific appointment? A: Contact your administrator. Specific exclusions can be added to automation conditions.
Best Practices
For Administrators
- Test thoroughly - Use test mode before production
- Clear naming - Name automations descriptively
- Document logic - Add descriptions explaining the automation purpose
- Monitor performance - Review run history regularly
- Handle failures - Include error handling and notifications
Notification Guidelines
- Don't over-notify - Consolidate where possible
- Clear messaging - Use plain language in notifications
- Actionable content - Tell recipients what to do next
- Timing matters - Send reminders at appropriate intervals
Related Features
- Automated Reminders & Confirmations - Notification details
- Inspection Result Recording - How results are submitted
- Permit Record Locking - Post-inspection locking
Technical Notes
Trigger Configuration:
- New field added for automation triggers on appointment status
- Configurable per calendar and status combination
- Supports complex conditions with AND/OR logic
Action Execution:
- Actions execute asynchronously
- Failures logged with retry capability
- Webhook actions support POST/PUT methods
Component Location:
- Automation Builder:
/apps/automation-builder-app/ - Trigger configuration: Workflow schema includes appointment triggers
For additional assistance, contact your System Administrator.