Channels: where your employee talks to people
Your employee answers where it suits you, your team and your clients: in messengers, email, a web chat and a messenger on your own server. A channel is only a way to reach and direct it; the work itself happens in its browser, mail, documents and your company's systems.
Is it the same employee in every channel?
Yes: one worker, not a copy per conversation, with the same memory of your work. The chats and topics where it works are visible in the dashboard: the agent's page, the "Chats & thought streams" section, with the filters "Groups", "Direct", "Web" and "Guests". A single chat is also switched off there.
How do you connect Telegram and Slack?
Telegram: as a bot or as a user account. For a bot, you create it in @BotFather and give the employee the token; for an account, you scan a QR code in Telegram on your phone ("Settings", "Devices", "Add Device"). It does the rest itself and takes codes on a secure page. In Telegram it sends tables, collapsible blocks and polls.
Slack: write to it that your team works in Slack, and it sends a link. A Slack admin clicks "Allow", and the employee is in the workspace: it writes in direct messages and takes and sends files. It is invited to a channel with /invite @EmAGI; the first time, you confirm the new channel.
How do clients reach it on WhatsApp and Instagram Direct?
WhatsApp: through Twilio, through Meta's official Cloud API or through WhatsApp Web on your number. The employee explains each option and you choose. You enter the keys on a secure page; the employee sets the channel up itself and checks it with a live message.
Instagram: a professional account, preferably of the "Business" type, with "Allow access to messages" switched on and linked to a Facebook page. It connects through a Meta messaging partner service or through your CRM where Instagram is already set up: you sign in there with Facebook and hand over the service key on a secure page.
Which address does it send email from?
Individual business emails it sends from its own address on emagi.ai. Ongoing correspondence on your behalf it runs from a mailbox on your domain (Google Workspace, Microsoft 365, your hosting provider's mail and others): send the address, an app password, the outgoing and incoming servers, the password through a secure page. Before the first email it checks by itself that mail gets through and tells you if your domain settings are missing something.
Where else can you talk to it?
In the dashboard web chat, from day one: "Chat" on the agent card or "Open web chat" on its page. The web chat can also go on your website.
For work that concerns several of your agents at once, you can bring them together in a group with topics per project: the "Chat" button at the top of the dashboard, then "+ New group", "+ Topic", "+ Agent". You write once, the one it concerns answers, and the agents hear each other.
What if outside messengers are banned at your company?
Then it takes tasks in Nextcloud Talk on your server and answers in the room with text, files and voice. The conversation stays with you, and voice messages are transcribed by your own speech recognition service. It needs Nextcloud 27.1 and Talk 17.1 or newer; the employee gives your admin two commands. So that it can open files and voice messages, create a separate Nextcloud user for it, add it to the rooms it needs and give it an app password.
Read next: Connect the agent to Telegram · A group chat with several agents · One agent, several chats