Connectors

/

Chorus

/

Find Chorus call participants missing from Harvest
Report
Cross-Connector

Find sales call attendees who are not Harvest contacts

For sales teams who want customer call participants from Chorus checked against a client's Harvest contacts, by asking their AI assistant.

Try PopdockAI free
Get a live demo
Find Chorus call participants missing from Harvest
Which people from Fabrikam have been on our Chorus calls in the last 90 days but are not contacts in Harvest?
2 people from Fabrikam joined calls but are not Harvest contacts. - Missing: Tom Reyes, tom@fabrikam.com, 4 calls, latest 29 October - Missing: Priya Shah, priya@fabrikam.com, 1 call, latest 12 October - Already in Harvest: Dana Whitfield, dana@fabrikam.com Shall I check a different client?
Chorus
Sample figures. Your results come from your own account.
chorus-get-engagements
chorus-get-conversation-participants
harvest-get-clients
harvest-get-contacts

On this page

The problem

The problem

The prompt

Who it's for

How it works

Tools used

Connector

Chorus

Chorus
Run it on your own Chorus data.

Connect Chorus, pick your AI tool and paste the prompt.

Try PopdockAI free

The problem

Call attendees never reach the billing contacts

Customers join sales calls in Chorus but are not always added as contacts in Harvest. Comparing attendees with contacts by hand is slow, and invoices or estimates end up with the wrong person.

Without PopdockAI

  • Open the client's calls in Chorus
  • Note every external attendee
  • Open the client's contacts in Harvest
  • Compare emails by eye

With PopdockAI

  • The client's calls and external attendees are collected
  • Duplicates are merged by email
  • Attendees are checked against Harvest contacts on email only
  • Skipped calls and missing emails are called out

The prompt

Use this prompt

Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.

Prompt
**Objective:** For `{client-name}`, list the people who took part in its Chorus conversations since `{since-date}` (default: the last 90 days) and show which of them are not yet contacts in Harvest.

**Step 1: Find the conversations**

Call `chorus-get-engagements` with `account-name.contains` set to `{client-name}` and `date.from` set to the since date. If several distinct `account-name` values come back, list them and stop. Record each `conversation-id`.

**Step 2: Get the participants**

For each conversation, up to 15, call `chorus-get-conversation-participants` with `conversation-id`. Keep only participants whose `type` is a customer or external attendee, not an internal user, and who have an `email`. Merge duplicates by email address, ignoring case.

**Step 3: Get the Harvest contacts**

Call `harvest-get-clients` with `name.contains` set to the Chorus `account-name`. If there is no match, report that the client does not exist in Harvest and stop. Otherwise call `harvest-get-contacts` with that `client-id` and collect the contact emails.

**Step 4: Report**

Two lists: participants already in Harvest (name, email, title) and participants missing from Harvest (name, email, title, number of conversations attended, latest conversation date). Mention any participant without an email, since they cannot be matched.

**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.
* Match people on email address only, never on name.

**Validation:**

* If there are no conversations in the window, say so and stop.
* If more than 15 conversations were found, say how many were not read.

Who it's for

One answer, three teams that use it

Account executives

Keep billing contacts current

See who from a customer has been on your calls but is missing from Harvest, so estimates reach the right people.

Who from Northwind Traders joined our Chorus calls since August but is not a Harvest contact?

Account managers

Send invoices to the right person

Check whether everyone active on recent calls is also a contact in the billing system before the next invoice goes out.

Check whether everyone on recent Contoso calls is a Harvest contact.

Sales operations

Close the contact gap

Get a list of missing people with their email, calls attended and latest call date, ready to be added by whoever owns the data.

List the people from Fabrikam on Chorus calls that are missing from Harvest.

How it works

What PopdockAI does when you ask

You name the client. Your AI assistant reads conversations and participants in Chorus and contacts in Harvest. It stops when the client is not in Harvest or the account name is unclear.

Ask

You name the client and, optionally, a start date.

Your AI tool

Find calls

It reads the client's Chorus conversations and stops if several account names match.

chorus-get-engagements
chorus-get-conversation-participants
harvest-get-clients
harvest-get-contacts

Compare

It collects external participants, merges them by email and checks them against the client's Harvest contacts.

No items found.

Report

You get who is in Harvest and who is missing, with calls attended.

Your AI tool

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.

get-data

chorus-get-engagements

Returns recorded calls and meetings from Chorus, with the subject, date, duration, participants and the account each conversation relates to. Filter by date range, owner or account to pull the conversations behind a deal or a period.
get-data

chorus-get-conversation-participants

Returns the people who took part in Chorus conversations, with their name, email, title and company. Use it to see who was on a call, and which side they were on.
get-data

harvest-get-clients

Returns clients from Harvest. Read-only Get data tool for the Harvest connector; accepts the filters the list supports.
get-data

harvest-get-contacts

Returns contacts from Harvest. Read-only Get data tool for the Harvest connector; accepts the filters the list supports.
Read only.Nothing in Chorus Changes

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.

How Popdock AI secures your data

The outcome

Billing contacts that match who you talk to

Try PopdockAI free
Get a live demo

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.

Try PopdockAI Free
See Documentation