About WhatsApp Business API Pricing ✆
Well, now that we can setup WA API on our FCRM, it's VERY IMPORTANT to know the prices/rates (and new way that they charge). Here's the official reference.
I think this is the summary that will to respond many doubts:
° Customer reaches out to you: $0 (Meta never charges you for receiving incoming messages from customers).
-
You reply manually as a human (no templates):
- It falls under the Service Message category.
- You are inside the 24-hour window that resets every time the customer sends a message.
- You pay nothing as long as you stay within the limit of 1,000 free service responses per month for each WhatsApp Business account/number.
- If you go over those 1,000 monthly replies, each additional response you send will be charged based on your local market rate starting October 1, 2026.
The golden rule for everyday manual chats is simple: as long as you keep the conversation within the 24-hour window and don't send paid marketing or utility templates outside of it, your first 1,000 monthly exchanges won't cost you a single cent on Meta's platform.
OBVIOUSLY: EVERY message you send (when it's delivered), it will cost you at the rate on the receiver's zone/country.
Jose Luis Duron thanks for sharing all this information. It is very helpful.
You need a NEW/exclusive phone number to setup with your FluentCRM.
You can't use your current WhatsApp Business number or a number used on another service like Pabbly Chatflow, SendWo, etc.
If you want to use your WhatsApp Business number with FluentCRM (API), you have to delete your number from your phone/app and your history/conversations will be deleted.
Your SIM, eSIM, etc. MUST be able to receive an SMS/call for a verification code during your setup process.
Jose Luis Duron Thanks for sharing your findings! Since Meta does allow a coexistence or migration path for certain WhatsApp Business accounts, does anyone know if that's an option here, or if the WPManageNinja team has plans to support keeping existing chat histories instead of forcing a completely new number?
Erick Laureano For now coexistence IS NOT an option, and as I read on WA documentation, the best practice is a dedicated number for your API.
And in my opinion, because my baggage is using WA as my main source of customers/sales for years, it's better separate numbers.