Create a ChatRex API key and connect it to imot.io. Completed conversations are automatically transferred to the analytics system, where the team evaluates the quality and subject matter of calls
The integration transfers the available ChatRex conversation to imot.io via a configured API connection
To connect, a separate key is created, which is entered into imot.io
Conversations come to imot.io without manually exporting the command
Transferred conversations become material for service evaluation
What happens to each request, why it matters to the business, and where the team saves time
To connect, a separate key is created, which is entered into imot.io
Conversations come to imot.io without manually exporting the command
Transferred conversations become material for service evaluation
The team can study the topics of client requests using imot.io
After connecting, the test dialog should appear in imot.io
The API key is not published, is not added to prompts and is stored as a secret
Practical scenarios with a clear handoff and an observable result for the team.
Conversations are available in imot.io without manual upload
The command analyzes the array of transmitted requests
Test and working conversations fall into a single analytics loop
Let's create a separate key, connect analytics and check the appearance of a test conversation.
We are releasing a separate API key in ChatRex
We add the key only to the protected service settings
We conduct a test conversation and find it in imot.io
