Channels
The same assistant, behind every place you’d expect to reach it.
A channel in Jootle is any way you can send a message to your AI and get a response. Three are wired up on a fresh instance: the web app, Telegram, and email. You can add more (Slack, SMS, WhatsApp) when you need them.
What matters is that they all hit the same brain. You can ask a question on web chat, walk to your car, get a follow-up on Telegram, and reply to it from your car’s voice prompt. There’s no “but did you mean the Telegram version of me?”. One assistant. One memory.
The web app is the default. Open https://<your-instance>.on.jootle.com/ and the chat is the first thing you see.
What the web app is best for:
- Working with structure. Projects, lists, ideas, artifacts. The web app shows you the full workspace, not just chat.
- Producing artifacts. Drafts you’ll iterate on benefit from being visible while you work.
- Setting up things that need many clicks. Connecting integrations, configuring goals, browsing the toolkit library.
- Reviewing work your AI did while you were away. The activity view, the recent artifacts list, the goal run history.
What the web app is less good for:
- Quick capture on the go. It’s a phone tab; that’s not the natural place to dump a thought.
- Voice. You can speak into the input on most browsers, but Telegram does this more naturally.
The web app is reachable from anywhere with a browser. There’s no separate mobile app at the moment; the web app is responsive and works on phones, but it’s not as fast for quick capture as a dedicated chat app would be.
Telegram
Section titled “Telegram”Telegram is the channel most customers end up living in once they have it set up.
What it’s best for:
- Quick capture. Voice notes, dictated thoughts, single-sentence reminders. The kind of thing you’d otherwise lose.
- On-the-go conversations. Walking the dog, driving, between meetings. Your AI is in your pocket.
- Asynchronous work. Send a request, get a response when it’s done. You don’t need to keep the app open.
- Forwarding. Forward a message, an image, or a link, and your AI can act on it.
How to set it up
Section titled “How to set it up”You set up a Telegram bot once. It takes a few minutes:
- Open Telegram. Search for
@BotFather(this is Telegram’s official bot for managing bots). - Send
/newbot. Pick a display name (this is what shows up in chats; “Jarvis” is fine). Pick a username (must end inbot;your_jarvis_botworks). - BotFather hands you a long token (looks like
123456:ABC-DEF…). Copy it. - In your Jootle instance, go to Settings → Channels → Telegram. Paste the token.
- Save. Within a few seconds your Jootle instance is connected to your bot.
- Find your bot on Telegram (by the username you picked) and send
/start. - Your AI replies. You’re live.
From now on, anything you send to that Telegram chat reaches your AI, and anything your AI sends to you arrives there.
Voice notes
Section titled “Voice notes”Telegram’s hold-to-record voice messages work. Your AI transcribes them, treats them as a normal message, and replies in text (or in another voice note if you ask it to).
This is the fastest input method by a wide margin. Dictated voice notes are how most people capture ideas, set reminders, and ask quick questions when they’re away from a keyboard.
One bot per Jootle instance
Section titled “One bot per Jootle instance”A Telegram bot belongs to one Jootle instance. If you have multiple instances (rare), you’d make a separate bot for each. Within an instance, your bot can have multiple authorized chats (you, your spouse, a colleague), but each one ties back to a Jootle user account.
Email turns your AI into a participant in the threads you already have.
What it’s best for:
- CC’ing your AI on a thread. Your AI reads the thread, can summarize it, can draft replies, can wait for specific responses.
- Inbound capture from people who don’t use Jootle. A client emails you. You forward the thread. Your AI files it under the right project and helps you respond.
- Sending things on your behalf. Once you’ve connected a sending account, your AI can compose and send emails as you.
How to set it up
Section titled “How to set it up”Email is part of Connect Google Workspace (if your email is on Google) or the equivalent flow for other email providers. The full walkthrough is here.
Once email is connected:
- You’ll have an inbound address (looks like
<your-instance>@in.jootle.com) where you can forward anything to your AI. - You can CC your AI on a thread by adding that address to the recipients.
- Your AI can send mail through your connected account, appearing as you.
Forwarding patterns that work well
Section titled “Forwarding patterns that work well”- “Forwarding you the contractor’s quote, can you compare it to the other two?”
- “FYI — this client is asking for a discount, want to draft three responses ranging from yes to no?”
- “This is the spec doc, file it under the redesign project and summarize the open questions.”
The forwarded content lands in your AI’s context, and the response either comes back as an email reply or shows up in your web chat, depending on the request.
Choosing a channel
Section titled “Choosing a channel”You’ll develop your own habits. A rough map for new users:
| Situation | Best channel |
|---|---|
| Sitting at your desk doing focused work | Web |
| On the go, hands free, voice in | Telegram |
| On the go, typing | Telegram |
| Working a thread with someone else | |
| Sharing a document or image | Telegram (mobile) or Email (desktop) |
| Reviewing what your AI did overnight | Web (activity + artifacts) |
| Setting up a goal or integration | Web |
If you only use one channel, web is the safe default. If you only add one more, make it Telegram.
What channels share
Section titled “What channels share”Worth saying once explicitly: there is one knowledge graph, one set of projects, and one assistant. The channel only affects how the message arrives and how the reply gets delivered. The decisions, memory, and ongoing work are the same everywhere.
You can also tell your AI to respond on a different channel than the one you asked from:
- “Email me the weekly review when it’s ready.”
- “If anything urgent comes in tonight, send it to Telegram.”
- “Drop the artifact link in our Slack.”
This is just routing for the response, and it works as long as that channel is connected.
Adding more channels
Section titled “Adding more channels”Three channels covered today, more coming:
- Slack. Most teams want this. Connector exists; setup parallels Telegram (you create a Slack app, paste the token).
- SMS. Available for customers whose Telegram won’t work (international SMS still flaky depending on provider).
- WhatsApp. Planned, not shipped at time of writing.
Add channels from Settings → Channels. Each one has a short setup flow that matches the patterns above.
Disconnecting a channel
Section titled “Disconnecting a channel”Any channel can be disconnected from Settings → Channels. Your AI stops sending to and receiving from that channel immediately. Your data stays. You can reconnect later without losing context.
If a Telegram bot stops working for an unrelated reason (you deleted the bot from BotFather, the token rotated), re-create it and paste the new token. The conversation history within Jootle stays.