30 Claude Prompts That Build CRM Dashboards

You are a CRM operations analyst who maps account ownership for admins. <context> I need an account ownership dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample accounts and users so ownership gaps render when I open it as a working screen in the chat. </context> <inputs> - Team: [TEAM] - User list with active or inactive: [OR "INVENT 8 USERS, 2 INACTIVE"] - What counts as multi-owned: [E.G. TWO TEAM MEMBERS ON ACCOUNT TEAM] - Account count: [E.G. 36] - Segments: [E.G. ENTERPRISE, MID-MARKET, SMB] </inputs> <task> Build the dashboard with: a KPI row (accounts, unowned, owned by inactive users, multi-owned); a bar of account count by owner including an Unowned and Inactive bucket; a segment split of the gaps; a sortable table (account, segment, owner, owner status, team members, ARR if present); and chips for unowned / inactive owner / multi-owned. Generate accounts and users in labeled JS arrays. Unowned means blank owner. Inactive-owned means the owner id is on the user list with active=false. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Gap flags are computed from owner and user status, not hardcoded. - Chips filter the table. Accessible contrast. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain each gap type and which arrays to replace with an account and user export. </format>

You are a CRM operations analyst who audits parent and child account trees. <context> I need a parent-child hierarchy dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample accounts so missing parents and broken rollups render when I open it as a working screen in the chat. </context> <inputs> - CRM or org name: [CRM] - Hierarchy fields: [PARENT ID, ACCOUNT TYPE HQ / CHILD / STANDALONE] - Rollup field: [E.G. OPEN PIPELINE OR ARR] - Account count: [E.G. 28, INCLUDE A FEW BROKEN LINKS] - Segments: [OPTIONAL] </inputs> <task> Build the dashboard with: a KPI row (accounts, children with no parent, parents with no children, dollars on broken links); a simple tree or grouped list of HQ accounts and their children; a watchlist of children whose parent id is blank or points at a missing account; a rollup table (parent, child count, rolled value, orphan value); and a click on a parent that lists its children. Generate accounts with parent ids in a labeled JS array, including broken links, and compute rollups in JS. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Broken-link flags are computed from parent ids, not hardcoded. - Do not invent a live CRM API. Sample tree plus a note on where an account export goes. - Responsive (tree can scroll); accessible contrast; data at the top. </constraints> <format> Return the full HTML file, then explain the rollup math and which array to replace with an account export. </format>

You are a CRM operations analyst who builds territory coverage boards. <context> I need a territory coverage dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample accounts and territories so assigned versus unassigned cells render when I open it as a working screen in the chat. </context> <inputs> - Territories: [TERRITORIES] - Assignment field: [E.G. TERRITORY NAME OR OWNER] - Named-account list size: [E.G. 40] - Segments: [E.G. ENTERPRISE / MID-MARKET] - Target: [E.G. EVERY NAMED ACCOUNT HAS A TERRITORY AND AN OWNER] </inputs> <task> Build the dashboard with: a KPI row (named accounts, assigned %, unassigned count, territories with zero accounts); a grid of territories by segment with account counts; a bar of assigned versus unassigned; a sortable table of unassigned accounts (name, segment, country or state, owner); and a click on a grid cell that filters the table. Generate accounts and a territory list in labeled JS arrays and compute assigned from the assignment field. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Coverage is computed from the assignment field, not hardcoded. - Empty territories stay visible. Accessible contrast, not color-only. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the assignment rule and which arrays to replace with a named-account export. </format>

You are a CRM operations analyst who scores account record completeness. <context> I need an account completeness dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample accounts so scores and missing-field charts render when I open it as a working screen in the chat. </context> <inputs> - Account list label: [ACCOUNT LIST] - Fields that count toward completeness: [E.G. INDUSTRY, EMPLOYEE BAND, BILLING COUNTRY, WEBSITE, OWNER, PARENT] - Score bands: [E.G. COMPLETE 90+, PARTIAL 60-89, THIN BELOW 60] - Account count: [E.G. 24] - Segments: [OPTIONAL] </inputs> <task> Build the dashboard with: a KPI row (accounts, average completeness, thin count, most-missing field); a bar of blank rate by field; a histogram of scores; a sortable table with each field as present or blank, a computed percent, and a band badge; and chips for thin / partial / complete. Generate sample accounts with some blanks in a labeled JS array. Score = filled required fields / required fields. Do not hardcode the percent on each row. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Scores and bands are computed from the field list, not hardcoded. - Band badges use a text label, not color alone. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the score formula and which array to replace with an account export. </format>

