Skip to main content
No. Your WhatsApp Business account, access token and every call to Meta stay with you. Ringg only receives the messages you forward and returns replies for you to send.
With the standard setup, Ringg holds the account and talks to Meta directly, so there is nothing to build. With Relay, you keep the account and run a service between Meta and Ringg. Choose Relay when the account must stay in your control, for example because your own CRM and human agents use the same number.
No. An account is either connected to Ringg directly or registered for Relay, never both. Ringg refuses a registration that would mix them.
Not yet. The relay is text only today: media messages are accepted but not answered, so route them to your human agents. Media understanding is planned.
202 means the message is safely stored, not that a reply will follow. See No reply for a message.
Yes. Ringg processes each value.messages[0].id once, so a retry never causes a second reply. Retry on timeouts and 5xx.
When messages arrive close together, the agent answers them together, as a person would, instead of replying to each.
Ringg retries each reply for about two minutes, backing off from 1 to 60 seconds and honouring Retry-After. Replies have a 60-second expires_at: if you receive one late, don’t send it, and ack it as skipped. While a reply is being retried, later replies in the same chat wait behind it, so order is kept.
No. message.typing is optional. Sending it shows the customer that the message was read and a reply is coming, which makes the wait feel shorter.
You send the conversation so far in prior_messages when you hand over. The AI agent continues from it without greeting again or asking for details the customer already gave. See Hand over from a human agent.
Yes, up to 200 messages. Ringg skips messages it already has, as long as each carries Meta’s message id. The AI agent’s own replies are recognised and kept as the AI’s.
Stop forwarding that chat’s messages to Ringg and let your human agent answer. When you hand it over again, include what was said in between.
That is set in the agent’s prompt, which Ringg agrees with you. By default, Ringg sets the agent up to write as your team, without a personal name, and not to volunteer that it is an AI. If a customer asks directly whether they are talking to a bot, it answers honestly and offers to have a person call them.
Only with an approved template, through /outbound, which follows WhatsApp’s 24-hour rule. You send the template; when the customer replies, the agent takes over.
Until the AI agent ends it, you call /close, Meta refuses a reply in a way that ends the conversation, or the agent’s idle or maximum-length timeout passes. The customer’s next message then starts a new chat.
Yes. Every relay conversation appears in Logs → WhatsApp with its transcript and analysis. You can subscribe to chat events such as chat_completed to receive them on your own endpoint.
Ask Ringg for a new one. Both the old and new secrets work until you confirm the switch and the old one is retired, so there is no downtime.
Yes. They have different base URLs, API keys, signing secrets and number registrations. Test on staging, then change those three values to go live.