Tell customers “on the way”, “arrived”, “done”

Each status change on a job sends the text you approved, from your own number.

HumonixACME Field ServicesSample data
Approvals: nothing goes out without a yes. Try Approve or Skip; every decision goes on the ledger. Sample data · ACME Field Services, an invented company.

The problem

Customers call to ask when the technician will arrive, and the office stops what it is doing to find out.

  1. 01

    What starts it

    A job’s status changes: on the way, on site, done, invoiced, rescheduled.

  2. 02Agent

    The approved template is filled in (arrival time, pay link).

  3. 03Agent

    Five checks run first: your switch, the platform switch, your number, the customer’s recorded consent and quiet hours.

  4. 04Agent

    If one fails, it records “would send” with the reason; texts held for quiet hours go at 08:00.

  5. 05Agent

    STOP and START are handled on your number.

  6. 06You

    What a person approves

    An owner approves each template. Then Humonix’s review, your own Twilio number and each customer’s recorded consent; a quality check on Hue’s texts must pass.

Tools it uses

The tool catalog →

What you see in the app

Built in

For the curious: the files that do this, in our codebase. lib/job-texts.js, lib/job-texts-core.js

Accurate to what runs today. Where a step waits for Humonix’s review, it says so; nothing on this page is a customer result.

Work email and website. We read your site (robots.txt first), train Hue on it and run a free audit with three quick wins. No card.