Jawcha
Sign inRequest a demo

JAWCHA / Product

A clear platform for your agents

Your AI agents, your channels, your tools — in one clear space, with you in control whenever you need it.

Three separate libraries

Your models, your channels and your tool servers (MCP) are three distinct, reusable spaces. A resource created once shows up in each agent’s context panel, with no mixing of categories.

An unambiguous model

Each agent shows the model connection actually assigned, the effective model and the key mode (your own key or the platform configuration). The provider test is explicit and capped.

Built-in help

A public help centre in English, French and Spanish is available from the header. Contextual help opens the page for the screen you are on, without losing your input.

From a message to an authorised action

Connect a channel, assign an agent and decide what each tool is allowed to do. Sensitive actions can pause for confirmation; an operator can take over with the conversation context.

Start small, then extend

Begin with a specific task and a test conversation. Check the answer, the tool permissions and the handover path before extending the agent’s scope.

Connections

A message comes in. An authorised action goes out.

The diagram below describes the real path of a conversation: the channels that carry it, the agent that handles it, the tools it may use, and the point where your team takes over.

Channels

  • WhatsAppCloud API · Meta
  • Telegrambot in your workspace
  • Web widgetembedded in your site

Agent

Jawcha agentone role, one tone, limits
  • Conversation context
  • Rules you write
  • Confirmation of sensitive actions
Human takeover at any time

Tools

Your MCP serversdeclared by your team
  • Check a status
  • Create a ticket
  • Update a record

Each tool is authorised one by one: ALLOW, CONFIRM or DENY.

How to read this diagram The solid line carries the customer’s message to the agent; the dotted line brings the reply back once the action is complete. A sensitive action stops for confirmation before it runs, and your team can take over the conversation at any moment.
Diagram of the real path — this is not a product screenshot. Only logos of channels that are actually connected are shown; no third-party service logo is presented without a proven integration.
Principle diagram: each connection depends on its own configuration and permissions.

Make it work for your team.

Start with one conversation, one connected channel and a clear set of rules.

Request a demoSign in