Conversations with X
The Conversations X concept supports the following functionalities:
- Messaging – Managing both new and ongoing conversations
- Conversations API
- Notes
- Tags
- Queues
- Drafts
- Conversation merging
- Conversations metadata
How to use Conversations with X
You can integrate the X concept into Conversations using:
-
- Use an API key linked to a defined application and entity.
- This setup automatically enforces access validation for specific conversation entities.
-
Embeddable customer engagement
- Integrate Conversations directly into your platform using the provided embeddable solution.
To begin using the X concept, you need to create an API key assigned to an application and/or entity.
When using this API key for embedding or any API calls within Conversations API, the system will automatically tag the resources (such as queues, notes, tags, etc.) created with that API key with the corresponding application and entity.
When retrieving information, the API key with the application/entity will act as a filter, ensuring that only resources labeled with that specific application and entity are returned.
Each resource mentioned above can be linked to a specific application and entity. If a resource is associated only with an application, it is identified solely by its applicationId.
Existing CPaaS customers who are already labeling traffic with the application and entity, without using X in Conversations, will not be impacted.
In Conversations, only one application and entity can be assigned to a sender. While the same application and entity can be assigned to multiple senders, assigning more than one application and entity to a single sender will cause issues with message processing. Therefore, with the X concept, a maximum of one application and entity is supported per sender.
If you choose to use X, please note that it is not compatible with access through the web interface. It is recommended not to combine the use of Customer engagement with X and the web interface.