A content pool is a curated reservoir of draft posts, source texts, and media items that Autogram draws from when running automated publishing tasks. Instead of generating every post from scratch at send time, automation tasks can pull from a pre-filled pool — rotating through items, recycling evergreen content, or consuming a queue of pre-approved drafts. Managing the pool separately from the schedule lets teams batch-prepare content in advance and keep the publishing pipeline running even when no new generation is triggered.
Writing and publishing run on different rhythms. Ideas arrive in bursts — an afternoon can produce a week of material — while a channel wants a steady drip. A reservoir absorbs that mismatch: you fill it when you have things to say and drain it at whatever rate the audience tolerates. Coupling the two directly means the channel goes quiet exactly when you are busiest.
A pool fails in two directions. Drained, it stops protecting the schedule at the moment protection matters. Overfilled and left alone, it accumulates drafts written for a context that has passed — an offer that ended, a reference nobody remembers. The useful habit is a depth target measured in publishing days rather than item count, plus a pass through the oldest entries before they are the ones next in line.
A pool and a calendar answer different questions. A calendar is a set of dated commitments: this piece, that day, for that reason. A pool is undated supply with no claim on any particular slot. Trying to make one do the other's job produces either a calendar too rigid to absorb a good idea or a queue with no sense of occasion.
Automate your Telegram publishing with AI content, quality scoring, and smart scheduling.