🚀 InituBot is in Beta — try the Pro experience for 14 days. Start trial

Channels

Support channels for a WhatsApp-first operation.

Start with WhatsApp and evolve into new channels as your operation, integrations, and support strategy mature.

Channel architecture

Current today, ready to evolve

WhatsApp-first

4

available today

8

roadmap or by request

AI

governed by channel

WhatsApp as the initial channel
InituBot automates and monitors
Handoff or expansion by feasibility
Available today

Start with the channel where volume already exists.

The current focus is WhatsApp, with handoff to contact centers and API integrations.

WhatsApp-first

WhatsApp is the main relationship channel for many companies. That is why InituBot starts where volume, urgency, and repetition already exist.

WhatsApp

Main channel for automated support with governed AI.

3CX handoff

Hand off conversations to human support with context.

Twilio Flex handoff

Integrate structured contact center operations.

Webhooks / APIs

Use Custom Tools and configurable integrations according to plan and scope.

Roadmap or by request

New channels with technical and commercial validation.

Expansion should follow real demand, technical feasibility, and contracted scope.

RCSSMSTelegramWebchatInstagramReclame AquiConsumidor.govEmail / internal inbox

These channels should not be treated as available in production until technical and commercial validation.

Why WhatsApp-first

The main channel deserves the best operation first.

This is not a promise of complete omnichannel. It is a clear strategy: solve WhatsApp well and evolve responsibly.

WhatsApp concentrates volume, urgency, and repetitive conversations for many operations. Starting there allows the team to validate the knowledge base, handoff, quality, and metrics before expanding into new channels.

How expansion works

Every new channel needs a use case and feasibility.

Expansion happens in stages, without treating roadmap as an available feature.

01

Validate demand

Understand channel volume, urgency, and impact.

02

Define use case

Separate what will be automated from what goes to humans.

03

Confirm feasibility

Evaluate API, permissions, costs, and technical limits.

04

Configure routing

Define handoff, rules, and context by channel.

05

Monitor quality

Track readiness, handoff, gaps, and issues by channel.

Start with WhatsApp. Evolve when it makes sense.

Try the Pro experience for 14 days and validate the operation before expanding channels.

Explore more

Go deeper without losing the path.

Explore InituBot’s strategic pages or move straight to the free trial.