You are a CRM operations analyst who checks whether accounts have the contacts a deal needs. <context> I need a buying-committee coverage dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample accounts and contacts so missing-role cells render when I open it as a working screen in the chat. </context> <inputs> - Required roles: [ROLES] - Accounts to show: [E.G. 18 TARGET ACCOUNTS] - Contact fields: [NAME, TITLE, ROLE, EMAIL] - Minimum contacts: [E.G. 2] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (accounts, accounts missing any required role, one-contact accounts, average contacts per account); an account-by-role matrix with present or missing; a bar of missing count by role; a table of accounts with contact count, missing roles listed, and owner; and a click on an account that lists its contacts. Generate accounts and contacts in labeled JS structures and compute missing roles from the role field versus [ROLES]. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Missing-role flags are computed from the contact roles, not hardcoded. - Matrix cells are clickable and not color-only. - Responsive (matrix can scroll); data at the top with comments. </constraints> <format> Return the full HTML file, then explain the role match and which arrays to replace with a contact-to-account export. </format>

You are a CRM operations analyst who measures whether work was logged, not whether work happened. <context> I need an activity-logging completeness dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample opportunities and activity rows so silent deals render when I open it as a working screen in the chat. </context> <inputs> - Team: [TEAM] - Window: [E.G. LAST 7 DAYS] - Activity types that count: [E.G. CALL, MEETING, EMAIL LOGGED] - Objects: [E.G. OPEN OPPORTUNITIES] - Owners: [3-6 NAMES] </inputs> <task> Build the dashboard with: a KPI row (open opps, opps with a logged activity in window, silent opps, silent dollars); a grouped bar of logged versus silent by owner; a daily bar of activities logged; a sortable table of silent opportunities (name, owner, stage, value, last logged date); and chips for owner and activity type. Generate opportunities and activities in labeled JS arrays. An opp is silent when it has no activity whose timestamp falls inside the window. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Silent flags are computed from activity timestamps, not hardcoded. - This is a logging board, not an outbound scoreboard. No call-target ranking. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the silent rule and which arrays to replace with an opportunity and activity export. </format>

You are a CRM operations analyst who builds overdue-task queues a manager can chase. <context> I need an overdue CRM task dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample tasks so the chase list renders when I open it as a working screen in the chat. </context> <inputs> - Owners: [OWNERS] - Task types: [E.G. CALL, EMAIL, MEETING PREP, RENEWAL] - Objects tasks sit on: [E.G. OPPORTUNITY, ACCOUNT, CONTACT] - Age buckets: [E.G. 1-3, 4-7, 8-14, 14+ DAYS OVERDUE] - Open task count: [E.G. 40] </inputs> <task> Build the dashboard with: a KPI row (open tasks, overdue count, median days overdue, owners with overdue work); a bar of overdue count by owner; a stacked bar by age bucket; a chase table sorted oldest first (subject, type, object, owner, due date, days overdue); and chips for owner and type. Generate tasks with due dates in a labeled JS array. Days overdue = now minus due date when due date is in the past and status is open. Include a now constant. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Overdue flags and day counts are computed from due dates. - Future-due open tasks stay on a separate upcoming list. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the age formula and which array to replace with a task export. </format>

You are a CRM operations analyst who builds last-logged-touch recency boards. <context> I need a last-touch recency dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic last-activity dates so recency buckets render when I open it as a working screen in the chat. </context> <inputs> - Recency window that is healthy: [WINDOW] - What counts as a logged touch: [E.G. CALL, MEETING, EMAIL LOGGED] - Decay buckets: [E.G. 0-14, 15-30, 31-60, 60+ DAYS] - Objects: [E.G. TARGET ACCOUNTS AND OPEN OPPS] - Record count: [E.G. 30] </inputs> <task> Build the dashboard with: a KPI row (median days since touch, records outside [WINDOW], dollars in 60+ days, records touched this week); a bar of count and dollars by decay bucket; a sortable table (record, object, owner, last touch type, last touch date, days since); and a filter to hide records inside the healthy window. Generate last-touch rows in labeled JS arrays and compute days since from those dates versus a now constant. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Days since and bucket assignment are computed from last-touch dates. - Darkest bucket flagged. Date formatting consistent. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the buckets and how to paste last-activity dates from the CRM. </format>

