CRM
Nutshell
Connect your AI to Nutshell
Sales reps, sales managers, and sales operations and CRM administrators run their pipeline through Nutshell, but the answers they need are spread across leads, companies, people, activities and tasks. AI can bring them together, but only if it works within what the connected Nutshell user is permitted to see and change, confirms before any record is created, changed or deleted, and shares personal contact details only as far as the request needs.
Why it matters
Capabilities that matter most for Nutshell
01
Pipeline answers across every list
Ask about leads, companies, people, activities, tasks, notes and products in one conversation instead of opening each Nutshell list on its own.
02
Confirmed changes to records
Add, update and delete companies, people and leads, and log activities, with an explicit confirmation before any record is created, changed or deleted.
03
Permissions that carry over
AI sees and changes only what the connected Nutshell user is permitted to, so each rep works within their own access.
03
Ready-made prompts for sales work
Prompt apps cover pipeline review, overdue work, account briefings and win rate by source, and combine Nutshell with Chorus, Constant Contact, GoTo Webinar and Mailchimp.
Use cases
Example AI Use Cases for Nutshell
scenario
-
Getting CRM contacts onto an email list means exporting or retyping them, then hoping nobody is added twice or mailed without permission. Typos creep in, duplicates pile up, and there is no quick way to see who is already on the list.
What popdock provides
--
Give the Nutshell owner and the Constant Contact list name, and it confirms the list matches exactly one list, then checks each of that owner's Nutshell contacts against Constant Contact by email. It shows the exact people who would be added, with name, email and job title, and asks you to confirm you have permission to market to them. Nothing is written until you say yes, and each added address is read back afterwards. Nutshell is never changed.
Business outcome
---
The right contacts reach the right email list once, with permission confirmed and each addition checked afterwards.
scenario
-
Duplicate companies and people build up in a CRM as reps add records by hand. Leads, notes and tasks end up split across the copies, so nobody sees the full history of an account and reports count the same customer twice.
What popdock provides
--
Say whether to sweep companies or people, and it scans the Nutshell records for likely duplicates by name, email and similar details. For each group it shows the copies side by side with the leads and notes attached and recommends which one to keep. It only proposes, nothing is merged or deleted, and it says when the sweep was capped at 500 records so you know what was not checked.
Business outcome
---
You see which duplicates are worth fixing and which copy to keep, without touching any record.
scenario
-
Contacts on open deals sometimes unsubscribe in Mailchimp, and the rep emailing them from the CRM never sees it. Nobody compares the two systems, so opted-out people keep getting email and the deal suffers.
What popdock provides
--
Name a Nutshell owner and it lists their open leads and the people on them, then checks each person's email in Mailchimp. People who are unsubscribed, cleaned or not in Mailchimp at all are flagged. Contacts with no email are listed separately and never treated as safe, and it warns when the results may have been cut off. It only reads, nothing is changed in either system.
Business outcome
---
Reps know who not to email on their open deals, and opted-out contacts stop getting messages by mistake.
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
-
Before an account review, nobody checks whether the people on the account registered for or attended your webinars, because it means looking up each contact in two systems. Webinar behaviour that signals interest never makes it into the conversation.
What popdock provides
--
Name a Nutshell company and it lists the people on that account, then checks GoTo Webinar for their registrations and attendance by email. It shows who registered, who attended and who did neither, next to the account's open leads. If it finds no webinar activity it says so rather than guessing. It only reads, nothing is changed in either system.
Business outcome
---
Account reviews include real webinar interest from the people on the deal, found in one request.
scenario
-
Reps add a new company and its first contact by hand, and often do not check whether either already exists. The result is duplicate companies, duplicate people and a contact that is not tied to any account.
What popdock provides
--
Give a company name and optionally a person, and it checks Nutshell for existing companies and people first. You see exactly what would be created and nothing is saved until you confirm. It creates only the records you approved and never updates or deletes anything. It also warns you that the new person is not linked to the company automatically.
Business outcome
---
New companies and contacts are added once, after a duplicate check, with nothing saved until you confirm.
scenario
-
Deleting a company, person or lead in Nutshell cannot be undone, and the screen does not show everything attached to it. Leads, notes and tasks can disappear with the record, and a similar name makes it easy to delete the wrong one.
What popdock provides
--
Name the record to remove and it finds exactly one match, refusing to act on fuzzy ones. It shows the leads, notes and tasks linked to it, then asks you to type the record id to confirm. Only one record is deleted per request, and nothing is added or updated. If you do not confirm the id, nothing is deleted.
Business outcome
---
Records are deleted only when you have seen what hangs off them and confirmed the exact id.
scenario
-
Customers who spend heavily in a Mailchimp connected store do not always exist in the CRM. Nobody notices without exporting both lists and comparing them, so valuable buyers never get an owner or a lead.
What popdock provides
--
Give a spend threshold and it finds the Mailchimp store customers above it, then looks for each one in Nutshell people and companies. A match on email is accepted, and a match on name alone is shown only as a possible match. It lists who is missing from the CRM. It only reads and never adds records to Nutshell.
Business outcome
---
High-spending customers who are missing from the CRM are listed, so sales can add them deliberately.
scenario
-
Accounts with open deals quietly go uncontacted because nobody sorts companies by when they were last touched. The CRM does not surface them, so a large deal can sit for weeks with no logged activity.
What popdock provides
--
Give a number of days and it checks Nutshell companies for their most recent logged activity and their open leads. It lists the companies with no recent contact, ranked by the value of their open leads. Companies that have never been contacted are reported rather than skipped, and it checks at most 30 companies per run and says so. It only reads, nothing is changed.
Business outcome
---
Reps and managers see which valuable accounts have gone quiet, ranked by what is at stake.
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
-
Tasks and activities that have slipped sit in separate Nutshell lists, so a manager checks each one to see what is overdue. Items get lost, and nobody can see at a glance who is behind and on which accounts.
What popdock provides
--
Ask for overdue work, optionally for one person, and it reads the Nutshell tasks and activities that are past due. It groups them by assignee with the company or lead each one relates to. If a user name matches more than one person it stops and asks, and it never invents an assignee. It only reads, nothing is changed.
Business outcome
---
Managers get one list of overdue work by person and account instead of checking each list by hand.
scenario
-
People who unsubscribe or bounce in Constant Contact can still sit on open deals in Nutshell. The sellers emailing them never see the suppression, so opted-out people keep getting mail and bad addresses stay in the pipeline.
What popdock provides
--
Give a lookback period and it reads recent Constant Contact unsubscribes and bounces, separating unsubscribes, hard bounces and soft bounces. It then matches them to Nutshell people who are on open leads, accepting a match only when the email address matches. You get a list of affected people with their leads. It only reads and writes nothing in either system.
Business outcome
---
Sellers know which people on open deals have opted out or bounced, before they send another email.
scenario
-
After a webinar, reps do not know which attendees already have live deals, so the hottest follow-ups wait while cold contacts get called. Matching the attendee list to the CRM is a manual spreadsheet job.
What popdock provides
--
Name a webinar and it lists the attendees from GoTo Webinar, then matches them to Nutshell people by exact email. Attendees with open leads are ranked by lead value so the biggest opportunities come first. It does not add up values across different currencies. It only reads, nothing is changed in either system.
Business outcome
---
Reps follow up with the attendees who matter most first, ranked by the value of their open deals.
scenario
-
Finding the people who registered but did not attend means comparing two exports by hand. The no-shows with deals in play are the ones who most need the recording, and they are the ones who never get it.
What popdock provides
--
Name a webinar and it finds the registrants who did not attend, then matches them to Nutshell people with open leads by exact email. It lists them for follow-up with their leads and, where available, the webinar recording. If the webinar has not happened yet it stops. It only reads and never registers anyone or changes the CRM.
Business outcome
---
No-shows with live deals get the recording and a follow-up, instead of being lost in two exports.
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
-
Calls and meetings are logged in the CRM late or twice, and once an activity is created the Nutshell API cannot edit or delete it. A duplicate or wrong entry stays in the history for good.
What popdock provides
--
Describe the call or meeting and the account, and it checks Nutshell for an existing activity that matches before anything is written. It shows you the details it will log and warns that activities cannot be edited or deleted afterwards. The activity is created only after you confirm, and nothing else is changed.
Business outcome
---
Calls and meetings are logged once and correctly, because nothing is saved until you have confirmed the details.
scenario
-
After an email campaign, the people who clicked sit in a Constant Contact report. Nobody matches them to CRM contacts and open deals, so the warmest prospects are not called and clickers who are not in the CRM at all are missed.
What popdock provides
--
Name a Constant Contact campaign and it lists the people who clicked, then matches them to Nutshell people by email address, never by name. For each match it shows the open leads so a rep knows who to call first, and it lists clickers who are not in Nutshell. If the campaign name matches more than one campaign it stops and asks. It only reads, nothing is added or changed.
Business outcome
---
Reps call the campaign clickers who have live deals first, and marketing sees who is missing from the CRM.
scenario
-
Marketers export a webinar's registrants and eyeball them against the CRM. New leads and existing customers get mixed up, and nobody knows which registrants the sales team already works with.
What popdock provides
--
Name a webinar and it lists the registrants from GoTo Webinar, then checks Nutshell people for each one. A match counts only on an exact email. A match on name alone is labelled possible, and anyone with no match is labelled new to the CRM. It only reads, and nothing is added, updated or deleted in either system.
Business outcome
---
Marketing knows which registrants are existing contacts and which are new, without comparing two exports.
scenario
-
Before a call, a rep opens a company in Nutshell, then its people, leads, tasks and notes one after another. The context is spread over several screens, so key details get missed in the few minutes available.
What popdock provides
--
Name a company and it builds a one-page briefing from Nutshell: the people on the account, open leads, upcoming and overdue tasks, recent notes and recent activity. If the company name matches several records it stops and asks which one. The briefing reports only what Nutshell returned and never fills gaps with guesses. It only reads, nothing is changed.
Business outcome
---
Reps walk into a call with the whole account in front of them after one request.
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
-
Sellers cannot tell which people on their open deals actually read marketing email. Opens and clicks live in Constant Contact and the deals live in Nutshell, so follow-up goes to the wrong deals and engaged buyers are overlooked.
What popdock provides
--
Name a Nutshell owner and it reads their open leads and the people on them, then looks up each person's opens and clicks in Constant Contact. It ranks the people by engagement and highlights warm leads and high-value leads that have gone silent. People who are not in Constant Contact are reported as not in email marketing rather than as having zero engagement. It only reads, and writes nothing to leads or activities.
Business outcome
---
Sellers know which deals have engaged readers and which valuable ones have gone quiet.
scenario
-
Staff retype a CRM contact's details into the webinar tool to register them. That invites typos and duplicate registrations, and nobody checks first whether the person is already signed up.
What popdock provides
--
Name the Nutshell contact and the webinar, and it looks up the person in Nutshell and checks GoTo Webinar for an existing registration. It shows the details it will use and waits for your explicit yes before the single registration is made. It never invents missing details and never deletes a registration. Afterwards it checks that the registration landed.
Business outcome
---
Contacts are registered once, with the right details, after you have approved them.
scenario
-
Marketing exports CRM contacts and compares them to the email list in spreadsheets. New contacts go unmailed, and people who have not given permission to send are easy to miss. The comparison is out of date almost as soon as it is done.
What popdock provides
--
Name a Nutshell owner and it reads their contacts and checks each email in Constant Contact. It lists the contacts that are missing or that do not have permission to send, with the people on open deals first. Contacts without an email are skipped and listed, and a contact counts as present if any of their addresses matches. It only reads, and nothing is added or updated in either system.
Business outcome
---
Marketing gets a current list of CRM contacts who are not on the email list, with deal contacts first.
scenario
-
Win rate by lead source is put together in spreadsheets from CRM exports. It takes time and is out of date quickly, so leadership argues about which sources work without current numbers.
What popdock provides
--
Give a period and it reads the leads closed in that time from Nutshell and groups them by source and outcome. You get win rates and values per source. Dates are checked first, missing values are shown as unknown, and sources with fewer than 3 closed leads are left out so small samples do not mislead. It only reads, nothing is changed.
Business outcome
---
Leadership sees current win rates by source on request, without building a spreadsheet.
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
-
Reps scan the CRM by hand for leads that are about to close. The ones that are past due, or that have tasks nobody has done, are easy to miss, so deals slip without warning.
What popdock provides
--
Name an owner and a closing window, and it reads their open leads closing in that time from Nutshell and the tasks attached to them. It flags leads that are past their close date and those with overdue tasks, then ranks them by weighted value. It does not guess status values, and it only reads, so nothing in Nutshell is added, updated or deleted.
Business outcome
---
Reps start the week knowing which closing deals are at risk and which are worth the most.
scenario
-
Before a call, a rep finds the contact in Nutshell, then searches Constant Contact by hand to see whether they opened or clicked anything. It is slow enough that most skip it, so reps call people without knowing whether they have unsubscribed or been reading email.
What popdock provides
--
Name a Nutshell contact and it finds the person in Nutshell, then matches them to Constant Contact by email. It reports their opens, clicks, bounces and unsubscribes over a lookback window you choose. If the contact matches several people or none, it stops and asks. A contact missing from Constant Contact is reported as no match rather than zero engagement. It only reads, nothing is changed.
Business outcome
---
Reps know a contact's email engagement and opt-out status before they pick up the phone.
scenario
-
Questions asked during a webinar sit in a report with no sign of who asked them or whether they are a customer. Answers go to the wrong people or to no one, and a question from a big prospect looks the same as any other.
What popdock provides
--
Name a webinar and it lists the questions asked from GoTo Webinar, then matches each asker to Nutshell by exact email. For each match it adds the contact, the account owner and any open leads. Askers who are not found in Nutshell are grouped separately. It only reads, and nothing is added or changed in either system.
Business outcome
---
Webinar questions reach the right owner with the account and deal context already attached.
scenario
-
Reps check Mailchimp by hand for a contact they found in the CRM, copying email addresses between tools. They miss opt-outs and the contact's other email addresses, so they do not see the full picture of how the person engages.
What popdock provides
--
Name a Nutshell contact and it looks the person up in Nutshell, then builds their Mailchimp profile by email: audience subscription, campaigns received, unsubscribes and store purchases. If more than one contact matches, or none, it stops and asks. Addresses that are missing from Mailchimp are reported as such. It only reads, nothing is changed.
Business outcome
---
Reps see a contact's subscription status, email engagement and purchases in one answer before they reach out.
scenario
-
Deciding who on a lead to approach means checking each person in Mailchimp one at a time. Someone who has unsubscribed or whose address has bounced is easy to email by mistake, and the best-engaged person is hard to spot.
What popdock provides
--
Name a Nutshell lead and it reads the lead, finds the people attached and their email addresses, then checks each one in Mailchimp. It reports each person's engagement and marks anyone unsubscribed or cleaned as do-not-email. Ambiguous name matches are flagged for you to check. It only reads, nothing is changed in either system.
Business outcome
---
Reps pick the right person to approach on a lead and avoid emailing anyone who opted out.
scenario
-
A Mailchimp campaign shows who opened it, but not whether those people have live deals. Reps do not know which openers are already in the pipeline, so warm interest goes unfollowed.
What popdock provides
--
Name a Mailchimp campaign and it finds the repeat openers, then matches each to Nutshell by email, or by name and company together. For every match it shows the open leads and their owners. Ambiguous matches are flagged, and if the campaign cannot be found it stops. It only reads, and nothing is added or changed in either system.
Business outcome
---
Reps follow up with campaign openers who already have deals, while the interest is fresh.
scenario
-
Adding a CRM contact to a Mailchimp audience by hand risks duplicates, and it is easy to re-subscribe someone who opted out. There is no quick check of whether the person is already a member before they are added.
What popdock provides
--
Name a Nutshell contact and a Mailchimp audience, and it finds the person in Nutshell and checks the audience for an existing membership. You see what it will add and nothing is written until you confirm. It never re-subscribes people who unsubscribed or were cleaned, and it stops if the contact or the audience is ambiguous. Afterwards it checks that the member was added.
Business outcome
---
Contacts are added to the right audience once, and people who opted out stay opted out.
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.