Journey into WhatsApp

Consent Flows

Consent flows support both brand and user-initiated conversations. Customer success management can share know-how on how you can create widgets and descriptions for Desktop Web, Mobile Web, e-mail, print to drive users into the messenger, ensuring that the opt-in gets captured and stored.

The MT-Flow (mobile-terminated) is intended for Desktop users where it's not clear if they have installed the app. Users check the box and enter their phone number. In e-Commerce solutions, the phone number might be already available - it can be pre-populated. The consent management would then send a welcome message (aka Welcome MT) to the given phone number.

The MO-Flow (mobile-originated) is intended for users who reach out on their own, by following a link to WhatsApp Web, by scanning a QR-code, or by typing in or sharing the phone number. In the user-initiated chat session, the consent management will first ask the user to agree on the terms & conditions. If the user agrees, the conversation can continue, if the user disagrees, then his profile and the incoming message get deleted.

Always ask for an active opt-in from the user. Any communication from the WhatsApp endpoint requires an active opt-in. "Active" means that it must be triggered by a user action, such as entering a phone number or checking a box to indicate consent (please consult the Opt-In requirements).

Please have a look at the demo page on how to best do it.

WhatsApp has a reporting and blocking mechanism that gets activated when the user receives a message without reaching out before (in a notifications case). If the user is unaware of receiving notifications this might lead to an increase in blocked numbers or users that want to opt-out. Try to get the Official Business Approval to show your brand instead of the WhatsApp number.

Contact Card sharing

Try to get started with MO-flows and send your business contact, so the customer can store it on his/her phone. This will improve the user experience and will reduce the risk of being flagged.

Deep & Universal Links

https://wa.me/<YOUR_WABA_PHONE_NUMBER>?text=<YOUR_START_MESSAGE> will take the user straight into WhatsApp (if it's installed) or to a landing page hosted by WhatsApp (if it's not installed).

Deeplinks

• whatsapp://r - account confirmation link - which doesn't seem to work on iOS

• whatsapp://send - contact picker

• whatsapp://chat - HomeActivity

• upi://pay - payments

*Universal Links

• http[s]://v.whatsapp.com - verify SMS deeplink

• http[s]://api.whatsapp.com- text and direct chat deeplink

• http[s]://wa.me- text and direct chat deeplink

• http[s]://chat.whatsapp.com - accept invite link deeplink

Contact validation

• Ensure that you only pass phone numbers consisting of digits, no leading zeros and a country prefix - use an E.164 format validation.

• Use a phone number validation library such as Google's phonelib or a number database such as Numverify, RealPhoneValidation or others to validate that the given number is well-formatted and that it should be valid; consider exceptions for Mexico and Argentina.

• Check the contact-endpoint before sending messages​

Message sending

• Manage cut-off control (don't send messages other than templated-based messages if there is a 470 response).

• Don't send text messages with more than 4096 characters.

• If you intend to benefit from URL-unfurling and you set preview_url to true the text message must contain a valid URL.

• Make sure that the file type is supported by WhatsApp and that the file size doesn't exceed given limit:

  • video files must have an audio track

  • audio and video files will require codecs supported by WhatsApp.

• ​Send files and images using a link rather than uploading them first. a) Store & Forward - the media file needs to be uploaded to the WhatsApp gateway (Google Cloud Platform Frankfurt/DE) -> Partner's client (client's country). b) Send-file-as-link - the media file is referenced in the message and served from the partner's server.

• Add a wa_id to the phones-object when the user receiving a contact shall be able to save it to the phone.

  "phones": [
                          {
                              "phone": "+1 (940) 555-1234",
                              "type": "HOME"
                          },
                          {
                              "phone": "+1 (650) 555-1234",
                              "type": "WORK",
                              "wa_id": "16505551234"
                          }
                      ]

  When you send a phone number without a wa_id it's only possible to "invite" users. If the wa_id (=E.164-formatted version of the phone number) is given, the WhatsApp client will allow to "add a contact" and "send a message" which might come in different flavours on Android and iOS.

• Implement the typical error scenarios mentioned in the FAQ.

• Implement handling for the quality limit - "warm up" the number when sending template-based messages; there will be a capping when the quality limit has been reached and the number will be switched to "Restricted" by Facebook for 24h.

• Make use of message formatting: bold (*), italics (_), ~strikethrough~ (~) and mono-space (```).

Latency issues

Respect that WhatsApp might have latencies in their network or that the user's device or app install might have issues which might impact message delivery. Possible reasons for delays seem to be device and/or network related, which is not in our hands. See:

• ​Troubleshooting guide by WhatsApp​

• ​Reddit articles on delayed message delivery​

• ​How to speed up the WhatsApp client​

• ​Reasons for delayed, incoming messages​

• ​Slow connections​s​

Typical fixes include:

• ​resetting the cache on the WhatsApp consumer app

• resetting the network connection

• killing and restarting the WhatsApp consumer app

• ensuring that there is enough RAM available for the WhatsApp consumer app

• saving the contact in the address book you are trying to reach

Callback handling

Only asynchronous handling of callbacks - acknowledge first, then process

Use valid SSL-certificates for the callback endpoint - the certificates must support TLS1.3, the certificate chain must not be broken.

Make sure that the DNS-entry of the callback endpoint is propagated and registered with official DNS-servers (ex. 8.8.8.8).

Chatbot integrations

Have a standard response while the service is not fully active: "Thank you very much for contacting us. Please note that this service is not yet fully operational. We plan to officially start on yyyy/mm/dd. Thank you for your patience."

Review that your chatbot does meet these minimum standards:

• Branding

  • Brand consistency: Does it look and feel like the company? Does it look out of place?

  • Conversational: Is the bot appropriately conversational? Does it use small talk, greet, engage?

  • Language consistency: Does the bot use language and phrasing that is consistent with the brand's website and image?

• Performance

  • Purpose: Is it clear what this bot is meant to do? Can you tell what the One True Goal is? Effectiveness: Is it effective at its job? Does it provide the right help? Knowledge: Can it answer common questions around the task it was built to perform? Can it help the user?

  • Feedback: Does it let the user know they are progressing towards their goal?

• Consistency

  • Doing its job: Can the bot consistently help the user achieve their goal? Journey consistency: Does the path the bot takes users on fit the expected path the company would take them on?

  • Up to date: Is the bot up to date?

  • Knowledge: Does the bot have a consistent amount of knowledge across the different topics it touches on?

• Humanity

  • Transparency: Does it pretend to be a human? Is it transparent and honest about being a machine?

  • Self-aware: Can it answer questions about itself? Does it know and is it open about its limitations?

  • Reaching humans: Can it hand conversations over to its human colleagues gracefully? Does it inform the users on how to skip straight to a human?

Other

• Read the official FAQ.