360dialog is the only WhatsApp BSP focusing on API-only. This makes 360dialog the perfect BSP for developer centric businesses. As the 360dialog API looks exactly like the original WhatsApp Business API, developers can use the original specifications of the WhatsApp Business API and do not need any proprietary documentations.
Compliance with WhatsApp policies and use cases that respect WhatsApp guidelines. WhatsApp requires compliance with their:
a) You offer or sell
Illegal, prescription or recreation drugs, including marijuana
Tobacco products and related paraphernalia
Weapons, ammunition or explosives
Adult items or services
Adult health items
Real money gambling services
Goods, items, or posts that we determine may be or are fraudulent, misleading, deceptive or offensive
Items or products with overtly sexualized positioning
Products or items that facilitate or encourage unauthorized access to digital media which do not comply with Facebook's policies.
b) Your audience might be younger than 16.
c) You request a phone number for countries or regions where WhatsApp/Facebook do not operate, such as the Crimea region.
A phone number already being used with the WhatsApp Business API cannot be migrated. You will have to pick a different phone number.
In the Documentation, it sounds like "migration" would be possible. What is meant by that? It's possible to backup the configuration of a server and to restore it to another server, for example when the installation has to move to another (more powerful) machine (in another network, in another VM).
Yes, sure! Just read our blog article.
Technically we can set up existing numbers if they are linked to the WhatsApp Business client (or, with some more effort, numbers linked to a regular WhatsApp consumer client), BUT we cannot migrate numbers that have been set up by another Business Solution Provider. This is not possible from a technical perspective.
a) A client is installed (WhatsApp consumer client or WhatsApp Business client)
b) The WhatsApp Business profile is still linked to the WhatsApp Business client. Make sure that your profile gets deleted first which might require that you reinstall an already uninstalled WhatsApp for Business client before you can delete the profile.
This can be achieved by setting up a new phone number, and by phasing out the old phone number. New phone numbers will start again at the lowest quality tier and will be automatically upgraded to higher tiers as more messages with a high quality are sent.
WhatsApp doesn't have many differentiators to distinguish a WhatsApp Business API-integration from a WhatsApp Business client. It's difficult to impossible for a user to find out that the integration is with the WhatsApp Business API. The only visual way is the green badge for an Official Business Account.
During the online transaction process
While setting up user profile and preferences
Via email, SMS, or within the mobile app
Via phone interactive voice response (IVR)
User action, such as entering a phone number, checking an "I agree" box
Explicit language containing "I agree to receive [noun], [logo and name], on [number]
Visual indication next to the WhatsApp name and log, such as a checkbox
The WhatsApp stack consists of
a message gateway which represents the encrypted endpoint (aka WACORE),
an API-gateway that is used to configure settings and to send and receive messages and (aka WAWEB)
a database to store messages and files.
Default deployment will happen to Google's Cloud Platform hosting centre in Frankfurt, Germany.
No, there is no such feature.
WhatsApp Business API supports location sharing, but real-time location sharing is currently unsupported and will result in “Message type is unsupported”.
Our servers are working only in HTTP SSL connection on port 443 (standard for HTTPS).
Communication to us is always realised by address IP 126.96.36.199.
Communication from us is always realised from one of those IPs:
What are acceptable methods of direct human escalation if a client is using automation in user-initiated messages?
Examples of direct channels supported include: human agent hand-off in chat, phone number, email, web support, support form and in-store visits. Escalation channels to social media accounts (Facebook, Messenger, Twitter, Telegram, etc.) are not supported because they require a user to have a login and account on another service. Furthermore, indirect channels such as a help center webpage or a link to an app do not meet this requirement.