ExplanationUnderstand the concepts

Understanding Agent Console

Agent Console is a centralised platform of AI agents that integrates with Storyteq CMP to automate time-consuming marketing tasks. Each agent runs with playbooks, reusable sets of instructions an administrator configures, so its output reflects how your organisation wants the task done.

What is Agent Console?

Agent Console is a centralised platform where AI agents perform specific marketing tasks.

Clients expect their Content Marketing Platform to be AI-enabled, with less friction, less manual work, and access to current models. Agent Console addresses this with purpose-built agents for specific marketing tasks.

Agent Console integrates with Storyteq CMP and Content Automation. Agents can act on your Storyteq CMP data: the briefing agent, for example, creates a brief in LUMA.

The primary goal is to build platform foundations for agent orchestration, usage tracking, client management, and future embedded AI capabilities across Storyteq’s products.

How Agent Console differs from other AI tools

With a general AI tool, you write a prompt for each task and the model works only from what you type. The quality of the result depends on how fully you describe your brand, audience, and constraints every time.

Agent Console agents run with playbooks: reusable, versioned sets of instructions that an administrator writes for an agent. A playbook captures how a task should be done for your organisation, so the agent applies the same guidance on every run without you restating it.

Consider writing marketing copy. With a general tool, you describe your tone of voice, preferred terminology, and any compliance rules in the prompt each time, then revise the output by hand. With Agent Console, the copywriting agent runs with a playbook that already carries that guidance, so its drafts start closer to your standards.

A playbook holds instructions, not your asset library or live brand data. An administrator selects the playbook an agent uses, and each run records the playbook version that produced it.

The vision: from destination to capability

This section describes the intended direction, not current behaviour.

Today, Agent Console is an application where users select an agent and run a task. The longer-term aim is to move agent capabilities into Storyteq CMP and Content Automation directly, so AI assistance appears inside existing workflows rather than in a separate application.

A further aim, Brand & Campaign Intelligence, would structure brand guidelines, campaign objectives, approved messaging, usage rights, and regulatory requirements into machine-readable data that agents query directly, instead of relying on hand-written instructions.

User roles

Superadmin (Storyteq employees)

Superadmins enable Agent Console for client organisations, configure which agents are available globally, and monitor platform health.

Client Admin

Client Admins select which agents their users can access, configure agent playbooks, set usage limits, view usage reports, and invite users. Client Admin capabilities are permissions applied to existing Storyteq CMP users.

Client User (Marketer)

Client Users select an agent, provide inputs, and review its outputs.

What Agent Console enables

Agent Console provides two agents:

  • Briefing agent: gathers a brief through a chat conversation and creates it as a project in LUMA, using your domains, types, and taxonomy.

  • Copywriting agent: generates and refines marketing copy in different styles, structures, and tones of voice, and can use web search to ground its drafts.

What’s out of scope

The following capabilities are out of scope:

  • Template rendering: Agent Console does not render templates using Storyteq’s template engines (Content Automation, Entropy, Fusion).

  • Campaign management: Agent Console does not manage campaigns or run multi-step workflows.

  • Channel distribution: Agents do not publish content to social media or advertising platforms.

  • External system integration: No integration with PIM, CRM, or advertising platform APIs.

  • Autonomous operation: Agents require human initiation and do not run scheduled tasks automatically.