In Qontak CRM, you can activate push notifications to get notifications on Whatsapp. In this feature, you can send automatic messages with triggers from CRM such as deal date, deal creation, deal moving, idle deal or birthday. Here are the steps.

Important
To enable this feature, there are a few things you should pay attention to, such as:
1. Must have a Chat Panel Account that has access to broadcast.
2. Must have available MCC balance to broadcast.
3. WhatsApp sender must be approved by WhatsApp.
4. Message templates must be approved by WhatsApp.
5. The destination number must begin with the country code.

A. How to Register a Chat Panel Account to CRM

1. Enter the Properties menu then select WhatsApp Notification.
   
2. Click “Create push notification” button.
   
3. Then you will be directed to the following page. Fill in the Omnichannel API token as shown in the following image.
   
   

   Input the Chat API Token which can be found when you click “See API Token” (in this case you must be logged in to the chat panel). Learn how to generate API token here.

4. If you successfully log in, you will see your account status is Connected.
   
   

B. How to Create Push Notification 

1. Click the “Create push notification” button.
   
   

2. Then, you will be directed to the following page.
   

3. In the Feature settings section, several features are available for selection: Deal, Ticket, Contact, and Company.
   

4. Below is the display and configuration that will appear when you select one of the Feature Names (Deal, Ticket, Company, or Contact).

   1. a. Feature Name: Deal
      

   No	Feature Name	Description
   1	Feature: Deal	Displays the type of feature currently selected. In the example above, the selected feature type is Deal.
   2	Pipeline	Displays the available Pipeline options. Learn more here about how to create a Deals Pipeline.
   3	Trigger	Determines when notifications will be sent, based on certain conditions in the feature (example shown above: Deal). There are two types of triggers that can be used: a. By action: Notifications are sent based on specific actions or activities, such as when a new Deal is created (Deal is created) or when it moves to another stage. For the By action type, notifications are sent whenever there is an activity or status change in the selected feature. Some examples of available action triggers include: Deal is created: notification is sent when a new Deal is created. Deal is on stage: notification is sent when a Deal moves to a specific stage in the pipeline. Deal is inactive for: notification is sent when a Deal has had no activity for a certain period. - If the user selects Deal is on stage in the Trigger section, an additional field called Stage will appear. This field is used to define a specific stage in the pipeline that will trigger the notification. For example, if the Qualified stage is selected, a push notification will be sent each time a Deal moves to the “Qualified” stage. - If the user selects Deal is inactive for in the Trigger section, two additional fields will appear: - Stage: used to specify a particular stage in the pipeline to monitor its activity level. - Inactive duration: used to determine how long a Deal remains inactive (in days) before a notification is sent. For example, if Stage: Qualified and Inactive duration: 7 days are selected, a push notification will be sent if a Deal in the Qualified stage remains inactive for 7 consecutive days. b. By date: Notifications are sent based on dates linked to specific data, such as one day before the deal’s closing date or on the due date. Some examples of available by date triggers include: You can customize all triggers with a Date data type or use the predefined triggers provided by the system. - Deal Expected Close / Order: notification is sent on or before the expected deal close/order date. - Deal Expire Date: notification is sent when the deal is approaching its expiration date. - Deal Start Date: notification is sent on the deal start date. If the user selects By date in the Trigger section, after choosing the reference date type (e.g., Deal Expected Close / Order), an additional field Send notification at (hours) will appear. This field is used to define the specific time (in hours) for sending notifications on the chosen date.

   
   ` b. Feature Name: Ticket

   

   No	Nama Fitur	Penjelasan
   1	Feature: Ticket	Displays the type of feature currently selected. In the example above, the selected feature type is Ticket.
   2	Pipeline	Displays the available pipeline options.
   3	Trigger	a. By action: Notifications are sent based on certain actions or activities, such as when a new Ticket is created (Ticket is created) or moves to another stage. For the By action type, notifications are sent whenever an activity or status change occurs in the selected feature. Some examples of available action triggers include: Ticket is created: notification is sent when a new Ticket is created. Ticket is on stage: notification is sent when a Ticket moves to a specific stage in the pipeline. Ticket is inactive for: notification is sent if a Ticket remains inactive for a certain period. - If the user selects Ticket is on stage in the Trigger section, an additional field called Stage will appear. This field is used to specify a particular stage in the pipeline that will trigger the notification. For example, if the Qualified stage is selected, a push notification will be sent each time a Ticket moves to the “Qualified” stage. - If the user selects Ticket is inactive for in the Trigger section, two additional fields will appear:   - Stage: used to determine a specific stage in the pipeline to monitor its activity level. - Inactive duration: used to specify how long the Ticket remains inactive (in days) before a notification is sent. For example, if Stage: Assigned and Inactive duration: 7 days are selected, a push notification will be sent if a Ticket in the Assigned stage has been inactive for 7 consecutive days. b. By date: Notifications are sent based on dates linked to certain data, such as one day before the ticket’s closing date or on the due date. Some examples of available by date triggers include: You can customize all triggers with a Date data type or choose from the predefined triggers provided by the system. Ticket Due Date: means the system will send a push notification at the specified time (via the Send notification at (hours) field) to remind users that a ticket is about to reach or has reached its due date. If the user selects By date in the Trigger section, after choosing the reference date type (e.g., Ticket Due Date), an additional field Send notification at (hours) will appear. This field is used to specify the notification sending time (in hours) on the selected date.

   
   c. Feature Name: Contact
   

   No	Nama Fitur	Penjelasan
   1	Feature: Contact	Displays the type of feature currently selected. In the example above, the selected feature type is Contact.
   2	Trigger	By date: Notifications are sent based on dates linked to certain data. Some examples of available by date triggers include: You can customize all triggers with a Date data type or use the predefined triggers provided by the system. '- Contact Date Of Birth: notifications are sent based on the contact’s date of birth, for example, to send birthday greetings or special promotions. - Contact Tanggal: notifications are sent based on another specific date stored in the “Tanggal” field within the contact data, such as the join date, follow-up reminder date, or other custom dates. If the user selects By date in the Trigger section, after choosing the reference date type (e.g., Contact Date Of Birth), an additional field Send notification at (hours) will appear. This field is used to define the specific time (in hours) for sending notifications on the selected date.

   
   d. Feature Name: Company
   

   No	Nama Fitur	Penjelasan
   1	Feature: Contact	Displays the type of feature currently selected. In the example above, the selected feature type is Company.
   2	Trigger	By date: Notifications are sent based on dates linked to certain data. You can customize all triggers with a Date data type or use the predefined triggers provided by the system. If the user selects By date in the Trigger section, after choosing the reference date type, an additional field Send notification at (hours) will appear. This field is used to define the specific time (in hours) for sending notifications on the selected date.

5. Click “Continue”.
   
   
6. Then, you will go to the Template message settings section and select the message template that was created earlier. You have to choose a template which is divided into two types, namely templates with media files and templates that contain only text.
   
7. Next select Message Templates.
   
   
8. If the user chooses a template that contains images, videos or documents, upload the media files that you want to include in the broadcast.
   
   

   The file format and maximum size are as follows:
   - Image: .jpg, .jpeg, .png, with a maximum size of 20MB.
   - Video: .mp4, .avi with a maximum size of 50 mb.
   - Document: .pdf with a maximum size of 10 mb.

9. A preview of the message template will appear as follows.
   
10. In the template above there are variables in which you can determine the contents of the template by selecting them in the Variable mapping section. Determine the variables in the Select mapping feature and Field sections. 
    
    
11. Then there is the Dynamic Link column. This column appears exclusively in templates that use dynamic URL variables and allows you to generate dynamically customisable URLs based on the modules and fields you specify. You can choose modules (such as Deal and Associated Ticket) and fields (such as Name and ID) to automatically generate the URL. 
    
    

    Here is an example of a Dynamic Link implementation flow:
    A Qontak CRM user sets up a Dynamic Link to send a message template with a URL so that their customers can easily access the URL to monitor the order status.
    The user will select the "Associated Ticket" Module and the "Ticket ID" Column. Then the system will automatically create a URL template like this: qontakticket.com/order/{ticketID}. When the WhatsApp message is sent, the system will dynamically replace {TicketID} with the unique ID of the selected ticket. Based on this, when the customer clicks on the link, they will be directed directly to their order status record on the previously set website

12. Select the recipient of the message in the WhatsApp sender section.
    
    

    The number that appears is a Whatsapp number that has been approved by WhatsApp from the Chat Panel based on the registered account.

13. Determine the recipient by selecting the Recipient field, and select the features and columns you want in the Feature and Field sections.
    
    
14. Click “Save”.
    
    
15. Then the Push Notification trigger that you have created will be formed as follows and will automatically activate.
    
16. The following is a display of the received push notifications.
    
    
17. You can also delete and disable the Push Notification trigger that has been created by clicking “Action” and then selecting Delete or selecting Details to see in more detail.