We’ve integrated the Genesys Cloud Web Messaging Guest API into our custom agent desktop. Everything works for sending actual messages, but the typing indicators and read receipts seem to be ghosted. When an agent types, the client fires the event, but the recipient never sees the ‘typing’ status.
Here is the snippet we use to emit the typing event:
guestApi.sendTypingIndicator({
conversationId: 'abc-123',
typing: true
});
The HTTP request to /api/v2/conversations/messaging/typing returns a 204 No Content. No errors in the console. We checked the network tab and the payload looks correct:
{
"conversationId": "abc-123",
"typing": true
}
We’re on the latest SDK version. Is there a specific permission or configuration flag we’re missing on the org side? Or does the Guest API require a different endpoint for these soft events? We tried polling the conversation state but it doesn’t reflect the typing status either. Feels like we’re shouting into the void.