Template Center
Last updated
Last updated
The Template Center provides access to Plum's collection of Fuse templates: prebuilt applications designed for a variety of industries and use cases. Starting with a template can help reduce the time needed to bring an application from development to deployment.
With a few clicks, you can add your desired templates to the Application Manager and begin customizing them to fit your needs.
The Template Center window will be displayed as shown in Figure 2.
The following fields and information are displayed in this window:
Show: Select a vertical from this dropdown menu to display only that vertical's templates.
Search Templates: Enter a keyword or phrase in this field to search available templates by their descriptions. The Template Center window will automatically display matching templates as you type.
Filter by: Select one or multiple tags from this dropdown menu to display only templates with the same tag(s).
Templates list: Select a template from this section. Templates are grouped by vertical (4a) and listed in alphabetical order (4b).
Each template appears as shown in Figure 3.
The following information is displayed in each template:
Preview image: Shows a preview of the template's application pages. Templates with multiple pages will also have a page count, and you can scroll through previews of each page.
Name: The template's name.
Description: Briefly describes the template's function(s).
Tags: Each template is assigned one or more tags based on its features.
Select: Select or deselect a template. A selected template is highlighted with a purple outline.
NOTE: For a list of available verticals and tags, see this section.
Select an added template to open it in the Application Editor.
A template is designed for you to customize to match your intended use before deployment.
Many templates include one or more default, placeholder messages that are meant to be replaced. A template must also be configured to interact with any external resources – a company database or API, for example. You may even wish to add or remove certain modules altogether.
The Payment Application template provides an example. As shown in Figure 6, the indicated Prompt and REST modules contain placeholder content that should be replaced.
First, you should review the template's pages and modules to familiarize yourself with how they were designed to work. Note which modules and content you either want or need to revise.
The following is a list of recommendations by module type:
NOTE: We recommend testing your modified template first before deploying for live use.
Once you have completed the initial configurations above, you can freely customize the template as desired. When satisfied, you can then deploy the template like any other application.
The following lists verticals and tags associated with available templates in the Template Center.
Last updated: 1/23/23
These are the industries in which available templates are grouped. You can search for templates by vertical using the Show dropdown menu in the Template Center window.
Banking
Education
Government
Healthcare
Information Technology
Insurance
Real Estate
Retail
Telecom
Transportation
Utilities
In the Application Manager, select Templates as shown in Figure 1.
Close : Close the Template Center window.
Add Template(s) : Add any selected template(s) to your current folder in the Application Manager. This button is inactive until at least one template is selected.
In the Template Center window, select one or multiple templates using the Select button . Your selected template(s) will be highlighted with a purple outline as shown in Figure 4.
Select any other desired templates, then select Add Template(s) . The prebuilt application(s) for each selected template will be added to the current folder as shown in Figure 5.
| Module | Why are revisions likely needed? |
|---|---|
| Module | Why are revisions recommended? |
|---|---|
| Module | What to consider about revising these modules? |
|---|---|
Some existing, default messages are placeholders until the user writes something more specific for their company or organization.
Example: "Thank you for calling Plum Insurance." Any messages referencing Plum/Plum Voice are placeholders and should be replaced.
These modules will contain a placeholder endpoint.
You must...
supply the template with an API endpoint for an API that you control.
ensure that the request (e.g. POST, PUT, etc.) is properly formatted to interact with your API.
Add your desired destination number. Some templates may contain placeholder numbers that should be updated.
Enter your...
DEV account credentials
An SMS-enabled number on your DEV account
ALL Input
In each of these modules, some (but not all) default messages are placeholders until the user writes something more specific for their company or organization.
Example: "Thank you for calling Plum Insurance." Any messages referencing Plum/Plum Voice are placeholders and should be replaced.
Review the existing menu options and add, remove, or otherwise customize these options as needed.
These require knowledge of JavaScript to revise properly. Leave these as is if unfamiliar with JavaScript.
Prompt
REST
Transfer
SMS
Menu
JS
