/
/
See how much of your Chorus email record is hidden or deleted
For IT and revenue operations teams who want the facts on deleted and private Chorus email threads, by asking their AI assistant.
On this page
Connector
Connect Chorus, pick your AI tool and paste the prompt.
The problem
Deleted and private email quietly hides the customer record
In Chorus, email threads can be deleted or marked private, and over time that hides part of the customer record from the team. Finding out what was removed, by whom and where privacy clusters means piecing thread data together by hand.
Without PopdockAI
- Pull deleted email threads and who deleted them
- Count private threads against the total
- Look up each person's role
- Group it all by account and owner by hand
With PopdockAI
- Deleted threads and private threads are read and counted
- Each person's role is added for context
- Private email is grouped by account and owner
- No private body is quoted and nothing is changed
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Audit the Chorus email record over the last `{lookback-days}` days (default 90): what has been deleted, by whom, and how much of the captured email is marked private and therefore invisible to the wider team.
**Step 1: Read the deletions**
Call `chorus-get-email-threads` with `deleted` set to true and `deleted-at.from` set to the start of the window. Keep `email-thread-id`, `deleted-by-name`, `deleted-at`, `private` and `user-id`. If `{deleted-by}` was supplied, narrow with `deleted-by-name.contains`.
**Step 2: Read the private threads**
Call `chorus-get-email-threads` with `private` set to true. Count them, and count all threads with no filter beyond `max-records` so you have a denominator.
**Step 3: Attribute**
For each distinct `deleted-by-name`, and for the owners of the private threads, call `chorus-get-users` with `name.contains` set to that name to get `email`, `role` and `title`. A deletion by an administrator reads differently from a deletion by a rep, and the report should let the reader tell them apart.
**Step 4: Cross check against the emails**
Call `chorus-get-emails` with `sent-time.from` set to the start of the window and note how many are marked `private` and which accounts they relate to, using `account-name`. This shows whether privacy clusters on particular accounts.
**Step 5: Report**
Produce:
* **Deletion summary** - how many threads deleted in the window, and the trend across the period.
* **Who deleted** - a table of person, role, count, and the date range of their deletions. Put anyone with an unusually concentrated burst first, and state the count rather than characterising it.
* **Private volume** - private threads as a share of all threads, and private emails as a share of all emails.
* **Where privacy clusters** - the accounts and owners with the most private email.
* **What to follow up** - the specific questions worth asking a person, each tied to a count.
**Rules & Guidelines:**
* This is read only. Do not call any tool that creates, updates or exports.
* Report counts and let the reader judge. Do not accuse anyone of concealment, and do not describe a deletion as suspicious.
* Do not quote the body of a private email into the report. Reference the thread by its id and its account only.
**Validation:**
* If nothing was deleted in the window, say so and report the private volume alone.
* If a `deleted-by-name` does not resolve to a current user, report the name as it stands and note that the account no longer exists.Who it's for
One answer, three teams that use it
IT administrators
Audit deletions with context
See who deleted threads and their role, so an admin clean up reads differently from a rep deletion.
Audit Chorus email deletions for the last 30 days and show who deleted what.
Compliance officers
Check privacy use across teams
Private email grouped by account and owner shows where privacy is used heavily.
Where does private email cluster in Chorus by account and owner this quarter?
Revenue operations
Know what the team cannot see
Counts of hidden and deleted email show how complete the shared customer record is.
How many Chorus email threads were made private or deleted by Jordan Lee in the last 90 days?
How it works
What PopdockAI does when you ask
You choose how far back to look and your AI assistant audits Chorus email privacy and deletions. It reports counts without calling anything suspicious.
01
Ask
You choose how far back to look, and optionally one person.
02
Read
It reads deleted threads with who deleted them and private threads against the total.
03
Attribute
It adds each person's role and groups private email by account and owner.
04
Report
You get the counts and questions to follow up, with nothing changed.
What PopdockAI provides
The tools behind the answer
Ready made tools for Chorus and one secure connection to your AI tool. No code, no exports.
chorus-get-email-threads
chorus-get-users
chorus-get-emails
This report is built from Get data tools only. PopdockAI applies the row, field and parameter rules your admin sets, and every query is written to the audit trail.
The outcome
See how much of the email record is hidden, with facts
Related use cases
More ways to put this data to work
One prompt template with infinite possibilities.
Your AI assistant adapts its approach, tone, and capabilities to match each unique context while you maintain a single, manageable workflow.
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.

.webp)
