17.1. Introduction to Policy Builder Apps
  • 11 Sep 2023
  • 4 Minutes to read
  • Dark
    Light

17.1. Introduction to Policy Builder Apps

  • Dark
    Light

Article summary

As mentioned in the Policy Builder Overview section, there are 3 types of policies: Call, Data Analytics and System CreatedMost apps and containers are available in Call policies. Data Analytics has the extra Debug app but not all of the containers and apps. To visualize this, please see this table below...

Type of Policy: Call

Container

Found

Available Apps

Configuration

Link

Apps

From Policy

Automatic insertion


Receiving Container


Inbound Numbers

Start block


Stand Alone Container


Extension Number

Start block


Stand Alone Container


Invokable Destination

Start block


Stand Alone Container


From SIP Trunk

Start block


Receiving Container


Action

Link tab


Simple Container


Action Apps tab

Speak

App




Action Apps tab

Record a Call

App




Action Apps tab

Call Queue

App



Action Apps tab

Rule

App



Action Apps tab

Notify

App




Action Apps tab

Query Object

App



Action Apps tab

Create a Record

App



Action Apps tab

Update a Record

App



Action Apps tab

Connect a Call

App



Action Apps tab

Hunt Group

App



Action Apps tab

Script Engine

App



Action Apps tab

Manage Properties

App




Action Apps tab

Record and Analyse

App




Action Apps tab

Request Skills

App



Switchboard

Link tab


Functional Container


Switchboard Apps tab

Switch Item

App



Switchboard Apps tab

Get Info

App


To Policy

Link tab


Simple Container



To Policy Apps tab

Call Policy

App




To Policy Apps tab

Data Analytics

App


Finish

Link tab


Simple Container



Finish Apps tab

Voice Mail

App




The Start Block

Every policy must start with either the Start block or the From Policy receiving container. The Start block in Call policies contains the Inbound Numbers stand alone container, the Extension Number stand alone container, the Invokable Destination stand alone container and the From SIP Trunk receiving container:

AVSAppSFRoPCStartBlock.png

The Configuration Tab

  • Receiving Containers receive calls from elsewhere and are configured at source.
  • Stand Alone Containers allow for specific items to be placed in the container without need for an App.
  • Simple Containers only give the option to change the Name of the container.
  • Functional Containers and Apps (all Apps are functional) have scope for individual configuration to route or otherwise affect the call.

The Link Tab

  • If the Link tab is available, it always gives the options of the four linkable containers: Action, Switchboard, To Policy and Finish.
    AVSAppSFRoPCLinkTab.png

Above the Or create new Container field is a dropdown list which displays what happens to a call after it has gone through the current container. By default this option is Hung Up - this makes sure that if a call has nowhere to go, it is terminated correctly. As new containers are added, this list is populated. If a link is automatically connected, the selected option in the list changes to match. This list always reflects the route of the connector.

Many of the apps have a Link tab, however, each is configured individually - by default, the call is passed to the next app in the container (or to the container itself) to further the call; however, in the case that they fulfil certain configuration but do not have a connector to move the call forward, the call is hung up.

The Apps Tab

  • The Apps tab is only available in the four linkable containers - it holds the Apps associated with that container, in which specific configuration takes place.

Type of Policy: Data Analytics

Container

Found

Available Apps

Configuration

Link

Apps

From Policy

Automatic insertion


Receiving Container


Inbound Message

Start block


Stand Alone Container


Action

Link tab


Simple Container


Action Apps tab

Debug

App




Action Apps tab

Rule

App



Action Apps tab

Notify

App




Action Apps tab

Query Object

App



Action Apps tab

Create a Record

App



Action Apps tab

Update a Record

App



Action Apps tab

Script Engine

App



Action Apps tab

Manage Properties

App



The Start Block

Every policy must start with either the Start block or the From Policy receiving container. The Start block in Data Analytics policies contains the Inbound Message stand alone container:

AVSAppSFRoPDAStartBlock.png

The Configuration Tab

  • Inbound Message is a Stand Alone Container - it requires the Trigger name field to be completed.
  • Action is a Simple Container, so only give the option to change the Name of the container.

The Link Tab

  • The Link tab gives the option of one linkable container: Action.
    AVSAppSFRoPDALinkTab.png

Above the Or create new Container field is a dropdown list which displays what happens to a call after it has gone through the current container. By default this option is Hung Up - this makes sure that if a call has nowhere to go, it is terminated correctly. As new containers are added, this list is populated. If a link is automatically connected, the selected option in the list changes to match. This list always reflects the route of the connector.

Many of the apps have a Link tab, however, in the case that they complete without having a connector to move the call forward, the call is always passed to the next app in the container (or to the container itself) to further the call.

The Apps Tab

  • The Apps tab is only available in the Action container - it holds the associated Apps in which specific configration takes place.

Type of Policy: System Created

When the app is installed into Salesforce, the system automatically creates three policies:

  • DDI Calls
  • Default Inbound
  • Outbound Calls

These are all Call policies and have the same capabilities as a normal Call policy, above, and can be edited if necessary. However, each policy has a specific purpose within the system.

DDI Calls

In addition to the start block, this policy has a container called DDI Numbers by default (instead of the From Policy container found in a normal Call policy). This leads to an Action container that holds a Connect a Call app, configured to Connect an inbound call routed via a DDI number to the DDI User.

This policy makes sure all DDI calls that are made are connected correctly through the system.

The Default Inbound Policy

In addition to the start block, this policy has a container called Catch All by default (instead of the From Policy container found in a normal Call policy). This leads to an Action container that is named Speak, which holds a Speak app named This number is not in service, configured quite simply to say "This number is not in service".

This policy 'catches all' calls that are not covered by another policy and gives them a neat resolution, given that they won't be answered.

The Outbound Calls Policy

In addition to the start block, this policy has a container called Outbound Numbers by default (instead of the From Policy container found in a normal Call policy). This leads to an Action container that holds a Connect a Call app, configured to Connect an outbound call made by a user to the Requested Number.

This policy makes sure all calls that are being made to external (PSTN) numbers are connected correctly through the system.


Was this article helpful?

Changing your password will log you out immediately. Use the new password to log back in.
First name must have atleast 2 characters. Numbers and special characters are not allowed.
Last name must have atleast 1 characters. Numbers and special characters are not allowed.
Enter a valid email
Enter a valid password
Your profile has been successfully updated.
ESC

Eddy AI, facilitating knowledge discovery through conversational intelligence