All templates

Automated Weekly Process Serving Throughput Report

Every Monday morning, WebRun opens ServeManager, pulls all jobs from the prior week, calculates jobs received, jobs completed, serve rate, total attempts, and server-by-server breakdown, logs the numbers to a Google Sheet for trending, and posts a clean weekly throughput summary to Slack so your Monday ops meeting starts with the right data.

Runs on WebRun · Strict Lockdown policy
Every Monday at 7:00 AM WebRunorchestrates each step
1 ServeManager pull prior week job activity
2 Google Sheets log metrics and trend data
3 Slack post weekly throughput summary
In short

How do I automatically generate a weekly process serving throughput report?

WebRun opens ServeManager every Monday, counts last week's jobs received, completed, and attempted, calculates completion rate and per-server throughput, and logs the metrics to a Google Sheet for trend tracking. It then posts a clean weekly summary to Slack with a comparison to the prior week so your ops meeting starts with the right numbers.

  • Monday ops meetings start with accurate throughput data without any manual number-pulling
  • Per-server completion and attempt data is visible week over week in Google Sheets
  • Completion rate trends are visible at a glance so performance issues surface early

Built for process serving companies · legal support firms · process service managers · operations directors

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

  2. 1
    ServeManager - pull prior week job activity
    servemanager.com
    WebRun in ServeManager: pull prior week job activity
    WebRun opens ServeManager to pull prior week job activity.
    • Open ServeManager and filter jobs by created date for the prior calendar week
    • Count total jobs received, total jobs completed, total attempts made, and jobs still open
    • Calculate completion rate (completed divided by received) and average attempts per serve
    • Break down completions and attempts by server to show individual throughput
    • Count rush jobs as a separate line item

    Done when Prior week totals and per-server breakdown are captured with completion and attempt metrics.

  3. 2
    Google Sheets - log metrics and trend data
    google.com
    WebRun in Google Sheets: log metrics and trend data
    WebRun opens Google Sheets to log metrics and trend data.
    • Open the Weekly Throughput sheet
    • Append a new row for this week: date range, jobs received, completed, open, completion rate, avg attempts, and rush job count
    • Add a per-server tab row for each server's completion and attempt totals
    • The sheet automatically updates the trend chart for month-over-month visibility

    Done when This week's throughput data is logged and the trend sheet is up to date.

  4. 3
    Slack - post weekly throughput summary
    slack.com
    WebRun in Slack: post weekly throughput summary
    WebRun opens Slack to post weekly throughput summary.
    • Post a weekly throughput summary to the ops channel
    • Lead with the headline numbers: jobs received, completion rate, and avg attempts
    • Include a short per-server table showing each server's completions and attempt count
    • Compare to prior week completion rate with a brief trend note

    Done when The ops channel has this week's throughput summary with trend context in Slack.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
www.servemanager.com
ScheduleRuns automatically on this cadence
Every Monday at 7:00 AM
DeliveryHow each run's result reaches you
Throughput report · Slack
OutputWhat each run produces - A weekly throughput summary with jobs received, completion rate, average attempts, per-server breakdown, and prior week comparison, logged to Google Sheets and posted to Slack.
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

What metrics does the weekly report include?

It covers jobs received, jobs completed, completion rate, total attempts, average attempts per serve, rush job count, and a per-server breakdown of completions and attempts.

Does it compare this week to previous weeks?

Yes. The Google Sheet accumulates a row per week and the Slack summary includes a brief comparison to the prior week's completion rate so you can spot trends at a glance.

Can I share the throughput report with clients or stakeholders?

The Slack post is an internal summary. If you need a client-facing version, your team can use the Google Sheet data to build a formatted report for sharing.

Put this on autopilot.

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