# Template Center

## Overview 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. ## Getting started In the Application Manager, select **Templates**

as shown in Figure 1.

*Figure 1: Opening the Template Center.*
*Select this image to zoom in.*

The Template Center window will be displayed as shown in Figure 2.

*Figure 2: The Template Center window.*
*Select this image to zoom in.*

### Window options The following fields and information are displayed in this window: 1. **Show:** Select a vertical from this dropdown menu to display only that vertical's templates. 2. **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. 3. **Filter by:** Select one or multiple tags from this dropdown menu to display only templates with the same tag(s). 4. **Templates list:** Select a template from this section. Templates are grouped by vertical (4a) and listed in alphabetical order (4b). 5. **Close**

: Close the Template Center window. 6. **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. ### Template entries Each template appears as shown in Figure 3.

*Figure 3: A template entry in the Template Center window.*

The following information is displayed in each template: 1. **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. 2. **Name:** The template's name. 3. **Description:** Briefly describes the template's function(s). 4. **Tags:** Each template is assigned one or more tags based on its features. 5. **Select:** Select or deselect a template. A selected template is highlighted with a purple outline. {% hint style="info" %} **NOTE:** For a list of available verticals and tags, [see this section](#available-verticals-and-tags). {% endhint %} ## Adding a template 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.

*Figure 4: Selecting a template.*
*The purple outline indicates that the template is currently selected.*

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.

*Figure 5: An added template in the Home folder.*

Select an added template to open it in the Application Editor. ## Configuring a template 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.

*Figure 6: Placeholder values in the Payment Application template's modules.*
*Enter your own company-specific messages and external resources where placeholders like these are used.*

### What to configure 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: #### Which template modules to revise? {% tabs %} {% tab title="NEEDED" %}

Module	Why are revisions likely needed?
Prompt	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.
REST	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.
Transfer	Add your desired destination number. Some templates may contain placeholder numbers that should be updated.
SMS	Enter your... DEV account credentials An SMS-enabled number on your DEV account

{% endtab %} {% tab title="RECOMMENDED" %}

Module	Why are revisions recommended?
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.
Menu	Review the existing menu options and add, remove, or otherwise customize these options as needed.

Module

Why are revisions recommended?

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.

Menu

Review the existing menu options and add, remove, or otherwise customize these options as needed.

{% endtab %} {% tab title="OTHERS OF NOTE" %}

Module	What to consider about revising these modules?
JS	These require knowledge of JavaScript to revise properly. Leave these as is if unfamiliar with JavaScript.

{% endtab %} {% endtabs %} ## Deploying a template {% hint style="info" %} **NOTE:** We recommend testing your modified template first before deploying for live use. {% endhint %} 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](/fuse/deployments/creating-deployments.md). ### Available verticals and tags The following lists verticals and tags associated with available templates in the Template Center. {% tabs %} {% tab title="Verticals" %} 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 {% endtab %} {% tab title="Tags" %} Last updated: 1/23/23 These are tags that are associated with one or more available templates. You can search for templates by tag using the **Filter by** dropdown menu in the Template Center window. * Activation * AI * Authentication * FAQ * Feature * Inquiry * Notification * Outbound * Payment * Reminder * Scheduling * SMS * Speech Recognition * Survey * Timecard {% endtab %} {% endtabs %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.plumvoice.com/fuse/template-center.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.