Workspace administration
Workflow automation: approval, queues and AI generation
Use business workflow rules to decide when work advances. AI can prepare content or perform permitted actions within those rules; it does not replace every approval or outcome check.
Choose the right kind of workflow
EleonEcho has several coordinated mechanisms rather than one generic automation setting. Lifecycle supplies publishing approval behavior. Queues supply reusable destination, slot and approval defaults. Recurring post schedules can clone eligible content or prepare AI-generated content with configured instructions. Tickets has its own routing, assignment, status and optional SLA rules.
Begin with the business transition you need: a draft ready for a reviewer, an approved post waiting for a slot, or a support case waiting for staff. This identifies which module’s settings should change.
Use Lifecycle for publishing approval
A post can inherit an approval flow from queue settings or use its configured flow. Submission starts or restarts the applicable Lifecycle process. The author and the assigned reviewer may see different working states because the current step has a particular owner.
Editing work already in approval can require confirmation and restart the review. Treat that as a meaningful workflow change, especially when a post has a near-term schedule. Review the post review guide before changing approval defaults for an active queue.
Use queue slots for repeatable publishing
A queue groups the channels and timing arrangement for a publishing stream. Queue settings can supply approval defaults for posts scheduled through that queue. The publishing slot is a time opportunity; it does not bypass required approval or guarantee provider acceptance.
For a recurring announcement stream, confirm the queue’s destinations and timing first, then add content. Inspect the planner and queue state to understand whether a post is awaiting review, assigned to a future slot or blocked by a delivery issue. See Queues for the operational details.
Prepare recurring content with the configured Posts Agent
Recurring generation uses eligible source posts, scheduling rules, instructions and a generation lead time. AI creation resolves the configured Posts Agent; it is not a free choice of any unrelated agent. That agent and its provider must be available when generation runs.
Generated content follows the configured publishing lifecycle. Draft output remains draft, while a successful generation intended for a new lifecycle can enter that process. Inspect the resulting post and its review state before assuming a recurring slot will publish. The schedule guide covers the difference between generation timing and publication timing.
Keep support rules and internal marketing work distinct
Support channels need explicit Ticket processing and Department routing. Ticket assignment, allowed status transitions and SLA settings belong to the case workflow. A private marketing task can use Tickets without becoming an external customer conversation.
If an AI agent participates, configure its exact job and tools. Automatic correction in publishing, a support response and an internal task update are separate capabilities. Use internal marketing tickets to organize private work without implying that a task automatically launches a campaign.
Diagnose a workflow that has stopped advancing
Inspect the current record, required approval, assigned person, queue slot and relevant channel outcome in that order. For generation, also inspect the agent and execution result. Shared Lifecycle workflow and report screens are available where enabled for your deployment and role.
Change one confirmed cause at a time, then verify the next business state. A successful scheduled job or AI run does not by itself mean a post reached its audience or a customer received a reply. Preserve those separate checks when expanding automation.