AIRONIK · Learn more

Connect your bot. Stay close to your customer.

Your bot keeps working on its familiar platform. AIRONIK brings together its conversations, incoming events and your team's participation through one integration.

Prices and connection terms
AIRONIK — Operator takeover: a manager replies to the customer instead of the bot
Operator takeover: a manager replies to the customer instead of the bot

Connecting an existing bot

Connection requires AIRONIK protocol support on your platform or help from its developer.

  1. Add an “External application”

    In AIRONIK, create an agent of this type for a bot already running on an external platform.

  2. Save the key and code

    Obtain the API key and confirmation code. They are issued when you create the connection; save them to configure the integration.

  3. Configure your platform

    Enter the key and code in your bot platform's AIRONIK integration. It must send conversations and events using the AIRONIK protocol.

  4. Choose settings

    Set the synchronization interval. If needed, enable the AIRONIK knowledge base and INS with the corresponding subscription.

The external bot's AI model and main settings stay on its platform. Its AIRONIK features depend on the integration and access permissions.

From observation to participation

View a conversation

Open a customer's conversation with the bot and read the context.

Take over the conversation

Enable operator takeover. The bot stays silent while an employee with the right permissions replies in the same conversation.

Hand the conversation back to the bot

End the operator's participation and return the conversation to the bot so it can continue.

Connect what your company needs

Synchronization

Set the external bot's synchronization interval. How current incoming conversations are also depends on how your platform sends data.

AIRONIK knowledge base (RAG)

Through the integration protocol, the external platform can search the bot's data stored in AIRONIK. This feature is enabled separately.

INS

Enable requests and their INS numbers. The bot's platform sends requests and their status through the integration.

Incoming webhooks

Create a source for your site or store, configure event delivery using its protocol and receive entries in “Channels”. Channels are for incoming events.

What working in the app looks like

This is AIRONIK: bots' customer conversations, operator participation, incoming events and requests.

Who takes part in connecting

Company owner

Creates the agent, chooses the subscription and assigns employee permissions.

Platform developer

Configures the AIRONIK protocol, event delivery and handling of operator participation.

Support employee

Views accessible conversations and replies to customers according to their permissions.

Frequently asked questions

Can I change the synchronization interval?

Yes, it is one of the external bot's settings. Data reception also depends on how the integration works on your platform.

Can I manage an external bot's rules in AIRONIK?

The external bot's main rules and settings are configured on its platform. Actions available in AIRONIK depend on the agent's type and capabilities.

How do channels differ from chats?

Chats contain conversations an operator can join with the right permissions. Channels collect incoming events: you can view, export and mark them as read, but cannot post to a channel.

Do I have to pay for the knowledge base and INS together?

No, these features are chosen separately for each bot. You can enable one, both or keep the basic subscription.

Start with one bot

Connect an existing bot and see how its customer conversations appear in AIRONIK. Then add the other agents and set up team access.