القائمة
Help admins understand what's driving their Duo dismiss rate by analyzing dismiss patterns across reasons, signals, lead attributes, and rep behavior.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Helps sales reps break into target accounts via Amplemarket. Runs deep research on the company and key people, identifies the buying committee, surfaces possible engagement angles, recommends who to reach out to and why, and creates personalized multi-channel sequences. Use when a rep wants to research, plan, or execute outreach against a target account — net-new or re-engagement.
Interactively refine your Ideal Customer Profile through guided questions, web research, and iterative Amplemarket searches until your targeting criteria are dialed in.
Build a visual, interactive org chart for any target account using Amplemarket and HubSpot MCP data. Combines contact discovery, enrichment, outreach history, CRM deal context, and relationship signals into a single React-based visual. Use this skill whenever the user asks to map an org structure, visualize contacts at a company, understand outreach status across an account, build a stakeholder map, do account-based research, cross-reference with CRM, see account penetration with CRM data, or map a specific team. Trigger phrases include: "show me the org chart for [company]", "who do we know at [company]", "map the buying committee", "show me outreach status for [account]", "pull all contacts at [domain]", "account map", "stakeholder map", "account penetration", "engineering org chart for [company]", "map the product team at [company]", "deal context for [account]".
Map untapped departments and roles within existing accounts to surface expansion opportunities, then find contacts in whitespace areas with personalization that references your existing relationship.
Analyze existing HubSpot customer accounts to find untapped departments and personas, map whitespace against the full organizational structure from Amplemarket, and generate expansion outreach referencing the existing customer relationship.
Help AEs get a status check on their accounts with open deals -- where things stand, where to focus, and what next steps to take.
| name | duo-copilot-dismiss-diagnostics |
| description | Help admins understand what's driving their Duo dismiss rate by analyzing dismiss patterns across reasons, signals, lead attributes, and rep behavior. |
| metadata | {"author":"amplemarket","version":"1.0.4","category":"Copilot Tools"} |
| compatibility | Requires Amplemarket MCP server |
Help admins understand what's driving their Duo dismiss rate by analyzing dismiss patterns across reasons, signals, lead attributes, and rep behavior.
When an admin wants to diagnose their Duo dismiss rate, query analytics and analyze the results top-down to find the biggest contributors and recommend fixes.
Confirm scope. Default to last 30 days, full account. Ask if the user wants a different timeframe or team scope.
Gather the data by submitting these analytics questions via mcp__claude_ai_Amplemarket__ask_analytics:
Submit all in parallel, poll with mcp__claude_ai_Amplemarket__get_analytics_result.
Analyze top-down. Work through the data in this order:
Present a well-formatted diagnostic report. Lead with a summary headline, then use tables and clear sections to walk the admin through the findings. End with specific, actionable recommendations tied to Duo configuration changes.
User prompt: "Our Duo dismiss rate is at 38%. What's going on?"
Simple example output: The agent finds that Bad company is the top dismiss reason (56%), discovers most of those are sub-50-employee companies coming from the Hiring Surge signal, notes rep dismiss rates are uniform (so it's a signal issue, not a rep issue), and recommends excluding small companies from Hiring Surge -- projecting the dismiss rate would drop to ~22%. All presented in a structured report with tables for the reason breakdown, signal contribution, and rep patterns.
| Problem | Solution |
|---|---|
| Analytics can't break down attributes by dismiss reason | Submit separate queries and cross-reference. |
