@@ -75,43 +75,33 @@ The table below lists events that Regal Voice sends to Segment. These events app
75
75
<td >Description</td >
76
76
</tr >
77
77
<tr >
78
- <td >`channel`</td >
79
- <td >The marketing channel: "voice" or "sms"</td >
80
- </tr >
81
- <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 >
78
+ <td >`call_id`</td >
79
+ <td >Task Id for the call</td >
84
80
</tr >
85
81
<tr >
86
- <td >`email `</td >
87
- <td >The last email associated with the contact </td >
82
+ <td >`campaign_id `</td >
83
+ <td >Campaign Id </td >
88
84
</tr >
89
85
<tr >
90
- <td >`ip `</td >
91
- <td >The IP address from where the subscription update was initiated. </td >
86
+ <td >`campaign_friendly_id `</td >
87
+ <td >Campaign Friendly Id as seen in the App </td >
92
88
</tr >
93
89
<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 >
90
+ <td >`campaign_name`</td >
91
+ <td >Campaign Name</td >
98
92
</tr >
99
93
<tr >
100
- <td >`text `</td >
101
- <td >The exact text the contact was presented for opt in </td >
94
+ <td >`channel `</td >
95
+ <td >The marketing channel: "voice" or "sms" </td >
102
96
</tr >
103
97
<tr >
104
- <td >`timestamp `</td >
105
- <td >Unix timestamp for when the event took place </td >
98
+ <td >`completed_at `</td >
99
+ <td >UTC Timestamp when the task was completed </td >
106
100
</tr >
107
101
<tr >
108
102
<td >`contact_phone`</td >
109
103
<td >Phone number of the contact</td >
110
104
</tr >
111
- <tr >
112
- <td >`regal_voice_phone`</td >
113
- <td >RegalVoice phone number</td >
114
- </tr >
115
105
<tr >
116
106
<td >`content`</td >
117
107
<td >Content of the message</td >
@@ -120,38 +110,54 @@ The table below lists events that Regal Voice sends to Segment. These events app
120
110
<td >`direction`</td >
121
111
<td >INBOUND or OUTBOUND</td >
122
112
</tr >
113
+ <tr >
114
+ <td >`disposition`</td >
115
+ <td >Task disposition</td >
116
+ </tr >
117
+ <tr >
118
+ <td >`email`</td >
119
+ <td >The last email associated with the contact</td >
120
+ </tr >
121
+ <tr >
122
+ <td >`ended_at`</td >
123
+ <td >UTC timestamp when the conversation was ended</td >
124
+ </tr >
123
125
<tr >
124
126
<td >`from_number`</td >
125
127
<td >Phone number that sent the message</td >
126
128
</tr >
127
129
<tr >
128
- <td >`to_number `</td >
129
- <td >Phone number to which the message was sent</ td >
130
+ <td >`handle_time `</td >
131
+ <td >Full duration task was being handled, including talk time and wrap time (completed_at - started_at< td >
130
132
</tr >
131
133
<tr >
132
- <td >`media_url `</td >
133
- <td >Media URL (if it was an MMS) </td >
134
+ <td >`ip `</td >
135
+ <td >The IP address from where the subscription update was initiated. </td >
134
136
</tr >
135
137
<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 >
138
+ <td >`media_url `</td >
139
+ <td >Media URL (if it was an MMS )</td >
138
140
</tr >
139
141
<tr >
140
- <td >`campaign_friendly_id `</td >
141
- <td >Campaign Friendly Id as seen in the App </td >
142
+ <td >`notes `</td >
143
+ <td >Task notes </td >
142
144
</tr >
143
145
<tr >
144
- <td >`campaign_id `</td >
145
- <td >Campaign Id </td >
146
+ <td >`objections `</td >
147
+ <td >Task objections </td >
146
148
</tr >
147
149
<tr >
148
- <td >`campaign_name `</td >
149
- <td >Campaign Name </td >
150
+ <td >`phone `</td >
151
+ <td >The phone number the subscription update was applied to. Phone number is the unique identifier for a contact in Regal Voice </td >
150
152
</tr >
151
153
<tr >
152
154
<td >`queue`</td >
153
155
<td >Task Queue</td >
154
156
</tr >
157
+ <tr >
158
+ <td >`regal_voice_phone`</td >
159
+ <td >RegalVoice phone number</td >
160
+ </tr >
155
161
<tr >
156
162
<td >`scheduling_agent_fullname`</td >
157
163
<td >Full name of the agent who scheduled the Callback</td >
@@ -161,7 +167,24 @@ The table below lists events that Regal Voice sends to Segment. These events app
161
167
<td >Email of the agent who scheduled the Callback</td >
162
168
</tr >
163
169
<tr >
164
- <td >`target_agent_fullname`</td >
170
+ <td >`sms_conversation_id`</td >
171
+ <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 >
172
+ </tr >
173
+ <tr >
174
+ <td >`source`</td >
175
+ <td >Source of the subscription update.
176
+ A source value that starts with "Brand." indicates that the subscription update was initiated by the Brand (outside of the Regal Voice platform).
177
+ A source value that starts with "RegalVoice." indicates that the supscription update was initiated through the Regal Voice platform. </td >
178
+ </tr >
179
+ <tr >
180
+ <td >`started_at`</td >
181
+ <td >UTC timestamp when the conversation was started<td >
182
+ </tr >
183
+ <tr >
184
+ <td >`talk_time`</td >
185
+ <td >Duration of conversation (ended_at - started_at)<td >
186
+ </tr >
187
+ <td >`target_agent_fullname`</td >
165
188
<td >Full name of the agent who contact (and all contact’s tasks) are assigned to</td >
166
189
</tr >
167
190
<tr >
@@ -173,49 +196,25 @@ The table below lists events that Regal Voice sends to Segment. These events app
173
196
<td >Unique identifier for the task. Will match the call_id or sms_conversation_id of a completed task event.</td >
174
197
</tr >
175
198
<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 >
199
+ <td >`text`</td >
200
+ <td >The exact text the contact was presented for opt in</td >
186
201
</tr >
187
202
<tr >
188
- <td >`objections `</td >
189
- <td >Task objections </td >
203
+ <td >`timestamp `</td >
204
+ <td >Unix timestamp for when the event took place </td >
190
205
</tr >
191
206
<tr >
192
- <td >`notes `</td >
193
- <td >Task notes </td >
207
+ <td >`to_number `</td >
208
+ <td >Phone number to which the message was sent </td >
194
209
</tr >
195
210
<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 >
211
+ <td >`type `</td >
212
+ <td >Task Type </td >
198
213
</tr >
199
214
<tr >
200
215
<td >`wrapup_time`</td >
201
216
<td >Duration task was in wrap up (completed_at - ended_at)</td >
202
217
</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 >
219
218
</table >
220
219
221
220
## Adding Destinations
0 commit comments