Sinch Community

Bipin_Patel · ‎11-17-2022

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.

Donna_M · ‎12-01-2022

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

Donna_M · ‎12-01-2022

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.

Donna_M · ‎11-17-2022

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.

Donna_M · ‎03-01-2023

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.

asenet · ‎11-17-2022

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.

Tauben_Tenty · ‎11-17-2022

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.

Tauben_Tenty · ‎11-17-2022

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.

Tauben_Tenty · ‎11-17-2022

Conversation API offers integration with Zapier. Customers have requested if we can also offer integration with Retool (www.retool.com).

Sinch Community

Getting Contact IDs

Conversation API should support new endpoint: send sender actions

Conversation API should support Calendar message type

Add Zalo as a new channel in Conversation API

Conversation API to have a message style that will be parsed by all adapters and display correctly.

Add SAP ERP integration

Message history and status in the Sinch Dashboard

Add support for Batch processing in Conv API

Consider Integration with Retool