The brief is the contract between research, campaign operations, sales, support, compliance, and the person whose account carries the platform risk.
Use the template below as a decision record. Replace every bracketed instruction with a concrete answer and link the evidence.
How to use this resource
A useful Telegram campaign brief makes nine decisions before scheduling: the business hypothesis, audience evidence, source quality, exclusions, message promise, reviewer, reply capacity, success metrics, and stop conditions. If any field is unknown, the campaign is not ready to scale.
Included in the template
01A copy-ready campaign brief.
02Approval and ownership fields.
03Metric definitions and stop rules.
04A post-campaign learning block.
1. Campaign identity and hypothesis
- Name: [audience + offer + period, not 'Campaign 7']
- Owner: [one accountable person]
- Business outcome: [qualified conversation, activation, partner meeting, or other verified outcome]
- Hypothesis: We believe [observable audience] experiencing [specific problem] will value [offer] because [evidence].
- Experiment variable: [one main selection, message, offer, or timing change]
- Decision date: [when results will be reviewed]
2. Source and audience
| Field | Required answer |
|---|---|
| Source set | Named groups or communities and why each is relevant |
| Rule review | Community and platform constraints checked on date |
| Eligibility | Observable inclusion criteria |
| Exclusions | Roles, regions, states, sensitive cases, and ambiguity rules |
| Deduplication | Identity keys and cross-list window |
| Suppression | Where and when live suppression is checked |
| Human review | Sample size, reviewer, and disagreement process |
3. Message and recipient value
- Identity: who is contacting and for which organization.
- Context: why this recipient may reasonably find it relevant.
- Value: the smallest concrete outcome or resource offered.
- Ask: one clear, low-friction next step.
- Decline: simple path to close and suppress.
- Prohibited claims: guarantees, false familiarity, hidden conditions, or unsupported proof.
4. Capacity, controls, and approval
| Control | Decision |
|---|---|
| Sending accounts | Named accounts, owners, configured proxies, and approved limits |
| Reply capacity | Daily useful-reply capacity and backup owner |
| SLA | Priority classes and ownership targets |
| Stop rules | Complaint, restriction, error, suppression, and backlog thresholds |
| Approvals | Audience, message, compliance, and launch approvers |
| Incident route | Named owner and runbook link |
5. Measurement and review
- Primary metric: [numerator, denominator, window, exclusions]
- Quality metrics: eligible rate, reviewer agreement, useful reply mix, qualification.
- Control metrics: suppression misses, complaints, errors, restrictions, unowned backlog.
- Outcome metric: pipeline, activation, revenue, or retained relationship with attribution rule.
- Result: continue, revise, stop, or collect more evidence.
- Learning: what changed in source, audience, message, capacity, or control policy.
Launch standard
A reviewer who did not design the campaign should be able to explain whom it contacts, why, what it promises, who owns replies, and exactly when it stops.
Research note
The template combines controlled-experiment practice with Telegram platform and outreach safeguards. It does not replace legal, platform, or community-specific review.
Use it in the next review
A campaign brief slows the first hour and saves the next hundred. It exposes weak assumptions before recipients, accounts, and reply teams pay for them.
Turn the approved brief into one connected workflow
TeleBoost links sources, lists, controlled campaigns, conversations, tickets, teams, analytics, API, webhooks, and MCP.
Continue the operating system
Related TeleBoost guides
Evidence base