Used by:
Setting up personal queues, Taking and sending a message from a caller, Using dynamic announcements in a Data Announcer applet, _ExcerptTaggingInteractionsSkills, Using dynamic audio in a Universal Contact Distributor (UCD) applet, Sending SMS messages from Vonage Contact Center, Using text-to-speech in announcementsYou can use any applet that stores data in a data source to create the data sources. The following applets create data sources:
- Data Connector applet. For information about the Data Connector applet, see Data Connector applet.
- IVR Collect Digit applet. For information about the IVR Collect Digit applet, see IVR Collect Digit applet.
- IVR Collect Digit String applet. For information about the IVR Collect Digit String applet, see IVR Collect Digit String applet.
- IVR Set Menu Digit applet. For information about the IVR Set Menu Digit applet, see IVR Set Menu Digit applet.
- IVR Set Menu String applet. For information about the Set Menu String applet, see IVR Set Menu String applet.
- Set Data Source applet. For information about the Set Data Source applet, see Set Data Source applet.
You can also use an existing data source; by default, all calls have the following data sources available:
- Call Guid
- CLID
Dialled Number
The Dialled Number (
$(DialledNumber)
) data source contains the ID of the interaction plan rather than its phone number. The ID and the phone number will often be the same, but this is not guaranteed. Therefore you should not use$(DialledNumber)
to indicate the number dialed by the caller.- Language
First Agent ID
First Agent ID is only populated after Vonage Contact Center has routed the call through an ACD applet to an agent.
- DisplayName. By default, DisplayName contains the CLID of the inbound caller. For information about using a custom value in the DisplayName data source, see Setting a display name for an inbound call.
- InteractionOutcome. By default, InteractionOutcome contains the outcome of the interaction. For information about interaction outcomes, see Interaction outcomes.
If you use a post-call named route for post-interaction processing, all data sources configured at the time the interaction finishes (including InteractionOutcome) are available to the target named route.