Choose
Select email, SMS, or a supported enterprise-IM campaign type for the authorized exercise.
Channel truth · TaiGong Drill 1.3.4
TaiGong supports email, SMS, DingTalk, Feishu, and WeCom—but not under one availability tier.
01 / Channel matrix
Native · Licensed · Integration · No
Exact delivery support in version 1.3.4.
“Multi-channel” means TaiGong offers several supported campaign types. A base campaign selects one delivery method. Licensed stages in 1.3.4 send follow-up email; they are not cross-channel orchestration.
| Channel or asset | Status | Delivered boundary |
|---|---|---|
| SMTP email | Core | Native campaign channel with templates, landing pages, SMTP profiles, delivery, results, and event evidence. |
| SMS | Licensed | Native providers: Aliyun, Tencent Cloud, and Twilio. The console provider is test output, not a carrier. |
| DingTalk | Licensed | Group robot webhook plus DingTalk App direct messaging and contact sync when configured. |
| Feishu (China) | Licensed | Group robot webhook plus Feishu App direct messaging and contact sync through the Feishu China endpoint. Feishu support does not imply Lark International. |
| WeCom / WeChat Work | Licensed | Group robot webhook only. No WeCom App direct messaging or directory sync in 1.3.4. |
| Slack | Integration-only | Outbound event webhook formatting only. Slack is not a phishing-simulation delivery channel. |
| Microsoft Teams | Unsupported | No native campaign provider and no Teams-specific event webhook adapter. |
| Lark International | Unsupported | No Lark platform option or international Lark endpoint in version 1.3.4. |
| QR code | Core | Generated content asset for a template or manual distribution. It is not an independent campaign delivery channel. |
| Event-triggered email stages | Licensed | Follow-up stages send email after supported campaign events. |
| Cross-channel stage orchestration | Unsupported | Stages do not switch a campaign from email to SMS or enterprise IM in version 1.3.4. |
02 / Operating model
Configure · Deliver · Observe · Follow up
Each channel keeps its provider boundary visible.
A licensed channel still needs the appropriate provider account, credentials, destination rules, and authorized audience. The license enables the TaiGong feature; it does not supply a telecom or enterprise-messaging service.
Configure
Connect the matching SMTP, SMS provider, robot webhook, or supported app credentials.
Prepare
Create channel-appropriate content and confirm the target group and written scope.
Deliver
Run the campaign through its selected delivery method and review provider or application status.
Observe
Review the campaign result and available event evidence before deciding on follow-up.
03 / Buyer boundaries
Read the qualifier, not only the logo
Four distinctions prevent channel overclaiming.
Provider names can look interchangeable in a feature list. In 1.3.4, the implementation boundary matters.
Feishu China support is not Lark International support.
The implemented app path uses the Feishu China endpoint and the accepted platform is Feishu. Lark International is unsupported in this version.
Use the group robot boundary.
WeCom delivery is available through a group robot webhook. WeCom App direct messages and directory sync are not delivered in 1.3.4.
Notifications are not simulation delivery.
Slack can receive outbound TaiGong event webhooks. It cannot deliver an exercise. Microsoft Teams is unsupported for both native campaign delivery and a Teams-specific event adapter.
A generated QR image does not create a fourth campaign transport.
Use QR content inside a template or distribute it manually. The native campaign delivery methods remain email, SMS, and supported enterprise IM.
04 / Channel planning
License · Provider · Scope
Confirm all three before scheduling an exercise.
Validate the TaiGong entitlement, the external provider or enterprise-app configuration, and the written recipient scope. If a program uses more than one channel, treat each as its own supported campaign workflow; do not assume stages can switch channels.
Channel fit, without ambiguity
Map one real exercise to supported delivery.
Bring the channels, providers, enterprise-messaging environment, and exercise scope you use today. We will identify what is core, licensed, integration-only, or unsupported.