/
/
Match Chorus accounts to Harvest clients and see the gaps
For leaders who want to know which customers talked to sales but are not billed, and which clients went quiet, by asking their AI assistant.
On this page
Connector
Connect Chorus, pick your AI tool and paste the prompt.
The problem
Two systems that only share a customer name
Sales conversations live in Chorus and billing lives in Harvest, and the only link is the name. Comparing the two lists by eye misses customers who never became clients and clients who went quiet.
Without PopdockAI
- Export accounts from Chorus and clients from Harvest
- Line up names in a spreadsheet
- Guess whether near matches are the same customer
- Miss gaps on either side
With PopdockAI
- Chorus accounts and Harvest clients are read for the same period
- Matches are labeled exact, loose or unmatched
- Gaps are listed on both sides
- Names are treated as suggestions, never proof
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Reconcile the customers that appear in Chorus sales conversations with the clients in Harvest for the period `{period-start}` to `{period-end}` (default: the last 90 days).
**Step 1: Collect the Chorus accounts**
Call `chorus-get-engagements` with `date.from` set to `{period-start}` and `date.to` set to `{period-end}`. Build the list of distinct `account-name` values with the number of conversations and the latest `date` for each. Ignore blank account names but count them and mention the count.
**Step 2: Collect the Harvest clients**
Call `harvest-get-clients` with `active` set to true. Then call `harvest-get-time-reports` with `period-start` and `period-end` set to the same dates, which returns hours and billable amount per `client-name`.
**Step 3: Match**
Match each Chorus `account-name` to a Harvest client `name` on a case-insensitive exact match first, then on one name containing the other. Mark each pair as exact, loose or unmatched. Do not guess beyond that.
**Step 4: Report**
Three lists: (a) Chorus accounts with engagements and no Harvest client, most conversations first; (b) Harvest clients with billable hours in the period and no Chorus engagements; (c) loose matches that a person should confirm. End with the counts of each.
**Rules & Guidelines:**
* Harvest tools (names starting harvest-) come from the harvest server and Chorus tools (names starting chorus-) come from the chorus server. Both servers must be connected.
* This is read-only. Do NOT call any Harvest create, update, delete or restart tool (for example `harvest-clients-create`, `harvest-contacts-create`, `harvest-invoices-create`, `harvest-estimates-create`, `harvest-invoices-update`, `harvest-time-entries-create`). Chorus has no write tools here.
* Chorus calls its customers accounts and Harvest calls them clients. The only link is the name, so match on exact name first, then a case-insensitive contains match, and always show which kind of match was used.
* Hourly rates, cost rates and invoice amounts are sensitive: show them only because the user asked for billing context.
**Validation:**
* If either side returns nothing for the period, say so and do not produce the lists that depend on it.
* Treat a name match as a suggestion, never as proof that two records are the same customer.Who it's for
One answer, three teams that use it
Sales leadership
Find customers sales talked to but never billed
See Chorus accounts with recent conversations that have no Harvest client, most conversations first.
Which Chorus accounts from the last quarter have no matching Harvest client?
Finance leaders
Spot billed clients that went quiet
List Harvest clients with billable hours that had no Chorus conversations in the period, so someone can ask why.
Which Harvest clients with billable hours had no Chorus conversations in the last 90 days?
Revenue operations
Settle name differences with confidence
Review the loose matches where one name contains the other, and confirm which are the same customer.
Show the loose matches between Chorus accounts and Harvest clients so I can confirm them.
How it works
What PopdockAI does when you ask
You give a period. Your AI assistant reads conversations in Chorus and clients and hours in Harvest, then matches on name and labels how. Both must be connected, and neither system is changed.
Ask
You give a period, or accept the last 90 days.
Collect
It reads the accounts in Chorus conversations and the active clients and hours in Harvest.
Match
It matches names exactly first, then loosely, and labels each pair.
Report
You get accounts missing from Harvest, clients missing from Chorus and loose matches to confirm.
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-engagements
harvest-get-clients
harvest-get-time-reports
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
Sales and billing gaps in plain view
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)
