πŸ‡¬πŸ‡§
Omnileads Docs
ComunidadForo
English
English
  • πŸ‘ΆIntroduction to OMniLeads
    • OMniLeads General Specs
    • Architecture and components
  • πŸš€OMniLeads installation methods
    • Deploy using Docker
      • Deploy with Docker-Destkop
      • Deploy with Docker for VPS Cloud or VM
      • Deploy with Docker for VPS Cloud or VM with External Bucket
    • Deploy with Ansible
      • AIO (All-In-One) Deploy
      • AIT (All-In-Three) Deploy
      • HA (High Availability) Deploy
      • Backups, Restores, Upgrades and Rollbacks
      • Migration from CentOS7
    • OMniLeads Enterprise
    • Development Enviroment Deploy
    • First Login
    • TLS/SSL Certificates
    • Monitoring and observability
    • Security considerations
  • βš™οΈInitial Configuration
    • External Authentication
    • Text To Speech (TTS)
  • 🎯CX Survey (Pro)
    • Reports
  • πŸ“ˆPremium Reports (Pro)
    • Activity Reports
    • Analyzing Results
  • 🎞️Video Calls (Pro)
    • Wordpress Plugin
    • Initial Configuration
    • Webphone Demo
    • Embedding the Webphone
  • ☎️Voice Channel Configuration
    • General SIP trunk parameters
  • πŸ†—Whatsapp Channel Settings (Pro)
    • OMniLeads & GupShup
    • Register WhatsApp Business in GupShup
    • Message Templates and Time Groups
    • Providers
    • Lines
  • 🚧Wallboard for Business (Pro)
    • Creating a Wallboard
    • Adding Widgets and Realtime Pages
    • Exploring Widgets and Metrics
  • πŸ“€Whatsapp Bulk Messaging (Pro)
  • πŸ’¬Contact Campaigns
    • Inbound Campaign
      • Incoming Call Routing
      • Forwarding incoming calls from the PBX
      • Time range conditioned routing
      • IVR - Interactive Voice Response
      • Incoming Caller ID
      • EjecuciΓ³n de dialplan personalizado
    • Manual Campaign
    • Preview Campaign
    • Dialer Campaing
    • Whatsapp Campaign (Beta)
  • 🎧Agent handbook
    • Login Logout
    • Manual calls from contact list
    • Preview Calls
    • Dialer inbound calls
    • Inbound calls
    • Calls between agents
    • Contact List
    • Whatsapp Messages
  • πŸ›‘Reports, recordings and monitoring
    • Recordings
    • Incoming Campaign Reports
    • Outbound Campaign Reports
    • General call report
    • Agent reports
    • Whatsapp reports (Beta)
    • Conversation Reports
    • Supervision
  • πŸ“ŠBackoffice - Management audit
  • ☎️Integration between OMniLeads and PBXs
  • πŸ› οΈIT administrator's tasks
  • 🧩CRM Integration
    • Interaction from OMniLeads to CRM
    • Interaction from CRM to OMniLeads
  • πŸ”Security considerations
  • πŸ“ŒOMniLeads RESTful API
    • Agent Session API in Asterisk
  • πŸ—’οΈRelease Notes
  • ❀️Community
  • πŸŽ‡About us
Con tecnologΓ­a de GitBook
En esta pΓ‘gina
  • Creating a WhatsApp Business Account (WABA)
  • Starting the GupShup Wizard
  • From Facebook Business Manager
  • Back to GupShup Wizard
  • Whatsapp Webhook Configuration
  1. Whatsapp Channel Settings (Pro)

Register WhatsApp Business in GupShup

AnteriorOMniLeads & GupShupSiguienteMessage Templates and Time Groups

Última actualización hace 11 meses

Creating a WhatsApp Business Account (WABA)

Once the account has been created in the BSP Portal in the previous section, we can proceed to create (or migrate) our WABA: Whatsapp Business Account.

In our case, GupShup makes its n available to help us move forward with the technical and integration aspects. It is always advisable to review it in case of possible changes in methods and procedures.

Below is an example of the complete activation wizard for WhatsApp Business with GupShup. Important: For correct use of WhatsApp Business API, Meta requires a valid WhatsApp Business number as well as a Meta/Facebook Business Account with its corresponding Business Manager in order to validate the Business that is subscribing to the service. With this, Meta ensures genuine and healthy contact mechanisms, while paving the way for the convergence of new Business channels: Meta Messenger and Instagram Messenger.

Starting the GupShup Wizard

Step 1: From the Control Panel -> Whatsapp, create an Application by clicking on the "+ Create Application" button and specifying a descriptive name.

Step 2: Once listed in the Dashboard, click on "Go Live" to go through the WABA (Whatsapp Business Account) creation wizard. In our case, we will select an existing Whatsapp Business account by clicking on "Migrate Existing WABA":

Step 3: Here you proceed to link the WhatsApp Business account with Facebook Business Manager. If the user has the access credentials to Facebook Business Manager, they can use the direct method (Facebook Embed):

If you are not the Facebook Business Manager account administrator, GupShup provides an option to share the URL with the Account Administrator for authorization:

Using any of the mechanisms described in point 3, the user must access the Facebook Business Manager and make the link.

From Facebook Business Manager

Step 4: Within Facebook Business Manager, create a New WABA (Whatsapp Business Account) and New Profile:

Step 5: Enter the WhatsApp phone number from which the new WABA will be created.

Step 6: Finally, copy the WABA ID once generated, to insert it into the GupShup Portal:

Back to GupShup Wizard

Step 7: Returning to GupShup, click on "I have completed the creation of WABA" and enter the WABA copied in the previous step:

Step 8: To verify the WhatsApp Business phone number, Meta establishes an OTP (ON-Time-Password) mechanism through which it verifies its validity:

Step 9: Finally, the process of linking WhatsApp Business and Facebook Business Manager is complete. As soon as Meta approves the WABA account (1 to 2 business days according to documentation), GupShup will reflect its "live" status within its Dashboard and it is now possible to use Meta's APIs safely:

Whatsapp Webhook Configuration

In order for WhatsApp messages to successfully reach the OMniLeads instance, it is important to configure the Callback URL (Webhook) address where events will be listened to.

To do this, within the GupShup Dashboard, click on the Application that we have instantiated to handle Whatsapp Business events (in the example, "OMLWhatsappAPI") and access the Webhooks tab, where we proceed to set the Callback URL with the following format:

https://<OMniLeads_FQDN>/webhook/<AppID>

Where OMniLeads_FQDN is the Domain Name reachable on the Internet, and AppID is the Identifier obtained in the Application details (step 1 of this Wizard).

And that's it! We are now ready to forward incoming messages to OMniLeads. In the next section we will cover the components needed to register Suppliers and Lines.

πŸ†—
official documentatio
URL de autorizaciΓ³n
El cliente con sus credenciales realiza la vinculaciΓ³n