Perfect Storm: Signal-Based Outreach

(Use the ZoomInfo MCP tools if available; otherwise use the GTM CLI. Use the tool schema or CLI help for supported commands.)

I just connected ZoomInfo. Help me complete the job below.

1. Read my saved business context with get_gtm_context, or the CLI equivalent. This read is free. Use the returned offerings, ICP, and role to frame the work. If context is missing, continue with the information we have. Save changes only if I explicitly ask; a first briefing does not require updating shared business context.

2. Run the "Perfect Storm: Signal-Based Outreach" workflow example I selected in the marketplace - a chained sequence of 5 steps. First, and before doing anything else, ask me for the essential input this workflow needs, in a single message (e.g. the account we just closed, and what we sell) - do not start any research, tool call, or skill below until I've answered. If I don't have a specific account handy, suggest I try a placeholder like "Acme Corp" to see how it works, then invite me to rerun with a real one to make it mine. Only once I've given you that input, run these steps in order, passing each one's output into the next:
   1. **Score Accounts** - Score and tier the ICP universe
   2. **Company Intent Monitor** - Watch for a "perfect storm" of signals (Company Intent Monitor is a per-account lookup - run it on your top tier only (Tier A, or Tier A & B per your minimum-tier setting), capped at roughly 20 accounts, not the full tiered universe.)
   3. **Recommend Contacts** - Recommend the right contact
   4. **Personalize Email** - Write the signal-anchored email
   5. Get it in front of the rep - no packaged skill yet, so this is a manual hand-off. Tell me plainly what to copy and where it typically goes (a CRM task, Slack ping, or shared inbox), instead of stopping silently once the automated steps are done.
Preserve this job instead of offering a new task menu. Close with a compact, copy-ready summary of the concrete result - the account and contact, and the final artifact itself (a draft, a briefing, a shortlist) in its own block, not a narrative recap - so it can be pasted directly into a CRM task, email, or message.

3. Before calling a tool, check its schema or documented inputs rather than guessing at parameters. Ask only for missing inputs, in a single message, then name the tools and give a credit estimate if supported by their documentation. Label it as an estimate: actual charges depend on records and work done. Ask for approval once before paid research, then complete the selected job.

If a tool call comes back "No approval received" or a similar permission response, say so plainly, name the tool, and continue with the remaining steps. Don't retry the same call hoping for a different result, and don't invent an approval that didn't happen.

Include a source-coverage note of no more than 3 lines. Separate an unavailable or unauthorized source from a successful search with no matching records. If connection status is unknown, say so. Never infer "no customer history" from an empty result. Continue with available evidence and identify what is missing; use https://gtm.ai/guides/connect-customer-context for source setup.

Recommend CRM changes as drafts. Applying them requires an available, separately connected CRM workflow and my authorization. Do not claim a CRM update was made by ZoomInfo research tools.