Skip to content

Commit 9e9a7b0

Browse files
author
markzegarelli
authored
Merge pull request #1824 from segmentio/regalvoice/doc_update_08_2021
Regalvoice Documentation Update 08/2021
2 parents e1e885b + 3281849 commit 9e9a7b0

File tree

2 files changed

+137
-112
lines changed
  • src/connections
    • destinations/catalog/regal-voice
    • sources/catalog/cloud-apps/regal-voice

2 files changed

+137
-112
lines changed

src/connections/destinations/catalog/regal-voice/index.md

Lines changed: 37 additions & 39 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ rewrite: true
33
title: Regal Voice Destination
44
---
55

6-
[Regal Voice](https://regalvoice.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) 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.
6+
[Regal Voice](https://regalvoice.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a next-gen customer engagement platform that helps brands proactively engage and convert customers before they buy elsewhere.
77

88
Regal Voice maintains this destination. For any issues with the destination, contact their [Regal Voice support team](mailto:[email protected]).
99

@@ -61,13 +61,44 @@ analytics.identify({
6161

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

64-
For Regal Voice to trigger outbound voice or sms messages, Regal Voice must have the user's explicit opt-in for those channels.
64+
Identify events are used to create users and update user attributes. If an identify event contains a phone, Regal Voice will create a contact in your Audience.
6565

66-
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.
66+
## Track
67+
68+
If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does.
69+
70+
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.
71+
72+
Segment sends `track` calls to Regal Voice as a track event. Pass all attributes relevant to your use case into the `properties` object.
73+
74+
Regal Voice communications can be triggered proactively to a user based on their activity or inactivity - in order to nudge them through your funnel.
75+
76+
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).
77+
78+
In that case, an example `track` call for the 'Loan Application Approved' event would look like:
79+
80+
```js
81+
analytics.track('Loan Application Approved', {
82+
loanType: 'Personal loan',
83+
amount: 30000
84+
currency: 'USD'
85+
term: 12
86+
})
87+
```
88+
89+
## Collecting OptIn
90+
91+
In order to trigger outbound calls or sms messages from Regal Voice, you must collect the user’s explicit opt-in for those channels along with the user’s phone number.
92+
93+
There are 2 options for how you can let Regal Voice know a user has opted in:
94+
95+
1. Anytime you collect opt-in for sms or voice calls, you can trigger a track event after a user opts in and let the Regal Voice team know what track event is synonymous with opt-in collected (there is no required format for this event). The product will then automatically subscribe users who perform that event. (Note: for Regal Voice to subscribe a user, there must already be a phone provided for that user.)
96+
97+
2. Alternatively, anytime you collect opt-in for sms or voice calls, you can use an `identify` call to pass that opt-in information to Regal Voice by adding an optIn object.
6798

6899
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:
69100

70-
```js
101+
```js
71102
analytics.identify({
72103
phone: '+19175554444',
73104
age: 30,
@@ -91,43 +122,10 @@ analytics.identify({
91122
})
92123
```
93124

94-
Supported messaging channels are: `sms`, `voice` and `email`.
125+
Supported messaging channels are: `sms`, `voice` and `email`.
95126

96-
The `ip` field is required if you are opting in users server side.
127+
For the identify method, the `ip` field is required if you are opting in users server side. (If you are opting in users client side, Segment automatically adds ip to the context, so you are not required to add it to the optIn object)
97128

98129
Make sure to include `timestamp` with the exact time the user opted in. Since traits are [cached](/docs/connections/sources/catalog/libraries/website/javascript/identity/#clearing-traits) and sent with subsequent Identify calls, Regal Voice ignores opt-ins that do not have a `timestamp` date.
99130

100-
101-
## Track
102-
103-
If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does.
104-
105-
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.
106-
107-
Segment sends `track` calls to Regal Voice as a track event. Pass allattributes relevant to your use case into the `properties` object.
108-
109-
Regal Voice communications can be triggered proactively to a user based on their activity or inactivity - in order to nudge them through your funnel.
110-
111-
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).
112-
113-
In that case, an example`track` call for the 'Loan Application Approved' event would look like:
114-
115-
```js
116-
analytics.track('Loan Application Approved', {
117-
loanType: 'Personal loan',
118-
amount: 30000
119-
currency: 'USD'
120-
term: 12
121-
})
122-
```
123-
124-
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:
125-
126-
```js
127-
analytics.track('Call Back Requested', {
128-
timing: '2020-09-01 15:40:00 -04:00',
129-
expiry: 3600,
130-
urgency: 'scheduled'
131-
}
132-
```
133131
---

src/connections/sources/catalog/cloud-apps/regal-voice/index.md

Lines changed: 100 additions & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -37,31 +37,39 @@ The table below lists events that Regal Voice sends to Segment. These events app
3737
<td>contact.unsubscribed</td>
3838
<td>A contact was unsubscribed from a marketing channel</td>
3939
</tr>
40-
<tr>
40+
<tr>
41+
<td>contact.attribute_edited</td>
42+
<td>A contact's attributes were edited by an agent</td>
43+
</tr>
44+
<tr>
4145
<td>sms.queued</td>
4246
<td>An sms was queued to be sent from RegalVoice to contact</td>
4347
</tr>
44-
<tr>
48+
<tr>
4549
<td>sms.sent</td>
4650
<td>An sms was sent from RegalVoice to contact</td>
4751
</tr>
48-
<tr>
52+
<tr>
4953
<td>sms.undelivered</td>
5054
<td>An sms was undelivered from RegalVoice to contact</td>
5155
</tr>
52-
<tr>
56+
<tr>
5357
<td>sms.received</td>
5458
<td>An sms was received from a contact</td>
5559
</tr>
56-
<tr>
60+
<tr>
5761
<td>task.created</td>
5862
<td>A call or sms task was created</td>
5963
</tr>
60-
<tr>
61-
<td>sms.conversation_completed</td>
64+
<tr>
65+
<td>task.canceled</td>
66+
<td>A call or sms task was canceled</td>
67+
</tr>
68+
<tr>
69+
<td>sms.conversation.completed</td>
6270
<td>An SMS conversation between a contact and an agent was completed in the Regal Voice agent desktop</td>
6371
</tr>
64-
<tr>
72+
<tr>
6573
<td>call.completed</td>
6674
<td>An inbound or outbound call with a contact was completed. This includes calls that were not answered</td>
6775
</tr>
@@ -75,42 +83,52 @@ The table below lists events that Regal Voice sends to Segment. These events app
7583
<td>Description</td>
7684
</tr>
7785
<tr>
78-
<td>`channel`</td>
79-
<td>The marketing channel: "voice" or "sms"</td>
86+
<td>`agent_email`</td>
87+
<td>Email of the agent who took an action</td>
8088
</tr>
8189
<tr>
82-
<td>`phone`</td>
83-
<td>The phone number the subscription update was applied to. Phone number is the unique identifier for a contact in Regal Voice</td>
90+
<td>`call_id`</td>
91+
<td>Task Id for the call</td>
8492
</tr>
8593
<tr>
86-
<td>`email`</td>
87-
<td>The last email associated with the contact</td>
94+
<td>`campaign_id`</td>
95+
<td>Campaign Id</td>
8896
</tr>
8997
<tr>
90-
<td>`ip`</td>
91-
<td>The IP address from where the subscription update was initiated.</td>
98+
<td>`campaign_friendly_id`</td>
99+
<td>Campaign Friendly Id as seen in the App</td>
92100
</tr>
93101
<tr>
94-
<td>`source`</td>
95-
<td>Source of the subscription update.
96-
A source value that starts with "Brand." indicates that the subscription update was initiated by the Brand (outside of the Regal Voice platform).
97-
A source value that starts with "RegalVoice." indicates that the supscription update was initiated through the Regal Voice platform. </td>
102+
<td>`campaign_name`</td>
103+
<td>Campaign Name</td>
98104
</tr>
99105
<tr>
100-
<td>`text`</td>
101-
<td>The exact text the contact was presented for opt in</td>
106+
<td>`cancelation_reason`</td>
107+
<td>Reason the task was canceled</td>
102108
</tr>
103109
<tr>
104-
<td>`timestamp`</td>
105-
<td>Unix timestamp for when the event took place</td>
110+
<td>`cancelation_source`</td>
111+
<td>Source of where the task was canceled</td>
106112
</tr>
107113
<tr>
108-
<td>`contact_phone`</td>
109-
<td>Phone number of the contact</td>
114+
<td>`canceled_by`</td>
115+
<td>Includes the email of the user who canceled the task, if applicable</td>
110116
</tr>
111117
<tr>
112-
<td>`regal_voice_phone`</td>
113-
<td>RegalVoice phone number</td>
118+
<td>`changes`</td>
119+
<td>Changes made for the contact.attribute_edited event</td>
120+
</tr>
121+
<tr>
122+
<td>`channel`</td>
123+
<td>The marketing channel: "voice" or "sms"</td>
124+
</tr>
125+
<tr>
126+
<td>`completed_at`</td>
127+
<td>UTC Timestamp when the task was completed</td>
128+
</tr>
129+
<tr>
130+
<td>`contact_phone`</td>
131+
<td>Phone number of the contact</td>
114132
</tr>
115133
<tr>
116134
<td>`content`</td>
@@ -120,38 +138,54 @@ The table below lists events that Regal Voice sends to Segment. These events app
120138
<td>`direction`</td>
121139
<td>INBOUND or OUTBOUND</td>
122140
</tr>
141+
<tr>
142+
<td>`disposition`</td>
143+
<td>Task disposition</td>
144+
</tr>
145+
<tr>
146+
<td>`email`</td>
147+
<td>The last email associated with the contact</td>
148+
</tr>
149+
<tr>
150+
<td>`ended_at`</td>
151+
<td>UTC timestamp when the conversation was ended</td>
152+
</tr>
123153
<tr>
124154
<td>`from_number`</td>
125155
<td>Phone number that sent the message</td>
126156
</tr>
127157
<tr>
128-
<td>`to_number`</td>
129-
<td>Phone number to which the message was sent</td>
158+
<td>`handle_time`</td>
159+
<td>Full duration task was being handled, including talk time and wrap time (completed_at - started_at</td>
130160
</tr>
131161
<tr>
132-
<td>`media_url`</td>
133-
<td>Media URL (if it was an MMS)</td>
162+
<td>`ip`</td>
163+
<td>The IP address from where the subscription update was initiated.</td>
134164
</tr>
135165
<tr>
136-
<td>`sms_conversation_id`</td>
137-
<td>Task ID for the conversation. (If the sms was part of a two-way conversation with an Agent, rather than just an automated outbound sms)</td>
166+
<td>`media_url`</td>
167+
<td>Media URL (if it was an MMS)</td>
138168
</tr>
139169
<tr>
140-
<td>`campaign_friendly_id`</td>
141-
<td>Campaign Friendly Id as seen in the App</td>
170+
<td>`notes`</td>
171+
<td>Task notes</td>
142172
</tr>
143173
<tr>
144-
<td>`campaign_id`</td>
145-
<td>Campaign Id</td>
174+
<td>`objections`</td>
175+
<td>Task objections</td>
146176
</tr>
147177
<tr>
148-
<td>`campaign_name`</td>
149-
<td>Campaign Name</td>
178+
<td>`phone`</td>
179+
<td>The phone number the subscription update was applied to. Phone number is the unique identifier for a contact in Regal Voice</td>
150180
</tr>
151181
<tr>
152182
<td>`queue`</td>
153183
<td>Task Queue</td>
154184
</tr>
185+
<tr>
186+
<td>`regal_voice_phone`</td>
187+
<td>RegalVoice phone number</td>
188+
</tr>
155189
<tr>
156190
<td>`scheduling_agent_fullname`</td>
157191
<td>Full name of the agent who scheduled the Callback</td>
@@ -161,7 +195,24 @@ The table below lists events that Regal Voice sends to Segment. These events app
161195
<td>Email of the agent who scheduled the Callback</td>
162196
</tr>
163197
<tr>
164-
<td>`target_agent_fullname`</td>
198+
<td>`sms_conversation_id`</td>
199+
<td>Task ID for the conversation. (If the sms was part of a two-way conversation with an Agent, rather than just an automated outbound sms)</td>
200+
</tr>
201+
<tr>
202+
<td>`source`</td>
203+
<td>Source of the subscription update.
204+
A source value that starts with "Brand." indicates that the subscription update was initiated by the Brand (outside of the Regal Voice platform).
205+
A source value that starts with "RegalVoice." indicates that the supscription update was initiated through the Regal Voice platform. </td>
206+
</tr>
207+
<tr>
208+
<td>`started_at`</td>
209+
<td>UTC timestamp when the conversation was started</td>
210+
</tr>
211+
<tr>
212+
<td>`talk_time`</td>
213+
<td>Duration of conversation (ended_at - started_at)</td>
214+
</tr>
215+
<td>`target_agent_fullname`</td>
165216
<td>Full name of the agent who contact (and all contact’s tasks) are assigned to</td>
166217
</tr>
167218
<tr>
@@ -173,49 +224,25 @@ The table below lists events that Regal Voice sends to Segment. These events app
173224
<td>Unique identifier for the task. Will match the call_id or sms_conversation_id of a completed task event.</td>
174225
</tr>
175226
<tr>
176-
<td>`type`</td>
177-
<td>Task Type</td>
178-
</tr>
179-
<tr>
180-
<td>`call_id`</td>
181-
<td>Task Id for the call</td>
182-
</tr>
183-
<tr>
184-
<td>`disposition`</td>
185-
<td>Task disposition</td>
227+
<td>`text`</td>
228+
<td>The exact text the contact was presented for opt in</td>
186229
</tr>
187230
<tr>
188-
<td>`objections`</td>
189-
<td>Task objections</td>
231+
<td>`timestamp`</td>
232+
<td>Unix timestamp for when the event took place</td>
190233
</tr>
191234
<tr>
192-
<td>`notes`</td>
193-
<td>Task notes</td>
235+
<td>`to_number`</td>
236+
<td>Phone number to which the message was sent</td>
194237
</tr>
195238
<tr>
196-
<td>`handle_time`</td>
197-
<td>Full duration task was being handled, including talk time and wrap time (completed_at - started_at)</td>
239+
<td>`type`</td>
240+
<td>Task Type</td>
198241
</tr>
199242
<tr>
200243
<td>`wrapup_time`</td>
201244
<td>Duration task was in wrap up (completed_at - ended_at)</td>
202245
</tr>
203-
<tr>
204-
<td>`talk_time`</td>
205-
<td>Duration of conversation (ended_at - started_at)</td>
206-
</tr>
207-
<tr>
208-
<td>`started_at`</td>
209-
<td>UTC timestamp when the conversation was started</td>
210-
</tr>
211-
<tr>
212-
<td>`ended_at`</td>
213-
<td>UTC timestamp when the conversation was ended</td>
214-
</tr>
215-
<tr>
216-
<td>`completed_at`</td>
217-
<td>UTC Timestamp when the task was completed</td>
218-
</tr>
219246
</table>
220247

221248
## Adding Destinations

0 commit comments

Comments
 (0)