You are a CRM operations analyst who finds meetings that never got logged. <context> I need a meeting-to-CRM match dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample meetings and CRM activities so unmatched rows render when I open it as a working screen in the chat. </context> <inputs> - Calendar label: [CALENDAR] - Match rule: [E.G. SAME ACCOUNT OR CONTACT AND SAME DATE] - Meeting types to include: [E.G. DISCOVERY, DEMO, QBR] - Period: [E.G. LAST 14 DAYS] - Owners: [NAMES OR "INVENT"] </inputs> <task> Build the dashboard with: a KPI row (meetings, matched, unmatched, match rate); a bar of match rate by owner; a table of unmatched meetings (title, date, attendees, related account if known); a table of matched pairs; and a filter for owner. Generate meetings and activities in labeled JS arrays, including several intentional misses, and compute a match from the rule. Do not invent a live calendar API. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Match flags are computed from the rule, not hardcoded. - Show the match rule on the page. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the match rule and which arrays to replace with a calendar export and an activity export. </format>

You are a CRM operations analyst who spot-checks whether notes are usable. <context> I need a note-quality dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample notes so thin and next-step-free notes render when I open it as a working screen in the chat. </context> <inputs> - Team: [TEAM] - Period: [E.G. LAST 14 DAYS] - Thin rule: [E.G. UNDER 12 WORDS OR EMPTY] - Next-step rule: [E.G. NOTE MUST CONTAIN A DATE OR THE WORDS NEXT STEP] - Note count: [E.G. 36] </inputs> <task> Build the dashboard with: a KPI row (notes in period, thin notes, notes with no next step, owners with the most thin notes); a bar of flag counts by owner; a table of flagged notes (object, owner, date, word count, flags, a 80-character preview); a clean sample of notes that pass; and chips for thin / no next step. Generate sample notes in a labeled JS array. Compute word count and next-step flags in JS from the note body and the rules. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Flags are computed from the note text and rules, not hardcoded. - Show the thin and next-step rules on the page. - Do not score writing style. Length and next-step presence only. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the flag rules and which array to replace with a note export. </format>

You are a CRM operations analyst who audits forecast-category fields, not the sales call itself. <context> I need a forecast-category completeness dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample opportunities so missing categories render when I open it as a working screen in the chat. </context> <inputs> - Team: [TEAM] - Allowed categories: [E.G. CLOSED WON, COMMIT, BEST CASE, PIPELINE, OMIT] - Period: [E.G. THIS QUARTER] - Stages that must have a category: [E.G. ALL OPEN STAGES] - Number of open opportunities: [E.G. 30] </inputs> <task> Build the dashboard with: a KPI row (open opps, categorized, missing category, missing-category dollars); a bar of count by category including a Missing bucket; a stage table of missing rate; a sortable list of uncategorized deals (name, owner, stage, amount, close date); and chips for owner. Generate sample deals in a labeled JS array with some blank categories. Compute missing as category blank or not in the allowed list. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Missing flags are computed from the category field, not hardcoded. - Do not build a commit-versus-quota stack. Completeness only. - Currency consistent; accessible contrast; data at the top. </constraints> <format> Return the full HTML file, then explain the missing rule and which array to replace with a forecast-field export. </format>

You are a CRM operations analyst who checks whether a deal may sit in commit. <context> I need a commit-gate checklist dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic late-stage sample deals so failed gates render when I open it as a working screen in the chat. </context> <inputs> - Commit rule / required gates: [COMMIT RULE] - Example gates if I want defaults: [NEXT STEP PRESENT, CLOSE DATE IN PERIOD, AMOUNT FILLED, CHAMPION CONTACT] - Period: [E.G. THIS QUARTER] - Late stages: [E.G. PROPOSAL, NEGOTIATION, VERBAL] - Number of late-stage deals: [E.G. 18] </inputs> <task> Build the dashboard with: a KPI row (late-stage deals tagged commit, commit that pass every gate, commit that fail a gate, failed-gate dollars); a bar of fail count by gate; a table of commit deals with a pass/fail chip per gate; a list of deals tagged commit that fail; and a toggle to also show best-case deals against the same gates. Generate sample deals with gate fields in a labeled JS array. A deal fails if any required gate is blank or false. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Pass and fail are computed from the gate fields, not hardcoded. - Show the gate list on the page so I can edit it. - This is a field checklist, not a quota burndown. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then list each gate in plain English and which array to replace. </format>

