CRM
Microsoft Dynamics 365 Sales
Connect your AI to Microsoft Dynamics 365 Sales
Sales reps, managers, and customer success teams run their pipeline through Dynamics 365 Sales but spend more time navigating between Accounts, Opportunities, Activities, and Quotes than acting on what they find. AI can compress that navigation into answers and actions, but only if it sees the right fields, joins the right entities, and respects the business rules the CRM enforces.
Why it matters
Capabilities that matter most for Microsoft Dynamics 365 Sales
01
Nearly 70 ready-made AI tools
Install Dynamics 365 Sales MCP tools, prompts, calculated fields and lookups from the app store instead of building each one.
02
Pipeline matrix reports
Ready-made summary and matrix lists roll up opportunities, quotes and orders by month, owner or stage.
03
CRM beside ERP
Join Dynamics 365 Sales with Business Central, GP or billing lists so a customer's pipeline and invoices sit together.
03
Governed by role and team
AI tools answer within per-user and per-team security and field redaction, and changes run only through approved actions.
Use cases
Example AI Use Cases for Microsoft Dynamics 365 Sales
scenario
-
Customer-side people on Chorus calls often never become contacts in Dynamics 365 Sales. Adding them means filtering out colleagues, checking each email against contacts and leads, and typing in names and titles one by one.
What popdock provides
--
Name the account, how far back to look and, optionally, its Dynamics 365 account id. It collects the people from the account's Chorus calls, drops colleagues and your own email domain, and checks Dynamics 365 Sales for each email as a contact and then as a lead, so existing leads are flagged rather than duplicated. You choose which people to create and nothing is written without that answer. It never guesses an account id, and creates contacts unlinked, saying so, when none is given.
Business outcome
---
The buyers on your calls become Dynamics 365 Sales contacts without duplicating people already in the CRM.
scenario
-
Account managers often walk into a customer call without knowing which Dynamics 365 Sales cases are still open, or whether those problems were already discussed with someone else. Checking means reading the case list, then searching call notes and emails for each issue.
What popdock provides
--
Name the customer and how far back to look. It lists the open Dynamics 365 Sales cases with priority, age and resolve-by date, then searches the customer's Chorus calls and emails for each case number, product or title words, marking each case as discussed on a date or not discussed. Issues raised on calls that match no open case are listed separately as possible cases not yet logged. It says which words matched, since a word match is a lead and not proof, and nothing is written.
Business outcome
---
You go into the next call knowing every open case and which ones the customer has already raised with your team.
scenario
-
Sales leaders want to know whether the behaviors scored in Chorus actually relate to winning deals, but scorecards and outcomes sit in different systems, often under different names. Lining up each rep's scores against their Dynamics 365 Sales wins and losses by hand is slow and error prone.
What popdock provides
--
Choose a period, and optionally one rep. It reads Chorus scorecards and averages each rep's scores overall and per question, then counts their won and lost Dynamics 365 Sales opportunities and won revenue, matching names through email when they differ. You get a table per rep and the questions whose scores differ most between higher and lower win rate reps. It describes a correlation, never a cause, flags small samples, lists reps it could not match, and changes nothing.
Business outcome
---
Coaching priorities rest on which scored behaviors actually track with wins, with small samples clearly flagged.
scenario
-
A deal closing this month with no recent conversation is a deal at risk, but Dynamics 365 Sales does not show when the customer was last on a call. Checking each closing opportunity against Chorus by hand rarely happens before the forecast meeting.
What popdock provides
--
Choose how far ahead to look, how many silent days to allow and, optionally, one owner. It reads the open Dynamics 365 Sales opportunities closing in the window and checks each customer once in Chorus for recent conversations, retrying with the distinctive part of the name. Only the silent deals are listed, by close date, with stage, probability, revenue and last conversation, plus the revenue at stake. Customers Chorus cannot find are marked as no match rather than silent, and nothing is changed.
Business outcome
---
You see which closing deals have gone quiet and how much revenue rides on them, before the quarter ends.
scenario
-
New leads in Dynamics 365 Sales are often people your team has already spoken to on a call, yet they sit in the queue unqualified with a cold rating. Spotting them means checking each lead against Chorus conversations one at a time.
What popdock provides
--
Choose how far back to look and, optionally, a lead source. It reads the open Dynamics 365 Sales leads and looks for each person in Chorus by email, or by company when there is no person match. Matches show the conversations, the latest date and a summary line, with a recommendation to qualify, raise the rating or leave, citing the words in the summary that support it. Company-only matches are labelled weaker and never used alone to recommend qualifying, and nothing is changed.
Business outcome
---
Leads your team has already talked to are qualified sooner, based on what was actually said on the call.
scenario
-
After a recorded call, someone should add the summary to the Dynamics 365 Sales opportunity or account and set a follow-up task. Doing it by hand means rereading the Chorus summary, finding the right record and checking nobody logged it already.
What popdock provides
--
Give the Chorus conversation, the Dynamics 365 Sales record id from the address bar, and how many working days until the follow-up is due. It reads the call summary and attendees, shows the matching opportunity or account for you to confirm, and checks for an existing note about the call. You see the drafted note and one follow-up task together and confirm once before anything is written. It never guesses a record id, puts nothing in the note that is not in the summary, and asks you for key points when the summary is empty.
Business outcome
---
Every recorded call lands on the right Dynamics 365 Sales record with a single follow-up task, logged once.
scenario
-
Reps hold more conversations than they log, and Dynamics 365 Sales ends up missing calls that really happened. Finding the gaps means comparing a rep's Chorus recordings against their phone calls, appointments and activities day by day.
What popdock provides
--
Name the rep and the number of days to compare. It finds the rep in Dynamics 365 Sales and in Chorus, noting if their email differs, then reads their recorded conversations alongside their logged calls, appointments and activities. A conversation counts as logged when an activity on the same day or the day after mentions the account or opportunity. You get totals, a table of unlogged conversations and a short list of logged activities with no recording, reported as facts rather than a judgement of the rep. Nothing is written.
Business outcome
---
Your CRM activity history catches up with reality, because you know exactly which conversations were never logged.
scenario
-
A Dynamics 365 Sales opportunity can show a late stage and a near close date with very little conversation to back it up. Checking means reading the account's Chorus calls and emails, and working out which customer attendees are not even contacts yet.
What popdock provides
--
Name the opportunity and the period to review. It reads its stage, probability, revenue and close date in Dynamics 365 Sales with the account's contacts, then the Chorus calls, attendees and emails for the account, matching on the distinctive part of the name and saying so. The review shows a conversation timeline, which customer attendees are not in the CRM, gaps such as the main contact never attending, and signals that contradict the stage. It ends with a verdict of supported, at risk or no evidence, and changes nothing.
Business outcome
---
Forecast calls rest on evidence, because each reviewed deal carries a clear supported, at risk or no evidence verdict.
scenario
-
When an account in Dynamics 365 Sales should start receiving your newsletter, someone has to copy each contact into a Constant Contact list. Done by hand, people who unsubscribed get added back, existing contacts get duplicated, and nobody records the consent basis.
What popdock provides
--
Name the Dynamics 365 Sales account and an existing Constant Contact list, and it reads the account's active contacts with an email. Each person is sorted into unsubscribed, already on the list, in Constant Contact but not on this list, or new, and anyone who unsubscribed is never added. You confirm the new group and say whether you have permission to email them, and permission is set only when you state a consent basis. It never creates a list, and it checks afterwards that each added person is on it.
Business outcome
---
An account's people join your campaign list correctly, with unsubscribes respected and no duplicate contacts created.
scenario
-
People who click or open a Constant Contact campaign are warm, but unless someone moves them into Dynamics 365 Sales they never get a follow-up. Doing it by hand means checking each email against existing contacts and leads first, or you end up with duplicates sales has to merge.
What popdock provides
--
Name the Constant Contact campaign, and choose clicks or opens, and it collects the unique people who engaged. Anyone already a contact or lead in Dynamics 365 Sales is dropped, as is anyone who unsubscribed. You see the proposed leads with name, company, title and phone, rows without a last name are marked as skipped, and you confirm all, some or none. Leads are created with the campaign name as the topic, then read back, and failures are reported without automatic retries.
Business outcome
---
Campaign interest turns into new leads in Dynamics 365 Sales, with no duplicates of people you already know.
scenario
-
Before a call, you want to know whether a person has open deals or support cases in Dynamics 365 Sales, and whether they still read your emails in Constant Contact. Gathering that from two systems, and noticing when they disagree on title or company, takes time you rarely have.
What popdock provides
--
Give an email address, and optionally a look-back period, 90 days by default, and it finds the person as a contact or lead in Dynamics 365 Sales, with their account's open opportunities and cases. It then reads their Constant Contact lists, recent activity, bounces, unsubscribes and notes. Where the two systems disagree on name, title, company or phone, both values are shown, and duplicates in Dynamics are called out. Watch-outs such as an unsubscribed contact with an open deal are flagged, and nothing is changed.
Business outcome
---
You walk into each conversation knowing the person's pipeline, open cases and email engagement, from a single request.
scenario
-
Marketing wants to show that a campaign reached people who matter to sales, but Constant Contact knows about clicks and Dynamics 365 Sales knows about pipeline. Linking the two means matching each engaged email to a contact or lead and then looking up open opportunities at each account.
What popdock provides
--
Name the Constant Contact campaign, and choose clicks or opens, and it collects the unique people who engaged and matches each to a Dynamics 365 Sales contact or lead. Open opportunities at the matched contacts' accounts are rolled up with total estimated revenue, nearest close date and owner. Engaged leads and people unknown to the CRM are listed separately, and a truncated result is called out. It never claims the campaign caused an opportunity, and it only reads.
Business outcome
---
You can show which campaigns reach accounts with live pipeline, using numbers sales already recognizes.
scenario
-
Account managers in Dynamics 365 Sales rarely see how their contacts respond to marketing email. Finding out who at an account opens, who clicks and who has bounced or unsubscribed means searching Constant Contact person by person.
What popdock provides
--
Name the Dynamics 365 Sales account, and optionally a look-back period, 90 days by default, and it reads the account's contacts with an email and checks each in Constant Contact. For each person you get their lists, sends, opens, clicks, last activity and a flag for bounces or unsubscribes, plus the account's five most clicked links. People not in Constant Contact are listed, a failed lookup shows as not checked rather than stopping the report, and a closing line says who is engaged and who has gone quiet. Nothing is changed.
Business outcome
---
Account managers see which contacts are paying attention to your emails and who can no longer be reached.
scenario
-
When an email bounces or someone unsubscribes in Constant Contact, the salesperson who owns that person in Dynamics 365 Sales usually never hears about it. They keep emailing a dead address or someone who opted out, and the bad data stays in the CRM.
What popdock provides
--
Pick a look-back period, 30 days by default, and it collects every bounce and unsubscribe in Constant Contact and matches each email to a Dynamics 365 Sales contact or lead. The report is grouped by owner, showing what happened and when, with permanent bounces called out separately as addresses that likely need correcting. It explains that an unsubscribe is a marketing opt-out, not a ban on one-to-one contact. Truncated results are flagged and nothing is changed in either system.
Business outcome
---
Each salesperson knows which of their contacts can no longer be emailed and which addresses need fixing in the CRM.
scenario
-
Contacts added to Constant Contact from forms and imports do not always exist in Dynamics 365 Sales, and when they do, names, companies, titles and phone numbers often disagree. Checking a list against the CRM means looking up each email and comparing fields side by side.
What popdock provides
--
Name a Constant Contact list, or use the contacts created in the last 30 days, and it looks up each email in Dynamics 365 Sales as a contact, then as a lead. Matched contacts are compared on name, company, job title and phone, with phones compared by digits only. You get four groups: matched and agreeing, matched with differences showing both values, lead only, and not in Dynamics at all. It does not decide which system is right, duplicates in Dynamics are reported rather than compared, and nothing is changed.
Business outcome
---
Marketing and sales work from the same picture of each contact, with every mismatch listed for someone to decide.
scenario
-
A contact's job title or company changes in Dynamics 365 Sales, but Constant Contact still holds the old details, so personalized emails go out wrong. Fixing one record means comparing both screens field by field and retyping the values.
What popdock provides
--
Give an email address and it reads the Dynamics 365 Sales contact and the Constant Contact contact with that address, stopping if either is missing or Dynamics has more than one match. Name, company, job title and phone are compared, phones by digits only, and a blank Dynamics value is never proposed as a replacement. You confirm all, some or none of the differences, then Constant Contact is updated once and read back to show the new values. Email and permission are never changed, and a failure is reported without retrying.
Business outcome
---
One contact's details in Constant Contact match the CRM, so your next email addresses them correctly.
scenario
-
Moving an opportunity forward in Dynamics 365 Sales is quick to do and easy to do badly: a close date in the past, a later stage with a lower probability, or a revenue jump the products do not support. The reason for the change is rarely written down, so nobody can tell later why the forecast moved.
What popdock provides
--
Name the opportunity, give its record ID and describe the change, and it reads the current state, refusing to touch closed deals. It checks that close dates are not in the past, probability fits the stage, and any revenue change over 25 percent is supported by the products. You see a before and after table with warnings and the note text, and nothing is written until you confirm. Only changed fields are sent, a note records why, and the values are read back. It never guesses a record ID.
Business outcome
---
Forecast changes are sense-checked and explained in a note, so the pipeline stays credible.
scenario
-
Adding a lead to Dynamics 365 Sales without checking first creates duplicates, or worse, treats an existing customer as a new prospect. Searching leads, contacts and accounts before every entry is the step people skip, and then the first follow-up never gets scheduled either.
What popdock provides
--
Give the person's name, company, topic and email, and it checks Dynamics 365 Sales for a matching lead and contact by email or name, and for an existing account. A matching lead or contact stops it, and if only the company matches it asks before going ahead. You see the lead it will create and nothing is written until you confirm. It creates the lead, then a first contact task due the next working day, and skips the task if the lead fails.
Business outcome
---
New leads go in once, never as duplicates of a known contact, with a follow-up already booked.
scenario
-
Correcting a phone number, email or address in Dynamics 365 Sales seems trivial, but it is easy to edit the wrong record when names repeat, to blank fields you did not mean to touch, or to give a contact an email that another record already uses. Each slip means bad data that someone else trips over later.
What popdock provides
--
Say whether it is an account, contact or lead, name it, give its record ID and describe the changes, and it finds the one matching record in Dynamics 365 Sales. It lists anything that cannot be changed, checks emails and website addresses look valid, and warns if a new email is already used elsewhere. You see a before and after table and nothing is written until you confirm. Only changed fields are sent, the record is read back, and a record ID is never guessed.
Business outcome
---
Record corrections go to the right account, contact or lead, without side effects on other fields.
scenario
-
Before calling a customer, you want the whole relationship on one page: who the contacts are, open deals and quotes, recent orders, unpaid invoices, open cases, contracts about to expire and the last conversation. In Dynamics 365 Sales that means visiting a dozen related views.
What popdock provides
--
Name the account and a lookback period, and it finds the account in Dynamics 365 Sales, asking you to choose if several match. It gathers contacts, opportunities, quotes, orders, invoices, cases, contracts, entitlements and recent activities and notes, then writes a one-page brief with a snapshot, people, open business, money, service, last contact and watch-outs such as overdue invoices or an expiring contract. Empty sections get one line. No account or activity is edited.
Business outcome
---
Anyone about to talk to a customer is fully briefed on one page.
scenario
-
Campaign reviews in Dynamics 365 Sales mean adding up activity costs, comparing them with budget and expected revenue, and spotting campaigns or activities that ran past their dates. Done by hand, overspend and campaigns that never formally ended are easy to miss.
What popdock provides
--
Name a campaign, or review every campaign started in a recent period, and it reads campaigns and their activities from Dynamics 365 Sales, leaving out templates. It compares spend with budget, flags anything over 100 percent, works out expected return from estimated revenue, and finds campaigns past their end date and activities still open past schedule. You get a campaign table, cost by channel and a problems list, with estimated revenue labelled as estimated. Campaign records stay as they are.
Business outcome
---
Marketing sees which campaigns are over budget or overdue, and their expected return, in one review.
scenario
-
Building a collections list from Dynamics 365 Sales means filtering invoices past due with money still owed, ageing them, and then looking up who to call, when they were last contacted and whether an open complaint explains the delay. By the time that is done, the morning is gone.
What popdock provides
--
Optionally name a customer and a minimum invoice total, and it finds unpaid invoices past due in Dynamics 365 Sales and ages them into 30-day buckets. Customers are ranked by amount overdue with credit limit breaches noted. For the five largest, it adds the contact details, owner, last contact date and any open case that may be holding up payment. Totals are kept per currency, and nothing is changed.
Business outcome
---
Collectors start each day with a ranked list and the context to make every call count.
scenario
-
Discounts creep in deal by deal. Seeing how far below list a product is really sold in Dynamics 365 Sales means comparing price lists with every opportunity, quote, order and invoice line, then working out effective prices, which is too tedious to do regularly.
What popdock provides
--
Name a product, a lookback period and a discount threshold, and it reads the product's list price, standard cost and active price lists in Dynamics 365 Sales. It works out the effective price on every opportunity, quote, order and invoice line, flags lines above the threshold or below cost, and summarizes by source and salesperson. Currencies are audited separately, never mixed. Invoices and accounts are only read.
Business outcome
---
Sales leaders see where discounting is eroding margin, line by line and by salesperson.
scenario
-
Sales goals in Dynamics 365 Sales show a percentage achieved, but not whether that is good enough for how far into the period you are, or whether the open pipeline could close the gap. Working that out for each person is a spreadsheet exercise that is out of date by the time it is finished.
What popdock provides
--
Optionally name an owner, fiscal year and period, and it reads active goals from Dynamics 365 Sales and compares progress with time elapsed, calling a goal behind when it trails by more than ten points. For revenue goals that are behind, it totals open deals closing before the goal ends, raw and probability weighted, and lists the three largest. Count-based goals are compared on deal numbers instead. Each behind goal gets a one-line verdict. Products and price lists are left untouched.
Business outcome
---
Managers know which goals are behind and whether the pipeline can still rescue them.
scenario
-
A weekly pipeline review in Dynamics 365 Sales means scanning open deals for close dates that have already passed, deals no one has touched in weeks, and probabilities that do not match the stage. With dozens of deals, the risky ones hide in plain sight.
What popdock provides
--
Optionally name an owner and a close window, and it confirms the owner's name, then reads open opportunities in Dynamics 365 Sales, including those whose close date has passed. It checks recent activity on the ten largest deals and flags deals overdue, untouched for 21 days, with a probability that contradicts the stage, or with no revenue. You get totals, weighted revenue, a stage breakdown, the at-risk deals and three actions naming specific deals. Goals and opportunities are not edited.
Business outcome
---
Reps and managers spend the week on the deals most likely to slip, not the ones that feel urgent.
scenario
-
Contracts and entitlements expire quietly in Dynamics 365 Sales. Unless someone checks which are ending soon and whether a renewal opportunity is already open, customers reach their end date with nobody talking to them, often while support cases are still unresolved.
What popdock provides
--
Set how far ahead to look, and optionally a customer, and it lists contracts and entitlements ending in Dynamics 365 Sales, plus entitlements nearly used up. For each customer it checks for an open renewal opportunity and counts open cases that could put the renewal at risk. You get counts, a by-customer view sorted by end date, and a list of uncovered customers to act on today. Opportunities are reported, never updated.
Business outcome
---
No renewal reaches its end date without an opportunity open and an owner engaged.
scenario
-
Summarising what a salesperson did in a week means counting calls, emails, meetings and tasks in Dynamics 365 Sales, then checking which deals moved and which closing deals got no attention. Pulling that from several activity views, one rep at a time, takes longer than the conversation it is for.
What popdock provides
--
Name the rep and a lookback period, and it confirms the user in Dynamics 365 Sales, then counts calls, emails, meetings and tasks, deals won and lost, and new leads. It shows which customers got the most attention, open deals closing within 30 days with no recent activity, and overdue tasks. It reports facts only, without grading the person, and changes nothing in Dynamics 365 Sales. If the rep is not found or is disabled, it says so and stops.
Business outcome
---
One-to-one meetings with reps start from recorded facts about activity and deal movement, not from memory.
scenario
-
Escalating a case in Dynamics 365 Sales should do three things: raise the priority, record why, and make sure someone follows up today. Under pressure, people often bump the priority and forget the note or the follow-up, so the escalation leaves no trail.
What popdock provides
--
Give the case number, its record ID and the reason, and it reads the case, refusing to reopen resolved or canceled ones. It gathers the latest activity, the customer's entitlement and other open cases, then shows the new priority, a note with the reason, case age and days since activity, and a follow-up task due today. Nothing is written until you confirm, and the priority is read back. The record ID must come from you; it is never invented.
Business outcome
---
Escalations are recorded properly with a reason and a same-day follow-up, every time.
scenario
-
Quotes sent from Dynamics 365 Sales often stall without anyone noticing. Finding which recent quotes never became orders, which are about to expire, and which have had no contact since they were sent means cross-checking quotes, orders and activities by hand.
What popdock provides
--
Set a lookback period and optionally an owner, and it reads active quotes in Dynamics 365 Sales and drops those already converted to an order, keeping uncertain matches marked as possible orders. It checks for activity since each quote was sent and ranks the rest by value and urgency, expiring and untouched quotes first. You get counts and a follow-up list with a one-line suggested action each. No opportunity is created for you.
Business outcome
---
Stalled quotes get chased before they expire, with the highest value and most urgent ones at the top.
scenario
-
After a customer call, logging it properly in Dynamics 365 Sales means creating the call, writing up the key points and setting a follow-up task, all on the right record. It is the admin people skip, so the next person to pick up the account has no idea what was agreed or what happens next.
What popdock provides
--
Name the record and paste your call summary, and it finds the matching opportunity, case, account, contact or lead and checks recent activities so the follow-up does not duplicate an open one. It drafts the call, a note of decisions and commitments taken only from your summary, and a follow-up task, and writes nothing until you confirm. Without a record ID it logs unlinked activities, skips the note and tells you. It asks for the next action if the summary is too thin.
Business outcome
---
Every call is logged with the key points and a follow-up, in the time it takes to paste notes.
scenario
-
Setting up a new customer in Dynamics 365 Sales takes several linked steps: the account, the primary contact, linking the two, and often a first opportunity and follow-up. Done by hand, steps get missed or the company gets created twice under slightly different names.
What popdock provides
--
Give the company and contact, and optionally a first opportunity topic, and it checks Dynamics 365 Sales for an existing account, contact or lead, stopping on a match and asking about an open lead. You confirm the plan once. It then creates the account, the contact linked to it, sets them as primary contact, and adds the opportunity and a follow-up task if asked. If a step fails it stops and reports what was created, without retrying or undoing.
Business outcome
---
New customers are set up completely and correctly linked in one confirmed pass, with no duplicates.
scenario
-
Opening a case in Dynamics 365 Sales without checking first means duplicate cases for the same issue, and support often does not know whether the customer has an active entitlement or whether a knowledge article already covers the problem. The customer then explains the same issue twice.
What popdock provides
--
Name the customer, describe the issue and give the customer's record ID, and it confirms the account or contact, then checks Dynamics 365 Sales for an open case about the same issue and asks before creating another. It notes the entitlement position and suggests up to two knowledge articles. You see the case to be created and nothing is written until you confirm. Articles are recorded as a note only if you want, and a record ID is never guessed.
Business outcome
---
Cases are opened once, with entitlement status and possible fixes in hand from the start.
scenario
-
Getting a straight answer about one deal in Dynamics 365 Sales means reading its products, quotes, emails, calls, meetings and notes, then judging whether the stage, probability and close date are believable. Busy reps rarely do this before a forecast call.
What popdock provides
--
Name the opportunity, and it reads its products and compares their total with estimated revenue, checks the latest quote for manual discounts, and builds a timeline of the last ten touchpoints from Dynamics 365 Sales. It checks whether stage, probability and close date fit the evidence and whether a next step is booked, lists risks each backed by a fact, and recommends one next step. Changes are suggestions only, missing evidence is stated plainly, and nothing is changed.
Business outcome
---
Forecast calls rest on evidence, with one clear next step for every reviewed deal.
scenario
-
Overdue tasks and calls pile up in Dynamics 365 Sales until the list is too long to act on. Without grouping them by the deal or case they relate to, it is hard to see which overdue work actually matters and which can simply be closed. Managers end up nagging about volume rather than the work that matters.
What popdock provides
--
Optionally name an owner and activity type, and it reads open activities past due in Dynamics 365 Sales, adds task and call detail, and groups them by the record they relate to. Work on high value deals or high priority cases comes first. You get counts by type and age, a grouped table, activities with no related record, and those over 30 days old suggested for closing or rescheduling. It suggests only and changes nothing.
Business outcome
---
Overdue work is cleared in order of importance instead of left to grow.
scenario
-
A batch of new leads in Dynamics 365 Sales usually hides existing customers, people already known as contacts, and duplicates. Calling them in the order they arrived wastes time and annoys account owners whose customers get cold-called by someone else on the team.
What popdock provides
--
Set a lookback period and optionally an owner and source, and it reads open leads in Dynamics 365 Sales and checks up to 50 against accounts by company and contacts by email. Duplicates need the same email or company, never name alone. The rest are ranked by rating, value and recency, and leads missing both email and phone go last. You get a ranked call list plus the customers, duplicates and unworkable leads. No lead is converted, merged or edited.
Business outcome
---
Reps call the best new leads first and stop cold-calling existing customers.
scenario
-
A large backlog of open cases in Dynamics 365 Sales makes it hard to know what to work first. Urgency depends on priority, age and resolve-by dates, and some customers have expired entitlements that need a commercial conversation as well as a fix. Sorting that out by eye across hundreds of cases rarely happens.
What popdock provides
--
Optionally filter by owner, customer and priority, and it reads open cases in Dynamics 365 Sales, works out age and resolve-by status, and marks a case urgent if it has top priority, has passed its resolve-by date or is over 14 days old. It checks entitlements for urgent customers, suggests up to two knowledge articles for the five most urgent cases without claiming they solve them, and gives a ranked work order with reasons. Cases are ranked, never edited.
Business outcome
---
Support works the backlog in the right order, with entitlement problems flagged for account owners.
scenario
-
After a webinar, attendees need to reach sales quickly, but importing them into Dynamics 365 Sales by hand creates duplicates of people who are already contacts or leads, and the context of what they asked during the session is lost. By the time the list is cleaned up, interest has cooled.
What popdock provides
--
Name the webinar, and optionally include no-shows, and it reads attendees, registrants and questions from GoTo Webinar, then drops anyone already a contact or lead in Dynamics 365 Sales, matched by email only. You review the list, can remove rows, and nothing is created until you confirm. Up to 25 leads are created per run, each with a note of attendance and questions quoted as asked. People missing an email or last name are listed, not created, and each lead is checked afterwards.
Business outcome
---
Webinar attendees reach sales as new leads with context, without duplicating anyone already in the CRM.
scenario
-
Account managers rarely know which people at a customer have been attending webinars. Finding out means listing the account's contacts and leads in Dynamics 365 Sales and searching GoTo Webinar for each email across registrations, attendance and questions.
What popdock provides
--
Name the account and a lookback period, and it finds the account's contacts and leads in Dynamics 365 Sales, then checks each email in GoTo Webinar for registrations, attendance, no-shows and questions. Matching is by email only, never by name. You get a table of active people, a count of those with none, the most engaged person and any webinar several people attended. People without an email are marked not checked. No contact or lead is created.
Business outcome
---
Account managers see who at a customer is engaging with webinars before their next conversation.
scenario
-
Judging whether a webinar campaign paid off means combining registration and attendance figures from GoTo Webinar with campaign costs and pipeline in Dynamics 365 Sales. Matching attendees to contacts and leads, then finding their accounts' open deals, is slow by hand.
What popdock provides
--
Name the campaign, and optionally the webinar, and it reads the Dynamics 365 Sales campaign and the matching GoTo Webinar session counts and attendee emails. Up to 50 emails are matched to contacts or leads, attendees first, and open opportunities at their accounts are totalled. You get a funnel table and cost per attendee when a cost exists. The report says the pipeline is associated with the webinar, not caused by it, and notes when counts are a lower bound. The campaign and its contacts stay untouched.
Business outcome
---
Marketing reports a webinar campaign's funnel and associated pipeline with honest caveats.
scenario
-
After a webinar, sales wants to know who registered: which are existing contacts, which are leads already being worked, and which are new names. Checking hundreds of registrants against Dynamics 365 Sales one email at a time is not practical, so the list often goes to sales unchecked and full of known names.
What popdock provides
--
Name the webinar, and optionally its date, and it reads GoTo Webinar registrants and attendees, marks who attended, then looks each email up in Dynamics 365 Sales as a contact, then a lead. Matching is by email only, attendees are checked first, and it stops after 50 and says how many were left. You get a summary and three tables with owners, and duplicate contacts are flagged. No lead or contact is created by this check.
Business outcome
---
Sales knows within minutes which webinar registrants are customers, active leads or brand new.
scenario
-
Not every webinar attendee deserves the same follow-up. Someone who stayed the whole hour, asked questions and answered the survey is far warmer than someone who dropped in for five minutes, but GoTo Webinar engagement data rarely makes it to the Dynamics 365 Sales owner.
What popdock provides
--
Name the webinar and how many top attendees you want, and it scores attendees from GoTo Webinar on minutes attended, questions, poll answers and survey responses, stating the rule once. The top attendees are matched by email to Dynamics 365 Sales contacts or leads, with owners and open opportunities at their accounts. Each gets a suggested next step based on what they asked, quoted as written and treated as data. Ties go to time attended, and nothing is changed.
Business outcome
---
Sales follows up the most engaged webinar attendees first, with context for every call.
scenario
-
Inviting the contacts at a key account to an upcoming webinar means exporting them from Dynamics 365 Sales and registering each one in GoTo Webinar, while checking nobody is already registered and remembering that every registration sends an email. One slip means a contact gets invited twice.
What popdock provides
--
Name the account and the upcoming webinar, and it finds only future sessions in GoTo Webinar and needs the organizer key, asking rather than guessing. It lists the account's contacts from Dynamics 365 Sales and skips anyone already registered. You see the webinar and people, are reminded each gets a confirmation email, and nothing is registered until you confirm. Up to 25 people are registered per run, contacts missing details are listed, and each registration is checked with its join link.
Business outcome
---
Key account contacts are registered for the right webinar once, with no double invitations.
scenario
-
Questions left unanswered at the end of a webinar are a buying signal that usually gets lost. Getting each one to the right person means finding the asker in Dynamics 365 Sales, working out who owns them, and checking whether their company already has an open case.
What popdock provides
--
Name the webinar, and optionally its date, and it finds the unanswered questions in GoTo Webinar and looks each asker up by email in Dynamics 365 Sales as a contact, then a lead. Questions are grouped by owner with the company and any open cases, up to five per company, and askers with no match go in a separate group. Questions are quoted as asked and treated as data, not answered unless you ask. No case, task or note is created.
Business outcome
---
Every unanswered webinar question reaches the person who owns the relationship, along with any open cases at that company.
scenario
-
When an account in Dynamics 365 Sales needs a nurture series, someone exports its contacts, filters by job title and imports them into the Drip campaign. Along the way people already in the campaign get added again, and contacts who unsubscribed from Drip can end up back on your mailing.
What popdock provides
--
Name a Dynamics 365 Sales account, a Drip campaign and optionally a job title, and it reads the account's active contacts and checks each email in Drip. Every contact is marked to add, skip as unsubscribed, skip as already in the campaign, or skip with no email. You confirm the add rows first, with a note that Drip creates people who are not there yet, and a warning if the campaign is not active. Unsubscribed people are never added, and the campaign is re-read afterwards to report added, skipped and failed.
Business outcome
---
The right account contacts land in the Drip campaign once, with opt-outs respected and every skip explained.
scenario
-
High lead scores in Drip mean nothing if sales never sees them in Dynamics 365 Sales. Acting on them means checking each email against contacts and leads, creating leads for new people and follow-up tasks for known ones, without duplicating a lead or reviving someone sales already disqualified.
What popdock provides
--
Set a minimum lead score and how many subscribers to check, and it reads active Drip subscribers and checks each email against Dynamics 365 Sales contacts and leads. People are grouped as not in the CRM, already open, or disqualified, and disqualified people are left alone. It proposes a lead for each new person and a follow-up task naming the score and tags for each known one. You can drop rows, and nothing is created until you confirm. New leads are read back and failures reported without stopping the rest.
Business outcome
---
Every hot Drip subscriber is either a new Dynamics 365 Sales lead or a follow-up task, with no duplicate leads.
scenario
-
A rep preparing for a meeting needs to know how a person engages with Drip email and where they stand in Dynamics 365 Sales: open deals, recent wins and losses, support cases. Gathering that means separate searches across contacts, leads, opportunities and cases, and conflicts like an unsubscribed buyer go unseen.
What popdock provides
--
Give an email address, and it reads the person's Drip status, lead score, lifetime value, tags and campaigns, then finds them as a Dynamics 365 Sales contact or lead. Using their account it pulls open opportunities with revenue, stage and close date, recent wins and losses, and open support cases. The profile ends with watch-outs such as unsubscribed in Drip with an open deal. It matches on email only, reports whichever side exists if the other is missing, and creates or updates nothing.
Business outcome
---
One read-only briefing covers marketing engagement, deals and support for a person before you talk to them.
scenario
-
Marketing wants to show that a Drip campaign touches real pipeline in Dynamics 365 Sales. Proving it means exporting subscribers, matching them to CRM contacts, rolling up to accounts and pulling opportunities, then making sure a deal is not counted twice when several subscribers share an account.
What popdock provides
--
Name a Drip campaign and an opportunity status, open by default, and it reads up to 100 subscribers, matches them to Dynamics 365 Sales contacts by email and pulls opportunities for their accounts. You see how many subscribers matched, a table of accounts with topic, revenue, stage, close date and owner, and total estimated revenue with each opportunity counted once. It describes subscribers as linked to deals, never as having generated them, says when the list was cut short, and changes nothing.
Business outcome
---
You see the Dynamics 365 Sales pipeline connected to a Drip campaign, counted once and framed honestly.
scenario
-
People who unsubscribe in Drip can still be active contacts or open leads in Dynamics 365 Sales, and a rep may add them to a marketing send without knowing. Spotting them means checking every unsubscriber against contacts, leads and their account's open opportunities, which rarely happens.
What popdock provides
--
Optionally give an email domain and how many unsubscribers to check, and it reads Drip unsubscribers and looks each email up as a Dynamics 365 Sales contact and lead, then pulls open opportunities for active contacts' accounts. The table shows record type, status, owner and open deals, with people tied to open opportunities first, and a count of unsubscribers with no CRM record. It treats an unsubscribe as do not send marketing email, not a reason to close a deal, and never resubscribes or edits anyone.
Business outcome
---
Sales knows which active contacts and leads opted out of marketing email, without any record being changed.
scenario
-
A customer with an urgent support case in Dynamics 365 Sales should not be getting cheerful promotions from Drip. Finding them means listing high-priority cases, working out the contacts behind each one, and checking what Drip is still sending, before anyone can hold the email.
What popdock provides
--
Choose a case priority and a tag, and it reads active Dynamics 365 Sales cases at that priority, finds the contacts behind each and shows which Drip campaigns they are still active in. A table lists case, customer, contact, Drip status and whether they are already tagged. Nothing is tagged until you confirm, and each tag is read back. If a name matches several contacts none are tagged. It never pauses or removes campaigns or changes the cases, though it may recommend a pause.
Business outcome
---
Customers with open high-priority cases are tagged in Drip so promotions can be held, with cases left untouched.
scenario
-
The contacts on a Dynamics 365 Sales account and the subscribers in Drip drift apart: people missing from Drip, contacts inactive in the CRM but still mailed, names spelled differently. Auditing one account means checking each contact by hand and noting what disagrees.
What popdock provides
--
Name a Dynamics 365 Sales account and how many contacts to check, and it reads the account's contacts and looks each email up in Drip. Every contact gets one finding: not in Drip, unsubscribed in Drip, inactive in CRM but active in Drip, name differs, matched, or no email, with counts per finding. If the account name matches several accounts it stops so you can pick. A failed lookup is marked and the rest continue. Fixes are suggested, never made, in either system.
Business outcome
---
A clear account-by-account list of where your CRM and Drip disagree, ready for someone to fix.
scenario
-
When a deal closes in Dynamics 365 Sales, the new customer keeps getting prospect emails from Drip until someone remembers to tag them. That means listing won opportunities, finding the contacts behind each customer, and tagging them in Drip one by one, so new customers are often missed.
What popdock provides
--
Give a start date and a tag, and it reads Dynamics 365 Sales opportunities won since then, finds the contacts behind each customer and checks each email in Drip. Rows are marked to tag, skip as already tagged, or skip as not in Drip. Nothing is tagged until you confirm the table, and each tag is read back afterwards. People missing from Drip are never created, customers with no reachable contact are listed rather than dropped, and nothing in Dynamics 365 Sales is changed.
Business outcome
---
New customers are tagged in Drip soon after the deal is won, so prospect messaging stops reaching them.
scenario
-
When sales signs up a new account in Dynamics 365 Sales, someone in finance has to create the same customer in Business Central before an order can be invoiced. Checking each account by number and name, retyping the address and credit limit, and avoiding near-duplicates is slow, so new customers are often missing when the first order arrives.
What popdock provides
--
Name a Business Central company, and optionally a state and how many to create, and it reads active Dynamics 365 Sales accounts and looks each one up in Business Central by account number, then by name. A name match only counts when the email or city also agrees, and anything doubtful is set aside as a possible duplicate rather than created. You see a table of the missing customers and nothing is created until you confirm, then each confirmed account is created once and the new customer numbers are reported.
Business outcome
---
Customers sold in Dynamics 365 Sales are ready to invoice in Business Central, without duplicates or retyped details.
scenario
-
Customers that buy through finance or are set up directly in Business Central often never reach Dynamics 365 Sales, so the sales team has no account, no owner and no reason to call them. Finding those gaps means comparing two customer lists by number and name and copying each record across by hand.
What popdock provides
--
Name a Business Central company and how many to add, and it reads Business Central customers that are not blocked, favoring those with sales, and checks each one in Dynamics 365 Sales by account number, then by name. Name-only matches that disagree on email or city are listed as possible duplicates and left alone. You review the missing customers, highest sales first, and nothing is written until you confirm. Each confirmed customer becomes a Dynamics 365 Sales account carrying the Business Central number, with a follow-up task to introduce the account owner.
Business outcome
---
Every customer that buys from you has an account and a next step in Dynamics 365 Sales, with no duplicates.
scenario
-
A rep closing a deal in Dynamics 365 Sales rarely knows the customer is over its credit limit or has invoices months overdue in Business Central. Finding out means asking finance, who look up the customer, add up open orders and overdue invoices and check for reminders, often after the order is already promised.
What popdock provides
--
Name the opportunity, and it finds it in Dynamics 365 Sales, resolves the account and matches the customer in Business Central by account number, then by name and email. It then reads overdue posted invoices and any reminders, and works out the credit headroom including the deal itself. You get a verdict of clear, caution or hold with the reasons, the credit and overdue figures, and a note when the two systems hold different credit limits. Nothing is changed in either system, and it says which match rule it used.
Business outcome
---
Reps know before closing whether finance will hold the order, so deals are not promised to customers on credit hold.
scenario
-
Quotes in Dynamics 365 Sales are built from price lists that drift away from the item prices, costs and stock in Business Central. Checking each line means opening every item in Business Central, comparing prices, working out margin and stock by hand, and it is usually skipped, so quotes go out below cost or for items that cannot ship.
What popdock provides
--
Name the quote, and it reads every product line in Dynamics 365 Sales and looks up the matching Business Central item by number. Each line shows the quoted price against the Business Central unit price, the margin against unit cost, and the stock available after open sales orders. Lines are flagged when they are below cost, priced differently, short on stock, blocked or missing from Business Central, with totals at quoted price, list price and cost. Nothing is changed in either system.
Business outcome
---
Quotes go out at a margin you meant, for items you can ship, before the customer sees them.
scenario
-
Orders won in Dynamics 365 Sales have to be keyed again into Business Central before they can ship. Finding the customer, matching each product to an item, copying quantities and prices and avoiding entering the same order twice is slow, and a missed check means duplicate or wrongly priced orders.
What popdock provides
--
Name the Dynamics 365 Sales order, and it first checks Business Central for an order already carrying that order id and stops if one exists. It matches the customer by account number, then name, stops if the customer is missing or blocked, and maps each product to a Business Central item. You see the mapped lines with both prices and any unmapped lines, and nothing is created until you confirm. The order and its lines are then created once, keeping the price that was sold, and the stored lines are read back and totaled against Dynamics 365.
Business outcome
---
Won orders reach Business Central once, at the price sold, without retyping or duplicate orders.
scenario
-
Finance chases overdue invoices in Business Central while sales keeps working new deals and orders for the same customers in Dynamics 365 Sales. Linking the two means grouping overdue invoices by customer, then searching Dynamics 365 Sales for each account and its open pipeline, which rarely happens before the next deal is signed.
What popdock provides
--
Name a Business Central company and a minimum overdue amount, and it totals overdue posted invoices by customer, then adds each customer's credit limit, balance and blocked flag. Each customer is matched to a Dynamics 365 Sales account by number, then by name, with name-only matches marked for checking. You get a list sorted by overdue total showing the open opportunities and unfulfilled orders at risk and their owners. Currencies are not converted, and nothing is changed in either system.
Business outcome
---
Sales and finance agree which deals to hold or escalate before more is sold to customers who are not paying.
scenario
-
The same customer is kept in Dynamics 365 Sales and in Business Central, and addresses, phone numbers, emails and credit limits drift apart. Finding the differences means opening both records and comparing every field by hand, and conflicting numbers between the two systems go unnoticed.
What popdock provides
--
Name a Dynamics 365 Sales account, and it finds the matching Business Central customer by account number, then name, then email, and says how it matched. Every shared field is compared, ignoring case, spacing, phone punctuation and country name versus code. You get a field-by-field table marked match, differs or missing on either side, the customer's balance due and blocked flag, and a recommendation of which system looks out of date. A number that points at a clearly different company is reported as a conflict. Nothing is changed in either system.
Business outcome
---
Customer records in sales and finance agree, and you know which side to correct for each difference.
scenario
-
When a customer asks where their order is, the rep sees it in Dynamics 365 Sales but the shipment, invoice and payment are in Business Central. Following it means finding the matching sales order, comparing lines, then hunting for the posted invoice and its balance, across two systems.
What popdock provides
--
Name the Dynamics 365 Sales order, and it finds the matching Business Central document by external document number, then by order name, then by customer, date and total. It compares each line's quantity, shipped and invoiced against Dynamics 365, then finds the posted invoice and its remaining amount. You get one stage, from not in Business Central to paid, a timeline and a line table with differences flagged. Totals that differ are shown side by side without assuming which is wrong, and nothing is changed in either system.
Business outcome
---
Anyone can answer where an order is, from quote to cash, in one step and without a Business Central login.
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.