Get started with EleonEcho: connect, configure and launch

Choose your first publishing or support workflow

EleonEcho brings publishing, customer conversations and AI-assisted work into a shared workspace. A useful first project is deliberately small: prepare a launch announcement for one publishing channel, or receive a customer message and answer it through one support channel. Choose the people responsible for the work and the outcome you will check before adding more destinations.

For a publishing pilot, collect an approved brief, a destination and a reviewer. For a support pilot, choose a mailbox or supported messaging connection, a Department and an available agent. The platform module map explains which area owns each step.

Confirm your workspace and access

Use the account and workspace address supplied for your deployment. The marketing website is separate from the signed-in application: a guided example does not create an account, grant an AI allowance or submit a ticket. Check the actual offer and onboarding details before relying on trial limits.

Confirm that the people performing the pilot can open the required modules. Support assignment also depends on Department membership and Ticket Agent permission. A visible menu is a starting point; actions and individual records can have additional access rules. See roles and permissions when an action is missing.

Connect an account, then configure its channel

1. Open External Connections and choose a supported connection type.
2. Complete its authorization or provider configuration and inspect its current status.
3. Create or configure the corresponding channel for the intended destination.
4. For support, enable ticket processing and select the Department; connecting a mailbox alone does not complete support routing.
5. Check the specific capability you need: publishing, incoming conversation, outgoing reply or mailing-list delivery.

The connection guide and channel guide explain the distinction. A provider icon in the catalog is not confirmation that every capability is available.

Give AI a defined job and a review boundary

For an AI-assisted pilot, write a specific instruction: the audience, source material, tone, desired output and situations that need a person. Use only the knowledge sources and tools enabled for that agent. More context is not automatically better; an outdated policy can produce a confident but unhelpful answer.

Keep publishing approval explicit. Draft generation, automatic correction, reviewer approval and external publication are separate steps. Start with human review and inspect the result before increasing permitted automation. Read AI tools and autonomy for the configuration concepts.

Check the result where it matters

For a post, inspect its content, approval state, schedule and channel outcome. For a support message, confirm the correct ticket, requester, Department and public reply. For email or SMS lists, inspect recipient outcomes separately from the post status. A successful AI reply does not by itself prove that a tool created a ticket or sent a message.

Record one successful example and one expected failure, such as an unavailable provider or a request outside the agent’s scope. Expand to more channels once the team knows where to review, recover and follow up.