Mihu AI

@mihu-ai list all active campaigns and show me which ones have the highest contact engagement this month

Found 12 active campaigns in your workspace. Top performers by engagement: 'Q1 Product Launch' (847 contacts, 34% response rate), 'Customer Win-Back' (612 contacts, 28% response), and 'Enterprise Outreach' (203 contacts, 19% response). The Product Launch campaign shows strongest activity in the last 7 days with 156 new conversations initiated. All three campaigns are currently within their scheduled run windows.

This example combines the List Campaigns tool with call analytics to surface actionable performance data. The MCP returns campaign metadata and engagement metrics but cannot modify campaign settings or trigger new outreach. Users need workspace-level API access to see cross-campaign analytics.

@mihu-ai show me all missed calls from the past 48 hours and create follow-up appointments for any contacts we haven't reached

Retrieved 23 missed calls since January 15, 3:00 PM UTC. Breakdown: 14 inbound (no voicemail), 9 web callback requests. I've identified 18 unique contacts without existing follow-up appointments. However, I cannot automatically create appointments through the Mihu AI MCP—this requires manual scheduling or a separate automation workflow. I can provide the contact list with phone numbers and last interaction timestamps if you'd like to batch-schedule callbacks.

Demonstrates the MCP's read capabilities (List Calls) while honestly surfacing a write limitation. Mihu AI's API supports appointment creation, but this example shows the AI recognizing when a requested action exceeds the MCP's current tool set. Users should verify appointment-creation permissions in their workspace before expecting automated scheduling.

@mihu-ai pull call analytics for our sales team last week and draft a performance summary highlighting cost per successful connection

Week of January 8-14: 1,847 total calls, 412 successful connections (22.3% connect rate), average duration 4m 32s per connected call. Total cost: $284.16, yielding $0.69 per successful connection. Peak performance Tuesday-Thursday (28% connect rate), notable drop Friday afternoon (11%). Outbound calls to existing contacts converted 2.1x better than cold outreach. Recommendation: concentrate high-value outreach mid-week and prioritize warm lead follow-up to improve cost efficiency.

Showcases the Get Call Analytics tool paired with AI synthesis to turn raw metrics into strategic insight. The MCP provides aggregate data for specified time windows but cannot drill into individual agent performance without additional List Calls queries. Cost figures reflect Mihu AI's usage-based pricing; actual costs vary by workspace plan and call volume.

When Mihu AI wins for daily sales call retrospectives

A 6-person outbound sales team runs daily 15-minute retrospectives to review yesterday's call outcomes and adjust today's pitch. Mihu AI is the right call here because Get Call Analytics pulls aggregate counts and duration by outcome in one query, and List Calls lets the manager filter by agent to spot who's stuck on objection handling. The team references wallet balance from Get Workspace to decide whether to throttle volume before month-end. This works cleanly when your team lives inside Mihu's dialer ecosystem and you're reviewing under 500 calls per day. If you're stitching call data from Aircall or RingCentral into Mihu after the fact, the sync lag makes same-day retrospectives unreliable. For teams running 100 percent native Mihu campaigns, this MCP turns call review from a 20-minute Looker drill-down into a 90-second Switchy query.

When this MCP handles CS scheduling at 50-contact scale

A 3-person customer success team juggles 50 active accounts and uses Mihu AI to schedule check-in calls. List Appointments filtered by contact and date range surfaces which accounts haven't had a touchpoint in 30 days, and List Contacts searched by pipeline stage flags accounts approaching renewal. The team runs this query every Monday morning to build the week's outreach list. Mihu AI wins here because the appointment and contact scopes live in the same workspace, so you're not joining HubSpot to Calendly to Slack. The threshold: if your contact list exceeds 200 or you're managing multiple pipelines with complex tag hierarchies, List Contacts starts returning paginated results that require follow-up queries, and the triage workflow gets clunky. For small CS teams with a single pipeline and under 100 accounts, this MCP makes Monday planning a 5-minute Switchy routine.

When this MCP is the fastest path to campaign spend visibility

A 2-person growth team runs 8 concurrent Mihu AI voice campaigns and needs to check daily spend against a $4,000 monthly budget. Get Workspace returns the current wallet balance, List Campaigns surfaces active campaign names, and Get Call Analytics breaks down cost by campaign over the last 24 hours. The team asks Switchy "how much did we spend yesterday and what's left in the wallet" every morning before approving new contact uploads. This scenario is a clean win because all three data points live in Mihu's native workspace model—no Stripe API, no spreadsheet reconciliation. The trade-off: if you're running campaigns across multiple Mihu workspaces or blending Mihu spend with Google Ads and Meta, you'll still need a separate BI tool to roll up total acquisition cost. For teams spending exclusively through Mihu and managing under 15 campaigns, this MCP turns budget monitoring into a 30-second Switchy check-in.