Client system

Collins guarded SMS follow-up bot

Live runnerEscalation workflow
Abstract workflow poster for a guarded SMS follow-up automation.
Outcome

The business can follow up faster without blindly texting people who should not get another message.

Leads needed fast text follow-up. The danger was sending texts after a reply, opt-out, wrong number, or sensitive message.

What was wasting time

Leads needed fast text follow-up. The danger was sending texts after a reply, opt-out, wrong number, or sensitive message.

What changed

I built a follow-up runner that checks the lead before each text. It stops when the conversation changes and alerts a person when needed.

Result

The business can follow up faster without blindly texting people who should not get another message.

How it works

  1. Add only approved leads.
  2. Check the lead before texting.
  3. Send only during allowed hours.
  4. Stop on replies or opt-outs.
  5. Alert a person when help is needed.

Tools, explained

  • Cloudflare Workers are small online jobs that can run follow-up checks on a schedule.
  • D1 is a simple database used to remember lead status and avoid duplicate sends.
  • A technical part of the build that supported the business outcome.
  • A Slack webhook sends an alert into Slack when a person needs to step in.
  • TypeScript is JavaScript with extra checks that catch mistakes earlier.

Related services

Impact

5 min cron interval
tag enrollment gate

Have a workflow like this?

Work with us