/
/
Tell the delivery team what the client said on the call
For account and project teams who want a Chorus call summary posted as a message in the client's Teamwork.com project, by asking their AI assistant.
On this page
Connector
Connect Chorus, pick your AI tool and paste the prompt.
The problem
What clients say on calls never reaches delivery
What a client says on a sales or account call rarely reaches the delivery team working on their project. Writing it up in Teamwork.com means rereading the summary, finding the project and checking nobody posted it already.
Without PopdockAI
- Reread the call summary
- Find the client's open project
- Check nobody posted it already
- Strip out pricing and contract terms by hand
With PopdockAI
- The call summary and attendees are read
- The client's open project is found and checked for an existing post
- The draft keeps out pricing and confidential terms
- It is posted privately after you approve, notifications off
The prompt
Use this prompt
Copy it into any AI tool connected to PopdockAI. Swap the values in braces for your own.
**Objective:** Share what was discussed on the Chorus conversation `{conversation-id}` with the delivery team by posting it as a message in the client's Teamwork project, after the user approves the wording. Post it as private unless `{is-private}` is false (default true).
**Step 1: Read the call in Chorus**
Call `chorus-get-engagements` with `conversation-id` set to `{conversation-id}` and keep `subject`, `date`, `user-name`, `account-name`, `opportunity-name` and `meeting-summary`. Call `chorus-get-conversation-participants` with the same id and keep each participant's `name`, `title` and `company-name`. If there is no `meeting-summary`, stop.
**Step 2: Find the project in Teamwork**
Call `teamwork-get-projects` with `company-name.contains` set to the distinctive part of `account-name`, keeping projects that are not completed. If several match, list them and ask. If none match, stop and say the client has no open Teamwork project.
**Step 3: Check it has not been posted already**
Call `teamwork-get-messages` with the `project-id` and `title.contains` set to the call subject. If a message for this call already exists, show it and stop.
**Step 4: Draft and confirm**
Draft a message titled "Client call: <subject> (<date>)" with a body containing who attended, a short summary, decisions made and follow-ups, taken only from `meeting-summary`. Show the title, body, project and privacy setting, and ask the user to approve or edit. Do not post until they approve.
**Step 5: Post and confirm**
Call `teamwork-create-message` once with `project-id`, `title`, `body` and `is-private`, and leave `notify` unset unless the user asks for notifications. Report the returned `id`.
**Rules & Guidelines:**
* `chorus-get-engagements` and `chorus-get-conversation-participants` are on the chorus server. `teamwork-get-projects`, `teamwork-get-messages` and `teamwork-create-message` are on the teamwork server.
* `teamwork-create-message` is the only tool that may write, and only after approval. Do not call `teamwork-create-comment`, `teamwork-update-message` or any chorus write tool such as `chorus-add-moment`.
* Do not include pricing, contract terms or anything the summary marks as confidential in the message; list those for the user instead.
**Validation:**
* If the conversation id returns nothing, say so and stop.
* If the call has no `account-name`, ask which project to post to rather than guessing.Who it's for
One answer, three teams that use it
Account managers
Brief delivery after client calls
Decisions and follow-ups reach the project team without writing a separate update.
Post a summary of today's Chorus call with Contoso to their Teamwork.com project.
Project managers
Hear client concerns first hand
Get what the client said as a project message, so your team acts on it.
Post yesterday's Fabrikam QBR from Chorus to their Teamwork.com project as a private message.
Delivery leads
Keep commercial terms out of projects
Pricing and contract terms stay out of the message, so the project space stays safe to share.
Summarise the Northwind Traders Chorus call for their Teamwork.com project, leaving out pricing.
How it works
What PopdockAI does when you ask
You name the Chorus conversation and your AI assistant drafts a project message for Teamwork.com. Anything left out is listed for you, and nothing is posted until you approve.
01
Ask
You name the Chorus conversation, and whether the message is private.
02
Find
It finds the client's open Teamwork.com project and checks nothing was posted.
03
Draft
It writes attendees, summary, decisions and follow-ups, leaving out pricing.
04
Approve
You approve or edit the message before it is posted.
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-conversation-participants
teamwork-com-get-projects
teamwork-com-get-messages
teamwork-com-create-message
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
The delivery team hears what the client said
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)
