Connectors

/

Chorus

/

Match Chorus calls to open Procore RFIs and submittals
Report
Cross-Connector

See which open RFIs and submittals were discussed on Chorus calls

For project managers who want open Procore RFIs and submittals checked against Chorus calls and emails by asking their AI assistant.

Try PopdockAI free
Get a live demo
Match Chorus calls to open Procore RFIs and submittals
For Riverside Tower, which open RFIs and submittals were discussed on calls or emails in the last 30 days?
Riverside Tower has 14 open items, 9 discussed in Chorus and 5 not discussed, 3 of them overdue. - RFI-0042: Discussed, call on 2026-11-03 - 03 30 00-004 submittal: Discussed, email on 2026-11-07 - RFI-0051: Not discussed, 8 days overdue - Conversations with no open item: 2 Want the full table with due dates and contractors?
Chorus
Sample figures. Your results come from your own account.
procore-get-rfis
procore-get-submittals
chorus-get-engagements
chorus-get-emails

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

Which open items were ever raised with the customer

To see whether open RFIs and submittals were mentioned, you read through call recordings and emails by hand. The items nobody raised are the hardest to spot, and they are the ones that slip.

Without PopdockAI

  • List the project's open RFIs and submittals in Procore
  • Read recordings and emails for each subject and number
  • Note by hand which were mentioned
  • Work out which overdue ones were never raised

With PopdockAI

  • Open RFIs and submittals are read in Procore
  • Chorus calls and emails are searched for each item
  • Each item is marked Discussed or Not discussed
  • The three overdue items not raised are named, and nothing is written

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 the project named `{project-name}`, show what was discussed in recorded calls and emails against what is still open in RFIs and submittals, looking back `{lookback-days}` days (default 30).

**Step 1: Find the project's open items in Procore**

Call `procore-get-rfis` with `project-name.contains` set to `{project-name}`. Keep RFIs whose status is not closed. Call `procore-get-submittals` with the same `project-name.contains` and keep those not approved or closed. If the project name matches more than one project, list the matches and stop.

**Step 2: Find the project's conversations in Chorus**

Call `chorus-get-engagements` with `account-name.contains` set to `{project-name}` and `date.from` set to the start of the lookback window. If it returns nothing, repeat with `subject.contains` set to `{project-name}`. Call `chorus-get-emails` with `account-name.contains` set to `{project-name}` and `sent-time.from` set to the same date.

**Step 3: Carry the join across**

For each open RFI take `subject` and `full-number`. For each open submittal take `title` and `formatted-number`. Look for those words or numbers in the Chorus `subject`, `meeting-summary` and email `body`. Mark each item Discussed (with the conversation id and date) or Not discussed.

**Step 4: Report**

One table of open RFIs and submittals with due date, responsible contractor, and Discussed or Not discussed. Then list conversations that mention no open item. End with the three overdue items that have not been discussed.

**Rules & Guidelines:**

* Tools named procore-get-* are on the procore-project-management server. tools named chorus-* are on the chorus server. Both servers must be connected.
* Names do not match exactly across the two systems. Match on a case-insensitive contains comparison and show the user which names you treated as the same.
* Read only. Do not call any create, update, delete or export tool on either server, including `chorus-create-playlist`, `chorus-add-moment`, `chorus-add-playlist-moment` and `chorus-export-recordings`.

**Validation:**

* If Chorus returns no conversations for the project, say the project has no recorded calls under that account name and still show the Procore table.
* If Procore returns no open items, say so and list the conversations only.

Who it's for

One answer, three teams that use it

Project managers

Know what to raise next

See the open RFIs and submittals that were never discussed on a call, so you raise them at the next meeting.

Which open RFIs on Fabrikam Depot have not come up in any Chorus call or email?

Account managers

Prepare for a customer call

Check what was already discussed about open items before you speak to the customer, and what still needs raising.

Match Chorus conversations to the open submittals on Contoso Warehouse for the last 45 days.

Delivery directors

Check the customer is informed

See whether overdue open items were ever raised with the customer, to judge the relationship risk.

Which overdue RFIs and submittals on Northwind Plaza were never discussed with the customer?

How it works

What PopdockAI does when you ask

You name the project and a look back period. Your AI assistant reads both systems and shows which names it treated as the same. It stops if the project name is ambiguous.

Ask

You name the project and optionally how far back to look.

Your AI tool

Read

It reads the project's open RFIs and submittals in Procore, stopping if several projects match.

procore-get-rfis
procore-get-submittals
chorus-get-engagements
chorus-get-emails

Match

It searches Chorus calls and emails for each item's subject or number and marks it Discussed or Not discussed.

No items found.

Report

You get one table, conversations with no open item and the three overdue items not yet raised.

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

procore-get-rfis

Returns Procore requests for information (RFIs) for a project, with status, due date and the responsible contractor.
get-data

procore-get-submittals

Returns submittals on a Procore project, with number, title, status, due date, responsible contractor and specification section. Filter by project name or submittal fields.
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-emails

Returns emails captured by Chorus, including the subject, body, sender, owner, account and sent time. Filter by account or date range to read the written trail alongside the calls.
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

No open item left unmentioned by accident

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