All templates

Automated Race Heat Reminder Texts

Through the day, WebRun watches the RaceFacer session manager for heats starting soon, and for each booked driver it drafts a short, friendly reminder text with the heat time and gate, then queues it in Twilio for a staff member to release so it never sends unchecked.

Runs on WebRun · Strict Lockdown policy
Every few minutes on race days WebRunorchestrates each step
1 RaceFacer find heats starting soon
2 Twilio queue the reminder texts
In short

How do I automatically remind go-kart racers before their heat?

WebRun reminds racers before their heat. Every few minutes it scans the RaceFacer session manager for heats starting soon, and for each booked driver it drafts a short reminder text with the time and check-in point, queued in Twilio for your staff to release, so fewer racers miss their grid.

  • Fewer racers miss their heat or hold up the grid
  • Reminders drafted per driver without staff typing each text
  • Every message reviewed before it leaves the building

Built for go-kart tracks · karting centers · race directors · front-desk teams

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 www.racefacer.com/en in a real browser with your saved login - no setup, no API keys.

  2. 1
    RaceFacer - find heats starting soon
    racefacer.com
    WebRun in RaceFacer: find heats starting soon
    WebRun opens RaceFacer to find heats starting soon.
    • Open the RaceFacer session manager and look at heats starting within the reminder window
    • Capture each booked driver's name, mobile number, heat time, and grid or gate
    • Skip drivers who have already checked in at the desk

    Done when Every driver in an upcoming heat is listed with a mobile number.

  3. 2
    Twilio - queue the reminder texts
    twilio.com
    WebRun in Twilio: queue the reminder texts
    WebRun opens Twilio to queue the reminder texts.
    • Draft a short reminder text for each driver with the heat time and where to check in
    • Queue the messages in Twilio rather than sending them
    • Leave the queue for a staff member to review and release, so no text goes out on its own

    Done when Reminder texts are queued in Twilio awaiting staff release.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.racefacer.com/en
ScheduleRuns automatically on this cadence
Every few minutes on race days
DeliveryHow each run's result reaches you
Reminder queue · Twilio
OutputWhat each run produces - A queued reminder text per driver for each upcoming heat, with the heat time and check-in point.
SMS drafts
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 racers automatically?

No. WebRun drafts each reminder and queues it in Twilio. A staff member reviews the queue and releases the messages, so nothing reaches a driver without a human approving it first.

How far ahead does the reminder go out?

You choose the window, for example 30 minutes before the heat. WebRun only drafts reminders for drivers whose heat falls inside that window on the live RaceFacer schedule.

Does it skip drivers who already arrived?

Yes. WebRun checks the live RaceFacer check-in status each run, so anyone already at the desk is left out of the reminder queue.

Put this on autopilot.

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