Interaction context mapping

Who should read this article: Administrators

Interaction context mapping lets administrators map incoming interaction data from supported sources to standardized fields in Voiso, so the information is displayed clearly to agents during the interaction and in Call Detail Records.

Introduction

Use the Interaction context mapping page to map incoming interaction data from supported sources, such as SIP headers and dialer campaign lead lists, to standardized Voiso UI fields. These mapped fields are displayed to agents in Agent Panel during the interaction and to supervisors and administrators in Call Detail Records.

Dialer campaign lead list

Dialer campaign lead list covers lead data captured from your dialer campaigns, whether the leads were added through the Add leads to a campaign API (Calling List API) or uploaded as a CSV file when creating or editing a campaign. Both intake methods are treated as one source for mapping purposes.

You can map any extra field present in your lead data — such as tier, language, or notes — to a display field. Field names and values are accepted in any format; there is no rejection based on SIP-header syntax.

Note: the system captures up to 15 extra context fields per lead. Any additional fields beyond the 15th are silently ignored — the lead is not marked invalid and the CSV upload is not rejected on this basis. This applies to both the CSV and Calling List API intake methods.

Note: for CSV uploads, the header row is optional and auto-detected. Files without a header row continue to work exactly as before; only files with a header row get the extra-column treatment described above.

For example, lead data might include:

"Client Order Id": "1234",
"Call Context": "discount_promo_code"

When you map these fields to a context field, you might create one called Order ID and one called Call context. These fields are displayed in Agent Panel and the Call Details Record with the associated value.

Reaching third-party bots via SIP

When Voiso sends dialer campaign lead list context to a third-party bot via SIP headers on a call:

• Field names that already match the SIP-safe character set (letters, numbers, and - _ . ! ~ * +) are sent as-is.
• Field names that are SIP-safe but missing the required X- prefix have X- added automatically before being sent.
• Field names or values containing characters outside the SIP-safe set are silently excluded from the SIP INVITE — they are NOT sent to the bot, but they still appear in Agent Panel and Call Detail Records.

Unmapped fields are never sent to bots, shown in Agent Panel, or shown in Call Detail Records.

BYOB SIP headers

Bring Your Own Bot (BYOB) SIP headers are metadata sent with inbound calls through custom SIP headers in the INVITE request. These headers can include information such as customer name, language, scenario, or Custom SIP headers, such as x-name or x-language. Any header can be mapped to Voiso fields for display to agents and in Call Detail Records.

When you map these headers to a context field, you might create one called Name and one called Language. These fields are displayed in Agent Panel and the Call Details Record with the associated value.

Interaction context mapping page

To view the Interaction context mapping page, navigate to Administration > Interaction context mapping. The page contains a table that lists your context mapping fields.

Adding mapping fields

To add a new interaction context mapping field, follow these steps:

1. Click Add mapping field. A panel opens requesting that you provide a display name (Display field label) for the metadata that you want to display in Agent Panel or in reporting. This label is used to generate the suggested field key in the next step. Specify a name that is short and descriptive. Note: after you click Continue, the display label cannot be edited.

2. Click Continue to display the Add mapping field page.

3. The following fields are shown in the General section.

   • Display field label: the display name you specified in step 1. You may copy but not modify this value.
   • Auto-generated context key: the name of the variable used to store metadata values.

4. In the Metadata source section, select one or more data sources to map to the context key. The following data sources are supported:

   • Dialer campaign lead list: refer to Dialer campaign lead list. Field name input placeholder: "Enter the field name as it is in your file or API".
   • SIP header: refer to BYOB SIP headers. Field name input placeholder: "Enter the header name as it arrives on the call".

   Note: when Dialer campaign lead list is selected, an info banner is shown inside that section: "Fields sent to third-party bots can't contain spaces or special characters (letters, numbers, and - \_ . ! ~ * +). Fields with such names will still show in Agent Workspace and CDR, but won't reach the bot."

5. When you select a source a field is displayed that enables you to specify a field name from the data source, such as tier, name, or other parameter. Enter the source field name to be associated with the mapping field. To specify more than one possible field name, click Add field to add another field. Note: the first field found in the source data matching one of the specified field names will be used.

6. Click Save.

Editing mapping fields

To edit the source fields that can be mapped to an interaction context mapping field, click the display name of the field in the table on the Interaction context mapping page. Follow steps 4 through 6 above to add more fields. Click 'X' next to a field to remove it from the mapping. Note: A context mapping field must have at least one associated metadata source field. Click Save when you are done.

Agent Panel

When the Interaction context mapping feature is enabled in your contact center a link is displayed in Agent Panel during inbound and Dialer campaign calls providing the display fields you defined and the associated values from the call metadata.

Call Detail Records

When the Interaction context mapping feature is enabled in your contact center the Interaction context section is added in Extended Call Details for inbound and Dialer campaign calls providing the display fields you defined and the associated values from the call metadata.