All templates

Automated Amtelco Daily Call Volume Digest

Every morning, WebRun opens Amtelco, pulls yesterday's call and message volume, average handle time, and abandon count for each client account, logs a row per client to a running tracker in Google Sheets, and posts the daily digest to Slack so the team starts the day with the numbers.

Runs on WebRun · Strict Lockdown policy
Every day at 7:30 AM WebRunorchestrates each step
1 Amtelco pull yesterday's call and message volume
2 Google Sheets log a row per client to the tracker
3 Slack post the daily digest
In short

How do I get a daily call volume digest for every client automatically?

Every morning, WebRun opens Amtelco and pulls yesterday's call volume, message count, average handle time, and abandoned calls for every client account. It logs a row per client to a running tracker in Google Sheets and posts the daily digest to Slack, flagging any client whose volume moved more than 20 percent from their average, so the team starts the day already informed.

  • The team sees yesterday's numbers before the day starts, every day
  • Volume swings over 20 percent get flagged instead of found weeks later
  • Every client's history builds automatically in one running tracker

Built for answering services · call center managers · 24/7 dispatch operations · telephone answering firms

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

  2. 1
    Amtelco - pull yesterday's call and message volume
    amtelco.com
    WebRun in Amtelco: pull yesterday's call and message volume
    WebRun opens Amtelco to pull yesterday's call and message volume.
    • Open Amtelco reporting and pull yesterday's totals per client: calls answered, messages taken, average handle time, and abandoned calls
    • Note any client whose volume moved more than 20 percent from their weekday average

    Done when Yesterday's volume is captured for every active client account.

  3. 2
    Google Sheets - log a row per client to the tracker
    google.com
    WebRun in Google Sheets: log a row per client to the tracker
    WebRun opens Google Sheets to log a row per client to the tracker.
    • Add a new row per client to the volume tracker with yesterday's date and figures
    • Carry forward the weekday average column so trends stay visible

    Done when Every client's numbers for yesterday are logged in the tracker.

  4. 3
    Slack - post the daily digest
    slack.com
    WebRun in Slack: post the daily digest
    WebRun opens Slack to post the daily digest.
    • Post the daily digest: total calls, total messages, and average handle time across all clients
    • List any client that moved more than 20 percent from its average at the top

    Done when The team has yesterday's digest in Slack before the day starts.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.amtelco.com
ScheduleRuns automatically on this cadence
Every day at 7:30 AM
DeliveryHow each run's result reaches you
Volume digest · Slack
OutputWhat each run produces - A logged row per client in Google Sheets plus a Slack digest of totals and any client with an unusual swing in volume.
Spreadsheet + digest
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

Does this change how any client is billed?

No. It only reads and logs volume figures for visibility. Billing runs through your existing process and is not touched by this digest.

How does it decide what counts as an unusual swing?

It compares yesterday's total against that client's own weekday average and flags anything more than 20 percent off. You can tighten or loosen that threshold.

Can it cover multiple locations or queues per client?

Yes. Give WebRun the queue structure for a multi-location client and it will log and total each one separately in the tracker.

Put this on autopilot.

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