/
/
See a customer's sales and billing activity side by side
For account owners who want Chorus conversations next to Harvest invoices and hours for one customer, by asking their AI assistant.
On this page
Connector
Connect Chorus, pick your AI tool and paste the prompt.
The problem
Sales and billing for one customer live apart
Conversations sit in Chorus and invoices and hours sit in Harvest, with no shared id between them. Flipping between the two and matching names by hand is slow and risks pairing the wrong customer.
Without PopdockAI
- Search the customer in Chorus
- Search the same name in Harvest
- Collect invoices, hours and unbilled work
- Piece the two views together yourself
With PopdockAI
- The account is found in Chorus and the client in Harvest
- Several matches prompt a question, not a guess
- Conversations sit beside invoices, hours and unbilled work
- The date window and name match are shown
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Build a single picture of `{client-name}` by pairing its sales conversations in Chorus with its billing and delivery in Harvest, looking back `{lookback-days}` days (default 90).
**Step 1: Find the account in Chorus**
Call `chorus-get-engagements` with `account-name.contains` set to `{client-name}` and `date.from` set to the start of the lookback window. If the results carry more than one distinct `account-name`, list the names and stop to ask which one is meant. Note each conversation's `date`, `subject`, `conversation-type`, `opportunity-name` and `user-email`. Then call `chorus-get-emails` with `account-name.contains` set to `{client-name}` and `sent-time.from` set to the same date, and count the emails.
**Step 2: Find the client in Harvest**
Take the Chorus `account-name` and call `harvest-get-clients` with `name.contains` set to it. If nothing matches, retry once with the `{client-name}` text you were given. If there is still no match, report the account as present in Chorus and absent from Harvest and go straight to Step 4. If more than one client matches, list them and stop.
**Step 3: Pull the Harvest side**
Using the matched client's `id` as `client-id`, call `harvest-get-invoices` (add `issue-date.from` for the window), `harvest-get-time-reports` (with `period-start` and `period-end` for the window) and `harvest-get-uninvoiced-report`. Collect invoiced amount, amount still due, hours worked, billable hours and uninvoiced amount.
**Step 4: Report**
Give two short sections, "Chorus activity" (conversation count, last conversation date, owners, open opportunities, email count) and "Harvest billing" (invoiced, due, hours, uninvoiced). Finish with up to three observations that only make sense with both together, for example heavy sales activity with no billing, or billing with no recent conversations.
**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 Chorus returns nothing, say so and still report the Harvest side if the client exists.
* If both systems return nothing, say the name matches nothing in either and suggest checking the spelling.
* State the exact date window used.Who it's for
One answer, three teams that use it
Account owners
Review both views before a meeting
See what sales has discussed and what has been billed for a customer, side by side, before you meet them.
Pair Chorus calls and Harvest invoices for Northwind Traders over the last 60 days.
Sales managers
Spot calls that never turn into billing
Check whether heavy sales activity with a customer has produced any invoices or hours in the billing system.
Has Fabrikam had a lot of sales activity in Chorus but no invoices in Harvest?
Customer success managers
Check conversations follow the work
Find customers who are billed regularly but have had no recent conversations, a sign the relationship needs attention.
Does Contoso have recent billing in Harvest but no recent Chorus conversations?
How it works
What PopdockAI does when you ask
You name the customer. Your AI assistant reads conversations and emails in Chorus and billing data in Harvest, then writes both views. It reports a customer missing from either system and changes nothing.
Ask
You name the customer and, optionally, how many days to look back.
Find in Chorus
It locates the account and asks which one if several names match.
Find in Harvest
It matches the client by name, reports a missing one and pulls invoices, hours and unbilled work.
Report
You get Chorus activity beside Harvest billing and up to three observations.
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
chorus-get-emails
harvest-get-clients
harvest-get-invoices
harvest-get-time-reports
harvest-get-uninvoiced-report
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
One answer instead of two systems
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)
