Rate limits

Medallia Conversations supports real-time communication without rate limits. The adapter must handle requests promptly, processing at least 100 messages per second, with performance evaluated per implementation.

Timeouts

The Medallia Conversations APIs operate asynchronously to handle numerous requests. Medallia Conversations Medallia Conversations requires an adapter response to HTTP requests within 10 seconds. The adapter should respond before message delivery and report any delivery issues via a separate status request.

Retries and error handling

Medallia Conversations retries communication with the channel adapter up to 5 times, with a 10-second delay between attempts. The adapter must respond with the correct status code before timeout to prevent duplicate message delivery.

The adapter should have a similar retry mechanism in case the Medallia Conversations APIs are not reachable at that moment.

Managing Conversations

To start a conversation, the channel adapter must specify the keyword or identifier, available in the Medallia Conversations admin interface.

The adapter can programmatically retrieve conversations using the Medallia Conversations list API, enabling dynamic integration with third-party UIs. This allows admins to select conversations without accessing the admin interface or updating adapter code, useful for mapping skills or intents in chat solutions.