Webroot Usage Reconciliation
Overview
Monthly billing check: what Webroot will bill the MSP for, per customer, against what the
MSP bills each customer. Every tool here is in Conduit's Read group.
Which count to use
webroot_usage_sites_report takes a reportType. Pick the one that matches how the MSP
bills, and say which one you used:
reportType |
Counts |
Use for |
EndpointsSeenInLast30Days (default) |
Devices seen in the 30 days before effectiveDate |
Usage-based billing (devices actually in use that month) |
ActiveEndpoints |
All active devices, hidden ones included |
Seat-based contracts; the largest number |
ActiveEndpointsWithoutHidden |
Active devices as the console shows them |
Matching what a technician sees in the console |
Pass effectiveDate for a specific day (for example the last day of the billing month).
A day's data is usually ready during the following UTC day; for "today" the tool returns
the most recent complete report.
Workflow: month-end reconciliation
webroot_console_get: console license type, seats allowed and end date.
webroot_usage_sites_report with the chosen reportType and effectiveDate = the last
day of the month. This is the per-site count to bill against.
webroot_sites_list: devices allowed, total endpoints, billing cycle, end date, and
deactivated or suspended state per site.
- For each site, flag:
- Over allowance: total endpoints or usage count above devices allowed.
- Billed but idle: a site with seats but zero or near-zero usage.
- Deactivated or suspended sites that still report usage.
- End date within 30 days: renewals to action.
- If a PSA plugin is connected, compare each site's count with the customer's agreement
or contract quantity for Webroot. Match sites to PSA companies by name, and list any
site you could not match instead of guessing.
webroot_statistics_console_get for console-wide trial, expired, expiring, suspended and
deactivated site counts, as a cross-check on step 4.
Output
One table, one row per site: site name, usage count (with report type), devices allowed,
PSA quantity (if available), difference, and a flag column. Then a short list of actions:
true-ups to bill, seats to reduce, trials to convert or close, renewals due.
Gotchas
- The three report types legitimately disagree. Hidden endpoints and machines that were
active once in 30 days explain most gaps; do not call a difference an error until you
know which count each side uses.
- Stale endpoints inflate
ActiveEndpoints. If usage looks high, run the stale-agent step
in endpoint-health and recommend deactivating retired
devices in the GSM console.
- Site names in Webroot are free text set by whoever created the site. They often differ
from PSA company names (abbreviations, "Inc", branch suffixes).
1---2name: webroot-usage-reconciliation3description: >4 Webroot seat and usage reconciliation for MSP billing: the per-site usage5 report and its three report types, console seats allowed vs. deployed,6 per-site devices allowed vs. total endpoints, trial, expiring, suspended7 and deactivated sites, and how to compare the result with PSA agreement8 quantities.9when_to_use: >-10 When reconciling Webroot endpoint counts against customer billing, the11 Webroot invoice, or PSA agreements, or reviewing trials and expiring12 sites. Use when: webroot billing, webroot usage report, webroot seats,13 webroot license count, webroot true-up, expiring webroot sites, webroot14 trial, or webroot invoice reconciliation.15metadata:16 source: https://skillmd.com/skills/wyre-ai/webroot-usage-reconciliation17---1819# Webroot Usage Reconciliation2021## Overview2223Monthly billing check: what Webroot will bill the MSP for, per customer, against what the24MSP bills each customer. Every tool here is in Conduit's Read group.2526## Which count to use2728`webroot_usage_sites_report` takes a `reportType`. Pick the one that matches how the MSP29bills, and say which one you used:3031| `reportType` | Counts | Use for |32|---|---|---|33| `EndpointsSeenInLast30Days` (default) | Devices seen in the 30 days before `effectiveDate` | Usage-based billing (devices actually in use that month) |34| `ActiveEndpoints` | All active devices, hidden ones included | Seat-based contracts; the largest number |35| `ActiveEndpointsWithoutHidden` | Active devices as the console shows them | Matching what a technician sees in the console |3637Pass `effectiveDate` for a specific day (for example the last day of the billing month).38A day's data is usually ready during the following UTC day; for "today" the tool returns39the most recent complete report.4041## Workflow: month-end reconciliation42431. `webroot_console_get`: console license type, seats allowed and end date.442. `webroot_usage_sites_report` with the chosen `reportType` and `effectiveDate` = the last45 day of the month. This is the per-site count to bill against.463. `webroot_sites_list`: devices allowed, total endpoints, billing cycle, end date, and47 deactivated or suspended state per site.484. For each site, flag:49 - **Over allowance**: total endpoints or usage count above devices allowed.50 - **Billed but idle**: a site with seats but zero or near-zero usage.51 - **Deactivated or suspended sites** that still report usage.52 - **End date within 30 days**: renewals to action.535. If a PSA plugin is connected, compare each site's count with the customer's agreement54 or contract quantity for Webroot. Match sites to PSA companies by name, and list any55 site you could not match instead of guessing.566. `webroot_statistics_console_get` for console-wide trial, expired, expiring, suspended and57 deactivated site counts, as a cross-check on step 4.5859## Output6061One table, one row per site: site name, usage count (with report type), devices allowed,62PSA quantity (if available), difference, and a flag column. Then a short list of actions:63true-ups to bill, seats to reduce, trials to convert or close, renewals due.6465## Gotchas6667- The three report types legitimately disagree. Hidden endpoints and machines that were68 active once in 30 days explain most gaps; do not call a difference an error until you69 know which count each side uses.70- Stale endpoints inflate `ActiveEndpoints`. If usage looks high, run the stale-agent step71 in [endpoint-health](../endpoint-health/SKILL.md) and recommend deactivating retired72 devices in the GSM console.73- Site names in Webroot are free text set by whoever created the site. They often differ74 from PSA company names (abbreviations, "Inc", branch suffixes).