Internal marketing agents
Turn a campaign request into clear, reviewable work. Keep the brief, next step and team discussion in a private marketing workflow.
Prepare the onboarding
campaign brief.
Confirm the guide URL before drafting the call to action.
How it works
Campaigns need more than a draft. Configure an internal agent around a focused task, relevant knowledge and permitted actions, while private Tickets provide a place for team ownership and follow-up.
Specify the audience, objective, deliverables and source material. Include the reviewer and any known constraints. A request for an onboarding campaign becomes easier to act on when it says who the campaign should help and what they should do next.
Ask the configured agent to structure the brief, identify missing information or suggest an outline. Keep speculative ideas visibly separate from approved product facts. AI assistance should make the next discussion more concrete, not turn unknown details into commitments.
Use the private Ticket workflow to organize responsibility and internal discussion. Team notes should stay internal. A customer conversation and a private campaign request have different audiences and should not share context indiscriminately.
Once the team has reviewed the brief, use the publishing workflow to develop and schedule the content. Treat this as a team process unless the exact automated action has been configured and verified. Internal approval alone does not publish a post.
A worked example
The marketing team requests a short campaign introducing a new guide. The agent helps organize the audience, key message and required assets. A private note identifies the guide URL as still awaiting confirmation.
Illustrative scenario. No account, post or Ticket is created.
Make the first
week count.
A practical guide to turning setup into your team’s next step.
Controls and setup
Start with a focused use case and verify the configured workflow.
Internal marketing Tickets organize staff tasks and notes. They are separate from customer-facing sales or support conversations. Configure the agent’s knowledge and tools for that internal audience.
The workflow does not promise that every campaign asset, approval or publishing action happens automatically. Define each agent’s task and verify its permitted actions. Reporting and revenue outcomes depend on other operational systems and evidence.
Service questions
Practical details for planning this workflow.
Internal Tickets and notes are intended for private team work. Keep this workflow separate from external conversations and apply the appropriate access configuration.
Not by assumption. Publishing has its own lifecycle. Any automated bridge must be explicitly configured and verified.
A focused task, relevant source material, the intended audience, permitted actions and a clear review or escalation path.
PUT IT INTO PRACTICE
Follow the setup, understand the controls and find the next step.
Create staff-only campaign requests, discuss and edit private messages, manage attachments and use Department access without customer delivery.
Understand EleonEcho workspace access, Ticket Department membership, publishing reviewer visibility, personal sessions and customer portal boundaries.
Work with publishing media, protected ticket attachments, form files and PDF versions, while keeping storage and AI knowledge access distinct.
Your next chapter, with AI
Bring your publishing, marketing and support work into Echo.
