If you’re building a team inbox on the WhatsApp Cloud API, these are the bugs that show up in the first week of real use.
Two agents reply at once
Both opened the chat and both typed a reply. Add ownership: assign on first open (or by a routing rule), and block or warn when a non-owner sends.Replying after the 24-hour window
The API rejects free-form messages sent more than 24 hours after the customer’s last message. Track the last inbound timestamp and switch the composer to template-only when the window closes. Don’t let agents type a reply that will fail.Chats stuck with an absent agent
An agent goes on leave with 30 open chats. Add a “reassign all” action, and auto-reassign chats that go unanswered for a set time.Duplicate contacts
“919876543210”, “+91 98765 43210” and “09876543210” become three contacts. Key contacts on the wa_id from the webhook, not on whatever the user typed in a form.Internal notes sent to the customer
If notes and replies share a table and a send function, one wrong flag sends “this customer is difficult” to the customer. Make notes a separate type that the send path can never pick up.Media URLs expire
The media URL from the API is short-lived. If you store the URL instead of the file, images and documents break later. Download and store the file when the webhook arrives.
Wabbiyo’s team inbox, a WordPress plugin on the official Cloud API, handles ownership, the service window, reassignment and media storage: Click here
Top comments (0)