CRM
Salesforce
Connect your AI to Salesforce
Sales reps and managers run every revenue decision through Salesforce, but accurate pipeline answers require system access and navigation skills most sales leaders don't have. AI can close that gap, but only if it respects the territory boundaries, role restrictions, and approval rules the organization actually runs on.
Why it matters
Capabilities that matter most for Salesforce
01
SOQL lists and calculated fields
Write lists as SOQL queries and add SOQL calculated fields, so pipeline, territory and account rollups come back exactly as your org defines them.
02
Over 100 ready-made AI tools
Install Salesforce MCP tools, prompts, lookups and API endpoints from the app store instead of building each one.
03
Pipeline beside billing and support
Joined and comparison lists put Salesforce opportunities and accounts next to ERP, billing or helpdesk data for one view of the customer.
03
Governed by role and team
AI tools answer within per-user and per-team security and field redaction, and changes run only through actions you approve.
Use cases
Example AI Use Cases for Salesforce
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
-
A Salesforce campaign has its member list, but the email itself goes out from Constant Contact, so someone has to copy the members across. Done by hand, people who unsubscribed sneak back in, existing contacts are duplicated, and consent is assumed rather than recorded.
What popdock provides
--
Name the Salesforce campaign and the Constant Contact list, and it reads the campaign members with an email and compares them with the list's current members. Missing people are split into new to Constant Contact, who will be created on the list, and existing contacts, listed for you to add by hand; anyone who unsubscribed is excluded. Nothing is added until you confirm, and permission stays unset unless you say they gave express consent. The list is never created, and you get a result for each person.
Business outcome
---
Your Salesforce campaign audience matches your email list, with unsubscribes respected and no duplicate contacts.
scenario
-
Clickers from a Constant Contact campaign are worth following up, but only if they reach Salesforce as leads, and only once. Checking each person against contacts and leads, then filling in names, companies and titles by hand, means many never make it.
What popdock provides
--
Name the Constant Contact campaign, and optionally a lead source, Constant Contact by default, and it collects the unique clickers and their details. Anyone already a contact or lead in Salesforce is dropped. Salesforce needs a last name and a company, so people missing either go in a separate table and no values are invented for them. Leads are created only after you confirm, with a fresh duplicate check if the confirmation took a while, and one failure does not stop the rest.
Business outcome
---
Campaign clickers become Salesforce leads with real details, never twice and never with made-up data.
scenario
-
The email lives in Constant Contact, the members, responses and won deals live in Salesforce, and nobody puts them side by side. Judging whether the email actually drove the Salesforce result means pulling both reports and working out how much the audiences overlap.
What popdock provides
--
Name the Constant Contact campaign, and optionally the Salesforce campaign if its name differs, and it reads sends, opens, clicks, bounces and opt-outs next to Salesforce members, responses, opportunities, won value and cost. It measures how many clickers are campaign members and how many responders never clicked. Rates are worked out against sends and shown as not applicable when there were none, and cost per response appears when cost is set. If the overlap is tiny it says the campaigns may not target the same audience, and nothing is changed.
Business outcome
---
You can judge whether your email moved the Salesforce campaign result, based on audience overlap rather than assumption.
scenario
-
A rep about to call someone wants to know their open opportunities and campaign history in Salesforce, and whether they have been opening or ignoring your emails in Constant Contact. Checking both takes time, and an unsubscribe or hard bounce on a key contact is easy to miss.
What popdock provides
--
Give an email address, and optionally a look-back period, 90 days by default, and it finds the person as a Salesforce contact or lead, reporting every match if there are several. For a contact you see the account's open opportunities and their campaign memberships and responses. From Constant Contact comes their permission, tags and a dated table of opens, clicks with links, bounces and unsubscribes. A short read flags anything sales should know, such as a hard bounce on someone with an open opportunity, and nothing is changed.
Business outcome
---
Reps see a person's deals and email engagement together, and catch an opt-out before it becomes an awkward call.
scenario
-
Some of the people clicking your Constant Contact campaigns are new to you, but you only find out by checking each email against Salesforce contacts and leads. Without that check, fresh interest never reaches sales. For a large campaign that check takes an afternoon, so it usually gets skipped.
What popdock provides
--
Name the Constant Contact campaign, and optionally how many people to check, 50 by default, and it collects the unique clickers, most clicks first. Each email is looked up in Salesforce as a contact, then as a lead. The people found in neither are enriched from Constant Contact with name, company, job title and the links they clicked. You get a table of those unmatched people and a count line, it says how many went unchecked if the limit was reached, and nothing is created or changed.
Business outcome
---
You get a clean list of new prospects from each campaign, ready to hand to sales.
scenario
-
Salesforce owners keep emailing contacts who unsubscribed or whose address bounced in Constant Contact, because nothing tells them. On accounts with open opportunities, that gap can cost a deal. Matching every opt-out and bounce to a Salesforce record and its owner by hand is slow enough that it rarely happens.
What popdock provides
--
Pick a look-back period, 30 days by default, and it collects every unsubscribe and bounce in Constant Contact and matches each email to a Salesforce contact or lead. For contacts it checks whether the account has open opportunities. You get separate tables for unsubscribes and bounces, sorted by owner with open opportunities flagged first, and temporary bounces such as a full mailbox are labelled as such. It treats an unsubscribe as a consent signal it does not try to change, and nothing is updated.
Business outcome
---
Owners learn which contacts opted out or bounced, live deals first, before they send the next email.
scenario
-
A click on a campaign is a buying signal, but in Salesforce it disappears unless someone creates a follow-up task. Doing that for every clicker means finding their contact or lead, checking nobody has a task already, and noting what they clicked.
What popdock provides
--
Name the Constant Contact campaign, and optionally an assignee and a due window, three days by default, and it matches each clicker to one Salesforce contact or lead. Emails that match several records go to a needs review list, and anyone who already has a task for this campaign is skipped. The assignee is checked as an active user, otherwise the task goes to the record owner. You see each planned task with the links clicked before anything is created, then a result per person.
Business outcome
---
Every campaign click becomes one follow-up task on the right Salesforce record, with no duplicates.
scenario
-
Reps with dozens of open Salesforce leads have no easy way to tell who is warming up. The signal is in Constant Contact, who opened and clicked recently, but checking each lead there takes longer than calling down the list. Meanwhile the warmest leads wait their turn.
What popdock provides
--
Optionally name an owner, a look-back period, 30 days by default, and how many leads to check, and it reads open, unconverted Salesforce leads with an email. Each lead's opens and clicks in Constant Contact are counted and scored, with a click worth three opens, and leads with no engagement are counted rather than ranked. You get a ranked table with the top link clicked and a suggested follow-up for the top five. It warns when opens may be inflated by mail privacy features, and nothing is changed.
Business outcome
---
Reps call the leads who are actually engaging first, instead of working down the list in date order.
scenario
-
Turning webinar attendees into Salesforce leads means checking every email against contacts and leads first, then filling in a company GoTo Webinar never captured. Skip the check and you create duplicate leads for people who are already customers.
What popdock provides
--
Name the webinar, and optionally a minimum time and lead source, and it reads the attendees and checks each email against Salesforce contacts, then leads. Only people unknown to Salesforce go forward, and ambiguous matches are listed, never picked. A business email domain is proposed as the company, and personal addresses wait for you to supply one. You review and edit the list, nothing is created until you confirm, and duplicate emails produce at most one lead.
Business outcome
---
New webinar attendees become Salesforce leads with no duplicates of existing contacts or leads.
scenario
-
Sales wants webinar attendance recorded on each contact or lead in Salesforce, but logging a task per attendee by hand is slow. Done twice, the same person shows two attendance tasks for one webinar and the activity history looks inflated.
What popdock provides
--
Name the webinar, and optionally a task status, and it reads the attendees and matches each email to a Salesforce contact, then lead, never on name alone. Anyone who already has a task for this webinar is skipped, and unknown or ambiguous attendees get nothing. You see the list and nothing is created until you confirm. Each match gets one task with minutes attended and the webinar date, and a rejected status stops the run after the first failure.
Business outcome
---
Webinar attendance shows on every matched Salesforce contact and lead exactly once, ready for sales follow-up.
scenario
-
After a webinar, reps need to know who to call first, but engagement such as time attended and questions asked sits in GoTo Webinar while lead status and open deals sit in Salesforce. Ranking attendees by hand rarely gets past the first few names on the list.
What popdock provides
--
Name the webinar and how many to rank, and it scores each attendee on minutes attended, questions asked and polls answered, showing each part of the score. The top attendees are matched to Salesforce contacts and leads by email, with open opportunities read for contacts. Each is placed in call now, nurture, not in Salesforce or check for ambiguous matches. Missing poll or question data is named rather than hidden. Nothing in GoTo Webinar or Salesforce is changed.
Business outcome
---
Reps call the most engaged attendees with open opportunities first, guided by a score they can inspect.
scenario
-
A webinar's Salesforce campaign should reflect who registered and attended, but members get added late, responses go unmarked and some registrants never make it in. Campaign reports then understate the event and its influence on pipeline.
What popdock provides
--
Name the webinar, and optionally the campaign, and it reads registrants and attendees, then finds the matching Salesforce campaign and its members. Everyone is compared by email only and placed as attended, no-show, webinar only or campaign only. Members whose responded flag disagrees with attendance are flagged, and duplicates and members with no email are listed. It ends with the biggest gap and what would close it, without doing it.
Business outcome
---
Your campaign results match who really registered and attended, with every gap listed.
scenario
-
Questions asked in a webinar often signal buying interest, but they sit in GoTo Webinar where account owners never see them. Routing each one means finding the asker in Salesforce, identifying the record owner and creating a task for them by hand.
What popdock provides
--
Name the webinar and it reads the questions, unanswered ones by default, grouped by asker. Each asker is matched to a Salesforce contact or lead by email, and each owner is resolved to an active user, left unresolved rather than guessed. You see the questions and owners and confirm which rows get a task. Each confirmed asker gets one task with their questions, set to high priority when any are unanswered. Unknown askers and anonymous questions are listed for a person to pick up.
Business outcome
---
Every webinar question reaches the right account owner as a follow-up task.
scenario
-
Before an account review you want to know whether anyone at the account has been registering for or attending your webinars, and whether that lines up with open deals. Checking means listing the account's contacts in Salesforce and searching GoTo Webinar for each of them in turn.
What popdock provides
--
Name the Salesforce account and a lookback period, and it reads the account's contacts and open opportunities, then the webinars in the window. Each contact's email is checked in GoTo Webinar for registrations and attendance, and only contacts on this account count, never a domain search. You get engaged contacts by webinar, the contacts with no activity, and each open opportunity marked when someone attended within 30 days before its close date. It reads from GoTo Webinar and Salesforce but writes nothing back.
Business outcome
---
You see how an account engages with your webinars alongside its open deals, ready for the account review.
scenario
-
Event and campaign lists built in Salesforce often need to reach a Mailchimp audience, but being a member of a Salesforce campaign is not permission to email. Importing by hand risks subscribing people without consent and re-adding contacts who already unsubscribed or were cleaned.
What popdock provides
--
Name the Salesforce campaign and the Mailchimp audience, and it reads the campaign members, drops anyone without an email and splits each name into first and last. Every address is checked against the audience, and anyone already there in any status is skipped. You see who will be added and are told each person gets a confirmation email, and nothing happens until you say yes. Members are always added as pending, never subscribed, and the report lists who was added, who was skipped and why, and any failures.
Business outcome
---
Salesforce campaign contacts join your audience through double opt-in, with consent respected and no unsubscribes revived.
scenario
-
People who click a campaign deserve a lead in Salesforce, but creating them by hand means checking each email against contacts and leads first. Skip that and you create duplicates, and rush it and leads land without the last name and company Salesforce requires.
What popdock provides
--
Name the Mailchimp campaign, and optionally a lead source, and it gathers the unique clickers with their names and companies. Anyone already a Salesforce contact or lead with that email, or who unsubscribed from the campaign, is dropped. Rows missing a last name or company are marked and left out unless you fill them in, and nothing is created until you confirm. Each lead is created once with your lead source, and the report gives totals for every reason a clicker was skipped.
Business outcome
---
Engaged clickers become Salesforce leads the same day, without duplicate records or half-filled leads.
scenario
-
The email numbers sit in Mailchimp while the members, responses and pipeline sit in Salesforce, so judging one campaign means two reports and a spreadsheet. It is also hard to tell how many Salesforce members were ever sent the email at all.
What popdock provides
--
Give a campaign name and it reads the Mailchimp report for sends, opens, clicks, unsubscribes, bounces and revenue, and the Salesforce campaign for members, responses, opportunities, won value and cost. It checks up to 200 Salesforce member emails against the Mailchimp recipients to count who was sent the email and who opened it. You get a side by side table with a few plain observations, and the exact names matched on each side so you can confirm they are the same campaign. E-commerce and opportunity revenue are kept apart, and nothing is changed.
Business outcome
---
You judge a campaign on email and pipeline results together, and spot members who were never sent the email.
scenario
-
Clicks from a campaign are wasted if the people behind them never reach Salesforce. Finding them means pulling the click list and searching each address in contacts and then leads, one at a time, before anyone can decide who deserves a follow-up.
What popdock provides
--
Name the Mailchimp campaign, and optionally how many people to return, and it collects the unique clickers with their names and companies. Each email is checked against Salesforce contacts, then leads, ignoring case and stray spaces. You get a table of the unmatched clickers with their click count and last click date, plus totals for contacts matched, leads matched and unmatched. It is read-only, so you decide who becomes a lead.
Business outcome
---
You get a short, ready list of interested people Salesforce does not know about yet.
scenario
-
Your biggest store buyers in Mailchimp may be invisible to the sales team in Salesforce, or sitting there only as a lead. Checking means searching each email in contacts and leads, then opening the account for its owner and any open opportunities.
What popdock provides
--
Set a minimum spend and a number of customers, and it takes the top Mailchimp e-commerce customers and looks each up in Salesforce by email, contact first and then lead. For contacts it reads the account, its owner and open opportunities. High spenders with no Salesforce record, and those who are only a lead, are called out separately. It matches on email only, never on a company name that merely looks similar, shows spend in the store's currency and changes nothing.
Business outcome
---
Sales knows which big buyers have no account owner or open pipeline, so no high spender goes unmanaged.
scenario
-
When someone unsubscribes or hard bounces in Mailchimp, their Salesforce record usually stays as it was, still sitting in active campaigns. Finding them means pulling two Mailchimp reports and searching each address in Salesforce contacts, leads and campaign members.
What popdock provides
--
Choose a lookback, 30 days by default, and it reads Mailchimp unsubscribes and hard bounces with the campaign and the reason or bounce type. Each email is matched to a Salesforce contact or lead with its owner, and the Salesforce campaigns that still include the person are listed. Results come in two tables, and someone who did both appears in both. It reports the records and does not change them.
Business outcome
---
You can clean up Salesforce records and campaign lists for people email no longer reaches, with the evidence in hand.
scenario
-
Reps working a contact in Salesforce rarely see that the person clicked last week's campaign. Logging clicks by hand means matching each clicker to a contact or lead and writing a task, and running it twice fills activity history with duplicates.
What popdock provides
--
Name the Mailchimp campaign and it groups the clicks by person with the links clicked and the last click date. Each email is matched to one Salesforce contact or lead, and anyone with no match, several matches or a task already logged for that campaign is skipped. You review the planned tasks and confirm before anything is written, then one completed task per person is added with the links and click count. The report lists what was created and why others were skipped.
Business outcome
---
Campaign clicks appear in Salesforce activity history once per person, so reps see the interest when they open the record.
scenario
-
Answering what you know about one person means opening Salesforce for their contact or lead, campaigns, tasks and opportunities, then Mailchimp for audiences, opens and unsubscribes. The two rarely agree, and someone unsubscribed in Mailchimp can still be an active campaign member in Salesforce.
What popdock provides
--
Give an email address and it finds the Salesforce contact or lead, listing every match with its owner if there is more than one, and the person's Mailchimp audiences with status, rating and tags. It adds email activity over your lookback period with campaign titles, plus the person's Salesforce campaigns, open tasks and open opportunities. A closing line says whether the two systems agree. It matches on email only, never on a name, and reads without changing anything.
Business outcome
---
You get one dependable picture of a person, with any conflict between email consent and Salesforce activity called out.
scenario
-
Moving a deal forward in Salesforce means changing the stage, writing the next step, adjusting the close date and probability, then remembering to create a follow-up task. Reps skip the task, push close dates into the past or move a deal backwards by mistake, and the forecast stops reflecting reality.
What popdock provides
--
Name the opportunity, the new stage and the next step, and optionally a new close date, and it finds exactly one open opportunity in Salesforce. Backward or closing stage moves need your explicit yes, a past close date is refused, and a probability is proposed with the reason when the stage usually carries a different one. You see current and proposed values side by side and nothing is sent until you confirm, then only the changed fields are updated. With a separate yes it adds a follow-up task for the owner due in three business days, and it never touches amount, account or owner.
Business outcome
---
Deals move stage with a clean next step and a follow-up on the calendar, so the forecast stays honest.
scenario
-
Adding a lead to Salesforce after an event or a call seems simple, but the person may already be a lead, or worse, a contact at a customer. Without checking first, sales ends up chasing an existing customer as a prospect or working two lead records for the same person.
What popdock provides
--
Give a name, company and email, and it checks Salesforce for existing leads by email and by company and surname, for a contact with the same email and for an account with that company name. An existing contact stops the job and shows you who they are, and an existing lead can be updated with just the new details instead. If the company is already a customer account, you are told before the lead is created. You see the exact values and nothing is saved until you confirm, and if no email is given it says the duplicate check was weaker.
Business outcome
---
New leads go into Salesforce once, and existing customers are never worked as cold prospects by mistake.
scenario
-
Setting up a new customer in Salesforce means creating the account, then the first contact, and linking them correctly. If the company already exists under a similar name, or the person is sitting in Salesforce as a lead, you end up with duplicate accounts and a lead that never gets converted.
What popdock provides
--
Give the account name and the contact's name and email, and it searches Salesforce for an existing account by exact and partial name, a contact with that email and an unconverted lead with it. An existing account stops the job and offers to add only the contact to it, an existing lead points you to qualifying it instead. You choose any extra details such as industry, website or billing city, see the exact values and confirm before anything is written. The account is created first and the contact is linked to it, and if the contact fails the new account id and error are reported without a retry.
Business outcome
---
New customers start in Salesforce as one clean account with its first contact, without duplicates or stranded leads.
scenario
-
When a customer calls, logging a Salesforce case means finding the right contact, checking whether they already have an open case about the same thing, and filling in priority, origin and account. Under pressure agents open a second case for the same issue or attach it to the wrong person.
What popdock provides
--
Give the subject and the contact's email, and optionally a priority, and it finds the contact in Salesforce, asking you to choose if several share the email and never creating a contact. It then checks that contact's open cases and, if one has a similar subject, asks whether you still want a new one. You see the exact values, including the contact and account it will be linked to, and nothing is created until you confirm. The new case number is read back so you can give it to the customer.
Business outcome
---
Customers get one case per issue, linked to the right contact and account, with a case number to quote back.
scenario
-
Escalating a case properly means raising its priority, changing its status, checking when the customer was last contacted and making sure the owner knows to act today. Done in a hurry, the priority changes but nobody tells the owner, and other open cases for the same account go unseen.
What popdock provides
--
Give the case number and the reason, and optionally a priority, and it finds the case in Salesforce, reads its comments and emails for the last contact date, lists other open cases on the account and resolves the owner to one active user. You see current against proposed priority and status and confirm before anything changes, and the reason is added to the description only if you agree. It then creates a high priority task for the owner due today carrying the reason. It never reassigns the case, and if the owner cannot be resolved it updates the case, skips the task and says why.
Business outcome
---
Escalations reach the owner the same day with full context, and the account's other open cases are in plain view.
scenario
-
Creating a follow-up in Salesforce means finding the right opportunity, account, contact or lead, working out who owns it and linking the task to the right fields. Tasks end up attached to the wrong record, assigned to the wrong person or created twice for the same follow-up.
What popdock provides
--
Give the subject and the record name, and optionally a due date and assignee, and it looks for the record across opportunities, accounts, contacts and leads, stopping if a lookup returns more than one. It assigns the task to the record's owner or the person you name, resolved to one active user, and checks for an open task with a similar subject first. You see the exact values and nothing is created until you confirm. Every id comes from a lookup in the same conversation, never a guess.
Business outcome
---
Follow-ups land on the right record and the right person's list, without duplicates cluttering the activity history.
scenario
-
When a contact changes jobs or was filed under the wrong company, moving them in Salesforce looks like a one-field change. What is easy to miss is that their deal roles, contract roles, open cases and tasks stay tied to the old account, so the history is split without anyone realizing.
What popdock provides
--
Give the contact's email and the new account, and optionally a new title, and it finds exactly one contact and one target account in Salesforce, stopping if the contact is already there. It lists the opportunity and contract roles, open cases and open tasks that stay with the old records so you understand what the move leaves behind. You see old and new account and title and confirm before the single update is made. Name, email and phone are never changed, and the linked records worth revisiting are listed in the report.
Business outcome
---
Contacts move to the right account with your eyes open about the deals and cases that stay behind.
scenario
-
Setting up a campaign in Salesforce is often done from memory: a name, dates and a budget typed in without checking whether the same campaign already exists or how similar ones performed. You end up with duplicate campaigns and budgets that were never sanity checked against expected return.
What popdock provides
--
Give the campaign name, type and dates, and it checks Salesforce for an active campaign with the same name and stops if one exists. It makes sure the end date follows the start date, asks for budgeted cost and expected revenue and warns when revenue is below cost. As a benchmark it shows the budget, actual cost and won value of the last three campaigns of the same type. You see the exact values and nothing is created until you confirm, and a date it cannot read is asked for again rather than guessed.
Business outcome
---
Campaigns start with realistic budgets set against past results, and no duplicates muddying attribution later.
scenario
-
Qualifying a lead by hand means creating an account, a contact and an opportunity, copying details across and updating the lead status. If the company or person already exists, it is easy to create duplicates, and an open deal on the same account can be missed entirely.
What popdock provides
--
Give the lead's email, and optionally a deal name and close date, and it finds the unconverted lead in Salesforce, then looks for an existing account by company name and a contact with the same email, reusing them when found. Open deals on that account are shown so you can decide whether a new one is needed. You review the whole plan, what is reused and what is created, and confirm before anything is written, then the records are created in order and the lead is marked qualified. It explains that the native converted flag stays false, and a failure stops the run and reports what was already created.
Business outcome
---
Qualified leads become a clean account, contact and deal in one confirmed step, reusing what already exists.
scenario
-
When a customer questions their balance, the invoices, payments, credit memos and refunds in Salesforce have to be tied out by hand. Unapplied payments and credits, refunds larger than the payment, or overdue invoices on an auto-pay account hide in long lists and take hours to spot.
What popdock provides
--
Name the account and optionally a lookback window, and it finds the account in Salesforce and gathers its invoices, payments, credit memos, refunds and payment methods for the period. It totals what was invoiced, paid, credited and refunded, and sets the open balance against unapplied payments and credits. It flags unapplied amounts, refunds larger than their payment, overdue invoices where auto-pay is on and accounts with no active payment method. Amounts are used exactly as returned, tax is not recomputed and nothing is changed.
Business outcome
---
You can explain a customer's balance with confidence, with every document that does not tie out listed.
scenario
-
Recording installed products as Salesforce assets keeps service and renewals accurate, but entering them by hand risks a second asset for the same serial number. When equipment moves between sites, the old record stays put and the new one is created alongside it.
What popdock provides
--
Give the product, serial number and account, and optionally an install date, and it resolves the account and a single active product in Salesforce, then looks for an asset with that serial number. If none exists it plans a new installed asset, and if one does it shows it and plans an update of only account, install date and status, saying when the asset is moving. You see the exact values and confirm before the one write. A blank serial number is refused, and no price is set unless you give one.
Business outcome
---
Each installed product has exactly one Salesforce asset at the right account, keyed by its serial number.
scenario
-
Overdue tasks pile up in Salesforce until the list is meaningless. Clearing it by hand means opening each task, picking a new date that does not overload one day, and closing tasks on deals that are already won or lost, which nobody has time to do.
What popdock provides
--
Name the user, and optionally a start date and how many tasks per day, and it finds their open overdue tasks in Salesforce. It proposes new weekday due dates in priority order, no more than the daily limit, and marks tasks on closed opportunities as suggested to close. You see the plan as a table and can accept it all, reject it or edit rows, and nothing changes until you confirm. Only the due date or completed status is changed, never subject, priority, assignee or related records.
Business outcome
---
An overdue backlog becomes a realistic schedule in minutes, with dead tasks closed instead of carried forward.
scenario
-
Preparing for a deal review means opening the opportunity, its products, quotes, contact roles, partners, competitors and activity history in Salesforce. Gaps such as an expired quote, an amount that does not match the line items or no primary contact are easy to miss when the data is spread across tabs.
What popdock provides
--
Name the opportunity and it reads its products, quotes and latest quote lines, contact roles, partners, competitors and recent and scheduled activity from Salesforce. It checks whether the amount matches the line items or latest quote, whether the quote has expired, whether there is a primary contact, whether anything has happened in 14 days and whether the close date has passed. You get a short brief with tables, the gaps found and three recommended next moves. It only reads, and missing quotes or products are noted rather than treated as errors.
Business outcome
---
Deal owners walk into reviews with the gaps already found and a clear set of next moves.
scenario
-
Before a customer meeting you want to know who the contacts are, what is in the pipeline, what is broken, what they owe and what happens next. In Salesforce that means opening contacts, opportunities, cases, invoices, contracts, orders and activities one tab at a time.
What popdock provides
--
Name the account and it gathers contacts, open and recently closed opportunities, open cases, unpaid invoices, contracts, recent orders and scheduled and overdue activity from Salesforce. You get a one-page view with a snapshot, pipeline, service, money, contracts ending within 90 days, next actions and up to three watch-outs. Numbers are reported exactly as returned, empty sections say None rather than vanishing, and nothing is changed. If the name matches nothing, it lists the closest account names.
Business outcome
---
You walk into any customer conversation with the full account picture on one page, risks included.
scenario
-
Judging whether a campaign paid off means pulling its costs, members, responses, converted leads and won revenue out of Salesforce and doing the arithmetic yourself. Missing costs and unconverted senior responders get lost in the spreadsheet.
What popdock provides
--
Name the campaign and it reads its cost, revenue and pipeline figures and its members from Salesforce, then checks how many responding leads were converted. It works out response rate, cost per response and per opportunity, return on actual cost and results against budget and expected revenue, falling back to budgeted cost with a note when actual cost is missing. You get a metrics table, a member status breakdown, the ten most senior responders not yet converted and a short verdict. It only reads and writes n/a instead of dividing by zero.
Business outcome
---
You know whether a campaign earned its budget, and which warm responders sales should call next.
scenario
-
Picking up a long-running case means reading comments, emails, chat sessions, solutions, work orders and attachments in separate Salesforce views. Working out who is waiting on whom, and what is actually blocking a resolution, takes longer than it should.
What popdock provides
--
Give the case number and it reads the case's comments, emails, messaging sessions, attached solutions, team members, work orders and files from Salesforce. It merges them into one dated timeline, oldest first, and says whether the customer or support is waiting, based on the last message in and out. You also get the blockers and a suggested next step. Long emails are summarized rather than quoted in full, and nothing is changed.
Business outcome
---
Anyone picking up a case understands its history and next step in one read, not twenty minutes of clicking.
scenario
-
Contact data in Salesforce decays quietly: the same email on two contacts, people with no way to reach them, contacts with no account and people who are also sitting there as open leads. Finding them by hand across thousands of records is not realistic.
What popdock provides
--
Optionally name an account, and it reads up to 2000 Salesforce contacts and checks for duplicate emails, duplicate names within an account, contacts with no email or phone and contacts with no account. Duplicates and orphans are also checked for an unconverted lead with the same email. You get a count per problem and a table for each, with duplicates grouped and the record worth keeping suggested. Nothing is changed, and it says when the audit is partial because the record limit was reached.
Business outcome
---
Your contact data gets cleaner with a clear list of what to merge and fix, and nothing changed behind your back.
scenario
-
Field work slips quietly when work orders sit in Salesforce without an appointment, or appointments pass their due date without anyone noticing. Dispatchers piece the backlog together from separate work order and appointment views, and parts needs only surface when a technician arrives without them.
What popdock provides
--
Optionally name an account, and it reads open work orders and service appointments due in the next 30 days from Salesforce. It flags appointments past due and not completed, appointments with no scheduled start and work orders with no appointment at all, then lists the parts each flagged work order needs. You get counts by status and priority, a table of flagged items and the parts needed summed by product. It only reads, and says so when nothing is open.
Business outcome
---
Dispatch sees late and unscheduled field work in one list, with the parts to order before the visit.
scenario
-
Support teams answer the same questions again and again because nobody has written the article. Working out which case topics in Salesforce have no solution, and which customer ideas are gathering votes, means reading through hundreds of cases and guessing at the patterns.
What popdock provides
--
Optionally set a lookback window, and it groups recent Salesforce cases by type and recurring subject words, then samples the largest groups for attached solutions. Groups with none are gaps, and it checks whether a matching solution exists but is unpublished or unreviewed. It also lists customer ideas with votes, highest first. You get topics ranked by volume, the top five articles to write with example case numbers and the top ideas. It says the subject grouping is approximate and changes nothing.
Business outcome
---
Your knowledge base grows where cases actually come from, so repeat questions get answered once and reused.
scenario
-
Collections work starts with an aging report, but an overdue balance in Salesforce is not always a customer who has not paid. Unapplied payments, unused credits and open complaints change who you should call, and finding them for each account is slow.
What popdock provides
--
Optionally name an account, and it reads Salesforce invoices past due and buckets them into 1 to 30, 31 to 60, 61 to 90 and over 90 days, totalled per bucket and per account. For the ten accounts owing most it checks for unapplied credit, payments received but not applied and open cases. You get the aging table, the top accounts with those offsets shown alongside rather than netted, and a chase list split into accounts to call, application problems and disputes to resolve first. Nothing is changed.
Business outcome
---
Collectors call the right customers first, and stop chasing balances that are really unapplied cash or open disputes.
scenario
-
A pipeline review means scanning every open Salesforce deal for close dates already passed, missing next steps, probabilities that do not fit the stage and big deals with nothing planned. On a long list the deals that most need attention are the easiest ones to scroll past.
What popdock provides
--
Optionally name an owner and how far ahead to look, and it reads the open Salesforce opportunities closing in that window, including any already past their close date. Each deal is checked against stated rules for overdue close dates, missing next steps, stage and probability mismatches, unforecast deals this quarter and large deals with no open task. You get totals by stage and forecast category, a table of flagged deals and the five to act on first with one concrete action each. It only recommends changes and never makes them.
Business outcome
---
Sales managers spend review time on the deals that need it, with a concrete action for each.
scenario
-
Reps cannot quote a product cleanly when its Salesforce price book entry is missing, inactive or set to zero. These problems hide until a quote fails, and checking every active product against a price book by hand is a job nobody gets round to.
What popdock provides
--
Optionally name a price book, defaulting to the standard one, and it reads your active Salesforce products and that book's entries. It flags active products with no entry, inactive entries for active products, active entries for retired products and zero list prices. For a non-standard book it also flags prices more than 25 percent away from the standard price. You get a count per issue and a table for each, and nothing is changed.
Business outcome
---
Price book problems are fixed before they stall a quote, so every active product can be sold cleanly.
scenario
-
Discounting creeps up one quote at a time. Without checking each Salesforce quote line against its list price, nobody sees a rep giving away 40 percent, the same product quoted at wildly different prices or lines priced above list by mistake.
What popdock provides
--
Optionally set a lookback window and a discount threshold, and it reads recent Salesforce quotes and their lines, working out each line's discount against list price and looking up the price book entry when list price is missing. It flags lines over your threshold, the same product quoted at very different prices, lines above list and products with no active price book entry. You get totals and the average discount, a table of flagged lines and the products and accounts with the heaviest average discount. It only reads.
Business outcome
---
You see where margin is being given away on quotes, and by whom, before the deals close.
scenario
-
Renewals are lost when a contract or asset reaches its end date and nobody opened a renewal opportunity. Checking every ending contract and asset in Salesforce against each account's open deals is tedious, so the gaps tend to show up after the date has passed.
What popdock provides
--
Optionally set how many days ahead to look, and it reads Salesforce contracts and assets ending in that window. Each account is checked for an open opportunity that closes in time or is named as a renewal, and for uncovered ones it finds the primary contract contact. You get a table sorted by end date showing coverage and the renewal deal or contact, plus the uncovered renewals as an action list, soonest first. It changes nothing.
Business outcome
---
No contract or asset reaches its end date without a renewal in motion and a named contact to call.
scenario
-
A one to one with a rep goes better when you know what is overdue, what is due this week and which deals have nothing planned. In Salesforce that means filtering tasks, events and opportunities separately and matching them by hand.
What popdock provides
--
Name the user and optionally how many days ahead, and it reads their open tasks, upcoming meetings and open opportunities from Salesforce. It checks each deal against those tasks and events to find the ones with nothing planned. You get overdue tasks oldest first, tasks due soon, the meeting schedule by day and open deals with no activity, largest first. It only reads.
Business outcome
---
Managers and reps see in one view what is slipping and which deals have gone quiet.
scenario
-
Salesforce user lists collect people who have not logged in for months, inactive users still in groups and accounts with no role or manager. Worse, inactive users can still own open deals and cases that nobody is working, and finding them means cross-checking several lists.
What popdock provides
--
Optionally set what counts as a stale login, and it reads up to 2000 Salesforce users. It flags active users with stale or no logins, standard users with no role or manager and inactive users still in groups, then counts the open opportunities and cases that stale and inactive users still own. You get a count per issue and a table, with inactive users who own open records listed first. It changes nothing and never suggests deactivating someone without saying their records need reassigning first.
Business outcome
---
Access reviews catch stale accounts and unattended deals and cases, with a safe order for cleaning them up.
scenario
-
Knowing why deals are lost means comparing won and lost Salesforce opportunities by size, source and type, and looking at which competitors keep showing up. Without the analysis, lessons come from memory and the loudest anecdote.
What popdock provides
--
Optionally set a lookback window and an owner, and it reads closed Salesforce opportunities and splits them into won and lost. It works out win rate by count and amount, average deal size, and win rate by lead source and type, then reads competitors and contact roles on the largest lost deals. You get a summary, competitors seen most often and three evidence-backed observations with inference labelled as such. Missing competitor data is reported as not recorded, small samples are called out and nothing is changed.
Business outcome
---
Sales leaders see what actually wins and loses deals, backed by data rather than anecdote.
scenario
-
With hundreds of open Salesforce cases, deciding what to work first means weighing priority, escalation, age and how long the customer has gone without hearing from you. Sorting by one column hides the high priority case nobody has replied to in a week.
What popdock provides
--
Optionally name an owner or a priority, and it reads open Salesforce cases and ranks them by priority, escalation and age. For the top 20 it reads comments and emails to find days since last contact, flagging high priority cases silent for more than three days. You get counts by priority and status, the oldest case, a ranked top 20 with flags, accounts with three or more open cases and unowned or queued cases. It only reads.
Business outcome
---
Agents start each day on the cases that matter most, and silent high priority cases stop slipping through.
scenario
-
New leads arrive faster than they are worked, and some are not new at all: duplicates of each other, or people at existing customers. Sorting recent Salesforce leads by who deserves a call first means checking each against contacts and accounts by hand.
What popdock provides
--
Optionally set a lookback window and an owner, and it reads recent unconverted Salesforce leads. It flags duplicate emails within the set, leads whose email matches a contact or whose company matches an account, leads still untouched after two days and leads with no email or phone. You get counts by status and source, a ranked follow-up list with known companies and senior titles first, and separate tables for duplicates and existing customers. Nothing is changed.
Business outcome
---
Reps follow up on the best new leads first, and existing customers are routed away from cold outreach.
scenario
-
Updating a Salesforce account sounds simple, but a rename can collide with another account, a field gets cleared by accident or a change lands on the wrong account with a similar name. Most of these mistakes are only noticed when a report looks wrong.
What popdock provides
--
Name the account and describe the changes, and it finds exactly one account in Salesforce and maps your changes onto name, type, industry, website, phone, billing city and country and description, telling you what is out of scope. A rename is checked against existing account names first. You see a table of only the fields that change, current against new, and nothing is written until you confirm. Fields are never cleared unless you ask for a blank.
Business outcome
---
Account details change exactly as intended, with no accidental blanks and no clashing names.
scenario
-
Sales builds a Salesforce campaign and wants those people in a Drip email series, so someone exports the members and adds them by hand. It is easy to re-add people already on the series, to email someone who unsubscribed in Drip, or to load everyone into a paused series and wonder why nothing went out.
What popdock provides
--
Name the Salesforce campaign and the Drip campaign, and it reads the Salesforce members and requires each campaign name to match exactly one campaign. It drops people with no email, people already on the Drip campaign and anyone unsubscribed in Drip, then tells you whether the Drip campaign is active and whether double opt-in will send a confirmation email first. Nobody is added until you confirm. You get counts for added, already enrolled, unsubscribed, missing email and failed.
Business outcome
---
Salesforce campaign members reach the right Drip email series once, with unsubscribed people kept out and paused campaigns flagged.
scenario
-
Marketing runs a series in Drip while sales tracks a matching campaign in Salesforce, and the two lists rarely agree. Checking who is on both means exporting each side and lining up emails in a spreadsheet. The most important mismatch, someone who unsubscribed in Drip but responded in Salesforce, is the easiest to miss.
What popdock provides
--
This is a read-only comparison, so neither campaign is changed. Name the Drip campaign and the Salesforce campaign, and it reads the subscribers on one and the members on the other, falling back to a partial name match and stopping to ask if more than one campaign fits. Everyone is matched by email, case-insensitively, into on both, only in Drip, or only in Salesforce. You get counts, a table for each one-sided group with status, lead score and response, and a separate list of people unsubscribed in Drip who are marked as responded in Salesforce.
Business outcome
---
Marketing and sales see exactly where their two campaign audiences diverge, including responders who have opted out of email.
scenario
-
Drip tags subscribers who show buying intent, but sales only works what is in Salesforce. Moving them across by hand means checking each email against Salesforce contacts and leads, guessing a company name Drip never captured, and typing in each lead. Skip the check and reps end up chasing duplicates of people they already own.
What popdock provides
--
Name a Drip tag and a lead source, and it reads up to 50 active Drip subscribers carrying that tag, then checks each email against Salesforce contacts and leads and drops anyone Salesforce already has. For the rest it proposes a lead with first name, last name and a company taken from the email domain, using Unknown for personal mailboxes. You review the table, remove rows if you like, and nothing is created until you confirm. You get the new Salesforce lead IDs, any failures, and the count skipped as already known.
Business outcome
---
Tagged Drip subscribers become Salesforce leads for sales to work, with no duplicates of existing contacts or leads.
scenario
-
Before you call a prospect you want to know how marketing sees them and how sales sees them, and that means opening Drip and Salesforce side by side. Lead score, tags and email series sit in one place, owner, campaigns and open deals in the other. Disagreements between the two, like an opt-out still on an active campaign, go unnoticed.
What popdock provides
--
Give an email address, and it reads the Drip subscriber with their status, lead score, lifetime value, tags and email campaigns, then finds the matching Salesforce contact or lead with its account, owner, campaign memberships and open opportunities. Nothing is changed in either system. The report lays out both sides, then lists the mismatches: names spelled differently, an unsubscribe in Drip against active Salesforce campaigns, a high lead score with no owner, or a customer still on prospect emails. If one system fails it says which rather than presenting half a picture.
Business outcome
---
You walk into every conversation knowing the full marketing and sales story for one person, and where the records disagree.
scenario
-
Your most engaged Drip subscribers are the people sales should be talking to, yet many never make it into Salesforce. Finding them means filtering Drip by lead score, then searching Salesforce contacts and leads for every email. Done by hand it takes hours and the list is out of date by the time it is finished.
What popdock provides
--
This job only reports and changes nothing. Set a minimum lead score and how many subscribers to check, and it reads active Drip subscribers above that score, then looks each email up as a Salesforce contact and, failing that, as a lead. A subscriber counts as missing only when neither turns up. You get the missing people ranked by lead score with lifetime value, tags and country, plus counts for checked, matched as contact, matched as lead and missing, and a warning if the limit may have cut the list short.
Business outcome
---
Sales gets a ranked list of high-scoring Drip subscribers it has never seen, ready to turn into leads.
scenario
-
When a Drip subscriber's lead score climbs, someone in sales should follow up, but the hand-off depends on a person noticing. Creating the follow-up means finding the matching Salesforce contact or lead, checking whether a rep already has an open task, and writing one with the context. Miss the check and a prospect gets two calls.
What popdock provides
--
Set a minimum lead score and how many days until the task is due, and it reads the hot Drip subscribers, finds each one in Salesforce as a contact or lead, and skips anyone with an open task already, noting what that task is. People not in Salesforce and emails matching several contacts are listed rather than guessed. You review the plan and no task is created until you confirm. Each task is high priority, carries the lead score, lifetime value and tags, and nobody gets two tasks in one run.
Business outcome
---
Hot Drip subscribers get a single, dated Salesforce follow-up task, with nobody already being worked contacted twice.
scenario
-
When a deal closes in Salesforce, the buyer's contacts often stay on prospect email in Drip because nobody tells marketing. Fixing it means pulling recent won opportunities, finding the contacts on each, getting their email addresses and tagging them in Drip one by one. People slip through and keep getting sales pitches after they have bought.
What popdock provides
--
Give a start date and a tag, and it reads the Salesforce opportunities won since then, follows each one to its contact roles and their email addresses, and looks each email up in Drip. Contacts missing from Drip, contacts with no email and opportunities with no contacts are reported, not guessed, and people already tagged are skipped. Unsubscribed people are flagged in the plan. Nothing is tagged until you confirm, each email is tagged once even across several deals, and campaign membership is left for marketing to decide.
Business outcome
---
New Salesforce customers carry a Drip tag your email automations can use, applied once per person and only after you approve.
scenario
-
Account owners in Salesforce rarely hear that a customer's Stripe payment failed or an invoice is past due until finance escalates it. Spotting the overlap means pulling failed charges from Stripe, matching each email to a Salesforce contact and checking the account for open opportunities, one customer at a time.
What popdock provides
--
Give a lookback period, and optionally a minimum deal size, and it collects failed Stripe charges and past-due invoices and groups them by customer email. Each email is matched to a Salesforce contact, and the account is checked for open opportunities. You get a list sorted by open opportunity amount with the failure reasons, open invoice amounts and the account owner, plus customers in Stripe that are not in Salesforce. Amounts in different currencies are never added together, and nothing is changed in either system.
Business outcome
---
Account owners act on payment failures before their deals move, instead of finding out from finance later.
scenario
-
Opportunities close in Salesforce while the same customer has urgent tickets open or bad satisfaction ratings in Zendesk, and the account owner never hears about it. Spotting the risk means matching each account to its Zendesk organization, checking tickets and ratings, and remembering to log a task, so deals are pushed through at the worst moment.
What popdock provides
--
Give a closing window, and it reads open Salesforce opportunities closing in that window and matches each account to a Zendesk organization by account id, exact name or website domain, treating several matches as ambiguous rather than guessing. Opportunities whose customer has unsolved urgent or high tickets, or bad ratings in the last 60 days, are proposed for a support risk task, skipping any that already have one. Nothing is created until you confirm, then one task per confirmed opportunity is added with the ticket details.
Business outcome
---
Account owners see support problems on closing deals in Salesforce, with one clear task each and no duplicates.
scenario
-
A renewal opportunity in Salesforce can look healthy while the customer's Stripe subscription is past due, set to cancel or under dispute. Reps only find out by asking finance or logging into Stripe, and the signals never make it onto the opportunity where the team can see them.
What popdock provides
--
Name an open opportunity, and it matches the account's contact emails to Stripe customers and reads their subscriptions, open invoices and disputes for churn signals. If the account is not billed in Stripe or shows no signals, it stops without writing. Otherwise you see the current and proposed next step, and nothing is written until you confirm. It then updates only the next step on the opportunity, keeping any existing text after the risk note, and reads the stored value back.
Business outcome
---
Churn signals from billing sit on the Salesforce opportunity where the deal team plans the renewal.
scenario
-
When a Stripe payment fails or an invoice goes unpaid, the account team in Salesforce should follow up, but the details sit in Stripe. Someone has to summarize what is outstanding, find the right contact and account, and create a task with the invoice links, so it often never happens.
What popdock provides
--
Give the customer's email, and it reads their open invoices and failed charges from the last 30 days in Stripe, stopping if the customer is paid up. It matches the email to a Salesforce contact and shows you the exact task it will create: the amount outstanding per currency, each invoice and failed charge, and the invoice links. Nothing is written until you confirm, then the task is created once on the contact and account and read back.
Business outcome
---
Every failed payment gets a dated follow-up in Salesforce with the details the account owner needs.
scenario
-
A customer raising more and more Zendesk tickets is an early warning the account team in Salesforce rarely sees. Spotting it means counting tickets by organization, comparing with the previous period and logging a task on the right account, which nobody has time to do every month.
What popdock provides
--
Give a lookback period and a ticket threshold, and it counts Zendesk tickets by organization, compares them with the previous period and notes urgent, unsolved and recurring themes. Each organization is matched to its Salesforce account, and accounts that already have an open trend task are skipped. You see the proposed tasks and nothing is created until you confirm, then one task per confirmed account is added with the counts, themes and example tickets.
Business outcome
---
Account teams hear about rising support load in Salesforce early, with one task per account and no duplicates.
scenario
-
Support works urgent Zendesk tickets in the order they arrive, without knowing which customers have large deals open in Salesforce. Ranking escalations by commercial weight means matching each organization to a Salesforce account and adding up its open pipeline, which nobody does in the middle of a busy queue.
What popdock provides
--
Give a lookback period and priorities, and it collects open urgent and high Zendesk tickets and finds the Salesforce account behind each organization, or behind the requester's email when there is no organization. Each account's open pipeline is totaled and its largest deal noted. You get one ranked table by open pipeline, priority and age, with escalations on deals closing within 30 days called out and unmatched tickets listed separately. Nothing is changed in either system.
Business outcome
---
Support works the escalations that matter most commercially first, and sales knows which deals are exposed.
scenario
-
Before a renewal or account review, the account team pulls opportunities, contracts and tasks from Salesforce, then asks support for ticket history and satisfaction scores from Zendesk. Assembling it takes an hour of searching two systems, and tickets filed by contacts outside the organization are missed.
What popdock provides
--
Name a Salesforce account, and it reads its open opportunities, contracts, contacts and open tasks, then matches the account to a Zendesk organization by account id, exact name or website domain. Tickets are collected by organization and by each contact's email, merged without double counting, and satisfaction ratings are added. You get one brief covering the commercial position, support history, the contacts raising tickets, requesters who are not in Salesforce, and three talking points based only on that data. Nothing is changed in either system.
Business outcome
---
Account reviews start with one accurate brief instead of an hour of searching two systems.
scenario
-
Opportunities marked closed won in Salesforce do not always become a Stripe customer or subscription, and the gap is only found when revenue does not reconcile. Checking means listing recent wins, finding each deal's contacts and searching Stripe for every email.
What popdock provides
--
Give a start date, and optionally an owner, and it lists Salesforce opportunities closed won since then and collects the emails of each deal's contact roles, falling back to the account's contacts and saying so. Each email is looked up in Stripe for a customer with an active or trialing subscription created after the close date. You get deals with no Stripe customer, deals with a customer but no new subscription, and a count of billed deals, largest first. Contacts with no email are listed as unverifiable. Nothing is changed in either system.
Business outcome
---
Nothing sold in Salesforce goes unbilled in Stripe, and gaps are caught weeks before month end.
scenario
-
Before calling a customer, a rep sees their Salesforce contact and deals but not whether their Stripe subscription is past due, an invoice is open or a charge was disputed. Getting that picture means asking finance or logging into Stripe and searching by email.
What popdock provides
--
Give an email address, and it finds the Salesforce contact, or the lead when there is no contact, with the account, owner and open opportunities. It then reads the matching Stripe customer's subscriptions, open invoices and charges over the lookback period, counting failures, refunds and disputes. You see both sides together and one line on what to know before reaching out, with any name mismatch between the systems flagged rather than decided. Nothing is changed in either system.
Business outcome
---
Reps reach out knowing the customer's billing picture, so no call is blindsided by a payment problem.
scenario
-
Renewals in Salesforce are forecast on contract dates and rep judgment, while the clearest churn signals, cancellations, past due subscriptions and disputes, sit in Stripe. Combining them means matching every renewing account to its Stripe customers and reading their billing, one account at a time.
What popdock provides
--
Give a window of days, and optionally an owner, and it finds Salesforce contracts ending and renewal opportunities closing in that window. Each account's contact emails are matched to Stripe customers, and their subscriptions, delinquency, open invoices and disputes are read. You get a table ranked high, medium or low churn risk with the renewal date, amount and the signals found, with accounts not billed in Stripe listed last. Nothing is changed in either system.
Business outcome
---
Renewal forecasts reflect real billing risk, so the accounts most likely to churn get attention first.
scenario
-
Salesforce shows an account's deals and contacts, but not what it pays in Stripe. Working out its subscriptions and monthly recurring revenue means searching Stripe for each contact email, adding up subscription items and converting yearly and weekly prices by hand.
What popdock provides
--
Name a Salesforce account, and it collects its contacts' emails and finds the matching Stripe customers, noting contacts with no match. Each subscription is listed with its status, period end and monthly recurring revenue, with yearly, weekly and daily prices brought to a month and totals kept per currency. Open invoices and delinquency are added, and you get a verdict of healthy, at risk or not billed in Stripe. Duplicate Stripe customers are flagged, and nothing is changed in either system.
Business outcome
---
Account owners see exactly what each account pays and whether billing is healthy, without leaving their workflow.
scenario
-
Renewal planning in Salesforce rarely accounts for how the customer is experiencing support in Zendesk. Checking means matching each renewing account to its Zendesk organization, counting unsolved and urgent tickets and reading satisfaction ratings, and it is usually done only after a customer complains.
What popdock provides
--
Give a renewal window, and optionally an owner, and it finds Salesforce contracts ending in that window with any open renewal opportunity, then matches each account to a Zendesk organization by account id, exact name or website domain. It counts unsolved and urgent tickets, recent volume and satisfaction ratings, ignoring unanswered surveys. You get each renewal rated at risk, watch or healthy, with the tickets driving each at-risk rating, and unmatched accounts listed rather than shown as healthy. Nothing is changed in either system.
Business outcome
---
Account teams see which renewals are at risk from support problems while there is still time to act.
scenario
-
A deal about to close in Salesforce can stall on an unsolved Zendesk ticket the sales owner never heard about. Finding them means matching each closing opportunity's account to a Zendesk organization and checking its open tickets, which rarely happens in the last weeks of a quarter.
What popdock provides
--
Give a closing window, and optionally a minimum amount, and it reads open Salesforce opportunities closing in that window and matches each account to a Zendesk organization by account id, exact name or website domain. Unsolved tickets are counted for each opportunity, and the urgent and high ones are listed with their assignee. Opportunities with no account or no Zendesk match are reported separately. Nothing is changed in either system.
Business outcome
---
Sales owners clear support problems before close instead of finding out from the customer on the call.
scenario
-
Your largest Salesforce accounts deserve the fastest support, but Zendesk queues do not know which customers matter most. Checking means ranking accounts by revenue, finding each Zendesk organization and listing its open tickets, which is too slow to do every week.
What popdock provides
--
Give how many accounts to check, and optionally a minimum annual revenue, and it ranks Salesforce accounts by annual revenue and matches each to a Zendesk organization by account id, exact name or website domain. You get every unsolved ticket for each account sorted by priority and age, accounts with nothing open noted in one line, and a summary of the oldest urgent work. Accounts with missing revenue are ranked last, and a failed lookup is reported as failed rather than as no tickets. Nothing is changed in either system.
Business outcome
---
Your most valuable customers never have urgent tickets sitting unnoticed in the queue.
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.