Skip to documentation
CCARTEL HQ

Product documentation

Cartel HQ Help Center

Set up your project, connect Telegram and learn each tool step by step.

Production verified 30 September 2026. Guides identify plan, permission and verification limits.

Sticker & Brand Tools

Use versions and review replacements for live stickers

Keep the live Telegram sticker working while assessing a candidate.

Who can use it
Project owners and authorized project administrators
Where to find it
Sticker Lab → Sticker Studio → sticker card
Before you start
  • A saved pack and an existing sticker
On this page

Review existing versions

Version History holds successful generations. A/B/C variations may be offered by the current studio for eligible stickers. Generating variants is deliberate AI work; a Failed variation does not mean the current successful image disappeared.

Replace a live sticker carefully

  1. Find the sticker marked Live on Telegram. Direct regeneration is locked to keep the live set synchronized.
  2. Choose Generate candidate only when ready for new AI work.
  3. Wait for the candidate to complete and inspect the quality and transparency.
  4. Use the offered review/approval replacement action only if you intend to change that specific Telegram sticker. Read the confirmation.
  5. Verify the returned result and the existing Telegram set. Until approval and replacement succeed, the previous live sticker remains the current live release.

Separate actions

A new generation, a candidate review, Current Motion approval and a Telegram replacement are not equivalent. Read the action summary to see whether it starts provider work, changes a saved pointer or changes Telegram.

Troubleshooting

Use the reported failure stage and Refresh status. Do not start repeated candidates while one is still running. Keep existing versions and the live set intact when investigating a failed candidate.

Service Partner boundary

This is an owner creative tool. The delegated Sticker tools scope does not grant Sticker Lab generation, uploads, pack publishing or native send tests. The project owner prepares and publishes packs first; a partner can then only schedule drops from published packs in the managed Sticker Drops panel.