sentlisted

# Sent Meta Dispatcher ## Overview This skill is a router, not a worker. When a request does not identify one clear Sent workflow, inspect the intent, ask only the clarification needed to select a route, and invoke the matching skill. Sent spans direct account operations through its MCP server and specialist guidance for SMS, WhatsApp, RCS, Sender Profiles, templates, and delivery analysis. Prefer a direct-operation skill for live Sent data or mutations and a specialist skill for planning, compliance, diagnosis, or product design. ## When to Use Use when: - The user mentions "Sent" broadly without naming a channel ("help me with Sent", "I want to use Sent for messaging") - The user asks an open-ended question like "what can you help with on Sent?" or "where do I start?" - The request could plausibly span multiple target skills (e.g., "messaging isn't working" — could be account readiness, 10DLC vetting, WABA template rejection, RBM capability, or an MDR funnel) - The channel is ambiguous (SMS vs WhatsApp vs RCS not stated; geography matters because 10DLC is US-only) - The surface is ambiguous (API integration vs dashboard UX vs compliance paperwork) - The user pastes a Sent dashboard URL or API path without further context Do **not** use when: - The user has already named one supported operation or specialist workflow; invoke that skill directly. - The question is purely about pricing, contracts, or unsupported product policy; point the user to `https://docs.sent.dm` or