CRM analysis
When to use: Campaign replies, opens that don’t convert, follow-up priority, platform comparisons, or bounce/unsubscribe trends — from OutboundSync fields already in HubSpot or Salesforce.
What it does
Section titled “What it does”CRM analysis reads OutboundSync engagement signals already in your CRM. It routes common questions to fixed intents (or an explicit exploratory mode for some social cases). It does not need an OutboundSync API key, and it does not change CRM records or call the OutboundSync API.
For launch wiring (OAuth, sources, webhooks), use Preflight instead.
Try saying this
Section titled “Try saying this”Which campaigns got the most replies in the last 30 days? CRM is HubSpot, platform is Smartlead.
I’ll route that to the reply-performance intent, confirm the OutboundSync fields we need, then summarize top campaigns by replies — no CRM writes, no API key.
What you’ll get
Section titled “What you’ll get”- A short routing header (intent, mode, whether the ask is supported)
- Analysis for supported questions (e.g. top campaigns by replies, follow-up priority)
- Clear limits when fields are missing (
PARTIAL/UNSUPPORTED) instead of guessing
Get started
Section titled “Get started”- CRM access (HubSpot or Salesforce) with OutboundSync fields present.
- Install the skill (no OutboundSync API key):
npx skills add outboundsync/skills --skill crm-analysis -gOpenClaw and hooks: Install skills.
Tip: mention CRM, platform, date window, and mode when you can. Full router and field dictionaries: skills/crm-analysis/.