Dubber Call Retrieval and Tagging
Overview
Most Dubber requests an MSP gets are "find the call where...". Dubber has no search by
person and no server-side date filter, so the work is: resolve the person or number to
Dub.Points, list recordings for each Dub.Point in a time window, then narrow by the call
details. Finding and reading calls is read tier in Conduit. Tagging and metadata changes
are write tier.
The plugin cannot play or download audio. Give the user the recording IDs and details so
they can open the calls in the Dubber portal.
Anti-triggers
- Checking whether lines are recording at all — use
dubber-recording-coverage.
Workflow
1. Pin down the request
Get the account ID, who or which line, and the time window in the client's local time.
Convert the window to ISO 8601 with an explicit offset, for example
2026-11-02T00:00:00+11:00 to 2026-11-07T00:00:00+11:00 for a Monday-to-Friday week
in Sydney daylight time. Ask for a narrower window if the user only says "last month".
2. Resolve the person or line to Dub.Points
- By person:
dubber_users_list to find the user ID, then dubber_dub_points_list and
keep the Dub.Points whose user URL ends in /users/<that ID>. A person can have more
than one Dub.Point (desk phone and softphone). Both lists return one Dubber page, so if
either may be truncated (the Dub.Point list came back at exactly 20), one of the
person's lines may be missing. Mark the search incomplete, whether or not it found
calls, and have the user confirm the person's lines in the Dubber portal.
- By phone-system identifier:
dubber_dub_points_find with the external-system
identifiers, then dubber_dub_points_get for detail.
- By team: use
teamId on the recordings call instead.
3. List recordings in the window
Call dubber_recordings_list once per Dub.Point with dubPointId, startTimeFrom,
startTimeTo and a limit that fits the request (100 is usually enough for a week).
query passes a search string to Dubber if the user has a number or keyword. If
hasMore is true, continue with cursor=<nextCursor> and offset=<remainingOffset>,
keeping the same dubPointId and window.
Narrow the results by the fields on each recording: from, to, call_type,
duration, start_time. Present a short table, newest first.
4. Read the candidates
dubber_recordings_get for each likely match returns its metadata, tags and duration.
Confirm the match with the user before marking anything.
5. Mark the calls (write tier)
dubber_recordings_add_tags to label calls, for example dispute-2026-114 or
legal-hold. Tags are the simplest way for the client to find the set again in the
portal.
dubber_recordings_update_metadata replaces or updates custom metadata fields. Read the
current metadata with dubber_recordings_get first and send the complete object you
want to keep.
dubber_recordings_delete_tags removes tags. It asks for confirmation; through
Conduit it needs confirm_destructive_action: true after the user agrees. Removing a
hold-style tag can let a retention rule act on the call, so confirm who asked for it.
Out of scope: deleting recordings
dubber_recordings_delete permanently destroys the audio and its compliance record. It is
write tier in Conduit, not admin, so a technician with write access can reach it. Do not
use it in a retrieval workflow. If the user asks to delete a call, stop and confirm there
is a written instruction from the client's authorised contact and no legal hold, then
confirm the exact recording ID before passing confirm_destructive_action: true.
Gotchas
- A window without an offset is UTC. A Sydney or Los Angeles day shifts by many hours.
- A date-only
startTimeTo includes that whole day. A date-time startTimeTo is
exclusive.
dubPointId and teamId cannot be combined, and a cursor must be reused with the
same one.
- Calls Dubber could not match to a Dub.Point will not appear under any Dub.Point. If a
call is missing, check
dubber_groups_list_unidentified_recordings on the group.
1---2name: dubber-call-retrieval-and-tagging3description: >4 Finding specific Dubber recordings for a complaint, billing dispute, HR5 matter or QA sample: resolving a person or line to Dub.Points, windowed6 recording searches in the client's timezone, reading recording details,7 and marking calls with tags or metadata for follow-up or retention. Covers8 which steps are read, which are write tier in Conduit, and why recording9 deletion is out of scope for this workflow.10when_to_use: >-11 When someone needs to locate, review or mark particular calls in Dubber.12 Use when: find a call, customer complaint call, call dispute, pull13 recordings for a technician, QA call sample, tag a recording, legal hold14 tag, recordings between dates, who called on, dubber recording details.15metadata:16 source: https://skillmd.com/skills/wyre-ai/dubber-call-retrieval-and-tagging17---1819# Dubber Call Retrieval and Tagging2021## Overview2223Most Dubber requests an MSP gets are "find the call where...". Dubber has no search by24person and no server-side date filter, so the work is: resolve the person or number to25Dub.Points, list recordings for each Dub.Point in a time window, then narrow by the call26details. Finding and reading calls is read tier in Conduit. Tagging and metadata changes27are write tier.2829The plugin cannot play or download audio. Give the user the recording IDs and details so30they can open the calls in the Dubber portal.3132## Anti-triggers3334- **Checking whether lines are recording at all** — use `dubber-recording-coverage`.3536## Workflow3738### 1. Pin down the request3940Get the account ID, who or which line, and the time window in the client's local time.41Convert the window to ISO 8601 with an explicit offset, for example42`2026-11-02T00:00:00+11:00` to `2026-11-07T00:00:00+11:00` for a Monday-to-Friday week43in Sydney daylight time. Ask for a narrower window if the user only says "last month".4445### 2. Resolve the person or line to Dub.Points4647- By person: `dubber_users_list` to find the user ID, then `dubber_dub_points_list` and48 keep the Dub.Points whose `user` URL ends in `/users/<that ID>`. A person can have more49 than one Dub.Point (desk phone and softphone). Both lists return one Dubber page, so if50 either may be truncated (the Dub.Point list came back at exactly 20), one of the51 person's lines may be missing. Mark the search incomplete, whether or not it found52 calls, and have the user confirm the person's lines in the Dubber portal.53- By phone-system identifier: `dubber_dub_points_find` with the external-system54 identifiers, then `dubber_dub_points_get` for detail.55- By team: use `teamId` on the recordings call instead.5657### 3. List recordings in the window5859Call `dubber_recordings_list` once per Dub.Point with `dubPointId`, `startTimeFrom`,60`startTimeTo` and a `limit` that fits the request (100 is usually enough for a week).61`query` passes a search string to Dubber if the user has a number or keyword. If62`hasMore` is true, continue with `cursor=<nextCursor>` and `offset=<remainingOffset>`,63keeping the same `dubPointId` and window.6465Narrow the results by the fields on each recording: `from`, `to`, `call_type`,66`duration`, `start_time`. Present a short table, newest first.6768### 4. Read the candidates6970`dubber_recordings_get` for each likely match returns its metadata, tags and duration.71Confirm the match with the user before marking anything.7273### 5. Mark the calls (write tier)7475- `dubber_recordings_add_tags` to label calls, for example `dispute-2026-114` or76 `legal-hold`. Tags are the simplest way for the client to find the set again in the77 portal.78- `dubber_recordings_update_metadata` replaces or updates custom metadata fields. Read the79 current metadata with `dubber_recordings_get` first and send the complete object you80 want to keep.81- `dubber_recordings_delete_tags` removes tags. It asks for confirmation; through82 Conduit it needs `confirm_destructive_action: true` after the user agrees. Removing a83 hold-style tag can let a retention rule act on the call, so confirm who asked for it.8485## Out of scope: deleting recordings8687`dubber_recordings_delete` permanently destroys the audio and its compliance record. It is88write tier in Conduit, not admin, so a technician with write access can reach it. Do not89use it in a retrieval workflow. If the user asks to delete a call, stop and confirm there90is a written instruction from the client's authorised contact and no legal hold, then91confirm the exact recording ID before passing `confirm_destructive_action: true`.9293## Gotchas9495- A window without an offset is UTC. A Sydney or Los Angeles day shifts by many hours.96- A date-only `startTimeTo` includes that whole day. A date-time `startTimeTo` is97 exclusive.98- `dubPointId` and `teamId` cannot be combined, and a `cursor` must be reused with the99 same one.100- Calls Dubber could not match to a Dub.Point will not appear under any Dub.Point. If a101 call is missing, check `dubber_groups_list_unidentified_recordings` on the group.