Customer Communications Blog | Sinch

Before the Sinch Verification API sends a verification code, it can ask your server whether to send it. That matters if your signup form passes the phone number straight to a start call, because then anyone who can reach the form can make your backend text any...

AI assistants are now part of the customer journey for many retailers, from offering product recommendations to sharing delivery updates. The question is which conversations shoppers are actually happy to hand them. When an order is delayed, or a card has been charged twice, do they type their question to the AI agent on the website, or go looking for a phone number to resolv...

Reminder calls the day before help cut no-shows, but calling a list of customers is more work than calling one. You need a queue so you don’t dial 500 numbers in the same second, a way to stop calling once the reminders are no longer useful, a plan for voicemail, and a way to tell afterwards who confirmed, who didn’t answer, and who never got called at all.

Batch ca...

The Sinch CLI (@sinch/cli) puts the Sinch platform in one terminal command: sinch. You can get a phone number, route calls to a Voice API v2 service, build and deploy a Sinch Function, send a message over the Sinch Conversation API, and then script the same steps i...

I have built plenty of voice and messaging integrations where a small HTTP service existed for one reason: receive a callback and turn it into the next action. The service was rarely complicated, but it still needed to be deployed, monitored, and kept available.