Update name for Regal Voice (#3688)

* Update name for Regal Voice

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

Co-authored-by: stayseesong <[email protected]>

Author: tcgilbert

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

@@ -1,28 +1,28 @@
 ---
 rewrite: true
-title: Regal Voice Destination
+title: Regal.io Destination
 id: 5f33e746fad0d620b8a4b144
 ---
-[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.
+[Regal.io](https://www.regal.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners){:target="_blank"} is a next-gen customer engagement platform that helps 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](mailto:[email protected]).
+Regal.io maintains this destination. For any issues with the destination, contact their [Regal.io support team](mailto:[email protected]).
 
 > note "Note:"
-> Regal Voice is available in the U.S only.
+> Regal.io is available in the U.S only.
 
 > note "Note:"
-> The Regal Voice Destination is in beta, which means that they are still actively developing the destination. To join the beta program, or if you have any feedback to help improve the Regal Voice Destination and its documentation, [contact the Regal Voice support team](mailto:[email protected])! 
+> The Regal.io Destination is in beta, which means that they are still actively developing the destination. To join the beta program, or if you have any feedback to help improve the Regal.io Destination and its documentation, [contact the Regal.io support team](mailto:[email protected])! 
 
 
 ## Getting Started
 
 {% include content/connection-modes.md %}
 
 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.
+2. Search for "Regal.io" in the Destinations Catalog, and select the "Regal.io" destination.
+3. Choose which Source should send data to the "Regal.io" destination.
 4. Email [email protected] to get your "API key".
-5. Enter the "API Key" in the "Regal Voice" destination settings in Segment.
+5. Enter the "API Key" in the "Regal.io" destination settings in Segment.
 
 
 ## Page
@@ -33,7 +33,7 @@ If you are not familiar with the Segment Specs, take a look to understand what t
 analytics.page()
 ```
 
-Segment sends Page calls to Regal Voice as a pageview. 
+Segment sends Page calls to Regal.io as a pageview. 
 
 
 ## Screen
@@ -44,7 +44,7 @@ If you are not familiar with the Segment Spec, take a look to understand what th
 [[SEGAnalytics sharedAnalytics] screen:@"Home"];
 ```
 
-Segment sends Screen calls to Regal Voice as a screen. 
+Segment sends Screen calls to Regal.io as a screen. 
 
 
 ## Identify
@@ -59,19 +59,19 @@ analytics.identify({
 });
 ```
 
-Segment sends Identify calls to Regal Voice as an identify event.
+Segment sends Identify calls to Regal.io as an identify event.
 
-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.
+Identify events are used to create users and update user attributes. If an identify event contains a phone, Regal.io will create a contact in your Audience.
 
 ## Track
 
 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. 
 
-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 recommends calling `track` on any user or system event that you may want Regal.io 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 all attributes relevant to your use case into the `properties` object. 
+Segment sends `track` calls to Regal.io as a track event. Pass all attributes 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. 
+Regal.io 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).
 
@@ -88,13 +88,13 @@ analytics.track('Loan Application Approved', {
 
 ## Collecting OptIn
 
-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.
+In order to trigger outbound calls or sms messages from Regal.io, you must collect the user's explicit opt-in for those channels along with the user's phone number.
 
-There are 2 options for how you can let Regal Voice know a user has opted in:
+There are 2 options for how you can let Regal.io know a user has opted in:
 
-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.)
+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.io 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.io to subscribe a user, there must already be a phone provided for that user.)
 
-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.
+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.io by adding an optIn object.
 
 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:
 
@@ -126,6 +126,6 @@ Supported messaging channels are: `sms`, `voice` and `email`.
 
 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) 
 
-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. 
+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.io ignores opt-ins that do not have a `timestamp` date. 
 
 ---