🚪 The door of intent
O channel is how the world talks to Jarvis and how it responds. It’s not a technical detail: it’s the intent entry point. When someone opens a conversation, they’re not just sending text—they’re bringing a need (to buy, solve something, schedule, complain). Without a channel, the smartest system in the world is an island: no one gets in, no one gets help.
🚪 The door before the room
Imagine an excellent store with no door: great products, but no one comes in. The channel is the door. It's the first contact with the customer's intent—and the quality of that door determines whether the intent even reaches the system.
💡 Practical tip
Before choosing technology, answer this: where does my customer already talk to me today? Start the channel there. The best door is the one the customer already knows how to open.
💬 WhatsApp, Telegram, and chat
The channels conversational are the most used in companies: WhatsApp, Telegram, and the chat on the website itself. The advantage is simple and powerful — the customer is already there. Meeting the customer on their channel brings friction close to zero: they don’t need to download anything, create an account, or learn a new tool.
✓ A good use of the conversational channel
- ✓Provide support where the customer already chats
- ✓Respond quickly, in natural language
- ✓Remember the context of the previous conversation
- ✓Escalate to a human when needed
✗ Common mistakes
- ✗Forcing a channel the customer doesn't use
- ✗Robotic and out-of-context responses
- ✗Forgetting everything with each new message
- ✗Trapping the customer with no way to reach a human
💡 Practical tip
In Brazil, WhatsApp is usually the highest-traffic entry point. But “more common” doesn't mean “always best”: a B2B customer may prefer email. The channel should follow the customer, not the trend.
📧 Email, Dashboard, Voice, and API
Chat is just one of the gateways. Jarvis also receives and responds through email, internal dashboard, app, voice, form, or API. Each channel serves a context different—and choosing the right channel is part of designing the solution, not a last-minute decision.
Formal matters, attachments, records with history.
Internal dashboard
The team operating the system within the company.
App / form
Structured input, defined fields, clean data.
Voice
Phone call or audio: hands are busy, service by phone.
API
Another system talking to Jarvis, with no human in the middle.
Each one, its own context
The right channel depends on who uses it and what they need.
🧩 Multichannel, one intelligence
The secret: multiple channels up front, a single brain behind it. WhatsApp, email, and API can be different doors to the same Jarvis—the intent decides, not the channel. You don’t build five systems; you build one with five doors.
🎯 Capture the intent
When a customer sends a message, they’re not just writing text: they’re bringing an intent. “How much does it cost?” signals intent to buy. “It didn’t arrive” is a problem to solve. “Do you have an appointment tomorrow?” is a booking. The system needs to capture what the customer truly wants — not just the words they typed.
From message to intent
The words change; what the system needs to read is the intent behind them.
💡 Practical tip
List the 5 to 8 most common intentions of your customers (buy, resolve an issue, schedule, complain, ask...). This small map of intentions is the basis for the routing you’ll see in the next topic.
🧭 Interpret and route
Once the intent is captured, the system interprets the context and triggers the the right service: sales, support, scheduling, finance. That’s the intelligence of routing — the bridge connecting the channel to internal services. It’s the heart of the workflow: without it, every message would go to the same place and nothing would be handled well.
A message’s journey
Reaches the channel
"How much does the plan cost?" comes in through WhatsApp.
Captures the intent
The system reads: this person wants to buy.
Interprets the context
New customer? Which plan makes sense? Have they spoken with us before?
Trigger the right service
Route it to the sales team, not support.
Responds
It comes back through the same WhatsApp with the right proposal.
💡 Practical tip
Routing fails when it confuses similar intents ("cancel" could mean a question or churn). When it gets it wrong, make a note—the intent map from the previous topic is what you refine to get it right more often.
🔁 The Communication Cycle
The channel is two-way: the intent goes in through it, and Jarvis’s response comes out through it, completing the communication cycle. Thinking about input and output together avoids a common mistake—systems that understand the customer very well, but respond bad: at the wrong time, in the wrong tone, or on the wrong channel.
✓ A well-closed loop
- ✓Responds in the same channel where it came in
- ✓Tone and format suited to the channel
- ✓Confirms that the customer was helped
✗ Broken cycle
- ✗Understands well, but responds poorly or too late
- ✗Reply in a channel the customer can't see
- ✗Leaves the conversation without a resolution
Self-check (optional): why do we say that “the channel is the entry point for intent”?
🚪 Module summary
End of Day 1:
You laid the foundation—mindset, infrastructure, deployment, and channels. On Day 2, you'll start building Jarvis from the inside: its soul, services, agents, and security.