Waitwhile supports integrating with your own preferred messaging provider instead of the providers that we natively support (incl. Twilio, Messagebird, Plivo).
Using your own SMS provider will only allow for 1-way messaging.
Currently 2-way messaging is only supported when you use Waitwhile's default messaging providers. That means that you will no longer see your customer's text replies directly inside Waitwhile anymore.
- Messaging provider with a transaction API
- Server Backend that is responsible for receiving message requests from Waitwhile and forwarding these to the Messaging Provider
- Set up your backend server and create an API endpoint to receive message requests (e.g. https://api.yourdomain.com/sendmessage)
- Within the Waitwhile UI, add a new Webhook endpoint under Settings > Integrations > Webhooks. Enter your endpoint URL and choose to trigger the webhook on the "Message created" event. Alternatively, you can also add the webhook directly using the Waitwhile API.
- Waitwhile API will now pass the sender object (e.g. phone number, name of customer etc.) to your server.
- In your server backend, set up an integration with your Messaging Provider to pass the sender object data to their API.
- Once everything is confirmed to work on your end, we will turn off the default Waitwhile SMS provider for your account.
Updated 2 months ago