Notes
Chorus
Connect your AI to Chorus
Sales reps, sales managers, and customer success leads record every customer call in Chorus, but the commitments, objections, and next steps buried in those conversations rarely make it back into the CRM or the support ticket. AI can pull out what matters from each call, but only if it reads only the conversations each person is allowed to see and keeps what customers actually said separate from guesswork.
Why it matters
Capabilities that matter most for Chorus
01
Calls beside the CRM record
Join Chorus conversations with CRM opportunities and helpdesk tickets so commitments from a call reach the record they belong to.
02
Ready-made endpoints and summaries
Install 19 Chorus API endpoints and summary lists from the app store for calls, meetings and trackers.
03
Only the calls each person may see
AI tools read conversations within per-user and per-team security, keeping what customers said separate from inference.
Use cases
Example AI Use Cases for Chorus
scenario
-
People you meet on recorded Chorus calls often never make it into Bloomerang, or exist there without the email they used on the call. Spotting them means comparing call participants with constituents one at a time, and a name match alone can attach an email to the wrong person.
What popdock provides
--
Choose a look-back period, and optionally a company name, and it collects the external participants from recent Chorus conversations and checks each email against Bloomerang. People already known are dropped, a single exact name match is shown as a probable match with the email missing, and everyone else as not in Bloomerang. For each row it proposes adding the email to the existing constituent or creating a new one, and you approve rows one by one. Only approved rows are written, a name match is never treated as certain, and participants with no email are counted rather than guessed.
Business outcome
---
Contacts from your calls end up in Bloomerang with the right email, without duplicate or misattached records.
scenario
-
Fundraising leaders want to know whether calls lead to gifts, but Chorus holds the conversations and Bloomerang holds the money. Lining up who was on each call with what they gave in the following weeks is a spreadsheet job most teams never get to.
What popdock provides
--
Choose a look-back period, how many days after a call to count gifts, and optionally one fundraiser, and it matches each external participant in Chorus to a Bloomerang constituent by email. It reads the gifts each donor made in the window after the call, excluding refunds and counting each gift once against the most recent conversation. You get results per fundraiser, a gift-by-gift table, and up to ten donors spoken to who have not given, ranked by engagement score. It only reads, and states plainly that a gift after a call shows timing, not proof of cause.
Business outcome
---
You see which conversations were followed by gifts and who is ready for another ask, broken down per fundraiser.
scenario
-
Promises made on a donor call, such as sending a report or setting up a visit, live in the Chorus summary and need to become Bloomerang tasks. Copying them over by hand is slow, commitments get missed, and the same task is created twice when two people both act on the call.
What popdock provides
--
Give the Chorus conversation, the Bloomerang user to assign and a default due period, and it reads the meeting summary and finds the donor among the participants by email, asking if more than one constituent matches. Each concrete commitment becomes a draft task in the summary's own words, and drafts that match an open task already on the donor are dropped. You confirm, edit or remove each task before anything is written. It never invents commitments the summary does not state, and if the assignee is rejected it stops rather than trying someone else.
Business outcome
---
Commitments made on donor calls become assigned Bloomerang tasks the same day, without duplicates.
scenario
-
Fundraisers record calls in Chorus but do not always log them in Bloomerang, so donor records miss conversations that happened. Finding the gaps means checking each call's participants against constituents and then hunting for a matching interaction near the call date.
What popdock provides
--
Choose a look-back period, and optionally one Chorus user, and it lists recent conversations, matches external participants to Bloomerang constituents by email and checks for any interaction logged within a day of each call. Unlogged donor conversations come back in a table with the owner and constituent, along with counts of calls checked, logged, unlogged and unmatched, and a tally per owner. Calls with no Bloomerang match are counted but not listed as gaps. It only reads, and warns when the result was capped so you can shorten the window.
Business outcome
---
Donor records reflect every recorded conversation, and you can see which fundraisers are falling behind on logging.
scenario
-
A recorded Chorus meeting with three donors should appear on each of their Bloomerang records with the right channel, purpose and summary. Doing it by hand means matching each attendee, checking whether someone already logged it, and retyping the notes several times over.
What popdock provides
--
Give the Chorus conversation and a purpose, or it asks for one, and it reads the meeting and keeps only external participants. Each is matched to Bloomerang by email; anyone unmatched is listed and never created. It skips constituents who already have an interaction logged that day, then shows who will be logged and the exact interaction, with the meeting summary and who led the call. Nothing is written until you confirm, and if Bloomerang rejects a channel or purpose it asks you rather than trying other values.
Business outcome
---
One recorded meeting is logged on every donor who attended, once each, with the summary attached.
scenario
-
Donors write in by email, and Chorus captures those messages, but Bloomerang only shows them if someone logs each one as an interaction. Doing it by hand is tedious, and it is easy to log the same email twice or include a message that was marked private.
What popdock provides
--
Give the donor's email and a look-back period, and it finds the constituent in Bloomerang, stopping if none or several match. It reads the emails that donor sent through Chorus, skips private ones and tells you how many, and drops any already logged on the same day with the same subject. You see what will be logged, choose one purpose for the batch, and confirm before anything is written. Each email becomes an inbound email interaction with an excerpt of the body, and a rejected purpose is asked about rather than guessed.
Business outcome
---
Donor emails appear on their Bloomerang record without double logging or exposing private messages.
scenario
-
Before calling a donor you want their giving and open tasks from Bloomerang next to what was said on past calls and emails in Chorus. Switching between the two and lining up dates takes time, and conversations that were never logged in Bloomerang stay invisible.
What popdock provides
--
Give the donor's email, and optionally how far back to look, and it finds the constituent in Bloomerang and reads their profile, gifts without refunds, open tasks and logged interactions. From Chorus it gathers recent calls, meetings and emails with that donor. You get a briefing covering who they are, giving in the window, open tasks, a merged timeline marked by source, the key points from call summaries, and Chorus conversations with no matching Bloomerang entry. It only reads, and never guesses a constituent from a name when the email does not match.
Business outcome
---
You start every donor call fully briefed, including what was said last time and what is still owed.
scenario
-
People you meet on Chorus calls often never make it into Capsule CRM, because adding them means checking each email, finding their organization and typing in their title. The contacts who matter most to a deal end up existing only in a recording.
What popdock provides
--
Choose how many days of Chorus calls to look back over, and optionally one account. It gathers the outside participants with an email, skips colleagues by matching email domains to Chorus users, and checks Capsule CRM for each email so existing people are dropped. You see each person with their company, Capsule organization if found and number of calls, and pick who to add; nothing is written until you answer. People are added only as people, linked to an organization only on a full match, and each is read back to confirm.
Business outcome
---
The people on your calls become Capsule CRM contacts linked to their organization, without duplicates or guessed names.
scenario
-
Before a customer call you flip between Capsule CRM for open deals, projects and overdue tasks, and Chorus for what was said on the last few calls and emails. Skip either and you walk in without knowing about a promise someone made last month.
What popdock provides
--
Name the account and how far back to look. It finds the organization in Capsule CRM, asking you to pick if several match, and reads its open deals, projects, tasks and recent history. It then reads the Chorus calls and emails for the same account, retrying with a shorter name if needed and saying so. The brief ends with three to five points that connect the two systems, such as a deal closing soon with no recent call. It never merges two organizations whose names only partly match, and nothing is changed in either system.
Business outcome
---
You walk into every customer call knowing the deal status and what was promised last time, from one brief.
scenario
-
A Capsule CRM deal can sit at the same milestone and probability for weeks while the calls tell a different story, such as pricing talk, a new decision maker or a slipped date. Spotting that means rereading call summaries and emails against the record, which rarely happens.
What popdock provides
--
Name the opportunity and how far back to look. It reads the deal and its history in Capsule CRM, then the Chorus calls and emails for the account, labelling account-level conversations separately. It looks for disagreements such as procurement talk at an early milestone, high probability with no contact in 30 days, or a close date a meeting summary contradicts, and cites the evidence for each. Suggested milestone, probability or date changes are given as text only; it does not infer a stage change from a single remark and changes nothing.
Business outcome
---
Deal records stay honest because mismatches with what customers actually said are caught with evidence, before the forecast relies on them.
scenario
-
The action items from a sales call are written in the Chorus summary, but turning them into Capsule CRM tasks means rereading it, finding the right contact and deal, and picking due dates. Some follow-ups get lost, others get created twice.
What popdock provides
--
Give the Chorus conversation and a default number of days until each task is due. It reads the meeting summary and pulls out only the follow-ups your side committed to, leaving out what the customer promised. It finds the matching organization, deal and rep in Capsule CRM, and marks any item an open task already covers. You choose which tasks to create and nothing is written before you answer, past dates move to today with a note, and each new task is read back to confirm it exists.
Business outcome
---
Promises made on calls become owned, dated Capsule CRM tasks the same day, without duplicating follow-ups already planned.
scenario
-
Reps record calls in Chorus but often forget to log them in Capsule CRM, so the customer history looks thin and last contacted dates go stale. Checking means matching each call to a contact and searching their history around the call date.
What popdock provides
--
Choose how many days to look back, and optionally one rep by email. It lists the Chorus conversations, matches each to a Capsule CRM organization or, failing that, to outside participants by email, then looks for a history entry within two days of the call. Each call is marked not logged, logged or no Capsule contact, with unlogged ones first and totals by rep. A call is never reported as unlogged when its contact could not be found, the match used is stated, and nothing is written.
Business outcome
---
Gaps in your CRM history are closed quickly because you know exactly which calls were never logged and by whom.
scenario
-
Copying a Chorus call into Capsule CRM means finding the right deal or contact, writing up who attended and what was agreed, and checking nobody logged it already. It is tedious enough that most calls never get logged at all.
What popdock provides
--
Give the Chorus conversation and whether the note should go on the deal or the contact. It reads the call and its outside participants, then finds the matching Capsule CRM opportunity, organization or person, and asks you to choose when several match. It checks for a note about the same meeting before drafting a new one with the subject, attendees, summary and next steps. You see the draft and the record it goes on, nothing is saved until you confirm, and the note is read back afterwards.
Business outcome
---
Calls are logged on the right Capsule CRM record with a consistent summary, and never logged twice.
scenario
-
An open deal can go quiet without anyone noticing, because silence does not show up in Capsule CRM. Finding the quiet ones means checking each account for recent calls, emails and logged history across two systems.
What popdock provides
--
Name an owner, or leave it blank, and how many quiet days to allow. It reads the open Capsule CRM opportunities, then checks each account for recent Chorus calls and emails and each deal for recent Capsule history, so contact logged in one place is not mistaken for silence. Quiet deals are listed largest first, with those due to close soon flagged and totals kept per currency. Accounts Chorus cannot find are marked as no match rather than quiet, and nothing is changed.
Business outcome
---
Deals at risk of going cold are found while there is still time to reach the customer, starting with the biggest.
scenario
-
Building a coaching playlist in Chorus means searching for calls on a topic, listening for the right part and clipping each by hand. It takes hours, and playlists often end up featuring the same rep or clips that miss the moment.
What popdock provides
--
Name the playlist, the topic and how far back to look. It finds or creates the playlist in Chorus, finds conversations on the topic, and picks up to five that actually handle it, spread across different reps. Each clip gets a start and length placed from the meeting summary, with approximate placements flagged. You see the proposed clips in seconds before anything is written, nothing is added until you approve, and it never guesses a playlist id or repeats a clip that already succeeded.
Business outcome
---
Reps get a focused coaching playlist of real examples from different colleagues, built in minutes instead of an afternoon.
scenario
-
Before a meeting with an account, the history is scattered across months of Chorus calls, meetings and emails. Reconstructing what was discussed, who is involved now and what is still open takes longer than the meeting itself.
What popdock provides
--
Name the account and how many days of history to cover. It finds the account in Chorus, asks you to pick if more than one matches, and reads its conversations oldest to newest. It lists the people on the customer side, marking anyone new or no longer appearing, and reads recent emails between meetings. The briefing covers where things stand, a timeline, open threads and three questions to ask; it quotes summaries as evidence, notes gaps in contact, and changes nothing.
Business outcome
---
You go into the next meeting knowing the history, the people and the open threads on the account.
scenario
-
In Chorus, email threads can be deleted or marked private, and over time that hides part of the customer record from the wider team. Finding out what was removed, by whom and where privacy clusters means piecing together thread data by hand.
What popdock provides
--
Choose how far back to look, and optionally one person. It reads the deleted Chorus email threads and who deleted them, the private threads against the total, and the role behind each name, so a deletion by an administrator reads differently from one by a rep. It shows where private email clusters by account and owner, and lists the questions worth following up. It reports counts without calling anything suspicious, never quotes the body of a private email, and changes nothing.
Business outcome
---
You can see how much of the email record is hidden or removed, and by whom, with facts rather than accusations.
scenario
-
Chorus licenses get assigned and then forgotten when people change roles or stop recording. Finding the idle ones means checking each user's calls, captured emails and team membership before renewal comes around.
What popdock provides
--
Choose how far back to look, and optionally a license type. It reads active Chorus users, counts each person's conversations and, for anyone with none, their captured emails, so an email-only user is not reported as idle. It checks team membership and lists users on no team. Anyone created inside the window is called out as too new to judge rather than put on the reclaim list, zero counts are shown as zero, and a truncated user list is flagged. Nothing is changed.
Business outcome
---
You reclaim or reassign idle licenses with evidence, without cutting off people who use Chorus differently.
scenario
-
A Chorus playlist library fills up with empty folders, stale collections, private playlists that should be shared and names like test or a bare date. Tidying it means opening each playlist and trying to remember what it was for.
What popdock provides
--
Optionally name an owner, and set how many days counts as stale. It reads the Chorus playlists and sorts them into empty, stale, unexpectedly private, badly named and owned by inactive users. Each problem playlist gets one proposed fix, such as a new name, a parent folder or a privacy change, and nothing is ever deleted. You choose which changes to apply, only approved playlists are touched, and it says plainly when making a playlist shared widens who can see customer conversations.
Business outcome
---
Your coaching library stays easy to navigate, with only the changes you approved applied.
scenario
-
Preparing a coaching session means pulling a rep's Chorus scorecards, reading question-level scores and comments, and checking what feedback they already got. Without that, coaching repeats old points or misses the real weak spot.
What popdock provides
--
Name the rep and how far back to look. It resolves the person in Chorus, reads their scorecards, the score and comment for each question, and the coaching moments already recorded, plus how many conversations the scores draw from. The review lists strengths and development areas with reviewer comments quoted, what was raised before and whether it seems to have landed, and one area to focus on. It keeps different scorecard types apart, warns when the sample is too small for a trend, and changes nothing.
Business outcome
---
Coaching sessions focus on the rep's real weak spots, backed by scores and reviewer comments rather than impressions.
scenario
-
Across a coaching program the same weaknesses come up again and again, but they are buried in hundreds of Chorus scorecard answers. Counting weak scores alone misleads, because some questions are asked far more often or scored harder by one reviewer.
What popdock provides
--
Name the coaching initiative and the score that counts as weak. It reads every Chorus score for the initiative, groups the weak ones by question, and gives each a weak rate against the total, not just a count. For the worst questions it quotes what reviewers wrote, shows whether weak scores spread across many people or a few, and checks whether one reviewer scores markedly harder before calling it a skills gap. It recommends one change, flags samples too small to rank, and changes nothing.
Business outcome
---
Training targets the skills your team genuinely struggles with, not the habits of a single reviewer.
scenario
-
By the end of a quarter, some reps have been reviewed several times and others not at all, and the gap shows up when it is too late. Checking means comparing a Chorus team roster against scorecards, coaching moments and call activity person by person.
What popdock provides
--
Name the team and how far back to look. It reads the team roster in Chorus, separates active members from inactive ones, and counts each person's conversations, scorecards and coaching moments. Members with calls but no scorecard come first, people with no calls are shown separately because the cause is different, and reviewer load shows whether one person carries the reviewing. Counts are exact, an empty result is reported as zero, and nothing is changed.
Business outcome
---
Managers close coaching gaps before the quarter ends, knowing exactly who has been missed and who carries the reviews.
scenario
-
Sharing a key part of a Chorus call means finding the conversation, scrubbing to the right moment and setting up a clip. Shared clips can be opened outside the company, so a missing expiry or the wrong account can expose more than intended.
What popdock provides
--
Name the conversation, describe what to capture, and set an expiry. It finds the conversation in Chorus, asks which one if several match, and places a 30 to 120 second clip from the meeting summary, asking you for a timestamp rather than guessing. You see the clip timing, title, note, expiry date and the account involved before anything is created, and nothing is written until you approve. An expiry is always set, and the moment is created only once.
Business outcome
---
You share exactly the part of a call you meant to, with an expiry date that stops it circulating forever.
scenario
-
Prospective supporters often join calls recorded in Chorus long before they are in DonorPerfect. Adding them means checking each email against donor records and additional addresses, then keying in names and a donor type by hand.
What popdock provides
--
Choose how many days of Chorus conversations to look back over, and optionally one account. It gathers the outside participants with an email and checks each against DonorPerfect donors and their additional addresses, keeping only people found in neither. You see each person with their company and recent conversations, choose which to add and the DonorPerfect donor type, and nothing is written without that selection. Names that do not split cleanly are shown to you to enter, and each new donor is read back with its new id.
Business outcome
---
New supporters from your calls become DonorPerfect donors, with no duplicate records and no guessed names.
scenario
-
Before calling a donor you need their giving history, open pledges and flags from DonorPerfect, plus what was said on the last few Chorus calls. Gathering it means two systems and a lot of scrolling, and a follow-up promised last time is easy to miss.
What popdock provides
--
Give the DonorPerfect donor by id or email, and how many recent conversations to include. It reads the donor's gifts, open pledges, recent and overdue contacts and flags from DonorPerfect, then finds their Chorus conversations and emails using every email on file. The one-page brief covers giving, recent conversations, outstanding follow-ups and three talking points grounded in the data. A follow-up counts only when a meeting summary states it, and nothing is changed in either system.
Business outcome
---
You start every donor call knowing their giving, their open pledges and what was promised last time.
scenario
-
Piecing together every conversation with one donor means searching Chorus for each email address they have used, plus calls filed under their organization. It is slow, and it is hard to tell a real match from a company with a similar name.
What popdock provides
--
Give the DonorPerfect donor by id or email, and how far back to look. It collects every email on the donor and their additional addresses, then lists their Chorus calls, meetings and emails in date order. Conversations found only through the organization name are labelled as weaker evidence, and ones that look unrelated are set apart as possible matches. It never widens the search to name matching, ends with totals and the most recent touch, and changes nothing.
Business outcome
---
You see the full conversation history with a donor in one timeline, with weak matches clearly labelled.
scenario
-
Your largest donors can go months without a conversation, and nothing in DonorPerfect raises a flag. Finding them means checking each major donor against Chorus calls, meetings and emails one at a time.
What popdock provides
--
Set the lifetime giving threshold and how far back to look. It reads DonorPerfect donors above the threshold and checks Chorus for recent calls, meetings and emails by email and by organization name, labelling organization matches as weaker evidence. Donors with no recent touch are listed by lifetime giving, with their last touch at any time if one exists, and donors with no email or organization are listed as cannot check. It warns when the list is capped and changes nothing.
Business outcome
---
Your most generous donors are not left without contact, because the ones gone quiet are listed by giving.
scenario
-
Pledges with a balance still owing need someone to talk to the donor, but DonorPerfect does not show whether that has happened. Checking means looking up each pledge and searching Chorus for conversations since the pledge date.
What popdock provides
--
Choose the earliest pledge date, or use the default of a year ago. It reads DonorPerfect pledges with a balance above zero, then checks Chorus for any call, meeting or email with each donor since the pledge was made. Pledges nobody has followed up are listed by balance, largest first, and ones with contact show the latest conversation and any summary line about the pledge or a payment. It never says a pledge was discussed unless the summary says so, and changes nothing.
Business outcome
---
Outstanding pledge balances get a timely follow-up, starting with the largest amounts nobody has discussed.
scenario
-
Every conversation with a donor should be recorded as a DonorPerfect contact, but logging a Chorus call means working out which participants are donors and writing the same summary for each. Calls go unlogged, or get logged twice.
What popdock provides
--
Give the Chorus conversation and, optionally, the activity code. It reads the call and its outside participants, matches each to a DonorPerfect donor by email only, and checks for a contact already logged that day. You see each participant's status and the exact contact to be written, can pick from the activity codes, and nothing is saved without your confirmation. Existing contacts are never overwritten, ambiguous and already logged donors are skipped and listed, and each new contact is read back.
Business outcome
---
Donor conversations are recorded in DonorPerfect once, against every donor who took part, with the summary attached.
scenario
-
Calls with donors recorded in Chorus often never become DonorPerfect contacts, so the donor history misses real conversations. Finding them means matching each participant to a donor and checking the contact log around each call date.
What popdock provides
--
Choose how far back to look, and optionally one Chorus user. It reads the Chorus conversations and their outside participants, matches each email to a DonorPerfect donor, and checks for a contact within two days of the call. You get a table of unlogged conversation and donor pairs, a count of logged ones, and outside participants who are not donors counted by company. Emails matching more than one donor are listed as ambiguous, the list warns when capped, and nothing is written.
Business outcome
---
Your donor records reflect every conversation, because you know exactly which calls still need logging.
scenario
-
Customer-side people on Chorus calls often never become contacts in Dynamics 365 Sales. Adding them means filtering out colleagues, checking each email against contacts and leads, and typing in names and titles one by one.
What popdock provides
--
Name the account, how far back to look and, optionally, its Dynamics 365 account id. It collects the people from the account's Chorus calls, drops colleagues and your own email domain, and checks Dynamics 365 Sales for each email as a contact and then as a lead, so existing leads are flagged rather than duplicated. You choose which people to create and nothing is written without that answer. It never guesses an account id, and creates contacts unlinked, saying so, when none is given.
Business outcome
---
The buyers on your calls become Dynamics 365 Sales contacts without duplicating people already in the CRM.
scenario
-
Account managers often walk into a customer call without knowing which Dynamics 365 Sales cases are still open, or whether those problems were already discussed with someone else. Checking means reading the case list, then searching call notes and emails for each issue.
What popdock provides
--
Name the customer and how far back to look. It lists the open Dynamics 365 Sales cases with priority, age and resolve-by date, then searches the customer's Chorus calls and emails for each case number, product or title words, marking each case as discussed on a date or not discussed. Issues raised on calls that match no open case are listed separately as possible cases not yet logged. It says which words matched, since a word match is a lead and not proof, and nothing is written.
Business outcome
---
You go into the next call knowing every open case and which ones the customer has already raised with your team.
scenario
-
Sales leaders want to know whether the behaviors scored in Chorus actually relate to winning deals, but scorecards and outcomes sit in different systems, often under different names. Lining up each rep's scores against their Dynamics 365 Sales wins and losses by hand is slow and error prone.
What popdock provides
--
Choose a period, and optionally one rep. It reads Chorus scorecards and averages each rep's scores overall and per question, then counts their won and lost Dynamics 365 Sales opportunities and won revenue, matching names through email when they differ. You get a table per rep and the questions whose scores differ most between higher and lower win rate reps. It describes a correlation, never a cause, flags small samples, lists reps it could not match, and changes nothing.
Business outcome
---
Coaching priorities rest on which scored behaviors actually track with wins, with small samples clearly flagged.
scenario
-
A deal closing this month with no recent conversation is a deal at risk, but Dynamics 365 Sales does not show when the customer was last on a call. Checking each closing opportunity against Chorus by hand rarely happens before the forecast meeting.
What popdock provides
--
Choose how far ahead to look, how many silent days to allow and, optionally, one owner. It reads the open Dynamics 365 Sales opportunities closing in the window and checks each customer once in Chorus for recent conversations, retrying with the distinctive part of the name. Only the silent deals are listed, by close date, with stage, probability, revenue and last conversation, plus the revenue at stake. Customers Chorus cannot find are marked as no match rather than silent, and nothing is changed.
Business outcome
---
You see which closing deals have gone quiet and how much revenue rides on them, before the quarter ends.
scenario
-
New leads in Dynamics 365 Sales are often people your team has already spoken to on a call, yet they sit in the queue unqualified with a cold rating. Spotting them means checking each lead against Chorus conversations one at a time.
What popdock provides
--
Choose how far back to look and, optionally, a lead source. It reads the open Dynamics 365 Sales leads and looks for each person in Chorus by email, or by company when there is no person match. Matches show the conversations, the latest date and a summary line, with a recommendation to qualify, raise the rating or leave, citing the words in the summary that support it. Company-only matches are labelled weaker and never used alone to recommend qualifying, and nothing is changed.
Business outcome
---
Leads your team has already talked to are qualified sooner, based on what was actually said on the call.
scenario
-
After a recorded call, someone should add the summary to the Dynamics 365 Sales opportunity or account and set a follow-up task. Doing it by hand means rereading the Chorus summary, finding the right record and checking nobody logged it already.
What popdock provides
--
Give the Chorus conversation, the Dynamics 365 Sales record id from the address bar, and how many working days until the follow-up is due. It reads the call summary and attendees, shows the matching opportunity or account for you to confirm, and checks for an existing note about the call. You see the drafted note and one follow-up task together and confirm once before anything is written. It never guesses a record id, puts nothing in the note that is not in the summary, and asks you for key points when the summary is empty.
Business outcome
---
Every recorded call lands on the right Dynamics 365 Sales record with a single follow-up task, logged once.
scenario
-
Reps hold more conversations than they log, and Dynamics 365 Sales ends up missing calls that really happened. Finding the gaps means comparing a rep's Chorus recordings against their phone calls, appointments and activities day by day.
What popdock provides
--
Name the rep and the number of days to compare. It finds the rep in Dynamics 365 Sales and in Chorus, noting if their email differs, then reads their recorded conversations alongside their logged calls, appointments and activities. A conversation counts as logged when an activity on the same day or the day after mentions the account or opportunity. You get totals, a table of unlogged conversations and a short list of logged activities with no recording, reported as facts rather than a judgement of the rep. Nothing is written.
Business outcome
---
Your CRM activity history catches up with reality, because you know exactly which conversations were never logged.
scenario
-
A Dynamics 365 Sales opportunity can show a late stage and a near close date with very little conversation to back it up. Checking means reading the account's Chorus calls and emails, and working out which customer attendees are not even contacts yet.
What popdock provides
--
Name the opportunity and the period to review. It reads its stage, probability, revenue and close date in Dynamics 365 Sales with the account's contacts, then the Chorus calls, attendees and emails for the account, matching on the distinctive part of the name and saying so. The review shows a conversation timeline, which customer attendees are not in the CRM, gaps such as the main contact never attending, and signals that contradict the stage. It ends with a verdict of supported, at risk or no evidence, and changes nothing.
Business outcome
---
Forecast calls rest on evidence, because each reviewed deal carries a clear supported, at risk or no evidence verdict.
scenario
-
Customer people on a Chorus call often never get added to Pipedrive, and adding them by hand means checking emails, matching their company to an organization and typing each one in. Editing an existing person by mistake can also wipe their other email addresses.
What popdock provides
--
Give the Chorus conversation. It reads the participants, keeps only outside people with an email, and checks Pipedrive for each, leaving existing people untouched. Organizations are matched by company name, with probable matches labelled, and are never created. You see the people to add, those who already exist, near matches by name and anyone skipped for having no email, and nothing is written until you confirm. It stops at the first failure and reads back each new person.
Business outcome
---
Your call participants become Pipedrive people linked to their organization, with existing records left exactly as they were.
scenario
-
Recorded calls that never make it into Pipedrive leave deals looking quieter than they are. Checking a rep's logging means comparing their Chorus conversations with their Pipedrive activities and call logs, day by day.
What popdock provides
--
Give the rep's email and how far back to look. It confirms the rep exists in both Chorus and Pipedrive, reads their recorded conversations and their Pipedrive activities and call logs, and treats a conversation as logged when an entry on the same calendar day names the same company or a similar subject. You get the logging rate, a table of unlogged conversations and, for context, completed activities with no recording. Uncertain matches are marked, facts are reported without judging the rep, and nothing is written.
Business outcome
---
You know your Pipedrive logging rate and exactly which calls to log, without auditing the calendar by hand.
scenario
-
Getting a Chorus call into Pipedrive means copying the summary, finding the right deal, person or organization, and remembering whether it was logged already. Most calls never make it, and some get logged twice.
What popdock provides
--
Give the Chorus conversation and, optionally, whether to attach the note to the deal, person or organization. It reads the call and participants, finds the matching Pipedrive records, and asks you to choose when there is no single match. It checks for a note already carrying that conversation and stops rather than duplicating it. You see the target record and the full note before anything is written, the note is added once after you confirm, and it is read back with its new id.
Business outcome
---
Each call is logged once on the right Pipedrive record, with the summary and attendees intact.
scenario
-
Open deals in Pipedrive can go weeks without a call or email while still sitting in the pipeline as if nothing has changed. Finding the quiet ones means checking each company in Chorus by hand, and by the time someone notices, the buyer has often moved on.
What popdock provides
--
Optionally give a deal owner's email, and choose how many days counts as quiet. It reads open Pipedrive deals, up to the 50 largest, and checks each company once in Chorus for recent calls, meetings and emails, labelling probable name matches. Quiet deals are listed by value with their last touch, deals with email but no calls are shown separately, and deals closing within 30 days are flagged as urgent. Deals with no organization are listed as not checked, a total mismatch is reported as a naming problem rather than silence, and nothing is changed.
Business outcome
---
Quiet Pipedrive deals are spotted while they can still be saved, biggest and most urgent first.
scenario
-
Understanding your history with one contact means checking Pipedrive call logs and activities, then Chorus calls and emails, and lining up the dates yourself. Calls that were recorded but never logged slip through.
What popdock provides
--
Give an email address or name, and how far back to look. It finds the person in Pipedrive, asking you to pick if several match, then gathers their Chorus conversations and emails by email address. Everything is merged into one timeline marked by source, with a short digest of each recorded call, and Chorus conversations with no Pipedrive entry that day are listed as unlogged. Matching is by email only, dates are compared by calendar day, and nothing is changed.
Business outcome
---
You see your whole history with a contact in one timeline, including the calls nobody logged.
scenario
-
Before a call on a Pipedrive deal you want the stage, value and contact, plus everything said with that company in Chorus calls and emails. Pulling it together means searching two systems and rereading old summaries.
What popdock provides
--
Give the deal by id or title, and how far back to look. It reads the deal in Pipedrive, asking which one if several match, then finds the company's Chorus conversations and emails, favouring calls tied to the deal and labelling probable name matches. The brief covers a deal header, conversation digests, emails, what the customer raised, what was promised and the open questions, with a warning if the last touch is over 21 days old. It uses only what was returned, and changes nothing.
Business outcome
---
You go into each deal conversation prepared, knowing what was promised and what still needs settling.
scenario
-
The next step agreed on a call often lives only in the Chorus summary. Scheduling it in Pipedrive means finding the deal, picking an activity type and checking nothing similar is already planned, so it tends to wait until it is late.
What popdock provides
--
Give the Chorus conversation and how many days until the follow-up is due. It reads the agreed next steps from the summary, stopping if there are none rather than inventing one, and finds the matching Pipedrive deal, person and organization. It checks for an open activity that already covers the step, then shows one proposed activity with its type, due date, links and quoted next steps, and tells you who it will be assigned to. Nothing is written until you confirm, only one activity is created, and it is read back.
Business outcome
---
Every call ends with a scheduled Pipedrive follow-up linked to the right deal, without duplicate activities.
scenario
-
A Salesforce opportunity can list a full buying committee while only one person ever turns up to calls. Finding out who has really been engaged means comparing contact roles with Chorus attendees, email by email.
What popdock provides
--
Name the opportunity and how many days of calls to review. It reads the opportunity and its contact roles in Salesforce, then the account's Chorus conversations and attendees, matched at account level when no call names the opportunity. You get a deal summary, a conversation timeline, coverage for each committee member, outside attendees not on the opportunity, and risks such as the primary contact never attending or a close date with no recent call. Contacts with no email are shown as unmatched rather than absent, and nothing is changed.
Business outcome
---
You see who on the buying committee is really engaged, and which deal risks to address before close.
scenario
-
Opportunities closing in the next few weeks need active conversations, but Salesforce does not show whether anyone has spoken to the account lately. Checking means looking up each account in Chorus before the forecast call.
What popdock provides
--
Choose how far ahead to look, how many quiet days to allow and, optionally, an owner. It reads the open Salesforce opportunities closing in the window and checks each account once in Chorus for recent calls, meetings and emails. Deals are grouped into silent, email only and active, each sorted by close date, with the total amount at stake in the silent group. Accounts Chorus does not know are put in silent and marked so, follow-ups are recommended in the report, and nothing is changed.
Business outcome
---
Leaders see how much closing revenue has gone quiet, and which accounts need a call this week.
scenario
-
People you meet on Chorus calls are often missing from Salesforce, or sit there as leads nobody connected to the account. Checking means looking up each outside participant as a contact, then again as a lead.
What popdock provides
--
Choose how far back to look and, optionally, one account. It collects the outside participants from recent Chorus conversations, treating every active Chorus user as internal, and checks Salesforce for each email as a contact and then as a lead. You get known contacts, flagging company names that differ, known leads with their status, and people not in Salesforce ranked by how many calls they joined. It offers to add the missing people as leads but adds nothing, and lists participants with no email separately.
Business outcome
---
You know which people from your calls are missing from Salesforce, ranked by how involved they are.
scenario
-
Recorded calls that never become Salesforce events or tasks leave accounts looking untouched. Measuring how much goes unlogged means comparing a rep's Chorus conversations against their Salesforce activity date by date.
What popdock provides
--
Give the rep's email and the period to compare. It confirms the rep in Chorus and Salesforce, then reads their recorded conversations and their Salesforce events and tasks over the same dates. A conversation counts as logged when an event or task on the same day matches the account or clearly refers to the same meeting. You get the share logged, unlogged conversations, events with no recording shown without treating them as errors, and accounts worked in Chorus with no Salesforce activity. Nothing is written.
Business outcome
---
You see how much of your team's real customer contact is missing from Salesforce, and which calls to log.
scenario
-
Logging a Chorus call in Salesforce means creating a completed task on the right opportunity or account, pasting the summary and attendees, and checking it was not logged already. A follow-up for the next steps often gets forgotten.
What popdock provides
--
Give the Chorus conversation and, optionally, how many days until a follow-up is due. It reads the call and participants, resolves the Salesforce account, the matching open opportunity, a contact and the rep, and checks for an existing task with the same subject. You see the completed task with the summary and attendee list, plus any follow-up task, before anything is created. Tasks are written only after you confirm, at most two, a failure is reported rather than retried, and the stored tasks are shown back.
Business outcome
---
Calls are logged in Salesforce on the right record with their follow-up, once and in a consistent format.
scenario
-
Before an account review you need its Salesforce opportunities and cases next to what was said on recent Chorus calls and emails. Comparing them by hand is slow, and the disagreements, like a deal stage the calls do not support, are easy to miss.
What popdock provides
--
Name the account and the number of days of conversations to include. It finds the account in Salesforce, asking you to pick if several match, and reads its open opportunities and cases, then its Chorus calls, meetings and emails. The brief shows each side, then where they disagree: opportunities with no conversation, stages or next steps the latest calls do not support, and problems raised on calls with no open case. Conversations about deals not open in Salesforce are listed separately, conclusions rest on returned data, and nothing is changed.
Business outcome
---
Account reviews start from one brief that shows where Salesforce and real conversations disagree.
scenario
-
The next step on a Salesforce opportunity is often weeks out of date, even though the latest call agreed something new. Updating it means finding the right call, reading the summary and rewriting the field, which keeps slipping down the list.
What popdock provides
--
Name the opportunity. It checks the deal is open in Salesforce, finds the most recent Chorus conversation with a summary in the last 90 days, and drafts a next step of at most 255 characters saying what happens, who does it and by when. You see the current and proposed next step and the call it came from; a suggested stage change is mentioned but never made. Only the next step field is written, after you confirm, and the stored value is read back. With no clear next step it asks you rather than inventing one.
Business outcome
---
Opportunity next steps reflect what was actually agreed on the latest call, with nothing else on the deal touched.
scenario
-
Client people who join your calls often need to be in Teamwork.com so the delivery team can work with them, but adding them by hand means checking each email and typing details in. Add someone the wrong way and they may get an invite they should never see.
What popdock provides
--
Name the client and how far back to look. It finds the client's company in Teamwork.com, then gathers the outside people from its Chorus calls, leaving out colleagues by email domain, and drops anyone Teamwork.com already has. You see each missing person with their title and number of calls, and confirm, edit or drop them before anything is written. They are added as contacts under the client company, never as administrators and without sending an invite, and names that do not split cleanly are shown to you first.
Business outcome
---
Client contacts from your calls are set up in Teamwork.com under the right company, with no invites sent.
scenario
-
A client whose projects are slipping in Teamwork.com and who has not heard from anyone in weeks is an escalation waiting to happen. Spotting them means checking health scores and late milestones, then searching Chorus for recent contact with each client.
What popdock provides
--
Set the health score that counts as unhealthy and how many quiet days to allow. It finds Teamwork.com projects at or below the threshold or with late milestones, groups them by client, and checks Chorus for recent calls or emails with each. Clients with no recent contact are listed most troubled first, with lowest health score, late milestones, last contact and who it was with. Names too generic to search are reported as unchecked rather than guessed, and nothing is changed.
Business outcome
---
Troubled clients get a call from your team before frustration turns into an escalation.
scenario
-
Before speaking to a client you want to know how their projects are really going in Teamwork.com and what they said on recent calls. Putting delivery and conversation side by side means opening every project and rereading Chorus summaries.
What popdock provides
--
Name the client and how many days of history to cover. It finds the company in Teamwork.com, asking which one if several match, and reads each open project's health score, late milestones and latest update. It then reads the client's Chorus calls and emails, saying when the two systems spell the name differently. The brief gives a one-line headline, a delivery table, the conversations, and anything the client raised that relates to a late milestone or poor health rating, quoted from the summary. Nothing is changed.
Business outcome
---
You speak to every client knowing both their delivery status and what they told your team last time.
scenario
-
Commitments made on a client call often live only in the Chorus summary. Getting them into the right Teamwork.com task list means rereading it, finding the project and checking nothing is already there, so some promises never become work.
What popdock provides
--
Give the Chorus conversation and, optionally, the task list. It reads the summary and pulls out only concrete commitments, with who made them and any dates, and stops if there is no summary. It finds the client's open Teamwork.com project and task list, asks when several match, and drops actions that already have an open task. You see each proposed task with the owner named in its description and confirm, edit or drop them before anything is created. It never invents actions or guesses the project.
Business outcome
---
Client commitments become Teamwork.com tasks in the right list the same day, without duplicating existing work.
scenario
-
Client calls take real time, but they often never make it onto a timesheet in Teamwork.com. Finding the gaps means comparing a person's Chorus call history with their time entries, day by day and project by project.
What popdock provides
--
Give the person's email and a date range. It confirms the person in Chorus and Teamwork.com, reads their client calls with durations in minutes, and reads their logged time for the same dates. A call is covered when a same-day entry sits on the client's project or mentions the call, and one entry can cover several calls if its minutes are enough. You get the uncovered calls with their likely project and the total uncovered minutes. Internal calls are counted but not listed, and nothing is written.
Business outcome
---
Unrecorded client time is caught before invoices go out, with the minutes and likely project for each call.
scenario
-
Logging time for client calls means checking your calendar, working out durations, finding the right Teamwork.com project and making sure you did not log it already. At the end of a busy week, much of that time never gets recorded.
What popdock provides
--
Give the person's email and a date range, and whether time is billable. It reads their Chorus client calls, rounds each up to the nearest 15 minutes, and finds the matching open Teamwork.com project, asking when several match and marking calls with no project as unplaceable. Calls already covered by a same-day entry on that project are skipped. You see every proposed entry and confirm, edit or drop them before anything is written; time is never logged on a project you have not seen, and failures are reported, not retried.
Business outcome
---
Client call time reaches Teamwork.com accurately and once, without rebuilding your week from memory.
scenario
-
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.
What popdock provides
--
Give the Chorus conversation, and say whether the message should be private, which is the default. It reads the call summary and attendees, finds the client's open Teamwork.com project, and stops if a message for this call was already posted. You see a drafted message with who attended, a summary, decisions and follow-ups taken only from the summary, and approve or edit it before it is posted. Pricing, contract terms and anything marked confidential are kept out and listed for you, and notifications stay off unless you ask.
Business outcome
---
The delivery team hears what the client said on the call, in one clear project message, posted once.
scenario
-
A customer often mentions a support problem on a sales call, but the agent working the Zendesk ticket never hears about it. Passing it on means finding the call, picking out the relevant points and adding a note without emailing the customer by mistake.
What popdock provides
--
Give the Zendesk ticket and the Chorus conversation. It reads both and checks they belong to the same customer, by the requester's email among the call participants or a clear company match, and asks you if neither holds. It drafts an internal note with only the points that bear on the ticket and any commitment made, and waits for your confirmation. The note is always private, so the customer is not emailed, and it is read back to confirm it is not public. Closed tickets and calls with nothing relevant get no note.
Business outcome
---
Support agents see what the customer said on the call, in a private note on the right Zendesk ticket.
scenario
-
Customers raise bugs, outages and billing problems on sales calls that never reach support. Checking whether each one already has a Zendesk ticket means reading the summary, working out who the customer people were and searching their tickets.
What popdock provides
--
Give the Chorus conversation. It reads the summary and lists each distinct problem the customer raised, ignoring commercial topics unless they describe a fault. It identifies the customer participants and searches Zendesk for their recent tickets, falling back to the organization when needed. You get each problem with the matching ticket, its status and priority, or none, and a list of problems with no ticket. Customers with no Zendesk record are noted, and nothing is created or changed.
Business outcome
---
Problems raised on calls do not fall through the cracks, because you can see which ones have no ticket yet.
scenario
-
Support and sales see different halves of the same customer: open tickets in Zendesk, conversations in Chorus. Before a renewal or escalation call, combining them means searching both systems and matching up issues by eye.
What popdock provides
--
Name the organization and how far back to look. It confirms the organization in Zendesk and reads its unresolved tickets by priority, then finds the matching Chorus account, asking which one if the name matches several, and reads recent calls and emails. The brief gives a status line, support and sales tables, issues that show up on both sides with ticket and conversation side by side, and up to three risks and next steps. It never implies an account is healthy just because there are no tickets, and changes nothing.
Business outcome
---
Support and account teams share one view of the customer, including the issues both sides are hearing about.
scenario
-
A bad Zendesk satisfaction rating should lead to a conversation from the account team, but sales rarely sees those ratings. Checking means grouping ratings by account and searching Chorus for any call since.
What popdock provides
--
Choose how far back to look and how many accounts to cover. It reads the bad Zendesk satisfaction ratings, groups them by organization or requester, and checks Chorus for conversations with each since the earliest bad rating, noting whether the support experience came up. The table runs worst first with the reason, conversations since and who held them, followed by the accounts nobody has spoken to. Partial name matches are labelled, and nothing is changed.
Business outcome
---
Unhappy customers hear from their account team quickly, starting with those nobody has spoken to since the rating.
scenario
-
When a support ticket comes in, the customer may already have raised the same problem with their account manager weeks earlier. Finding out means searching Chorus by hand for their calls and emails around the ticket date, then reading each summary to see whether the issue came up.
What popdock provides
--
Give a Zendesk ticket number, and optionally how many days either side to search, and it reads the ticket and the customer's own words, then finds the requester's Chorus calls and emails in that window. If the requester appears on no call, it falls back to searching by their organization and says that match is weaker evidence. You get a dated table of each conversation, whether the issue came up with a short quote, and whether sales heard about it before support did. Nothing in Zendesk or Chorus is changed.
Business outcome
---
Support sees what the customer already told sales, so nobody asks them to repeat the story and slow hand-offs come to light.
scenario
-
A customer mentions a bug or outage on a sales call, and it is up to the account manager to remember to raise a support ticket afterwards. Doing it by hand means rereading the call notes, checking Zendesk for an existing ticket, and writing it up without letting internal pricing or deal notes slip into what the customer sees.
What popdock provides
--
Name the Chorus conversation, and optionally the issue, and it reads the call summary and picks the customer who raised the problem as the requester, asking when that is unclear. It checks Zendesk for the requester and for an unresolved ticket from the last 60 days that already covers the problem, and stops if one exists. You see a draft written to the customer with no sales notes, pricing or deal details, and the ticket is created once, only after you confirm, then read back. If the requester is new to Zendesk, it tells you they will be added as an end user.
Business outcome
---
Problems raised on calls reach support as one clean ticket, without duplicates and without internal deal details shown to the customer.
scenario
-
Buyers join calls that sales never records as contacts. Finding them means opening each recent Chorus conversation for an account, copying out the customer attendees and searching HubSpot for every email, so new stakeholders often never make it into the CRM.
What popdock provides
--
Name an account and a lookback period, and it reads the account's recent Chorus conversations, collects the customer-side attendees with an email and checks each one in HubSpot. You get a numbered list of the people who are missing, with title, company and how many calls they joined, and you choose who to add. Only the people you pick are created, your own colleagues are never added, and each new contact is read back to confirm it exists.
Business outcome
---
Every buyer who shows up on calls becomes a HubSpot contact, without copying names from call recordings.
scenario
-
Support picks up a HubSpot ticket without knowing what sales has already told the customer. The calls and emails are in Chorus, so agents either ask sales or go in blind and repeat or contradict a promise.
What popdock provides
--
Give a ticket ID, and it reads the ticket and its company in HubSpot, then pulls the company's Chorus calls and emails from shortly before the ticket opened until it closed. You get the ticket summary, what was said before and during it, any calls that raised the same problem, and the commitments or frustrations support should know about. It only paraphrases what Chorus recorded and changes nothing in either system.
Business outcome
---
Support handles each ticket knowing what the customer was told, without chasing sales for context.
scenario
-
Reps hold calls and meetings recorded in Chorus but forget to log them in HubSpot, so account history looks thinner than it is. Finding the gaps means comparing each conversation with the company's activity by hand.
What popdock provides
--
Set a lookback period and optionally one rep, and it lists the Chorus conversations, matches each account to a HubSpot company and checks for a call or meeting logged around the same date. You get the unlogged conversations with their IDs, the accounts that are not in HubSpot at all, likely matches to double check, and totals. It only reads, and each result can be logged later with the matching log prompt.
Business outcome
---
Close the gaps in HubSpot activity history without auditing calendars rep by rep.
scenario
-
A deal due to close this month with no recent customer conversation is a forecast risk, but spotting one means cross-checking every closing deal against call recordings. Most teams only find out when the deal slips.
What popdock provides
--
Set how far ahead to look and how long counts as quiet, optionally for one owner, and it reads the open HubSpot deals closing in that window and checks Chorus for recent conversations with each company. Every deal is marked silent, account-only or covered, silent ones first, with the total value at risk and the last conversation for account-only deals. Nothing is changed in either system.
Business outcome
---
Find closing deals nobody is talking to, while there is still time to act.
scenario
-
HubSpot shows what the pipeline says about a company, but Chorus holds what customers actually said. Preparing for a meeting means reading both and noticing where they disagree, which rarely happens under time pressure.
What popdock provides
--
Name a company and a lookback period, and it reads the HubSpot company with its open deals and tickets, then the company's recent Chorus calls, meetings and emails. You get the company profile, open deals, open tickets, recent conversations with one-line digests, and a section showing where they disagree: deals with no recent conversation, stages the calls do not support, and problems raised that have no ticket. Nothing is changed.
Business outcome
---
A briefing that shows where the CRM and the customer conversations disagree before your next meeting.
scenario
-
Call summaries live in Chorus, but the team works from HubSpot, so the record of what was agreed never reaches the deal. Copying it across by hand is slow, and easy to do twice or put on the wrong record.
What popdock provides
--
Give a Chorus conversation ID, and it reads the call summary and attendees, finds the matching HubSpot company and, where the opportunity name matches, the deal. It checks the conversation has not already been logged, then drafts a note with the date, rep, attendees, summary and next steps. Nothing is written until you confirm, exactly one note is added, and it reads back to confirm the note exists. Deal stages are never changed.
Business outcome
---
Call outcomes reach the right HubSpot deal or company once, without retyping summaries.
scenario
-
A deal's stage, amount and close date in HubSpot are only as good as the rep's optimism. Checking them against what the customer actually said means listening back to calls or reading summaries in Chorus.
What popdock provides
--
Name a deal and a lookback period, and it reads the deal and its company in HubSpot, then the company's Chorus conversations, separating the ones about this deal from general account calls. You get the conversations with one-line digests, the customer attendees, a verdict of supported, not supported or no evidence for stage, amount and close date with the words that justify it, and the risks raised. Nothing is changed.
Business outcome
---
Test every deal's forecast against what the customer actually said, before you commit it.
scenario
-
Managers who want to know whether a rep's logged CRM work matches their real call volume have to open Nutshell for tasks and activities, then Chorus for calls, and line the numbers up by hand. Calls that never get logged go unnoticed.
What popdock provides
--
Name a rep and a period, and it reads that rep's Nutshell tasks and activities and their Chorus call count and talk time for the same dates. It places the two side by side so gaps are easy to see. Nutshell activities cannot be filtered by rep, and it says so rather than guessing. If the rep name is ambiguous it stops and asks. Nothing is changed in either system.
Business outcome
---
Managers see logged CRM work next to real call volume and spot unlogged calls without compiling two reports.
scenario
-
Deals near their close date should have recent conversations, but the deals live in Nutshell and the recorded calls live in Chorus. Managers cannot easily see which deals have had no call, so at-risk deals look fine until they slip.
What popdock provides
--
Give a closing window and a call lookback, and it reads the open Nutshell leads closing in that window, then checks Chorus for calls with each lead's company. It lists the deals with no recent call, ranked by value. It checks at most 30 leads, and leads with no company are listed as unmatched rather than as having no calls. It only reads, nothing is changed.
Business outcome
---
Managers see which closing deals have gone without a recorded call, ranked by value, before they slip.
scenario
-
Calls recorded in Chorus have to be retyped into the CRM, and that happens late, twice or not at all. A Nutshell activity cannot be edited or deleted once it is created, so a wrong entry stays.
What popdock provides
--
Name a rep or account and a period, and it reads the Chorus calls and the Nutshell activities already logged, then lists the calls that are missing from Nutshell. You choose which specific rows to log, and nothing is written until you approve them. It warns you that activities cannot be edited or deleted afterwards, and skips calls with no usable start time.
Business outcome
---
Recorded calls appear in the CRM once, with nothing logged that you did not approve.
scenario
-
Before a meeting a rep checks Nutshell for the account's deals and then searches Chorus for its recorded calls and emails. Few have time to do both, so they miss how much contact has really happened and when the account was last touched.
What popdock provides
--
Name an account and it reads the open leads from Nutshell and the calls and emails from Chorus for the same company. It compares the last contact dates in each system and shows them side by side. If the account name is ambiguous it stops and asks, and if the account is not in Chorus it says so rather than guessing a match. It only reads, nothing is changed.
Business outcome
---
Reps see deals and real conversations together before a meeting, and know how recent the last contact was.
scenario
-
Coaching a deal means opening the lead in the CRM and then hunting through Chorus for the scorecards of its calls. The two systems are not connected, so the coaching conversation starts without the evidence.
What popdock provides
--
Name a Nutshell deal and it reads its status, confidence and company, then finds the Chorus calls for that company and their scorecard scores. It shows the deal and the scores side by side. Calls that were not scored are listed as unscored rather than as zero, and it looks at no more than 10 calls. It only reads, nothing is changed.
Business outcome
---
Managers coach a deal with its status and call scores in front of them, in one request.
scenario
-
Finding every recorded conversation with a contact means looking up their email in the CRM and then searching the call tool by hand. It takes several steps for one person, so it rarely gets done before a follow-up.
What popdock provides
--
Name a Nutshell contact and it finds the person and their email in Nutshell, then looks for the Chorus conversations they took part in. It lists the conversations with dates and participants and does not print phone numbers. If the name matches several people it stops and asks, and a contact with no email is reported as unmatchable. It only reads, nothing is changed.
Business outcome
---
Reps see every recorded conversation with a contact in one request, ready for the next follow-up.
No items found.
Ready to unlock your data?
Start building tools that turn your business systems into AI superpowers
Join forward-thinking companies that are transforming their operations with intelligent, secure AI automation.