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.

Communication & Broadcasts

Receive member messages and reply through Project Inbox

Manage captured private bot conversations without exposing Telegram identities.

Who can use it
Owners and operators with Project inbox scope; Pro required
Where to find it
Community Command → Inbox
Before you start
  • A selected project
  • A member conversation captured by the bot
  • Reply capture enabled for relevant replies
On this page

Configure capture

  1. Open Inbox and inspect Reply capture. Enable it when you want supported replies to official bot messages captured for the project.
  2. If desired, enable Allow new member conversations. Plain private bot messages can start a thread only when the sender’s project relationship is unambiguous.
  3. Explain to members that they should use the private bot conversation. Group messages and commands are not ordinary Inbox messages.

Reply to a member

  1. Use All, Needs reply, Waiting on member, Open or Resolved to locate a thread.
  2. Select the member reference and read the conversation carefully. The reference is deliberately not a Telegram username or ID.
  3. Enter a reply in Reply to this member, up to 3,500 characters.
  4. Press Send through bot. The response includes the official project identity wrapper and goes through the bot.
  5. Check the message status. Queued, sent, failed and uncertain outcomes have different meanings; do not claim delivery until it is confirmed.

Organize conversations

Open, Needs reply, Waiting on member and Resolved are internal statuses. Changing one does not send a notification. Eligible new replies can reopen resolved conversations. Block member is a conversation control; use it only for the intended member.

Troubleshooting

No thread can mean capture is off, the message was a command/group message, or the member belongs to multiple projects so the bot cannot safely choose one. Ask the member to reply to the project’s official private bot message. An uncertain delivery may already have reached the member, so do not resend automatically. Acknowledge uncertainty records that you reviewed it and unlocks another deliberate reply; it does not prove the send failed and does not resend the message.

Privacy

Inbox screenshots in this help center do not include real member conversations. Do not share private message content when reporting a problem.

Related guides

Choose between a group broadcast, watcher update and Inbox reply

Select the audience before composing so you know who can receive the message.

Watch a launch and manage your own notifications

Understand explicit opt-in, private controls and My Watchlist.

A message, reminder or sticker did not arrive

Distinguish audience, queue state, Telegram confirmation and schedule eligibility.