You are a CRM operations analyst who finds win-probability values that drifted off the stage default. <context> I need a probability-versus-stage drift dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample opportunities so drift rows render when I open it as a working screen in the chat. </context> <inputs> - Stages and default probabilities: [STAGES] - Drift rule: [E.G. MORE THAN 15 POINTS OFF THE STAGE DEFAULT] - Team: [NAME] - Number of open opportunities: [E.G. 30] - Period: [E.G. THIS QUARTER] </inputs> <task> Build the dashboard with: a KPI row (open opps, drifted count, average absolute drift, dollars on drifted deals); a scatter of stage default versus actual probability; a bar of drift count by stage; a sortable table (name, stage, default %, actual %, points off, owner, amount); and chips for over-default versus under-default. Generate sample deals with a probability field in a labeled JS array. Compute drift from actual minus the stage default map. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Drift flags are computed from the default map, not hardcoded. - Show the default map on the page. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the drift rule and which arrays to replace with a stage and probability export. </format>

You are a CRM operations analyst who finds forecast categories that do not match the close date. <context> I need a close-date versus forecast-period dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample opportunities so out-of-period commit rows render when I open it as a working screen in the chat. </context> <inputs> - Forecast period: [PERIOD] - Categories that must close inside the period: [E.G. COMMIT AND BEST CASE] - Team: [NAME] - Number of open opportunities: [E.G. 28] - Period start and end dates: [DATES] </inputs> <task> Build the dashboard with: a KPI row (deals in commit or best case, those with close date inside [PERIOD], those outside, outside dollars); a bar of in-period versus out-of-period by category; a calendar-style week strip of close dates; a sortable table of out-of-period commit and best-case deals; and a second list of in-period pipeline that has no category. Generate sample deals in a labeled JS array. Compute in-period from close date versus the period start and end constants. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - In-period flags are computed from dates, not hardcoded. - Do not compute quota coverage. Date versus category only. - Currency consistent; accessible contrast; data at the top. </constraints> <format> Return the full HTML file, then explain the period test and which array to replace. </format>

You are a CRM operations analyst who audits opportunity splits and overlays. <context> I need a revenue-split hygiene dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample split lines so totals that miss 100 percent render when I open it as a working screen in the chat. </context> <inputs> - Split types: [SPLITS] - Tolerance: [E.G. MUST SUM TO 100 PLUS OR MINUS 1] - Overlay roles: [E.G. SE, CSM, PARTNER] - Number of opportunities with splits: [E.G. 16] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (deals with splits, deals that do not sum to 100, dollars on broken splits, deals with no split on a multi-owner account); a histogram of split-sum percent; a table of deals with each split line (owner, role, percent) and a computed total; a watchlist of totals outside tolerance; and a click that expands the lines. Generate deals and split lines in labeled JS arrays, including a few broken totals, and compute the sum in JS. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Broken totals are computed from the lines, not hardcoded. - Show the tolerance on the page. - Currency consistent; accessible contrast; data at the top. </constraints> <format> Return the full HTML file, then explain the sum rule and which arrays to replace with a split-line export. </format>

You are a CRM operations analyst who scores accounts against a target-account rule. <context> I need a target-account fit dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample accounts so fit scores and bands render when I open it as a working screen in the chat. </context> <inputs> - Fit rules and weights: [FIT RULES] - Example if needed: [INDUSTRY MATCH 40, EMPLOYEE BAND 30, COUNTRY 30] - Bands: [E.G. FIT 70+, ADJACENT 40-69, OUTSIDE BELOW 40] - Account count: [E.G. 24] - Book name: [NAME] </inputs> <task> Build the dashboard with: a KPI row (accounts, fit, adjacent, outside); a stacked bar of band by industry; a table with each rule result, the computed score, and a band badge; a watchlist of outside accounts that still have open pipeline; and a formula callout of the weights. Generate sample accounts with firmographic fields in a labeled JS array. Compute the score from editable weights. Do not hardcode the score on each row. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Scores are computed from the rules, not hardcoded. - Band badges use a text label, not color alone. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the score formula and which array to replace with an account export. </format>

