Case Study

Workiz API Bridge.

How we used Google Apps Script middleware to automate technician follow-ups — this deployment reported a 35% lift in review velocity (example outcome; results vary), with no human intervention.

Start the conversation

01 / Deployment Log: Chimcare

The friction point

The friction point.

Chimcare relies on Workiz to manage thousands of service calls across the Pacific Northwest. While excellent for scheduling, Workiz created a data silo.

Technicians would complete a job, but the "Review Request" process was manual. Techs often forgot to send the link, or sent it hours later when the customer's excitement had faded. This "Lead Leakage" meant hundreds of review opportunities were never captured online.

What the silo cost

Manual follow-ups leak reviews.

✓ Review requests sent manually by technicians

✓ Links sent hours late, or never at all

✓ Hundreds of review opportunities never captured online

02 / System Architecture

The automation bridge

Three steps,
zero humans.

Job Complete

Workiz status change fires the event. The moment a job flips to completed, the bridge wakes up.

Webhook Listener

Google Apps Script middleware catches the payload, filters for high-value service types, and routes it forward.

Trigger SMS

A personalized SMS sequence goes out automatically via Twilio / Email API — triggered the moment the job flips to completed. No tech action required.

03 / The Engineering Fix

middleware/workiz_bridge.gs

We didn't replace Workiz. We bridged it.

We built a middleware layer using Google Apps Script. This script listens for the specific API payload job_status: completed, filters for high-value service types, and immediately triggers a personalized SMS sequence.

Code

The bridge.

function doPost(e) {
  // 1. Parse incoming Webhook from Workiz
  var data = JSON.parse(e.postData.contents);
  if (data.event_type === "job.status.completed") {
    // 2. Extract Customer Data
    var phone = data.payload.customer_phone;
    var techName = data.payload.tech_name;
    // 3. Trigger Review Sequence (automatic)
    sendReviewRequest(phone, techName);
    // 4. Log to BigQuery for Analysis
    logToBigQuery(data.payload);
  }
  return ContentService.createTextOutput("200 OK");
}

04 / Impact Report

Quantitative results

+35%— Review Velocity

0h— Manual Entry Time

100%— Automated coverage of completed jobs

Figures reflect this deployment; individual results vary.

Serverless.
No servers to maintain.

This entire system runs serverlessly on Google Cloud. No server maintenance, and no maintenance fees on the automation itself — the third-party services it connects to (like Twilio) keep their own pricing.

Request Similar Audit ↗

Make the next move yours.

Leaking reviews to
manual follow-ups?

Request a Similar Audit ↗