We're launching AI agents for business operations, with a developer API. Read the announcement
All templates
For air duct cleaning companies, field service dispatchers & HVAC and IAQ crews

Confirm tomorrow's duct cleaning appointments before your crew rolls out

Every evening, WebRun opens Workiz, pulls every job scheduled for tomorrow, drafts a confirmation text for each customer through Twilio asking them to confirm or reschedule, and cross-checks each technician's Google Calendar to flag any double-booked or unconfirmed slot before your team starts the day.

  • No credit card
  • Under $0.01 per run
  • Cancel anytime
14,115 templates Safe automation No code
Every evening at 5:00 PM WebRun
1 Workiz pull tomorrow's scheduled jobs
2 Twilio draft the confirmation text per customer
3 Google Calendar flag any scheduling conflicts
Run a sample
Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.workiz.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Workiz - pull tomorrow's scheduled jobs
    workiz.com How to Automate Workiz
    WebRun in Workiz: pull tomorrow's scheduled jobs
    WebRun opens Workiz to pull tomorrow's scheduled jobs.
    • Open Workiz and filter jobs scheduled for tomorrow
    • Capture the customer name, phone number, appointment window, and assigned technician for each
    • Note any job still marked unconfirmed from a prior day

    Done when Every job scheduled for tomorrow is listed with its customer and technician details.

  3. 2
    Twilio - draft the confirmation text per customer
    twilio.com How to Automate Twilio
    WebRun in Twilio: draft the confirmation text per customer
    WebRun opens Twilio to draft the confirmation text per customer.
    • Draft a confirmation text for each customer naming their appointment window and assigned technician
    • Ask the customer to reply to confirm or request a reschedule
    • Leave every message as an unsent draft for the office to release

    Done when A confirmation text draft exists for every job scheduled tomorrow.

  4. 3
    Google Calendar - flag any scheduling conflicts
    calendar.google.com How to Automate Google Calendar
    WebRun in Google Calendar: flag any scheduling conflicts
    WebRun opens Google Calendar to flag any scheduling conflicts.
    • Open each technician's Google Calendar for tomorrow
    • Check for any overlapping appointment windows or a technician booked past a reasonable end of day
    • Flag any conflict directly on the confirmation batch for the office to resolve before texts go out

    Done when Every technician's calendar for tomorrow has been checked, with conflicts flagged if found.

How do I confirm tomorrow's duct cleaning appointments and catch scheduling conflicts?

Every evening, WebRun opens Workiz to pull every job scheduled for tomorrow and drafts a confirmation text for each customer through Twilio, asking them to confirm or reschedule. It also checks each technician's Google Calendar for overlapping bookings and flags any conflict, so your office starts the morning with a clean, confirmed schedule instead of surprises.

  • Customers get a confirmation text drafted the night before, not a rushed morning call
  • Calendar conflicts are caught before the crew leaves instead of at the customer's door
  • Office keeps full control since every text is released, not sent, by a human

Built for air duct cleaning companies · field service dispatchers · HVAC and IAQ crews · residential service schedulers

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.workiz.com
ScheduleRuns automatically on this cadence
Every evening at 5:00 PM
DeliveryHow each run's result reaches you
Confirmation batch · Google Calendar flags
OutputWhat each run produces - A confirmation text draft per scheduled job and a flagged list of any calendar conflicts for tomorrow's crew.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it text customers without the office releasing the message first?

No. Every confirmation is drafted in Twilio and left unsent. Your office reviews the batch and releases each text, so no customer hears from WebRun directly.

What happens if two jobs overlap on the same technician's calendar?

WebRun flags the conflict directly on the confirmation batch so your office can resolve the scheduling clash before any confirmation text goes out.

Does it check every technician or just one crew?

It checks every technician's Google Calendar for tomorrow, so conflicts are caught across your whole crew, not just a single truck.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.