---
title: "Content Queue"
id: "1814"
type: "page"
slug: "queue"
published_at: "2026-09-20T22:08:59+00:00"
modified_at: "2026-09-21T01:36:28+00:00"
url: "https://xedant.com/agents/telegram/docs/queue"
markdown_url: "https://xedant.com/agents/telegram/docs/queue.md"
excerpt: "The Queue is the channel’s content pipeline: Ideas → Drafts → Review → Schedule →…"
---

# Content Queue

[https://xedant.com/agents/telegram/docs/queue.md](https://xedant.com/agents/telegram/docs/queue.md)

The Queue is the channel’s content pipeline: Ideas → Drafts → Review → Schedule → Published. One set of tabs shows what has piled up, what is ready for editing, what waits for your “yes”, what is scheduled and what is already out. Plus the shared tag pool and keyword taggers that label the collected messages on their own.

## The pipeline

Five tabs with live counters on the channel’s page:

- **Ideas** — raw sketches: text, media, a slot, grouped by creation date. An idea created from competitor messages shows its origin — the source, the title, the author and a link into the feed;
- **Drafts** — working copies. The order is set by dragging and is kept; “Edit in the editor” opens the full-screen editor;
- **Review** — the gate before the schedule: “Approve” (if no slot is set, its picker opens) or “Reject” with a reason;
- **Schedule** — a list by dates (each item offers “edit”, “send back to review”, “delete”) and a weekly calendar: items sit in the slot cells, in the slot’s color;
- **Published** — grouped by publish dates; an item opens the actual post in Telegram.

## Creating manually

An item is created with the “Add idea” or “New draft” buttons in the queue — or you simply write a post in the editor: it appears among the drafts by itself. Transitions between states are flexible: an idea can go straight to the schedule or to rejected, a draft to review, and so on.

## Ideas from other people’s messages

In the message feed every message has a “capture an idea” action: the idea is created in the chosen channel and references the source messages — their origin is visible right in the ideas list. Routing creates auto-ideas: a message that matched a rule lands in the channel’s queue by itself, with the text and the source’s name — details in the [Routing](/agents/telegram/docs/routing)
 section.

## Tags and taggers

Tags are a shared pool of colored labels for messages, authors and taggers: creating, renaming, color, description and search; deleting a tag removes its assignments everywhere at once. A keyword tagger is a rule “if the text contains a word, assign these tags”: keywords one per line, the “any” mode (one is enough) or “all” (every one is needed), stop keywords that block a match, and the choice of fields to search — text, title, author.

A tagger can be tested on a sample text (without changing any data), run over all the already collected messages, or left to work automatically: every new message is checked by all enabled taggers in order, and one tagger’s failure does not stop the rest. An author’s tags are inherited by all their new messages — details in the [Authors](/agents/telegram/docs/authors)
 section.

## What is next

Where to view and triage the messages ideas are born from is the [Message Feed](/agents/telegram/docs/messages)
 section, how slots determine dates is [Scheduling](/agents/telegram/docs/scheduling)
, and how the editor works is [Publishing](/agents/telegram/docs/publishing)
.

[← Back to the documentation index](/agents/telegram/docs)