Direct Telegram placements: briefs, approvals and acceptance

What this guide delivers

A direct placement is an arrangement with a channel representative about a specific publication. This guide covers the editorial handover: what to request, how to record the approved version and how to establish whether the delivered publication matches it. It does not repeat a channel selection or audience growth guide. The deliverable is an evidence pack that another colleague can check without relying on a private conversation.

The steps and templates below are our editorial method, not official Telegram requirements or a standard contract. Rules of Telegram Ads must not automatically be applied to direct placements. Nor does the absence of a rule in this guide establish permission. Prices and applicable commercial terms should be checked in the relevant personal account; direct arrangements also require written confirmation from the counterparty.

The Russia boundary

The FAS explanation dated 25 March 2026 refers to the prohibition on advertising on resources with legally restricted access and describes a transition period without enforcement measures for Telegram and YouTube. Non-enforcement is not positive permission for a new paid campaign. We therefore do not recommend a paid Telegram launch targeting Russia. Both exercises below remain unpublished preparation. Translation into another language does not change this geographic boundary.

The document was checked in reproductions at ConsultantPlus and Garant on 20 October 2026; this is not a complete review of subsequent legislation. A disclosure, an agreement or a channel representative's consent cannot independently resolve the legal issue. Record a separate legal decision for the actual product, parties, audience and publication date before considering any live use.

Documented project: Gov.sg and a consistent message

On 2 April 2020, Singapore’s MCI announced Gov.sg Telegram for COVID-19 information, carrying the same messages as Gov.sg WhatsApp.

Gov.sg launch announcement.

The official directory, updated 14 September 2026, identifies Telegram @Govsg. These are the operator’s statements, not an independent evaluation. Internal approvals, individual post comparisons, paid-placement agreements and Telegram-attributed conversions are not established by these sources.

Official channel directory.

Our editorial diagnosis: when a message is handed to another channel, its promise, link and preview can diverge. An identifiable publisher and a common package make the differences checkable. We propose freezing copy and destination together and asking another reviewer to compare delivery. This method and the worksheet below are ours; we do not claim Gov.sg used them. The case documents public information in Singapore, not a paid campaign or advertising permission in Russia.

Assemble the brief and confirm authority

Begin with the reader's task, not the channel's sales presentation. Write what the reader will learn, what is offered, who supplies it and what the next action means. Gather the source for every product claim, the right to use each image, the intended destination and the advertiser's written source restrictions. If a required fact is missing, leave the corresponding claim out of the copy.

Use the channel's established public contact route to confirm who can approve the publication. Compare the address with the channel's own information; a forwarded message or copied avatar is insufficient evidence of authority. Do not request passwords, login codes, subscriber lists or unrelated private conversations. Unresolved identity means the handover stops.

Brief template: reader task [ ]; product and responsible supplier [ ]; allowed source and geography [ ]; supported claim and evidence [ ]; intended action [ ]; destination [ ]; rights to materials [ ]; disclosure responsibility [ ]; approving person [ ]; unresolved questions [ ].

If AffiliateCore fits the intended partnership, prepare this brief before discussing an offer. Our platform does not approve a Telegram placement or replace the channel agreement. No suitable offer is assumed to be available. You can prepare a publisher profile while the material remains a draft.

Agree the publication, not just the topic

Record the exact copy, image file and destination together as a named version. Describe the planned publication window, retention arrangement, whether pinning or edits are included, how corrections are requested and what happens if delivery differs. These are matters to agree, not benefits automatically provided by Telegram. Confirm who checks required disclosures and any applicable registration or reporting obligations; do not invent a universal disclosure recipe.

Approval note: channel [ ]; copy version [ ]; image [ ]; destination [ ]; publication window [ ]; retention and editing arrangements [ ]; disclosure text and responsible party [ ]; permitted changes [ ]; acceptance evidence [ ]; correction contact [ ]; explicit approval [ ].

Read the preview as a subscriber would. The opening must identify the useful material, the action must match the destination, and restrictions must not disappear behind an attractive claim. A change to the link or promise invalidates the old editorial approval. Ask for a revised version rather than accepting “the same meaning” without examining it.

Exercise: a workflow template for service teams

This is an unpublished fictional exercise, not a customer result. A publisher prepares a placement for a channel about running service teams. The useful asset is a task-handover checklist. The advertiser supplies the template, its description and confirmation that the publisher may use the illustration. The editorial objective is to help the reader decide whether the template suits their workflow, without promising productivity gains.

Draft copy: “A task handover often loses the owner, the next action or the completion criterion. This checklist brings those fields together, with an example you can inspect before using it. Open the template description and check whether it matches your team's process.” Add the applicable advertising disclosure only after its requirements and wording have been checked.

