01
Reception, support and sales
One agent greets and directs, another resolves support questions and another guides the sale up to the payment link. You define what each one does and with which resources.
BotDynamics brings your conversation channels together in Inbox Central. Your AI agents reply with your business knowledge, and your team steps in when it matters.
These are not separate products: each piece rests on the one before it. Channels feed the inbox, agents work on those conversations, and what happens there is what you can build on and measure.
WhatsApp, Messenger, Instagram, Telegram, webchat, voice, SMS and email land in one inbox, where your team works alongside your automations.
A router directs, a knowledge agent answers and a flow agent runs the process. They hand off to a person when it matters.
Your configured sources feed the agents' answers. When the evidence falls short, the agent says so or hands off.
You describe the process and Builder proposes the flow, validated against the resources you already have. Applying, saving and publishing are your actions.
Internal chat with groups, images and documents, so your team coordinates without leaving the platform.
Ask your operation in plain language: indicators, trends and conversations that need attention.
Messaging campaigns over your contact lists, with the status of every send on record.
Builder and Kortex work on what already lives in the platform: Builder builds with configured resources and does not create integrations on its own, and Kortex queries the operation hosted in BotDynamics. That is why the pieces come in this order.
Stop jumping between tabs. Messaging, voice and social media converge in a single interface for your whole team.
Can I change the billing details?
Do you ship to Monterrey?
I'd like to book an appointment
September invoice
Example with synthetic data. It does not reflect any customer's operation.
Every conversation lands in the same inbox, whichever channel it comes from.
Receive calls on the same platform, with the conversation's context.
WhatsApp, Messenger, Instagram, Telegram, webchat, voice, SMS and email.
Your team handles everything from the same place, with each conversation's history.
Your agents resolve the repetitive work and hand your team what needs a person.
Kortex answers about this operation: indicators, trends and reports.
A router identifies the need and directs the conversation. A knowledge agent answers from your configured sources. A flow agent guides questions, forms and handoffs according to the logic you define.
One agent greets and directs, another resolves support questions and another guides the sale up to the payment link. You define what each one does and with which resources.
Voice calls inside WhatsApp, in the customer's same conversation.
Books appointments, collects data with forms and sends the payment link, following the flow you define and the resources you have configured.
When the customer asks or the evidence falls short, the conversation moves to your team with the full history.
Every agent version records who published it and when, and nothing ships without a human review.
Conversations are grouped by what prompted them: what your customer asks for and how often.
You organize your information sources so your agents find relevant content and ask for help when the evidence falls short.
You upload files and web addresses. Every update creates a knowledge version, so you know what the agent answered with and when it changed.
Retrieval combines semantic and text search, then ranks the results before answering. This is not keyword matching.
Every answer is validated against the retrieved sources. If the citation does not hold, the answer is not sent.
These are the only three possible outcomes. When the evidence falls short, the agent asks or passes the conversation to a person instead of improvising.
If the customer asks something outside the process under way, the agent can answer and resume where it left off. Enabled by configuration; not on by default.
A version is not published if its configuration was not evaluated or if sources remain unprocessed under a different profile.
Uploading documents is not training or fine-tuning a model: the agent consults your sources at answer time. The scope of the answers depends on the sources you have configured.
Example with synthetic data. It does not reflect any customer's operation.
You turn your instructions into flow proposals, review their technical validation and test every path before publishing it.
Verified resources: checkOrderStatus operation ✓ · general_support queue ✓
Example with synthetic data. The proposal is not applied or published on its own.
You explain the process in plain language inside the flow designer and Builder proposes the matching flow.
Every proposal arrives with what changes, the resources it uses and the warnings it found. You review it before anything is applied.
It builds with your configured API operations, queues, forms and payments. If a resource is missing it says so and stops: it will not invent a queue that does not exist.
Faced with an ambiguous instruction it asks for clarification instead of inventing dates, times or business rules.
You test the happy, invalid and error paths in the simulator, with API and payment doubles.
Applying, saving and publishing are human actions. Builder never publishes on its own, and every version records who published it and when.
Builder does not manage the runtime agent's identity or model, does not create integrations or resources, and does not query your customers' data. Usage is subject to per-account configurable limits.
Internal chat for agents and supervisors to coordinate while they work, without leaving the platform.
With members and roles defined by your account.
Between agents and supervisors, one to one or in a group.
Images and documents inside the chat.
Browser alerts, with adjustable sound and volume.
Kortex lives inside your admin panel. Ask in plain English and it answers with your operation's data: indicators, channels, team and conversations that need attention.
"How many conversations did we close yesterday?" or "Which channel had the most?" — with a breakdown by channel and status.
Compare how your indicators evolve between periods and surface what needs attention.
Compare your agents' performance, check your bots' health and generate the period's report from the same conversation.
Kortex queries the whole operation hosted in BotDynamics: WhatsApp, social and voice in one reading.
Top of the day
WhatsApp › Sales — 560 (47%)
Example with synthetic data. It does not reflect any customer's operation.
Exclusive Black Friday!
Up to 50% off the entire catalog. Today only.
You define the message, choose the channel and the recipient list, and follow the campaign's status from start to finish.
You build the campaign on a contact list, with filters over your base.
You define the message the campaign goes out with.
You set the spacing between messages so the channel is not flooded.
Sent, delivered, read and failed, campaign by campaign, with total duration.
Sends go out through the configured channel, subject to its template and consent policies.
Four answers before the demo, so you know exactly what you are looking at.
Kortex answers questions about your operation: indicators, channels, conversations that need attention, team performance and reports. Kortex Builder does not query data: it lives inside the flow designer and turns your instructions into flow proposals that you review and publish. One reads the operation, the other builds the process.
At three points. The agent hands the conversation to someone on your team when the evidence falls short or when the customer asks, and that person picks it up in Inbox Central. In Kortex Builder, applying, saving and publishing a flow are always human actions. And in TeamChat your team coordinates while it works.
That the resource already exists and is configured: the API operation, the queue, the form or the payment method. Kortex Builder builds on those resources, but it does not create or connect them on its own. If one is missing, it says so and stops rather than inventing it.
WhatsApp, Facebook Messenger, Instagram, Telegram, webchat, voice, SMS and email. Each channel is configured separately and they do not all offer the same features, so in the demo we review which ones apply to your operation.
Book a 30-minute demo and we'll show you how your channels, your agents and your business knowledge are configured.