Use cases development in WhatsApp

Introduction

When developing a use case in WhatsApp, the general procedure for this task must be followed, depending on the use case type:

• Local use cases

However, due to the distinctive features and limitations for each channel, if the use case is to be developed for WhatsApp, then certain extra steps must be carried out, which are described in the following documents:

• Build Aura response taking into account the rendering limitations of WhatsApp.
• Rendering Aura response components: learn how aura-bridge renders every component of Aura response.
• Use of files in WhatsApp: configure the use case to send a file to the user and vice versa.
• Use of templates in WhatsApp: configure the use case to send a template to the user.
• Use of catalogs in WhatsApp: configure the use case to send a catalog of products and services to the user.
• Use of interactive messages in WhatsApp: how to use reply buttons and list messages in WhatsApp graphical interface.
• Redirect the login dialog: how to redirect certain intents that need authentication when the user is anonymous and requires to be authenticated through SMS-OTP.
• Error management: guidelines for the resolution of error in WhatsApp channel.
• Use of emoticons: how to create a prompt to render emoticons properly.
• Use of section title: how to use a section title in interactive messages.
• Use of footer: how to use footer in interactive messages.
• Use of WhatsApp referral functionality: how to retrieve referral info from a product advertisement.

Pre-requisites

• The use of all the available Aura features in WhatsApp requires the previous activation of the channels:

  • WhatsApp activation

• The OB must previously register Aura’s number in WhatsApp (Kernel procedure) and configure the channel in Aura. This should be done by OB, not by use case.