Talk to Jon where you already work.
Jon connects to the channels you're already on — WhatsApp, iMessage, Slack, Discord, and the web. Same AI, same context, different screen.
Short replies. No formatting. No scrolling. Jon knows WhatsApp is for quick exchanges — he matches the medium. Send a business question on the way to work. Get an answer before you sit down.
iMessage is the most informal channel — Jon knows that. Lowercase when it fits. Short bursts. The same Jon, looser register. Available for Apple users in the US. iPhone or Mac, same conversation.
Jon lives in your Slack as a bot — DM him directly, or @-mention him in a channel. He knows he's in a workplace context and responds accordingly. Thread-aware. Markdown-friendly. Safe to share with your team.
Invite Jon to your Discord server — he'll respond to @-mentions in channels or DMs. Discord-native formatting, community tone. Good for creator communities, dev teams, or anyone whose business runs on Discord.
The web dashboard has everything — chat, DIFM tools, compliance tools, research, your account settings, and your agent's activity feed (Apex). Best for deep work. Other channels are great for quick exchanges.
Apex: Jon has his own email address.
Apex users get a dedicated agent with a real email inbox — {agent_name}@arkoda.app. Jon receives emails, drafts replies, and works through your inbox so you don't have to. Available on Apex ($1,497/mo).
One context, every channel.
Every conversation with Jon — no matter which channel — feeds into the same memory system. Ask Jon something on WhatsApp on Monday. Follow up on Slack on Wednesday. He knows the history. Your business context moves with you. Jon doesn't forget when you switch screens.
FAQ
Yes — each channel requires a one-time connection. It takes about 2 minutes per channel. After that, Jon is available on all connected channels automatically.
Yes. Jon's memory is account-wide, not channel-specific. A context established on WhatsApp is available when you talk on Slack.
Your Jon is tied to your account. If your team needs separate instances, each person would need their own Arkoda account. Apex users' agents can be shared with a team — contact support for setup.
Conversations flow through Arkoda's infrastructure, not stored by the channel platform (WhatsApp/Slack/etc.). Your data lives in your Arkoda account. It does not train any external AI model.