Back to Details

sent

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Sent Meta Dispatcher

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.
该技能是一个路由工具，而非执行工具。当请求未明确指定一个清晰的Sent工作流时，需识别用户意图，仅询问选择路由所需的澄清信息，然后调用匹配的技能。
Sent通过其MCP服务器覆盖直接账户操作，并提供针对SMS、WhatsApp、RCS、Sender Profiles、模板和交付分析的专业指导。对于实时Sent数据或变更操作，优先使用直接操作类技能；对于规划、合规性检查、诊断或产品设计，优先使用专业指导类技能。

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 Sent support.
适用场景：
  • 用户宽泛提及“Sent”但未指定渠道（例如“帮我处理Sent相关事宜”、“我想使用Sent发送消息”）
  • 用户提出开放式问题，如“在Sent上你能帮我做什么？”或“我该从哪里开始？”
  • 请求可能涉及多个目标技能（例如“消息发送失败”——可能涉及账户就绪状态、10DLC审核、WABA模板驳回、RBM功能问题或MDR漏斗分析）
  • 渠道不明确（未说明是SMS、WhatsApp还是RCS；地域因素很重要，因为10DLC仅适用于美国）
  • 操作场景不明确（API集成、控制台UX还是合规文书工作）
  • 用户粘贴Sent控制台URL或API路径但未提供更多上下文
不适用场景：
  • 用户已明确指定某个受支持的操作或专业工作流；直接调用该技能即可。
  • 问题纯粹关于定价、合同或不支持的产品政策；引导用户访问
    https://docs.sent.dm
    或Sent支持团队。

Routing rules

路由规则

MCP-backed operations

MCP支持的操作

User intentTarget skill
Preview or send a templated message; inspect one message and its activity
sent-messaging
List, inspect, create, summarize, or delete Sent contacts
sent-contacts
Find, inspect, or delete existing Sent templates
sent-templates
Query dashboard messaging metrics or look up number capabilities
sent-analytics
Check the selected account, balance, onboarding state, or readiness to send
sent-account-readiness
用户意图目标技能
预览或发送模板化消息；查看单条消息及其活动情况
sent-messaging
列出、查看、创建、汇总或删除Sent联系人
sent-contacts
查找、查看或删除现有Sent模板
sent-templates
查询控制台消息指标或查看号码功能
sent-analytics
检查所选账户、余额、入驻状态或发送就绪状态
sent-account-readiness

Specialist guidance

专业指导

User intentTarget skill
SMS compliance, 10DLC, brand or campaign registration, TCR vetting, or carrier rejects
sms-10dlc-registration
Authoring WhatsApp template content, choosing a category, or fixing a Meta rejection
waba-template-author
Connecting a WABA through Embedded Signup, callbacks, token exchange, or phone-number mapping
waba-embedded-signup
Launching RCS, preparing an RBM agent, or deciding capabilities and fallback
rcs-agent-onboarding
Designing multi-tenant Sender Profile boundaries, routing, or rate-limit ownership
sender-profile-architect
Diagnosing delivery from MDR exports, funnels, cohorts, or cross-channel failure codes
messaging-performance-analyzer
Designing or auditing a tenant-facing template-builder UI
template-builder-ui
If the request matches one row cleanly, invoke that skill and stop. If it spans several rows, state the proposed order and begin with the prerequisite. For example, check 
sent-account-readiness
before a live send, use 
sent-templates
to locate an existing template before 
sent-messaging
, and use 
messaging-performance-analyzer
when the user provides an export rather than asking for live dashboard metrics.
用户意图目标技能
SMS合规性、10DLC、品牌或活动注册、TCR审核或运营商驳回
sms-10dlc-registration
编写WhatsApp模板内容、选择类别或修复Meta驳回问题
waba-template-author
通过Embedded Signup、回调、令牌交换或号码映射连接WABA
waba-embedded-signup
启动RCS、准备RBM agent或确定功能与fallback方案
rcs-agent-onboarding
设计多租户Sender Profile边界、路由或速率限制归属
sender-profile-architect
从MDR导出数据、漏斗分析、群组分析或跨渠道错误代码诊断交付问题
messaging-performance-analyzer
设计或审核面向租户的模板构建器UI
template-builder-ui
如果请求完全匹配某一行，则调用该技能并停止。如果涉及多行，则说明建议的顺序并从先决条件开始。例如，在实时发送前先检查
sent-account-readiness
，在调用
sent-messaging
前先使用
sent-templates
查找现有模板，当用户提供导出数据而非请求实时控制台指标时，使用
messaging-performance-analyzer
。

