Invitation Modes

As touched on in some of the previous topics, Trigger supports the following invitation modes:

Contact (previously 'On-Exit')

Most common

The invitation asks the user for an email address or a mobile number. After submitting the information, the invitation is dismissed and the user is sent back into the app. No survey presents in this mode. Instead, after a period of time, the user is sent an email or an SMS text message with a link to the survey. (The default time period is five minutes after the invitation is accepted; if desired, this can be configured to a different value by Verint Support). Detailed information on the SMS messages can be found here: SMS Details.

📘

Contact invitation tip!

Contact details can be supplied to the SDK using the ForeSee.setContactDetails(ContactType contactType, String contactDetails) method ahead of any user interaction. The format for these contact details should be [email protected], 555-123-1234 or 5551231234. If contact details are given to the SDK in this way, they are prepopulated for the user on the second screen of the Contact invitation. The acceptable contact types are ContactType.Email and ContactType.PhoneNumber.

Note: There are some configurations required on the backend to ensure the Contact invitation mode works correctly. Please contact Verint Support first if you would like to use this mode.

Updated Invitation Styling (SDK version 5.1+)

Original Invitation Styling (SDK version 5.0 and before)

**Note:** The client's surveys must be configured on the Verint servers for this option to work properly.

Contact invitation mode may be enabled in the configuration file, but a survey link won't be delivered unless properly configured remotely as well.

In-Session (previously 'Immediate')

Default invitation mode. The survey is displayed at the point where the user accepts the invitation. The survey is displayed in a WebView and is automatically dismissed when the survey is completed, or the user abandons the survey by tapping the Back button.

Updated Invitation Styling (SDK version 5.1+)

Original Invitation Styling (SDK version 5.0 and before)

Exit Invite (New!)

The invitation appears as a local notification displaying after the app is exited. If the user accepts the invitation, they are taken to a survey page. [This does not work for those who have disabled their setting for local notifications.] Both hard exits and pushing the app to the background count towards the launchCount display criteria, and both actions trigger the survey. The time the local notification takes to appear after the user ends their app session can be customized, as well as the verbiage.

Exit Survey (previously 'Local')

In this mode, when the user accepts the survey invitation, a local system notification is queued. Once the user exits the your app, they see a local system notification informing them that they can take a survey. Both hard exits and pushing the app to the background count towards the launchCount display criteria, and both actions trigger the survey. The time the local notification takes to appear after the user ends their app session can be customized, as well as the verbiage.

Updated Invitation Styling (SDK version 5.1+)

Original Invitation Styling (SDK version 5.0 and before)

Invitation Styling

For the invitation types that have a top banner image, the recommended size is 450 pixels by 125 pixels. If an appropriate brand image isn't available, a solid color can be used as well.

The recommended size for the client logo is 200 pixels x 200 pixels. The actual display size may vary from these dimensions, but they provide guidance as to the height x width ratio.

📘

Notification Icons

For Exit Invite and Exit Survey modes, an icon to be displayed in the notification bar is also required. The SDK looks for an icon named ic_notification.png (defaults to the res/drawable directory). However, the name of the icon to be used can be customized by setting the ‘notificationIcon’ property in the JSON Configuration file.