Open Messaging Typing Indicators not working

We are trying to use the new typing indicators with open messaging. It has been enabled in the platform config assigned to the platform integration, and we DO see an outbound webhook message going from Genesys to the open messaging client.

The Inbound event is failing when using the API: -

POST /api/v2/conversations/messages/{integrationId}/inbound/open/event

{
"channel": {
"from": {
"nickname": "Chat Client",
"id": "name@mail.com",
"idType": "Email",
"firstName": "Dev",
"lastName": "Lead",
"email": "name@mail.com"
},
"time": "2023-09-28T10:09:40.022Z"
},
"events": [
{
"eventType": "Typing",
"typing": {
"type": "On"
}
}
]
}

We get a "202 - Accepted" response, but we don't see the indicator in the GC Agent UI, here's the response from the API call:

{
"id": "xxx",
"channel": {
"id": "[integrationId]",
"platform": "Open",
"type": "Private",
"to": {
"id": "[integrationId]"
},
"from": {
"nickname": "Chat Client",
"id": "name@mail.com",
"idType": "Email",
"firstName": "Dev",
"lastName": "Lead",
"email": "name@mail.com"
},
"time": "2023-09-28T10:09:40.022Z"
},
"type": "Event",
"events": [
{
"eventType": "Typing",
"typing": {
"type": "On"
}
}
]
}

Has anyone had a similar experience? Are we missing something, the OAUTH client has the correct permissions and the agent has relevant messaging permissions.

Cheers,
Lee

Hi Lee,
So sorry to hear you are having issues with open typing indicators. would you be able to provide the correlation Id That is returned in the headers when you are given the 202 response ? and a date when the request was made and I will be able to look into that issue for you.
Best Regard's,
Colum

Hi Colum,
Thanks for responding on this; it has taken me a while to get the information as the Development team had a festive holiday yesterday. I have an example now that I can share with you though:

ININ-Correlation-Id: 9edc164e-bf6f-48db-8a9e-9a2b21b215b2

Thanks,
Lee

Hi Lee,
Had a quick look and a few points of interest:

  1. Typing indicators only get displayed on active conversations so ensure you have an agent connected to the conversation.
  2. Typing indicators are only a UI additive so you are unable to start a conversation using this event try starting a conversation with a single text message.

I hope these pointers help however if your issue persists. Please reach out to the CARE team and we can look into this issue further.

Best Regard's,
Colum

Thanks for looking into this Colum, it would appear it wasn't tested with a live interaction (don't know why the Dev Team did that) so they weren't trying to start a new conversation; I will see if I can get an example against a live interaction. Sorry for that.

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.