| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Previously, interaction plans in Interaction Architect were associated with a single destination. To use an interaction plan with different destinations, the admin user needed to copy the interaction plan, once for each additional destination. Any time the plan needed to change, the admin user needed to change multiple copies of the plan. In Interaction Plan Mapping, the destination and interaction plan are separate entities; an admin user can map many destinations to one interaction plan.
In Interaction Plan Management, an admin user can perform the following tasks:
- Map any number of destinations to a single interaction plan for real interactions
- Map any number of destinations to a single test interaction plan for test interactions from one or more specified sources
- Use data sources at the destination, mapping or interaction plan level to influence what happens to interactions in the interaction plan
- View where traffic is routed for both production and testing purposes
- Understand which interaction plans are being used through their Mapped or Unmapped status
| Panel | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||
|
Destinations
...
Using Interaction Plan Management, admin users can create, edit, and delete API destinations. Admin users can only edit PSTN destinations; only Vonage can create and delete PSTN destinations.
For information about configuring destinations, see Using Interaction Plan Management.
Interaction plans
...
Using Interaction Plan Management, admin users can create, edit, clone, and delete interaction plans. When an admin user creates an interaction plan in Interaction Plan Management, the plan appears also in Interaction Architect. The user can then configure the interaction plan’s applets.
For information about configuring interaction plans in Interaction Plan Management, see Using Interaction Plan Management.
Mappings
...
Using Interaction Plan Management, admin users can create, edit, and delete mappings.
For information about configuring mappings, see Using Interaction Plan Management.
Data sources
...
In Interaction Plan Management, destinations, interaction plans, and mappings can each have up to 20 data sources. The values of the data sources are set on associated interactions before being routed through an interaction plan. Interaction plans can be configured in Interaction Architect to behave differently depending on the values.
For example, two destinations mapped to the same interaction plan may have different data source values. The interaction plan’s behavior may be determined by the data source’s value and therefore the destination through which an interaction arrives at the VCC account.
For information about configuration data sources in destinations, interaction plans, and mappings, see Using Interaction Plan Management.
Data source hierarchy
...
For example, if the destination's Language data source value is en-gb, the mapping’s Language data source is es-es, and the interaction plan’s Language data source is pl-pl, the Language data source on an interaction is set to en-gb.
| Note |
|---|
| Applets within an interaction plan can also set data source values. Values set by applets take precedence over values set by the destination, mapping, or interaction plan. |
Example destination, mapping, interaction plans
Production interaction plan
Using the following example:
...
Destination A is included in Mapping A. Mapping A has data sources DS1 and DSM and sets DSM on the interaction to y. Destination A has already set DS1 on the interaction, so Mapping A does not set DS1.
...
Mapping A maps Destination A to Interaction Plan A for real (non-test) interactions.
Interaction Plan A has data sources DS1 and DSP, and sets DSP on the interaction to x. Address A has already set DS1 on the interaction, so Interaction Plan A does not set DS1.
VCC now routes the interaction with four data sources—DS1, DSA, DSM and DSP—through Interaction Plan A’s applets as configured in Interaction Architect.
Testing interaction plan
In this example, the source of the initiated interaction is +449876543210. Interactions from this source are identified as test interactions and therefore go to the testing plan: Interaction Plan B. Interaction Plan B has data sources DS1 and DSP, and sets DSP on the interaction to w.
Migrated interaction plans
If you previously configured interaction plans along with their destinations in Interaction Architect, some of the data from your interaction plans will have been migrated into Interaction Plan Manager. Migration removes destinations from their interaction plans and stores them as separate destination and interaction plan entities. Default mappings are created to reconnect destinations and interaction plans. One interaction plan in Interaction Architect results in one interaction plan, one destination and one mapping in Interaction Plan Management.
| Info | ||
|---|---|---|
| ||
Mappings created from migrated interaction plans (known as default mappings) are not visible in Interaction Plan Management. Destinations that are associated with a default mapping do not appear to be mapped other than in the list of available destinations when creating or editing a mapping. When creating or editing a mapping, destinations that are mapped by default to the interaction plan it was migrated from are indicated by an icon containing a tilde: Interaction plans that are associated with a default mapping have a status of Mapped. |
Use the following information to identify your migrated interaction plans and destinations. You can still find your interaction plans in Interaction Architect, however, addresses and service names no longer appear.
...
Entity
...
Field
...
Value
...
Destination
...
Destination
...
Line or named route
For example, “0123456789” or “NamedRouteForSalesEmails”
...
Type
...
A line in Interaction Architect Line sets Type to “PTSN”.
A named route in Interaction Architect Line sets Type to“API”
...
Name
...
Service name
For example, “Primary call plan“
...
Interaction plan
...
Reporting group
...
Service name
For example, “Primary call plan“
...
Name
...
Line | named route + " - " + service name
For example, “0123456789 - Primary call plan”
...
Mapping
...
Default mappings created from migrated interaction plans do not appear in Interaction Plan Management.
| Panel | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||
|
...