Home-services contractors

Every visit confirmed before the truck rolls.

Each customer on tomorrow's schedule gets a confirmation text, requests to reschedule or cancel go straight to your dispatcher, and the unconfirmed list is ready before the morning huddle.

One-time build
$1,500
Live in
3 weeks*
Your time
About 3 hours
After launch
We keep it running
Runs on FlowRunner
$45/month**

* The timeline may need to be adjusted depending on the requirements we receive.

** FlowRunner pricing varies with the volume of calls and messages.

What you get

  • Tomorrow, confirmed today

    Every customer on tomorrow's schedule gets a confirmation text in the afternoon.

  • Reschedules go to dispatch

    Requests to move or cancel reach your dispatcher with the job attached.

  • Gate codes and dogs noted

    Access notes from replies ride along with the job.

  • A morning nudge

    Customers who have not confirmed get a second text the day of the visit.

  • The unconfirmed list

    Dispatch gets it before the morning huddle, not after the truck rolls.

  • Tested before launch

    We run it on a real day's schedule and walk your dispatchers through it.

How it runs

One real example, start to finish.

  • Runs on its own
  • A person on your team decides
  1. Tomorrow's visits pulled

    In the afternoon, tomorrow's appointments come from your field-service system.

  2. Customers confirm

    Each customer gets a text with the window and replies to confirm.

  3. Notes reach the tech

    Gate codes and notes go to dispatch with the job.

  4. Dispatcher moves it

    A person decidesA reschedule request goes to your dispatcher, who replies with the new window.

  5. Stragglers called

    A person decidesAt your cutoff, your CSR calls anyone still unconfirmed.

What changes for your team

Your CSRs stop spending the afternoon calling through tomorrow's schedule to confirm.

They call only the customers who did not answer a text, and by then the list is short.

Your dispatcher stops learning about a reschedule when the tech is already in the driveway. Requests arrive the day before with the job attached, and the dispatcher makes the call they are best at: where that job fits on the board. Techs get gate codes and access notes before they arrive. On a full day, the same dispatch team keeps more of the schedule intact, because the changes surface while there is still time to act on them. Fewer wasted trips means more billable visits per truck.

You stay in charge.

The routine runs on its own. At these moments it stops, asks a person, and waits for the answer.

  • A customer asks to reschedule or cancel.

    Slack message or text to your dispatcher, who replies with the new window or confirms the cancellation

  • A customer's reply changes the job, such as a second problem or something that sounds like an emergency.

    Phone call to your dispatcher, with the customer's message in a follow-up text

  • An appointment is still unconfirmed at the morning cutoff you set.

    Text to your CSR, who calls the customer before the tech heads out

You set the rules, and can change them any time

  • When the confirmation goes out, and when the morning reminder and the cutoff happen.
  • The wording of each text, by visit type.
  • Which job types get a confirmation, such as skipping same-day emergency calls.
  • Who handles reschedules on which days, and by Slack or text.
  • What in a reply counts as a change to the job that needs a call.
  • Who calls unconfirmed customers in the morning.

Your part is small.

3 hours

of your team's time

3 weeks*

to live

* The timeline may need to be adjusted depending on the requirements we receive.

We build, connect, and testMidnight Flow
Field-service loginOwner, 30 min Week 1, day 1
Phone system loginOwner or office manager, 15 min Week 1, day 1
Accounts setup callOwner, 30 min Week 1, day 1
Confirmation wordingDispatcher or office manager, 30 min Week 1, day 3
Reschedule contactsDispatcher, 15 min Week 1, day 3
Test run reviewOwner or dispatcher, 1 hour Week 3, day 15

Project start

Monday, November 2

Going live

Monday, November 23*

An estimate, if we start next Monday.

Want to start Monday, November 2?

Book a call
What can move the date
  • Business texting registration for your number, if it is not registered yet.
  • Customer phone numbers that are missing or out of date in your field-service system.
  • Your team's time to review the test run and approve go-live.

Works with what you already use

  • ServiceTitan, Housecall Pro, or Jobber

    Knows tomorrow's schedule, each job, and the customer's mobile number.

  • Text messages and phone calls (Twilio)

    Sends the confirmations, hears every reply, and calls your dispatcher when a reply changes the job.

  • RingCentral

    Sends the texts from your RingCentral business number, if that is the number your customers know.

  • Slack

    Gives dispatch the reschedule requests and the unconfirmed list, and carries the dispatcher's reply back to the customer.

The details

Included

  • Tomorrow's appointments pulled from ServiceTitan, Housecall Pro, or Jobber every afternoon, with each customer's mobile number.
  • A confirmation text to each customer with the arrival window, in your wording, asking them to reply to confirm or to reschedule.
  • Replies read and handled. Confirmations are checked off on dispatch's list, and reschedule or cancel requests go to your dispatcher with the job and the customer's message.
  • Access notes from replies, such as a gate code or a dog in the yard, passed to dispatch with the job.
  • A second text on the morning of the visit to customers who have not confirmed.
  • A list of unconfirmed appointments sent to dispatch at the time you set, before techs head out.
  • A test run on a real day's schedule before go-live, and a walkthrough for your dispatchers.

Not included

  • Moving jobs on your dispatch board. Your dispatcher reschedules; the automation tells them what the customer asked for.
  • Route planning, technician assignment, or capacity planning.
  • Replacing the on-my-way texts your field-service system already sends. Those stay on.
  • Your FlowRunner subscription and AI model usage, which are billed separately.
  • Ongoing changes after launch, which are covered by the care plan or priced per change.

After launch, we keep it running.

On our care plan

We monitor it, fix it, and make your changes, with a named contact. Your team does nothing.

$300 a month, unlimited changes, cancel any month

Or run it yourselves

We hand it over and train your team on what it does and what to do if something looks off.

Changes later: $75 an hour

It keeps running. Your automation lives in a FlowRunner account in your business's name, so it never depends on us, and we hand everything over to you or whoever you choose.

$1,500

One-time build. Live in 3 weeks*. We keep it running.

* The timeline may need to be adjusted depending on the requirements we receive.

Our price covers the build: setup in your accounts, tuning on your own past data, and training your team. FlowRunner runs it from there. How we work

Extras that apply: your FlowRunner subscription, $45/month**, billed by FlowRunner, and your AI model usage, billed by your AI provider. Neither is included in our price. We set both accounts up for you. See FlowRunner pricing. ** FlowRunner pricing varies with the volume of calls and messages.

Frequently asked questions

My field-service software already sends appointment reminders. Why add this?

Keep those if they work for you. This adds what happens after the customer replies. A reschedule request reaches your dispatcher with the job attached, an unconfirmed visit is flagged before the truck leaves, and a reply that changes the job reaches a person.

Does it reschedule the job for the customer?

No. Your dispatcher moves the job, because they know the board. They reply with the new window, and the customer gets it by text.