Prepare a destination containing the actual template description and a visible explanation of the next action. In a rehearsal, a colleague follows the proposed link on a phone and compares the material with the promise. They discover that the draft destination asks for a consultation instead of showing the checklist. Record the mismatch; do not solve it by making the invitation less clear.

The advertiser can supply the promised material or the publisher can rewrite the promise truthfully. Send the revised copy and destination through approval again. The exercise passes when the reader can find the stated material and understand any later enquiry separately. It stops if the advertiser insists on a claim or route that cannot be substantiated. Even a successful rehearsal does not authorize publication in Russia.

Finish the rehearsal with a separate fictional enquiry sheet; do not send it to a CRM or partner tracker. A voluntary request for help applying the template is accepted for review because it concerns the material and has an assigned owner. A repeated request is marked as a duplicate linked to the original, not a new result. Downloading the template alone does not constitute an accepted lead. Leave attribution unresolved when the source is unknown. These are exercise decisions, not universal advertiser acceptance rules.

Exercise: an educational workshop and an unapproved edit

A second unpublished exercise concerns a workshop on organizing a document archive. The publisher has an approved programme, presenter biography, participation conditions and image permission. The proposed copy describes the topic and links to a page where a reader can inspect the programme before choosing whether to register. It makes no employment or certification promise.

Draft copy: “How can a team keep document versions understandable? This workshop examines naming, ownership and handover using a sample archive. Read the programme and participation conditions before deciding whether to register.”

Rehearse acceptance using a mock publication, clearly marked as a training sample. The mock editor has replaced “read the programme” with “receive a professional qualification” and changed the destination to a general contact page. Compare the sample against the approved version, record both discrepancies and hold acceptance. The fact that the topic is still document management does not make these changes acceptable.

Correction request: approved version [ ]; observed wording or link [ ]; supporting screenshot [ ]; reader impact [ ]; requested correction [ ]; person responsible [ ]; verification after correction [ ].

Restore the substantiated wording and intended destination in the mock. Have a colleague verify the full route again, including the participation conditions. The result is a completed rehearsal record, not evidence of a real campaign or registrations. Continue preparation only when the corrected version is explicitly approved; stop if the publication representative cannot preserve the material or identify who controls edits.

In a separate fictional registration sheet, define the exercise rule: accept an enquiry only after the selected workshop and participation conditions have been confirmed. Mark a matching record accepted; reject a request for professional certification as outside the programme and flag it to the editor as evidence of a misleading promise. If the participant later withdraws, retain the change from accepted to cancelled and its reason. Keep the original decision. All records stay outside production systems; accepting the mock publication proves no real registration.

Copyable worksheet: brief, version and link acceptance

Use this sheet after the two rehearsals. Copy the blank part into a document, attach the exact copy and image, and ask a second reviewer to reproduce the checks. The filled examples are fictional, offline exercises. File names describe mock materials, not live URLs or AffiliateCore endpoints. The inline sheet contains everything needed; downloading is optional.

Download the worksheet as UTF-8 text

TELEGRAM EDITORIAL HANDOVER — BLANK WORKSHEET

Purpose: internal review, not publication permission.
Do not enter passwords, subscriber data or private customer records.

BRIEF

Record name / owner: [ ]
Reader’s task / supplier: [ ]
Exact promise / evidence file and location: [ ]
Prohibited or unverified claims: [ ]
Audience / geography / source restriction: [ ]
Legal review / disclosure wording / responsible role: [ ]
Channel URL / publisher’s own page confirming it: [ ]
Representative’s authority / verification record: [ ]
Text version / exact copy attachment: [ ]
Image file / rights evidence: [ ]
Visible link label / actual target URL: [ ]
Expected final page / expected reader action: [ ]
Publication window with time zone / retention / edit agreement: [ ]
Publication status: [draft / rehearsal / separately authorized]

VERSION AND APPROVAL

Package name: [ ] Previous package: [ ]
Changes to copy, image, link, preview or disclosure: [ ]
Approver / role / timestamp and time zone: [ ]
Approval record naming the exact package: [ ]
Unresolved issue / owner / next check: [ ]
Silence, an emoji or approval of the topic is not explicit approval of a package.
Any material change returns the package to review; retain the previous version.

ACCEPTANCE RECORD

Draft or post reference: [ ] Check time and time zone: [ ]
Device / browser / login state: [ ]
Expected wording and link: [ ] Observed wording and link: [ ]
Observed final destination / preview: [ ]
Evidence file: [ ] Decision: [pass / revise / stop]
Correction owner / revised package / retest evidence: [ ]
Acceptance of the post and acceptance of a lead remain separate.

FILLED EDUCATIONAL EXAMPLE A — TASK HANDOVER, NO PUBLICATION

