CRM
OnePageCRM
Connect your AI to OnePageCRM
Sales reps, sales managers, and business owners and account managers run their pipeline through OnePageCRM, but the answers they need span contacts, companies, deals, next actions, calls, meetings, and notes that live on separate screens. AI can pull those together in seconds, but only if it respects each user's account rights and record ownership, and only surfaces the records the signed-in user is allowed to see.
Why it matters
Capabilities that matter most for OnePageCRM
01
Your next actions, in one answer
Ask which contacts have no next action or a lapsed one, and get the list from the OnePageCRM action stream instead of filtering screens by hand.
02
Deals, companies and contacts together
Popdock joins the contacts, companies and deals of an account, so one question returns the whole picture with its totals and risks.
03
Calls, meetings and notes included
The history behind a contact is readable too, so a call brief or an activity summary draws on what was actually logged.
03
Ready-made apps in the app store
Read-only OnePageCRM apps for pipeline review, forecasts and overdue actions install from the Popdock app store without building anything.
05
Joined to your email and call tools
Use OnePageCRM with Mailchimp, Constant Contact, Drip and Chorus to check who is missing from a list or has no recorded call, matched on email.
06
Governed by your account rights
Answers respect OnePageCRM user rights and record ownership, so people only see the records they are allowed to see.
Use cases
Example AI Use Cases for OnePageCRM
scenario
-
Leads go cold in OnePageCRM because nobody sees the contacts with no next action, or one whose date has already passed. Finding them means filtering the action stream, then checking each contact for when it last changed, and the quiet ones are easy to miss.
What popdock provides
--
Optionally name an owner or a contact status, and it reads the OnePageCRM action stream and sorts contacts into three lists: no next action, a lapsed action date, and nothing changed in 30 days. Each list shows the contact, company, last change and tags, most neglected first, with counts. It suggests a next step for the five most neglected. It is read-only, creates no actions, and says so plainly when nothing comes back.
Business outcome
---
Neglected contacts surface before the lead goes cold, ranked so you know who to call first, with nothing changed in OnePageCRM.
scenario
-
Before a call a rep clicks through a contact, then their deals, actions, notes, calls and meetings in OnePageCRM to piece the history together. It takes minutes, and a recent note or an overdue action is easy to miss.
What popdock provides
--
Give an email address or a last name and it finds the one contact in OnePageCRM, and stops to ask if several people match or none do. It then gathers their deals, actions, notes, calls and meetings into one brief: who they are, open deals and amounts, what is next and what is overdue, the last five touches and two or three talking points. Notes are quoted as written and it is read-only.
Business outcome
---
You walk into the call with the full history in one brief, drawn only from what OnePageCRM holds.
scenario
-
At an account, nobody can say which OnePageCRM contacts have ever spoken on a recorded Chorus call, or who joins calls but was never added to the CRM. Comparing the two means matching names and emails across systems by hand.
What popdock provides
--
Name the company and how far back to look, and it reads the company contacts from OnePageCRM and the attendees of its Chorus conversations. It joins them on email, falling back to an exact name match that it marks as weak. You see who attended and how often, who has never been heard on a recording, and external attendees missing from OnePageCRM as candidates to add. It is read-only and creates or updates no contacts.
Business outcome
---
You see which contacts are engaged on calls and which attendees are missing from the CRM, matched on email, with nothing written.
scenario
-
To see how a contact reads your email, a rep looks them up in Constant Contact, then opens OnePageCRM for their deals. The opens, clicks and opt-outs never sit beside the pipeline, so a rep can chase someone who has already opted out.
What popdock provides
--
Give a contact email and it finds the person in OnePageCRM, stopping if none or several match, then finds the same address in Constant Contact. It counts campaign opens and clicks over your lookback window and notes any unsubscribe or bounce with its date and reason. That sits beside their OnePageCRM deals and next action, and an opt-out against an open deal is flagged. It is read-only.
Business outcome
---
You see email engagement and open deals for one person together, with opt-outs flagged before anyone sends another message.
scenario
-
People unsubscribe or bounce in Constant Contact while sales keeps emailing them about a live deal in OnePageCRM. Nobody lines the two up, so the conflict is found when the customer complains.
What popdock provides
--
Choose a lookback window and optionally a campaign, and it collects the Constant Contact unsubscribes and bounces, then looks each person up in OnePageCRM by email. For those found it keeps open deals and pending actions, and reports the reason, date, deal stage, amount and action due. It never suggests emailing an unsubscribed person, treats hard bounces as address errors to correct, and is read-only.
Business outcome
---
Owners learn who has opted out while a deal is live, so outreach stops or moves to the phone before it causes harm.
scenario
-
Reps open a deal in OnePageCRM and then dig through Drip separately to see whether the contact reads their emails. The subscription, tags and campaigns live in another system, so most reps skip the check.
What popdock provides
--
Name a deal and a Drip account and it finds the deal in OnePageCRM, stopping to list them if several match. It takes the deal contact email, looks that person up in Drip, and reports their subscription status, lead score, lifetime value, tags and each campaign. Matching is on email only, an unsubscribed contact is called out prominently, and it is read-only.
Business outcome
---
You see how a deal contact engages with email without leaving the deal, with unsubscribed contacts flagged up front.
scenario
-
Engaged subscribers pile up in Drip while the CRM never hears about them, because nobody cross-checks the two systems. The people most worth a call are the ones with a high lead score and no OnePageCRM record.
What popdock provides
--
Name a Drip account and optionally a start date and a limit, and it reads the subscribers, then checks each email in OnePageCRM. Subscribers with no matching contact are listed by lead score with their name, tags and created date, and the matched ones are counted. Subscribers with no email are listed separately. Matching is on email only and nothing is written to either system.
Business outcome
---
High-scoring subscribers who are missing from the CRM are ranked for follow-up, with no records changed.
scenario
-
Marketers compare a CRM export against a Mailchimp audience by hand. Contacts who were never added, or who sit on the audience but have unsubscribed, go unnoticed until a campaign misses them.
What popdock provides
--
Name a Mailchimp audience and optionally an owner, and it reads the OnePageCRM contacts that have an email and the members of that audience. It matches on email and reports three groups: contacts missing from Mailchimp, contacts present but not subscribed with the status and reason, and contacts with no email. It is read-only and never re-subscribes anyone who unsubscribed or was cleaned.
Business outcome
---
You know exactly who to add to the audience and who must be left alone, without a spreadsheet match.
scenario
-
Comparing CRM contacts with the email list by hand leaves gaps nobody notices. A contact is missing from Constant Contact, or is there with permission to send withheld, and the campaign quietly skips them.
What popdock provides
--
Optionally give a contact status and a limit, and it reads OnePageCRM contacts that have an email, then checks each address in Constant Contact. You get three results: contacts missing from Constant Contact with their owner and lead source, contacts present where permission to send is not granted, and a count that match cleanly. Contacts with no email are skipped, it says when the limit cut the list short, and it writes nothing.
Business outcome
---
Gaps between the CRM and the email list are listed with owners, so the right people can be added or asked.
scenario
-
Revenue forecasts get built by exporting OnePageCRM deals and totalling them in a spreadsheet. Open deals get mixed with won and lost ones, and nobody agrees which deals are likely and which are at risk.
What popdock provides
--
Give a start and end date and optionally an owner, and it reads the deals expected to close in that window. It separates open from won and lost deals, totals the open amounts by stage, and splits late-stage deals as likely from early-stage ones as at risk. You get a short summary and a table by expected close date, and deals with no amount are named. The figures are unweighted, no probabilities are invented, and invalid dates stop the run.
Business outcome
---
You get a clear open-deal forecast for any window in one answer, with honest unweighted totals and no spreadsheet.
scenario
-
Clicks on a campaign never reach the reps who could act on them. The marketer sees who clicked in Constant Contact, but nobody checks which clickers already have an open deal or a next action in OnePageCRM.
What popdock provides
--
Name a campaign and a lookback window and it finds the Constant Contact campaign, stopping if several match. It counts each clicker clicks and distinct links, then looks them up in OnePageCRM by email and keeps their open deals and next action. The result ranks clickers by clicks with company, deals and the CRM next step, and lists clickers who are not in OnePageCRM separately. It is read-only.
Business outcome
---
Reps see which warm clickers already have live deals, so follow-up goes to the right people first.
scenario
-
Unsubscribes sit in Mailchimp while reps keep emailing the same people about live deals in OnePageCRM. Nobody lines the two up, so the conflict surfaces when the customer complains.
What popdock provides
--
Choose a lookback window and optionally a campaign, and it reads recent Mailchimp unsubscribes, then looks each address up in OnePageCRM. For people found it lists their open deals, amounts, owner and next action date, sorted by pending amount, with a note on who should be told to stop email outreach. Duplicates are listed rather than guessed, it stops if there are no unsubscribes, and it is read-only.
Business outcome
---
Owners know which people with live deals have opted out of email, so outreach stops before it does damage.
scenario
-
Preparing for an account means checking the company, contacts and deals in OnePageCRM, then hunting through Chorus recordings and emails separately. The two never get lined up, so a deal with no recorded conversation hides in plain sight.
What popdock provides
--
Name the company and it finds it in OnePageCRM, listing the options and stopping if several match. It reads the contacts and deals, then carries the account over to Chorus and reads its conversations and emails for the window, telling you whether the match was exact or partial. The briefing sets deal totals, next actions and open deals beside the latest conversation and flags deals with no recorded conversation. It is read-only and does not quote email bodies.
Business outcome
---
You get one account briefing that joins the CRM picture with what was said on calls, and shows which deals have no conversation behind them.
scenario
-
Coaching reviews mix OnePageCRM activity counts with Chorus scorecards by hand. The manager ends up with one-sided evidence, either what the rep logged or how the calls were scored, and rarely both.
What popdock provides
--
Give a rep email and a lookback window and it finds the person in both systems, carrying on with one side if the other has no match. It counts completed and overdue actions and open deals in OnePageCRM, and reads the rep Chorus conversations, scorecards and question scores. You get volume against deals owned, accounts with open deals but no recorded call, the average score and the lowest questions, and two or three coaching points tied to the evidence. Sample sizes are stated, reps are not ranked against each other, and it is read-only.
Business outcome
---
A coaching conversation rests on evidence from both systems, with sample sizes stated and no comparison between reps.
scenario
-
Managers cannot tell which open deals have gone quiet without opening OnePageCRM and Chorus deal by deal. A deal can look healthy in the CRM while nobody has spoken to the customer for weeks.
What popdock provides
--
Give a close-by date and a quiet period and it reads the open deals in OnePageCRM, then checks Chorus for a recent conversation on each deal company, retrying with a partial name match. Where there is no conversation it checks emails to tell a silent deal from one run over email. The table, sorted by amount, flags each deal Quiet, Email only or Active with totals per flag. Company names that do not match are marked as unmatched rather than called quiet, and it is read-only.
Business outcome
---
Leaders see which open deals have gone quiet and how much money sits in them, without opening both systems deal by deal.
scenario
-
Reps cannot tell which open deals have contacts actually reading their email. Without that, follow-up goes to whoever is loudest in the pipeline rather than to the deals that are warm.
What popdock provides
--
Optionally give a stage and a campaign name, and it reads the open deals in OnePageCRM and finds each deal contact email. It then looks each address up in Mailchimp for subscription status, open and click rates, and whether they opened the named campaign. Deals are ranked by amount with a one-line suggestion such as follow up now or nurture, and unsubscribed contacts are marked do-not-email. Missing rates show as unknown, never invented, and it is read-only.
Business outcome
---
Reps spend their follow-up on the warmest deals, and nobody emails a contact who unsubscribed.
scenario
-
Marketers compare OnePageCRM contact lists with Drip by hand, so people who are missing from Drip, or still active in the CRM after unsubscribing, go unnoticed. A campaign then reaches the wrong people.
What popdock provides
--
Optionally give a contact status, a limit and a Drip account, and it reads the OnePageCRM contacts and looks each email up in Drip. You get three tables: matched contacts with their CRM and Drip status, contacts in OnePageCRM only, and contacts with no email. Matches where Drip shows unsubscribed but the CRM contact is active are flagged. Matching is on email only, ambiguous matches are listed rather than guessed, and it is read-only.
Business outcome
---
You see exactly where the CRM and Drip disagree, including active contacts who have unsubscribed, without a manual match.
scenario
-
Names, statuses and tags drift apart between OnePageCRM and Mailchimp. Nobody can see where without a manual spreadsheet match, so a lost lead stays subscribed or a tag is missing on one side.
What popdock provides
--
Name a Mailchimp audience and optionally an owner, and it reads the OnePageCRM contacts with an email and the audience members. It matches on email and compares only name, status and tags, since Mailchimp returns no company or phone here. Only the disagreements are reported, one row per person with both values, a suggested fix and which system to change, followed by counts. Differences in case or spacing are treated as minor, and it is read-only.
Business outcome
---
You get a short list of real disagreements with a suggested fix for each, instead of a full export to compare by hand.
scenario
-
Meetings and calls logged in OnePageCRM, and conversations recorded in Chorus, get compared by eye. Unlogged meetings and unrecorded ones both go unnoticed, so the CRM and the recordings tell different stories.
What popdock provides
--
Name the company and a lookback window and it finds the company in OnePageCRM, then reads the meetings and calls for its contacts. It reads the account Chorus conversations and matches by calendar day, using the participants to settle days with several calls. You get matched pairs, CRM meetings or calls with no recording, and Chorus conversations with no CRM record, with counts. Day matching is described as a heuristic, it stops if the company cannot be found, and it is read-only.
Business outcome
---
You see which meetings are missing from the CRM and which were never recorded, so records and recordings line up.
scenario
-
Understanding an account in OnePageCRM means opening the company, then each contact, then each deal, and adding up the totals yourself. The company totals and the deal list do not always agree, and the notes that explain why sit on separate records.
What popdock provides
--
Name a company and it finds it in OnePageCRM, listing the options and stopping to ask if several match. It reads the contacts and deals, and the latest notes for up to five of the most active contacts. The review gives the company totals, contact and deal tables, risks such as open deals past their close date and contacts with no next action, and a short paragraph on the relationship based only on the records. If the totals disagree with the deal list it says so, and it is read-only.
Business outcome
---
You get a complete account review in one answer, with risks called out and any mismatched totals flagged.
scenario
-
Overdue follow-ups hide in individual contact records, so nobody sees which reps are behind. Finding them means opening contacts one at a time and checking each action date.
What popdock provides
--
Optionally give a cut-off date, which defaults to today, and an assignee. It reads the OnePageCRM actions due on or before that date and not yet done, then names the people behind the assignee ids. The overdue actions are grouped by assignee with the action text, due date, days overdue, contact and company, oldest first, followed by counts and the five most overdue items. It never changes actions, pointing you to the reschedule job instead, and says so when nothing is overdue.
Business outcome
---
Managers see which reps are behind and which follow-ups are most overdue, with no records changed.
scenario
-
Managers scan the OnePageCRM deal list by hand to spot stalled deals. Overdue deals and half-filled ones, with no amount or close date, slip through, and nobody agrees which deals to act on first.
What popdock provides
--
Optionally name a stage or an owner and it reads the open deals from OnePageCRM, working out which status means open if that is unclear. It flags deals overdue past their expected close date and deals missing an amount or close date, and notes the largest deals and any with low margin. You get a table grouped by stage, the top five deals to act on with the reason, and the open amount per stage. It never invents amounts or dates, and it is read-only.
Business outcome
---
Managers know which deals to act on first and which records are incomplete, without scanning the list by hand.
scenario
-
Managers cannot easily see how much calling, meeting and note-taking the team did in a period. The numbers sit in three separate OnePageCRM logs, so a summary means counting by hand.
What popdock provides
--
Give a date range and optionally an author and it reads the calls, meetings and notes logged in that period. It counts each per author, breaks calls down by result and finds the contacts touched most often. You get a headline, a per-author table, the call result breakdown, the top contacts, and contacts with notes but no calls or meetings. It warns when a result may be cut short by the limit, stops on missing or reversed dates, and is read-only.
Business outcome
---
Managers see who did how much activity in any period, with truncation warnings, and no counting by hand.
scenario
-
Marketing cannot easily tell which subscribers of a Drip campaign are tied to live deals in OnePageCRM. Without that link, nobody knows how much pipeline a campaign actually reaches.
What popdock provides
--
Name a Drip campaign and a Drip account and it finds the campaign, listing the options and stopping if several match. It reads the campaign subscribers up to your limit, then looks each email up in OnePageCRM and reads their deals. You get a table of subscribers with subscription status, CRM contact and deals, and the total open pipeline reached by the campaign. Subscribers with no CRM contact are counted, matching is on email only, and it is read-only.
Business outcome
---
Marketing can state how much open pipeline a Drip campaign reaches, and which subscribers are tied to deals.
scenario
-
Preparing for a call means opening the CRM for the contact's deals, actions and notes, then hunting through old meeting notes for what was said last time. Open items get missed when the two are viewed in separate tabs.
What popdock provides
--
Give a contact's email and how many past meetings to include. It reads the OnePageCRM record, open deals, pending actions and notes, then adds summaries of the contact's past Granola meetings, using the transcript only when a summary is empty. If the contact is not in the CRM it still reports the meetings. Read-only: nothing in OnePageCRM is changed, it stops if several contacts match, and nothing is quoted that was not returned.
Business outcome
---
You go into the next conversation knowing the deals, open actions and past discussions, with talking points taken from unresolved items.
scenario
-
Deals quietly go cold and nobody notices until the quarter review. Spotting them means listing open deals, finding each contact's email, and then searching meeting records to see when anyone last spoke to them.
What popdock provides
--
Say how far back to look, and optionally which owner, and it lists the open OnePageCRM deals, then checks Granola for each contact's email in recent meetings. You get the deals with no recent meeting, largest first, with stage, expected close date and the date of the last meeting if there was an earlier one. Contacts with no email are listed separately as not checkable. It changes no deals and adds no actions, and meeting content stays with the signed-in user.
Business outcome
---
Quiet deals stand out, largest first, before they go cold, and nothing in the CRM is touched.
scenario
-
Reps compare a meeting's attendee list to OnePageCRM by hand, one email at a time. People who were never added to the CRM go unnoticed, and so does the follow-up they need.
What popdock provides
--
Give part of the meeting title and, if you like, how many days to look back (14 by default). It finds the Granola meeting, merges attendees and invitees by email and counts any rows with no email, then looks up each address in OnePageCRM ignoring case. You get a matched table with company, status and owner, a not in CRM list, and counts. It stops if several meetings or contacts match and never adds, updates or deletes anything.
Business outcome
---
You see which meeting guests are in OnePageCRM and which were never added, with nothing in the CRM changed.
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.