- Customer messages: you forward each one to Ringg.
- Replies: Ringg answers with a ready-to-send WhatsApp message on your webhook.
- Sending: your service posts that reply to Meta, then tells Ringg whether it went out.
If Ringg can hold your WhatsApp Business account instead, the standard WhatsApp setup is simpler: connect the account in the dashboard and Ringg talks to Meta directly. Relay is for businesses that need the account, the token and the Meta traffic to stay with them.
How it works
- Forward: a customer messages your number. Meta notifies your service, and your service forwards the message to Ringg’s
/inboundendpoint, signed with your keys. - Reply: Ringg’s agent reads the whole conversation and writes a reply. Ringg posts it to your webhook as a
message.outboundevent, in a format you can send to Meta unchanged. - Send and acknowledge: your service sends the reply to Meta, then reports the result to Ringg’s
/ackendpoint. Ringg uses this to keep its record of the conversation true to what the customer actually saw.
In this section
What's supported
Message types, conversation features and limits, and what is not supported yet.
What we need from you
The details to share for setup, and what your WhatsApp service has to do.
What Ringg provides
Credentials, the AI agent, delivery guarantees, and dashboard visibility.
Integration guide
Authentication, every endpoint, the events Ringg sends you, and error codes.
Hand over from a human agent
Pass a conversation from your agent to the AI agent, and take it back.
Troubleshooting
Symptoms, causes and fixes, and what to send us when you need help.
FAQ
Short answers to the questions integrators ask most.