You are a CRM operations analyst who builds lifecycle-stage mix boards. <context> I need a lifecycle-stage mix dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample records so the mix and stalled list render when I open it as a working screen in the chat. </context> <inputs> - Lifecycle values in order: [LIFECYCLE] - Stall rule: [E.G. NO STAGE CHANGE IN 30 DAYS] - Objects: [E.G. CONTACTS OR ACCOUNTS] - Record count: [E.G. 40] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (records, largest stage, stalled count, stalled share); a funnel or horizontal bar of count by lifecycle value; a stacked bar of stalled versus moving; a table of stalled records (name, stage, days in stage, owner, value if any); and chips that filter the table to one stage. Generate sample records with stage-entered dates in a labeled JS array. Compute days in stage and stall flags from those dates. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Mix percents and stall flags are computed from the records. - Stage chips filter the table. Accessible contrast. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the stall rule and which array to replace with a lifecycle export. </format>

You are a CRM operations analyst who cuts the book by industry and company size. <context> I need an industry-and-size segment dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample accounts and opportunities so the cut renders when I open it as a working screen in the chat. </context> <inputs> - Industry and size bands: [SEGMENTS] - Size bands: [E.G. UNDER 50, 50-200, 200-1000, 1000+] - What to sum: [E.G. ACCOUNT COUNT AND OPEN PIPELINE] - Account count: [E.G. 30] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (accounts, industries present, size bands present, dollars on blank industry or size); a heatmap of industry by size with account count; a toggle that switches cells to open dollars; a table of each slice (count, dollars, blank-field count); and a click on a cell that lists the accounts. Generate accounts and open dollars in labeled JS arrays. Blank industry or size stays in an Unknown row, never dropped. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Cell values are computed from the arrays, not hardcoded. - Heatmap shows the number, not color alone. - Responsive (grid can scroll); data at the top with comments. </constraints> <format> Return the full HTML file, then explain the cut and which arrays to replace with an account and opportunity export. </format>

You are a CRM operations analyst who builds territory heatmaps that mix coverage and hygiene. <context> I need a territory segment heatmap as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample accounts so coverage and hygiene cells render when I open it as a working screen in the chat. </context> <inputs> - Territories: [TERRITORIES] - Hygiene flags to roll up: [E.G. UNOWNED, MISSING INDUSTRY, NO NEXT STEP] - Segments: [E.G. ENTERPRISE, MID-MARKET, SMB] - Account count: [E.G. 40] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (territories, accounts, hygiene-flagged accounts, territories over a flag threshold); a territory-by-segment heatmap of account count; a second mode that colors by percent flagged; a table per territory (accounts, unowned, missing industry, no next step); and a click on a cell that lists those accounts. Generate accounts with territory, segment, and flag fields in a labeled JS array. Compute percents from those fields. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Heatmap numbers and percents are computed, not hardcoded. - Color plus a number so it is not color-only. - Responsive; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the flag rollup and which array to replace with a territory export. </format>

You are a CRM operations analyst who measures buying-role coverage across a book. <context> I need a role-coverage mix dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample accounts and contacts so role mix renders when I open it as a working screen in the chat. </context> <inputs> - Roles to track: [ROLES] - Account count: [E.G. 20] - Contacts per account: [E.G. 1-5] - Segment split: [OPTIONAL] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (accounts, percent with each required role, accounts missing two or more roles, average roles per account); a bar of account coverage by role; a stacked mix of role counts; a table of accounts with a yes/no for each role; and a filter for accounts missing a selected role. Generate accounts and contacts with a role field in labeled JS arrays. Coverage for a role is the share of accounts with at least one contact in that role. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Coverage percents are computed from contacts, not hardcoded. - Filter chips must hide rows. Accessible contrast. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain the coverage math and which arrays to replace with a contact-role export. </format>

You are a CRM data-quality analyst who measures required-field completeness. <context> I need a required-field completeness dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample records so blank rates render when I open it as a working screen in the chat. </context> <inputs> - Required fields by object: [REQUIRED FIELDS] - Objects: [E.G. ACCOUNT, CONTACT, OPPORTUNITY] - Owners: [NAMES OR "INVENT"] - Record counts: [E.G. 20 PER OBJECT] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (records, fields in scope, worst field blank rate, owners below an editable threshold); a bar of blank rate by field; a grouped bar of blank rate by object; an owner table of completeness percent; a drill table of records missing a selected field; and field chips that filter the drill. Generate records with some blanks in labeled JS arrays. Compute blank rate as blank count / record count per field. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Blank rates are computed from the records, not hardcoded. - Show the required-field list on the page. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the blank-rate math and which arrays to replace with a field export. </format>

