Status:
Investigating
Submitted on
11-17-2022
03:50 AM
Submitted by
Bipin_Patel
on
11-17-2022
03:50 AM
Bipin_Patel
on
11-17-2022
03:50 AM
Customers need to fetch the Contact ID of an end client, based on the WhatsApp identity.
The use case is basic, a contact was automatically created within Conversation API by a business-initiated WhatsApp template and while using theWhatsApp end client identity to initiate the conversation. Now the customer is asserting to reconcile programmatically the Contact ID. We have endpoints to list contacts, create/delete/update/merge contacts, but currently they only method in the API to retrieve the initially created Contact Id based on WhatsApp identity, is using the callback.
... View more
Status:
Investigating
Submitted on
12-01-2022
02:00 AM
Submitted by
Donna_M
on
12-01-2022
02:00 AM
It will be helpful for companies, for example, restaurants, deliveries, dental/health clinic to send a Calendar message when time and date feedback is needed from the user.
... View more
Status:
Investigating
Submitted on
12-01-2022
02:11 AM
Submitted by
Donna_M
on
12-01-2022
02:11 AM
Some social channels can display to the recipient the actions of the sender such as typing, seen.
Conversation API should add support a new endpoint: send sender actions
... View more
Status:
Investigating
Submitted on
11-17-2022
03:45 AM
Submitted by
Donna_M
on
11-17-2022
03:45 AM
Customers have suggested that we add Zalo as a new channel to Conversation API. Zalo is the largest social media channel in Vietnam, with an estimated 53 million monthly active users.
Having Zalo in Conversation API will enable Conversation API customers to engage with Zalo users.
... View more
Some channels, like Whatsapp, Viber, Telegram support markdown but each channel has its own message styler. The rest of the channels in Conversation API don't support markdown at all. For example, if I want to create an omni-channel template with some "bold" characters, it is not possible to work in all channels. If I use the WhatsApp markdown, then it will show up strange when sent via fallback to another channel that doesn't support message styling. To have an omni-channel template to support all channels, Conversation API should identify a single message styler so that it can be transcoded correctly to the channel specific markdown or not at all.
... View more
As SAP ERP is one of the biggest ERP tool on the market (with impressive number of clients), potentially this could be worth to consider such integration.
... View more
Status:
Investigating
Submitted on
11-17-2022
03:42 AM
Submitted by
Tauben_Tenty
on
11-17-2022
03:42 AM
Tauben_Tenty
on
11-17-2022
03:42 AM
Full text message search function is not currently available in Conversation API. This makes it difficult to provide useful information to customers if they have issues sending their messages.
It would be useful if we could have message history and status reporting for Conversation API in the Sinch Customer Dashboard.
... View more
Status:
Accepted
Submitted on
11-17-2022
03:39 AM
Submitted by
Tauben_Tenty
on
11-17-2022
03:39 AM
Tauben_Tenty
on
11-17-2022
03:39 AM
Customers have requested that we add support for batch sending for up to 1000 parameterised messages without having to invoke the Conversation API for each message.
This could be implemented using a separate end point, or could be an extension of the existing functionality.
... View more
Conversation API offers integration with Zapier. Customers have requested if we can also offer integration with Retool (www.retool.com).
... View more