All templates

Automated Missed Call Callback Queues

Every hour, WebRun opens the CallTrackingMetrics call log, picks out calls that rang out or went unanswered, captures the caller number, the tracking line they dialled, and the time, adds each to an Airtable callback queue, and blocks a callback slot in Google Calendar so the lead gets a return call today.

Runs on WebRun · Strict Lockdown policy
Every hour WebRunorchestrates each step
1 CallTrackingMetrics find this hour's missed calls
2 Airtable build the callback queue
3 Google Calendar block callback time
In short

How do I make sure every missed call gets a callback the same day?

WebRun reads your CallTrackingMetrics call log every hour, picks out the calls that rang out, and captures the caller number, the tracking line dialled, and the time. It builds an Airtable callback queue and blocks time in Google Calendar, so a missed ring turns into a returned call the same day.

  • Missed callers are queued within the hour, not found at end of day
  • Every callback shows the advert or source that produced the call
  • Callers who ring back on their own drop off the queue automatically

Built for home service businesses · marketing agencies · sales teams · clinics and practices

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 app.calltrackingmetrics.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    CallTrackingMetrics - find this hour's missed calls
    calltrackingmetrics.com
    WebRun in CallTrackingMetrics: find this hour's missed calls
    WebRun opens CallTrackingMetrics to find this hour's missed calls.
    • Open the call log and filter to the last hour
    • Keep calls that were missed, abandoned, or went unanswered
    • Capture the caller number, the tracking number dialled, and the timestamp
    • Note the reporting tags on the tracking line so the source is clear

    Done when Every missed call in the last hour is captured with its number and source.

  3. 2
    Airtable - build the callback queue
    airtable.com
    WebRun in Airtable: build the callback queue
    WebRun opens Airtable to build the callback queue.
    • Add a row per missed call with number, tracking line, tag, and time
    • Check earlier rows so a caller who already got through is not queued twice
    • Mark a row Done once the call log shows a later connected call from that number
    • Keep the queue sorted oldest first

    Done when The callback queue holds every caller still owed a return call.

  4. 3
    Google Calendar - block callback time
    calendar.google.com
    WebRun in Google Calendar: block callback time
    WebRun opens Google Calendar to block callback time.
    • Block a short callback slot on the phone owner's own calendar
    • List the numbers to ring and their tracking line in the event notes
    • Never invite the caller and never place a call. A person makes every callback

    Done when There is time on the calendar to work today's callback queue.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.calltrackingmetrics.com
ScheduleRuns automatically on this cadence
Every hour
DeliveryHow each run's result reaches you
Callback queue · Airtable
OutputWhat each run produces - A callback queue of missed callers with the number, the tracking line they dialled, the source tag, and the time they rang.
Text
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 call or text the caller back for me?

No. WebRun builds the callback queue and blocks the time. It never dials a number, sends a text, or leaves a voicemail. A person on the phones makes every return call.

What stops the same caller being queued twice?

WebRun checks the call log for a later connected call from that number before adding a row, and marks existing rows Done once the caller gets through.

Does it know which advert the call came from?

Yes. It records the tracking number dialled and the reporting tags on that line, so each callback shows the campaign or source that produced the call.

Put this on autopilot.

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