What are message templates?
Message templates are used for storing an outline of an Alert message (including any normal Alert content: images, links, attachments). This can be useful if you regularly send similar messages to different groups of users, to save time in composing similar content repeatedly.
Templates may also be useful from an organisation perspective, so that they may provide an outline for certain types of messages, such as those that may always include certain content, this allows for a more consistent style of messages over many different senders.
Create a new message template / editing an existing message template
From within the main admin area, you can create a new message template or edit existing templates from: Message Console > Message Templates.
You can then select 'New Template' to create a new template, or select an existing template from the dropdown here, to edit an already added one.
You can then compose the content of the template using the exact same options as when composing a standard Alert message, this includes adding in the merged fields from the 'personalise message' option, which is especially useful within templates.
For the template, you can also set the urgency level and message types. The urgency level selected for the template will be the default when composing a message after selecting the template. However, in this case, you will still have the option to change the urgency level when composing the message.
When creating a template, you can choose the relevant message types that will be available for a sender to use, when using this template to compose an Alert.
You can also add SMS content to a template from the SMS tab. Please note: that this will potentially add sms messages to Alerts sent with this template, possibly incurring some cost for sending.
Saving / Deleting a message template
At the bottom of the page, you will see the option to save the template. If you have selected an existing template to edit, you will also see the option to delete the template.
Comments
0 comments
Article is closed for comments.