Echo integrations

Connect your channels.
Reach your mailing lists.

Publish to email and SMS lists, share content on connected social channels and bring customer questions into support. Choose the connection and workflow that fit your audience.

Your audience, directly

Email mailing lists.
SMS lists. Built into Echo.

Create with AI, refine with your team, and publish to the people on your lists.

Email mailing lists

Keep your audience
in the loop.

Product news, useful guides and customer updates. Manage recipients and publish from a connected mailbox.

CSV importSubject & formatDelivery status
Explore email mailing lists

SMS lists

A short message.
A timely next step.

Reach your SMS list through 019SMS. Preview the final text and follow each recipient’s delivery outcome.

Phone listsMessage previewOpt-out controls
Explore SMS lists
SMS previewIllustrated workflow
EYour connected senderExample message
Your guide is ready. Open your workspace to read it.
52 / 70 units
Preview the exact text Check the recipient list Review delivery outcomes
Illustrated example. No email or SMS is sent.
  1. 01

    Build your list

    Add, paste or import recipients. Review duplicates and invalid entries.

  2. 02

    Prepare & preview

    Refine the content, choose the sender and check the final message.

  3. 03

    Publish & follow through

    Use the publishing workflow, inspect delivery and respect opt-outs.

A supported, configured connection is required. Unsubscribe is optional and needs setup. SMS is short text; MMS is not included.

Your channels, connected

Explore all 27 predefined channels.

Social networks. Messaging. Email. Publishing platforms. Find your audience in the Echo channel catalog.

Core connections

Configure for your workflow
  • EmailMailing lists & support
  • TelegramBots & user accounts
  • WhatsAppCloud API messaging
  • FacebookPage publishing
  • InstagramAccount publishing
  • SMS / MMS019SMS · SMS lists

Account setup and deployment requirements apply. Facebook and Instagram are publishing connections. SMS depends on the enabled 019SMS service; MMS is a catalog capability.

Extended channel catalog

Limited or partial implementation
  • Threads
  • X
  • LinkedIn
  • TikTok
  • YouTube
  • Pinterest
  • Google Business Profile
  • Bluesky
  • Mastodon
  • Reddit
  • Discord
  • Slack
  • Viber
  • Discourse
  • WordPress
  • Ghost
  • Blogger
  • Tumblr
  • Medium
  • RSS Feed
  • Stack Exchange / Stack Overflow

Includes connections that are not fully implemented. Publishing formats, support conversations and activation vary by provider and deployment.

Your website belongs here, too.Add an AI agent with a configured Ticket handoff.
Explore website AI

A practical channel guide

The right channel for the right workflow.

This matrix distinguishes product capabilities from account setup and activation requirements. It is not a claim that every connection is enabled in every workspace.

Echo integration capabilities and requirements
ConnectionPrimary workflowWhat to check
Email mailing listsRecipient lists, reviewed and scheduled email publications, and per-recipient delivery results.Supported Microsoft 365, Gmail or IMAP / SMTP sender. Individual delivery or BCC batches; optional unsubscribe requires individual mode and setup.
SMS mailing listsPhone-number lists, short-message previews, scheduled publishing and recipient delivery outcomes.Authorized 019SMS sender. The 70-unit total includes any opt-out URL; no MMS, attachments or multipart messages.
Email: Microsoft 365Customer email conversations and Ticket replies.Delegated, shared and application mailbox permissions differ. Shared delegated mailboxes use polling.
Email: GmailCustomer email intake and replies.Connect with OAuth and the required account permissions.
Email: IMAP / SMTPMailbox polling and outgoing replies.TLS is required. Password or app-password authentication; polling cadence is configurable.
Telegram BotSupported publishing and direct customer conversations.Configure the bot, destination and support capture. Group/history import is not implied.
Telegram UserSupported account-backed communication.Runtime enablement, application credentials and current environment acceptance are required.
WhatsApp Cloud APICustomer conversations and supported outbound delivery.Business account setup, channel activation and provider messaging rules apply.
Facebook PagePublishing to a connected Page.Page publishing permissions. This listing does not promise Messenger support.
Instagram professional accountPublishing supported content.Professional-account setup and provider format restrictions. Support DMs are not included in this listing.
SMS / MMS catalog: 019SMS connectionConfigured SMS delivery and inbound support intake.Requires the enabled 019SMS runtime, provider setup and routing. The broader SMS / MMS catalog does not establish MMS support for this connection.
Website AI AgentWebsite questions and configured Ticket handoff.Connect the deployed agent, allowed website origin and Ticket routing. Live staff takeover requires its own enabled connection.

Connect and activate the specific workflow you intend to use. A provider appearing in a catalog does not mean every publishing format, conversation mode or AI action is available.

Bring the workflow with you

A connection is the starting point.

After account authorization, configure the destination, agent and rules for the work you want Echo to do.

Publishing destinations

Select the correct account and destination. Check supported content formats, configure review and scheduling, and verify an actual publication result before expanding a queue.

Explore AI Publishing

Customer conversation channels

Enable the intended intake path and department routing. Test a new request, a follow-up reply and a failure case. Keep the customer’s public conversation separate from private team notes.

Explore AI Customer Support

A little more clarity

Good questions.
Clear answers.

What to know before you put Echo to work.

Are all integrations active automatically?

No. Connections need authorization and configuration. Some also require deployment settings and environment acceptance. Check the actual workspace before promising a customer an active channel.

Can we import recipients for email and SMS lists?

Yes. Add recipients manually, paste addresses or numbers, or preview a CSV import. Review duplicates and invalid entries before importing. Each publishing channel owns its list, with up to 1,000 recipients and preserved opt-outs.

Can AI help prepare messages for our mailing lists?

Use AI assistance within the publishing workflow to draft and refine content, then apply your configured approvals and scheduling. Preview the email subject and format or the exact SMS text before sending. Explore email mailing lists and SMS lists.

Does list publishing include unsubscribe controls?

Unsubscribe is optional and needs configuration. Email unsubscribe uses individual delivery, not BCC. SMS opt-out links must fit within the message-length limit. An import does not automatically reactivate unsubscribed recipients.

Can we use Facebook and Instagram for support DMs?

This website lists Facebook Pages and Instagram professional accounts as publishing integrations. It does not advertise support inbox or direct-message capabilities for them.

Will email synchronization change our mailbox read state?

Email synchronization is designed to preserve upstream read state, folders and labels. Threading and Ticket routing happen inside Echo’s workflow.

PUT IT INTO PRACTICE

Explore the documentation.

Follow the setup, understand the controls and find the next step.

Connect external accounts to EleonEcho

Understand external account authorization, provider readiness, reconnection and the connection settings used by EleonEcho publishing and support channels.

Your next chapter, with AI

More ideas out.
More conversations moving.

Bring your publishing, marketing and support work into Echo.

Start a free trial See Echo in action Explore the trial details before you begin.

Echo website agent

AI assistant

Answers are generated by AI. Please avoid sharing sensitive information.

Explore a guided example ↗