How to create a template on portal
A template can be either a single message (for broadcast campaigns) or a sequence of questions and messages (for conversational campaigns) created for use in Bulk campaigns.One conversation template can be reused across multiple Bulk campaigns, helping save time during campaign creation.Currently, there are several types of templates available: Viber templates, RCS templates, Facebook templates, and WhatsApp templates.Select Manage Template on drop-down menu list
Select the Official account associated with the broadcast template you want to create
Check the type of messages below to understand the features of each type of message.
Set Expire type: (not available for Whatsapp template)Set by campaign: The broadcast template will be based on the configuration of each campaign you create.
None: not set expire time for template.
Expire time: set the exact date and time for the expiring => once expired, the status of all messages as Sent will change to Failed.
TLL: specify the expiration time for a template, for example 1 hour, 2 hours, 1 day....etc.... => the time is calculated from when the template is sent.
For conversation templates, there is no need to select an Official account because one conversation template can be used for many different OA (of course, it must be the same channel).| No | Element | Description | Reference URL/Input |
|---|
| 1 | Name | Your template’s name | Test 1 |
| 2 | Type | Your template’s type | Broadcast only: only display broadcast [1 message only]- Conversation: display conversation [multiple messages] |
| 3 | Channel | Select channel you would like to use for sending message | Viber [Broadcast type only] - Viber bot [Conversation type only] - RCS - Facebook - Telegram - Whatsapp |
| | | |
| 4 | Description | Describe your template | Test Whatsapp Message |
Click directly on template's name you would like to create questions flow (list of questions)
Click on New message button to start
Input the information for your template.
| No | Element | Description | Reference URL/Input |
|---|
| 1 | Message ID | Use to combine with Message name to identify your Message. Very important in creating the question/message flow. Users will use this MessageID-Message name to specify the question/message which should appear next in the flow. | Message ID : 1 - Message Name : Request basic info => Identifier of this question would be: 1-Request basic info |
| 2 | Message Name | Use to combine with Message ID to identify your message | |
| 3 | Type | The type of message you want to send to your customers | Rich Card: up to 6 (not available for Whatsapp) - Text - Picture - Video - File: pdf is not applicable for RCS - Whatsapp interactive (not available for rcs or viber) |
| 4 | Next Message Base On | Set up trigger for next message | User Answer - Script |
| 5 | Answer ID | Configure the variable so that it can be displayed in the following questions/messages | Example: Set answer ID as ‘name' - If a customer inputs the name as John and in the next sentence we put in the description: Name: {{name}} It will display as follows: Name: John |
| 6 | Status | Set up the questions/messages so that the system recognizes the flow of the list of questions. | Start: Use for 1st question/message - Normal: The questions/messages are in the middle of the question flow - Complete: Use for last question/message - Error: Use for displaying error while user input information is not in the preset data. |
| 7 | Next Question | Use to arrange the question/message which should appear next in the question/message flow of the list of questions. | Example input: 3-Accept |
| 8 | Add suggestions | Use to set buttons for messages. | Type of button: REPLY: direct to next message - DIAL: call the phone number configured in Post back data - OPEN URL: open URL configured in Post Back data |
| 9 | Add API | Implement API calls such as GET or POST....etc... to your own or 3rd party APIs. | |
| 10 | Is need reply | If selecting this option, you will need to input a response before moving on to the next message. | |

Modified at 2026-03-02 06:56:37