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.

Missions

Start and close an X mission from Telegram

Use the verified group commands and monitor the stored mission record in HQ.

Who can use it
Authorized Telegram group administrators; Pro required
Where to find it
Connected Telegram group; Community Command → Missions
Before you start
  • A Ready connected group
  • A valid X post link
  • Permission to run missions in that group
On this page

What a mission does

An X mission organizes community activity around an X post and tracks configured targets from available measurements. X is the social platform previously known as Twitter. A target is a goal, not guaranteed engagement.

Run a mission

  1. Open the intended connected Telegram group and confirm you are using the correct project community.
  2. Send /mission followed by the X post link, for example /mission https://x.com/account/status/1234567890. Replace the example with the real post URL.
  3. Review the mission card created by the bot. Its duration and goal come from the project’s saved mission defaults at the moment it starts; later changes do not alter it.
  4. Open Community Command → Missions to inspect the recorded lifecycle, history and metrics. This web list does not start or close missions.
  5. When authorized and ready, send /mission close in the connected group to close the active mission. Check the returned result and stored state.

Read measurements correctly

A dash means an unavailable or unknown measurement, not zero. Stored snapshots are not a guarantee of current real-time X counts. Do not promise likes, reposts, replies or reach.

Troubleshooting

Use a real X status link and the correct group. Check admin permissions, Pro access, any active mission conflict and the bot’s reply. If pinning or command cleanup fails, inspect those bot permissions separately from the mission’s lifecycle.

Related guides

Configure mission defaults and official-post suggestions

Save project-wide settings for future missions without starting one or changing a running mission.

Bot permissions, verification and installation messages

Understand Ready, permissions and the difference between installation and member welcomes.

Missing controls, upgrade gates and wrong-project data

Check account, role, scope and selected project before assuming a feature is broken.