Regal Voice Destination

Regal Voice is a next-gen outbound phone marketing and sales platform that helps consumer and financial services brands proactively engage and convert customers before they buy elsewhere.

Regal Voice maintains this destination. For any issues with the destination, contact their Regal Voice support team.

Getting Started

1. From the Destinations catalog page in the Segment App, click Add Destination.
2. Search for “Regal Voice” in the Destinations Catalog, and select the “Regal Voice” destination.
3. Choose which Source should send data to the “Regal Voice” destination.
4. Email support@regalvoice.com to get your “API key”.
5. Enter the “API Key” in the “Regal Voice” destination settings in Segment.

Page

If you are not familiar with the Segment Specs, take a look to understand what the Page method does. An example call looks like:

analytics.page()

Segment sends Page calls to Regal Voice as a pageview.

Screen

If you are not familiar with the Segment Spec, take a look to understand what the Screen method does. An example call looks like:

[[SEGAnalytics sharedAnalytics] screen:@"Home"];

Segment sends Screen calls to Regal Voice as a screen.

Identify

If you are not familiar with the Segment Spec, take a look to understand what the Identify method does. An example call looks like:

analytics.identify({
  phone: "+19175554444", 
  firstName: "Anne",
  lastName: "Smith"
});

Segment sends Identify calls to Regal Voice as an identify event.

For Regal Voice to trigger outbound voice or sms messages, Regal Voice must have the user’s explicit opt-in for those channels.

Anytime you collect opt-in for sms or voice calls, you should use an identify call to pass that opt-in information to Regal Voice. For many brands, this may happen before a user creates an account in your application.

Below is an example of what an identify call would look like for a user who opted into multiple channels (sms and voice calls) at once:

analytics.identify({
  phone: '+19175554444',
  age: 30,
  firstName: "Anne",
  lastName: "Smith",
  optIn: [
    {
      channel: "sms",
      subscribed: true,
      timestamp: "2020-08-25T21:23:43Z",
      ip: "172.16.254.1",
      text: "By clicking the 'Submit' button below, I agree to receive automated marketing SMS and calls."
    }, 
    {
      channel: "voice",
      subscribed: true,
      timestamp: "2020-08-25T21:23:43Z",
      ip: "172.16.254.1",
      text: "By clicking the 'Submit' button below, I agree to receive automated marketing SMS and calls."
  }]
})

Supported messaging channels are: sms, voice and email.

The ip field is required if you are opting in users server side.

Make sure to include timestamp with the exact time the user opted in. Since traits are cached and sent with subsequent Identify calls, Regal Voice ignores opt-ins that do not have a timestamp date.

Track

If you aren’t familiar with the Segment Spec, take a look at the Track method documentation to learn about what it does.

Segment recommends calling track on any user or system event that you may want Regal Voice to be able to use for lead scoring or as triggers or conditions when sending voice and sms campaigns.

Segment sends track calls to Regal Voice as a track event. Pass allattributes relevant to your use case into the properties object.

Regal Voice communications can be triggered proactively to a user based on their activity or inactivity - in order to nudge them through your funnel.

An example for a financial services company might be that you want to tigger an outbound call to a user for whom a ‘Loan Application Approved’ event has been received, but not a ‘Loan Signed’ event (with some parameter around timing).

In that case, an exampletrack call for the ‘Loan Application Approved’ event would look like:

analytics.track('Loan Application Approved', {
  loanType: 'Personal loan', 
  amount: 30000
  currency: 'USD'
  term: 12
})

Regal Voice communications can also be triggered reactively in response to a user’s request for a call back. For example, when a user schedules a call back on your site, the associated track call would look like:

analytics.track('Call Back Requested', {
  timing: '2020-09-01 15:40:00 -04:00', 
  expiry: 3600, 
  urgency: 'scheduled'
}

Personas

You can send computed traits and audiences generated using Segment Personas to this destination as a user property. To learn more about Personas, contact us for a demo.

For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Personas sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it’s been more than 30 days since their last order), Personas sets that value to false.

When you first create an audience, Personas sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.

Settings

Segment lets you change these destination settings from the Segment app without having to touch any code.

API Key

Email support@regalvoice.com to get your “API key”