Owner: training editor. Supplier: fictional service team.
Reader task: inspect a task-handover checklist.
Promise: a template showing owner, next action and completion criterion.
Evidence: training-template.txt; image: training-preview.png, assumed cleared for this exercise only.
Channel: offline mock, no real account. Geography: Russia exercise; paid launch not recommended.
Legal and disclosure review: unresolved; no publication window assigned.
Package: HANDOVER-A. Link label: Open the checklist.
Actual URL: not assigned; offline destination fixture: consultation-page.txt.
Expected fixture: template-description.txt.
Observation: consultation request replaces the promised material.
Decision: REVISE; retain HANDOVER-A and the mismatch record.
Correction owner: training editor. New package: HANDOVER-B.
Change: substitute template-description.txt and preserve the truthful promise.
Recheck: another reviewer finds the template and a separate optional enquiry.
Training approval: HANDOVER-B, rehearsal only; reviewer and actual check time must be recorded when run.
Final state: rehearsal passes after recorded recheck; legal publication gate remains closed.

FILLED EDUCATIONAL EXAMPLE B — WORKSHOP

Package: ARCHIVE-A; promise: read the programme, no qualification claim.
Expected fixture: workshop-programme.txt.
Observed mock: qualification promise and general-contact.txt.
Decision: REVISE; record wording and destination as separate defects.
Correction: ARCHIVE-B restores programme wording and programme fixture.
Pass only after a second reviewer checks programme and participation conditions and records explicit package approval.
STOP if no one can confirm authority to preserve or correct the post.
No registrations, CRM entries or partner results are generated by this exercise.

REPEATABLE CHECKLIST AND DECISION RULES

[ ] Compare exact copy, image, disclosure and package approval.
[ ] Compare the visible label with the actual link target; do not trust the label.
[ ] On a permitted test destination, follow the link without submitting a form; record the final page and any unexpected redirect.
[ ] Inspect the preview separately. A correct preview does not prove a correct destination.
[ ] Confirm the promised material and next action remain visible on mobile.
[ ] Negative test: substitute the contact-page fixture; expected outcome is REVISE.
[ ] Negative test: remove the approval record; expected outcome is STOP, not assumed consent.
[ ] Retest the corrected full package and retain old evidence.
PASS: exact approved package and destination match, evidence is reproducible.
REVISE: a specific mismatch has an owner; acceptance waits for correction and reapproval.
STOP: authority, rights, claim evidence or legal basis is unresolved.
Editorial PASS alone never authorizes publication or proves a conversion.

Acceptance and result review are separate

For any future legally permissible placement, collect the publication link, the approved version, a dated capture and the correction history. Check the publication itself rather than only an administrator's screenshot. Retain only the evidence necessary for the agreed purpose and restrict access. If a post is removed or the destination changes, record the observation and contact the responsible party; do not declare a breach before checking the agreement.

Acceptance answers whether the promised publication was delivered. Result review asks what happened after the reader's voluntary action. A view is not an enquiry, an enquiry is not an accepted partner result, and a later cancellation should not disappear from the record. Use the advertiser's agreed reasons and identifiers without copying personal data into public reports. Where attribution is unavailable, record “unknown” instead of inventing a relationship.

If a suitable AffiliateCore offer is available and the source is permitted, the agreed result can be checked against its conditions in your publisher account. This is separate from proving that the channel delivered the post. Sign in as a publisher to review your own available conditions, not to obtain Telegram authorization.

Stop, revise or continue

Stop preparation when authority, rights, substantiation or the legal basis cannot be established. Revise when a specific mismatch can be corrected and rechecked. Continue to the next internal review when the brief, copy, destination and evidence agree, with an accountable owner for outstanding work. None of these editorial states means “launch permitted”.

Your practical assignment is to complete the brief and approval note, rehearse a destination mismatch, and write an acceptance record that another reviewer can reproduce. Keep version history rather than overwriting the evidence. Use the current conditions in the relevant personal account; this guide intentionally supplies no tariffs, spending assumptions or numerical performance targets.

Sources and further reading

Checked on 20 October 2026: FAS explanation reproduced by ConsultantPlus and the dated reproduction at Garant. These support the Russia boundary, not the editorial templates. Telegram Ads guidelines explicitly concern its advertising platform; they are not presented here as direct-placement rules.

For the separate task of maintaining your own channel, see our owned-channel guide. Its existence does not establish current legal permission for advertising. The present article is limited to preparation, version control and acceptance.

Sources rechecked on 25 October 2026. The FAS original at fas.gov.ru/news/34584 timed out again; the cited reproductions remained accessible. The Russia caveat is retained, not replaced by a fresh legal clearance. Telegram Ads guidelines were accessible but show no publication date. The Gov.sg dates above belong to the specific source pages, not to this article’s publication.