Deployment refers to active surveys that can be taken either by phone or on the web and record user responses.
The Deployment manager interface displays a list of currently deployed surveys and information related to those surveys.
They key features of the Deployment Manager include:
Click the yellow “Deploy Survey” button in the upper right hand corner to deploy a survey from the Deployment Manager. This opens a new dialog window with a dropdown menu that lists all available surveys.
Select the name of the desired survey from the drop down menu and click “Submit.” This redirects users to the Deployment Settings menu, where they can modify the deployment settings.
To abandon deploying a survey, click the 'x' in the upper right hand corner or the grey “Cancel” button.
Deleting a deployed survey makes it unavailable to respondents via both phone or the web. Deleted surveys cannot gather additional responses.
To delete a deployment, click the trash can icon for that survey located in the “Actions” column of the Deployment Manager. This brings up a dialog window asking users to confirm the deletion of the survey deployment:
To confirm the deletion, click the yellow “Yes” button.
To dismiss this dialog window, click the “x” in the upper right hand corner of the window or click the grey “Cancel” button.
Note: Deleting a survey deployment removes any outbound call data associated with that survey.
Modifying the deployment settings of a deployed survey is done through the Deployment Setting menu. This is the same menu users see when initiating a new survey deployment. To access this menu click the “Edit” icon in the “Actions” column of Deployment Manager.
Deployment settings are broken into two sections: Deployment Methods and Deployment Settings.
Respondents have the option of taking surveys over the phone or via a web browser. Surveys are compatible with browsers on desktops and mobile devices.
This section displays information that respondents need to take the survey:
The deployment settings section provides more granular control over deployed survey behavior.
To save any deployment changes made in this menu, click the yellow “Save” button in the bottom left hand corner.
The outbound queue is an interface that allows users to view pending and completed outbound calls, as well as to queue outbound calls for a deployed survey. Some aspects of the Outbound Queue are also accessible through the Plum Insight API.
To reach the outbound queue menu, click the phone icon for the desired survey in the “Actions” column in the list of deployed surveys.
This menu present two different types of information: completed and pending. The “Completed” tab displays outbound calls that have finished their outbound attempts. A completed outbound call can result from the following scenarios:
The “Completed” tab of the Outbound Queue:
The key items in this interface include:
The “Pending” tab is similar to the “Completed” tab with some minor differences.
The items in this menu include:
Click the yellow “Queue Calls” button to queue outbound calls for your deployment. This opens the queue calls dialog window.
Users have the following options in the queue calls dialog window:
Users who need to queue a single, immediate outbound call attempt and provide a properly formatted CSV file of contact data can safely ignore the optional fields.
Once users complete the desired fields to meet their needs, clicking the yellow “Submit” button schedules the calls to be queued. To dismiss the call queue window, click the 'x' in the upper right hand corner of the window or the grey “Close” button.
When queuing outbound calls from CSV file data, whether through the survey API or the outbound queue interface, users need to format the CSV list of phone contacts properly so that Insight will be able to read them.
The first cell of the first line of the CSV must be “destination”. A valid first line of the CSV simply reads:
Another option when queuing from CSV is to supply metadata values to associate with an outbound call. To do this, include the column headers of the metadatabase that you wanted to include in the header of your CSV file. For example, the first line of the CSV when including metadata values may be:
The next lines of the CSV file should only contain the contact info of the callers receiving the outbound calls. For example, a CSV file that queues three (3) outbound calls without using any metadata would look like this:
"destination" "1234567890" "1234567891" "1234657892"
The destination phone number can be formatted as any valid phone number. Phone numbers may also include the optional “tel:” prefix and/or the optional “ani” and “postd” attributes, which are added to the end of the phone number.
Valid destination examples include:
6175551234 tel:+16175551234 tel:16175551234;ani=2125551234 (**Note:** In this case the ANI determines the number the caller sees) tel:16175551234;ani=2125551234;postd=2 (**Note:** In this case, the ANI determines the number the caller sees, //and// enters the DTMF tone "2" after the call connects)
As of 2019, ANI should be set on all outbound phone calls as federal regulation requirements means that most inbound carriers will block outbound calls that do not originate somewhere. ANI should be a number that you own.
For more information about this, please see here.
An example of a CSV file containing metadata values would look like:
"destination","userID","FirstName","LastName" "1234567890","1","Robert","Weir" "1234567891","2","Jerome","Garcia" "1234657892","3","Philip","Lesh"
Queuing calls with a metadata not only schedules the outbound calls to be queued, but before any calls are made Insight also creates an entry in the metadatabase that is associated with that particular survey, which, in turn, is associated with that specific outbound call.