Dubber Recording Coverage Audit
Overview
A recorded line can stop capturing without anyone noticing: a phone-system change, a
re-provisioned handset, or a Dub.Point left inactive. For clients with a recording
obligation (financial advice, healthcare, collections) a silent line is a compliance gap.
This audit checks each Dub.Point for recent recordings and looks for calls Dubber captured
but could not place. Every tool used here is read tier in Conduit.
Anti-triggers
- Finding specific calls for a dispute or QA review — use
dubber-call-retrieval.
- Adding or removing Dubber users — use
dubber-user-lifecycle.
Inputs
- Account ID (required; there is no tool that lists all accounts).
- Group ID (optional; needed for the unidentified-recordings check).
- Look-back window. Default: the last 7 days. Use the client's local offset.
- Which lines are expected to record. Ask the user if they have a list; otherwise treat
every Dub.Point with an active status as expected.
Workflow
- Confirm the connection.
dubber_test_connection. If it fails, stop and report
the credential or region problem (see dubber-api-patterns).
- Confirm the account.
dubber_accounts_get with the account ID. Note the account
name and timezone for the report.
- List the recorded lines.
dubber_dub_points_list. For each Dub.Point record its
id, name/label, status, external_type, external_identifier and owning
user (the user ID is the last segment of the URL). If exactly 20 come back, the list
may be truncated; say so in the report.
- Check each line for recent calls. For each Dub.Point call
dubber_recordings_list with dubPointId, startTimeFrom set to the start of the
window, and limit: 1. One returned recording is enough to prove capture. Then note
its start_time as "last seen". An empty result means "silent" only when the scan
finished: if scanCapReached or hasMore is true, call again with
cursor=<nextCursor> and offset=<remainingOffset>. If excludedUnparseableStartTime
is above 0, mark the line "unknown" rather than silent.
- Date the silent lines. For a Dub.Point with no recording in the window, call
dubber_recordings_list with accountId, dubPointId and limit: 1 and no time
filter to find the most recent call it ever recorded. No result at all means the line
has never recorded.
- Look for unmatched calls. If you have the group ID, call
dubber_groups_list_unidentified_recordings. A growing pile here usually means a line
is recording but is not mapped to a Dub.Point, which is the other half of a "missing
recording" complaint.
- Check integrations.
dubber_notifications_list. For each subscription, note
event, url and active. For active ones, call
dubber_notifications_list_unclaimed; a non-empty backlog means the receiving system
(PSA, CRM, archive) is not taking events.
Flagging rules
| Finding |
Severity |
| Expected line with no recording in the window and none ever |
High: never captured |
| Expected line silent for the whole window but recorded before it |
High: capture stopped; give the last-seen date |
| Unidentified recordings present on the group |
Medium: mapping gap |
| Dub.Point status not active |
Medium: confirm whether intentional |
| Inactive subscription, or active one with unclaimed events |
Medium: integration broken |
| Line silent but the user is known to be on leave or the line is a spare |
Info: note and move on |
A quiet line is not always broken. Weekend-only windows, part-time staff and fax or
alarm lines produce false positives. Ask before escalating a single quiet line.
Report
Per account: account name, window, then a table of Dub.Points with name, external
identifier, user, status, recordings-in-window (yes or no) and last-seen date. Follow with
unidentified-recording count, integration status, and a short list of actions. State any
truncated list and any Dub.Point whose scan hit scanCapReached.
Gotchas
- Use
limit: 1 for the presence check. Scanning a busy line's whole week costs up to
25 Dubber requests per call against a 500-calls-per-day token budget.
start_time without an offset is read as UTC. A "Monday" window in Sydney or London
needs the right offset or it shifts by hours.
- This audit does not change anything. Fixing a silent line usually happens in the phone
system or the Dubber portal, not through these tools.
1---2name: dubber-recording-coverage-audit3description: >4 Read-only audit that proves Dubber is actually capturing calls for a5 client: which Dub.Points (recorded lines) have recent recordings and which6 have gone silent, recordings Dubber could not match to an account, and7 whether REST-hook integrations are active and draining. Covers the tool8 sequence, the thresholds for flagging a line, and how to report gaps9 honestly when a list may be truncated.10when_to_use: >-11 When an MSP needs to confirm call recording is working for a client, before12 a compliance review, after a phone-system change, or when a client says a13 call "wasn't recorded". Use when: recording coverage, are calls being14 recorded, silent dub point, missing recordings, unidentified recordings,15 dubber health check, call recording compliance audit, webhook backlog.16metadata:17 source: https://skillmd.com/skills/wyre-ai/dubber-recording-coverage-audit18---1920# Dubber Recording Coverage Audit2122## Overview2324A recorded line can stop capturing without anyone noticing: a phone-system change, a25re-provisioned handset, or a Dub.Point left inactive. For clients with a recording26obligation (financial advice, healthcare, collections) a silent line is a compliance gap.27This audit checks each Dub.Point for recent recordings and looks for calls Dubber captured28but could not place. Every tool used here is read tier in Conduit.2930## Anti-triggers3132- **Finding specific calls for a dispute or QA review** — use `dubber-call-retrieval`.33- **Adding or removing Dubber users** — use `dubber-user-lifecycle`.3435## Inputs3637- Account ID (required; there is no tool that lists all accounts).38- Group ID (optional; needed for the unidentified-recordings check).39- Look-back window. Default: the last 7 days. Use the client's local offset.40- Which lines are expected to record. Ask the user if they have a list; otherwise treat41 every Dub.Point with an active status as expected.4243## Workflow44451. **Confirm the connection.** `dubber_test_connection`. If it fails, stop and report46 the credential or region problem (see `dubber-api-patterns`).472. **Confirm the account.** `dubber_accounts_get` with the account ID. Note the account48 name and timezone for the report.493. **List the recorded lines.** `dubber_dub_points_list`. For each Dub.Point record its50 `id`, `name`/`label`, `status`, `external_type`, `external_identifier` and owning51 `user` (the user ID is the last segment of the URL). If exactly 20 come back, the list52 may be truncated; say so in the report.534. **Check each line for recent calls.** For each Dub.Point call54 `dubber_recordings_list` with `dubPointId`, `startTimeFrom` set to the start of the55 window, and `limit: 1`. One returned recording is enough to prove capture. Then note56 its `start_time` as "last seen". An empty result means "silent" only when the scan57 finished: if `scanCapReached` or `hasMore` is true, call again with58 `cursor=<nextCursor>` and `offset=<remainingOffset>`. If `excludedUnparseableStartTime`59 is above 0, mark the line "unknown" rather than silent.605. **Date the silent lines.** For a Dub.Point with no recording in the window, call61 `dubber_recordings_list` with `accountId`, `dubPointId` and `limit: 1` and no time62 filter to find the most recent call it ever recorded. No result at all means the line63 has never recorded.646. **Look for unmatched calls.** If you have the group ID, call65 `dubber_groups_list_unidentified_recordings`. A growing pile here usually means a line66 is recording but is not mapped to a Dub.Point, which is the other half of a "missing67 recording" complaint.687. **Check integrations.** `dubber_notifications_list`. For each subscription, note69 `event`, `url` and `active`. For active ones, call70 `dubber_notifications_list_unclaimed`; a non-empty backlog means the receiving system71 (PSA, CRM, archive) is not taking events.7273## Flagging rules7475| Finding | Severity |76|---|---|77| Expected line with no recording in the window and none ever | High: never captured |78| Expected line silent for the whole window but recorded before it | High: capture stopped; give the last-seen date |79| Unidentified recordings present on the group | Medium: mapping gap |80| Dub.Point status not active | Medium: confirm whether intentional |81| Inactive subscription, or active one with unclaimed events | Medium: integration broken |82| Line silent but the user is known to be on leave or the line is a spare | Info: note and move on |8384A quiet line is not always broken. Weekend-only windows, part-time staff and fax or85alarm lines produce false positives. Ask before escalating a single quiet line.8687## Report8889Per account: account name, window, then a table of Dub.Points with name, external90identifier, user, status, recordings-in-window (yes or no) and last-seen date. Follow with91unidentified-recording count, integration status, and a short list of actions. State any92truncated list and any Dub.Point whose scan hit `scanCapReached`.9394## Gotchas9596- Use `limit: 1` for the presence check. Scanning a busy line's whole week costs up to97 25 Dubber requests per call against a 500-calls-per-day token budget.98- `start_time` without an offset is read as UTC. A "Monday" window in Sydney or London99 needs the right offset or it shifts by hours.100- This audit does not change anything. Fixing a silent line usually happens in the phone101 system or the Dubber portal, not through these tools.