You are a CRM data-quality analyst who finds picklist values that drifted off the official list. <context> I need a picklist drift dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample records and official lists so drifted values render when I open it as a working screen in the chat. </context> <inputs> - Picklists to audit: [PICKLISTS] - Official values per picklist: [LISTS] - Objects those fields sit on: [E.G. ACCOUNT INDUSTRY, OPPORTUNITY TYPE] - Record counts: [E.G. 30] - Team: [NAME] </inputs> <task> Build the dashboard with: a picklist selector; a KPI row (values in use, official values, drifted values, records on a drifted value); a bar of record count by value with drifted bars flagged; a table of drifted values (value, field, record count, sample records); and a click that lists those records. Generate official lists and records in labeled JS constants. A value is drifted when it is non-blank and not in the official list. Case-fold before compare. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Drift is computed from the official lists, not hardcoded. - Blank is incomplete, not drifted. Show that rule. - Accessible contrast; data at the top with comments. </constraints> <format> Return the full HTML file, then explain the compare rule and which constants to replace with official picklists and a record export. </format>

You are a CRM data-quality analyst who flags emails and phones that fail a simple format check. <context> I need an email-and-phone validity dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample contacts so bad formats and blanks render when I open it as a working screen in the chat. </context> <inputs> - CRM or book name: [CRM] - Email rule: [E.G. HAS @ AND A DOT IN THE DOMAIN] - Phone rule: [E.G. AT LEAST 10 DIGITS AFTER STRIPPING SPACES] - Contact count: [E.G. 40, INCLUDE BAD AND BLANK] - Owners: [OPTIONAL] </inputs> <task> Build the dashboard with: a KPI row (contacts, valid email, valid phone, both valid); a bar of invalid / blank / valid for email and for phone; a fix list of invalid emails and invalid phones (contact, owner, raw value, why it failed); chips for email-invalid / phone-invalid / blank; and a search box. Generate contacts in a labeled JS array. Compute validity in JS from the rules. Do not call any email or phone API. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Validity is a format check only. Say that on the page. - Do not invent a bounce or a carrier lookup. - Responsive and accessible; data at the top with comments. </constraints> <format> Return the full HTML file, then write the format rules and which array to replace with a contact export. </format>

You are a CRM data-quality analyst who finds records with no usable owner. <context> I need an owner-assignment gap dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample records and users so blank, inactive, and queue owners render when I open it as a working screen in the chat. </context> <inputs> - Active users and inactive users: [OWNERS] - Queue names if any: [E.G. INBOUND QUEUE, UNASSIGNED] - Objects: [E.G. LEADS, ACCOUNTS, OPPORTUNITIES] - Record counts: [E.G. 20 PER OBJECT] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (records, blank owner, inactive owner, queue owner); a stacked bar of those three gaps by object; a table of gap records (name, object, owner value, gap type); chips for blank / inactive / queue; and a user table (user, active, record count). Generate users and records in labeled JS arrays. Blank = empty owner. Inactive = owner id on the user list with active=false. Queue = owner matches a queue name. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Gap types are computed from the user list, not hardcoded. - Chips filter the table. Accessible contrast. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain each gap type and which arrays to replace with a user list and a record export. </format>

You are a CRM data-quality analyst who queues likely duplicate contacts and accounts. <context> I need a merge-candidate dashboard as one self-contained HTML file with inline CSS, vanilla JS, and a CDN chart library, seeded with realistic sample contacts and accounts so likely pairs render when I open it as a working screen in the chat. </context> <inputs> - Match keys: [MATCH KEYS] - Contact key: [E.G. LOWERCASED EMAIL] - Account key: [E.G. NORMALIZED WEBSITE HOST OR EXACT NAME] - Sample size: [E.G. 30 CONTACTS AND 20 ACCOUNTS, INCLUDE DUPES] - Team: [NAME] </inputs> <task> Build the dashboard with: a KPI row (contacts, accounts, contact pairs, account pairs); tabs for contacts and accounts; a pair table (left record, right record, matched on, confidence high if exact key, review if only name); a click that shows field-by-field compare; and a keep/drop note column I can edit in the page (session only). Generate records with a few intentional duplicates in labeled JS arrays. Compute pairs from the keys. Do not auto-merge. </task> <constraints> - One self-contained HTML file; one CDN charting library only. - Pairs are computed from the keys, not hardcoded. - Do not delete records. Queue and compare only. - Show the match keys on the page. - Data constants at the top with comments. </constraints> <format> Return the full HTML file, then explain each match key and which arrays to replace with a contact and account export. </format>