Clarifying questions to ask before routing

路由前需询问的澄清问题

Ask only what's needed to pick a lane. Stop as soon as the channel + workflow are unambiguous.
  1. Channel — SMS, WhatsApp, RCS, or unsure?
  2. Workflow stage — fresh setup, in the middle of integration, or debugging something that was working?
  3. Geography — US only, international, or both? (Matters for SMS — 10DLC / TCR is US-only.)
  4. Surface — live account operation, API/backend integration, dashboard UX, or compliance paperwork?
  5. Audience — are you an end-tenant of Sent, or are you building the multi-tenant Sent platform itself? (Sender Profile vs single-tenant onboarding.)
  6. Symptom (if debugging) — error code, rejection reason, low vetting score, or pure delivery-rate drop?
  7. Artifact in hand — do you have a contact, template or message ID, template draft, MDR export, RBM agent ID, or 
    config_id
    ?
One question per turn is fine; never fire all seven at once.
仅询问选择路由所需的信息。一旦渠道+工作流明确，立即停止询问。
  1. 渠道 — SMS、WhatsApp、RCS，还是不确定？
  2. 工作流阶段 — 全新设置、集成过程中，还是调试之前正常运行的功能？
  3. 地域 — 仅美国、国际，还是两者皆有？（对SMS很重要——10DLC/TCR仅适用于美国。）
  4. 操作场景 — 实时账户操作、API/后端集成、控制台UX，还是合规文书工作？
  5. 受众 — 你是Sent的终端租户，还是正在构建多租户Sent平台本身？（涉及Sender Profile与单租户入驻的区别。）
  6. 症状（若调试） — 错误代码、驳回原因、审核评分低，还是纯粹的交付率下降？
  7. 手头的资料 — 你是否有联系人、模板或消息ID、模板草稿、MDR导出数据、RBM agent ID或
    config_id
    ？
每次询问一个问题即可；切勿一次性抛出全部七个问题。

When to handle without routing

无需路由直接处理的场景

This skill is not a fallback for general questions. If the user asks about:
  • Balance, onboarding state, or whether the selected account can send — use 
    sent-account-readiness
    .
  • Contracts, plan pricing, invoices, or account access that the available operations cannot answer — direct them to Sent support or 
    https://docs.sent.dm
    .
  • Generic engineering such as retries, queueing, or observability with no Sent-specific work — answer normally.
  • Meta, Google, TCR, or carrier policy outside a specialist skill's scope — use current upstream documentation.
If after the clarifying questions the request still doesn't fit any target skill, say so plainly. Don't force a route.
该技能并非通用问题的fallback。如果用户询问：
  • 余额、入驻状态或所选账户是否可发送消息 — 使用
    sent-account-readiness
    。
  • 可用操作无法解答的合同、套餐定价、发票或账户访问问题 — 引导用户联系Sent支持团队或访问
    https://docs.sent.dm
    。
  • 通用工程问题，如重试、队列或可观测性，且无Sent特定工作内容 — 正常回答即可。
  • 专业技能范围之外的Meta、Google、TCR或运营商政策问题 — 使用最新的上游文档。
若经过澄清问题后，请求仍不匹配任何目标技能，请直接说明情况。切勿强行路由。

Shared terminology

共享术语

Read 
references/sent-glossary.md
when a routing decision depends on Sent, SMS, WhatsApp, RCS, or MCP terminology. Keep operational details in the target skill rather than duplicating them here.
当路由决策依赖Sent、SMS、WhatsApp、RCS或MCP术语时，请阅读
references/sent-glossary.md
。操作细节保留在目标技能中，勿在此处重复。