Skip to content

Commit ad55c3d

Browse files
author
markzegarelli
authored
Add verbiage about regional availablitly for Engage (#4864)
1 parent d5070de commit ad55c3d

File tree

2 files changed

+15
-1
lines changed

2 files changed

+15
-1
lines changed

src/engage/onboarding.md

Lines changed: 12 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,11 @@ This guide lists all required onboarding steps and walks you through Engage setu
1414
> info ""
1515
> The steps in this guide are only required if you plan to send email, SMS, and WhatsApp messages with Engage. Visit the [Engage Foundations Onboarding Guide](/docs/engage/quickstart) for general onboarding steps to set up your Engage space, connect sources, create audiences, and more.
1616
17+
> info "Regional Segment"
18+
> You can use Engage Premier on [Segment's regional infrastructure in the EU](/docs/guides/regional-segment/). Twilio Engage ensures data residency in the EU, but the channels you connect to, may not guarantee the same level of data residency. Check directly with the providers of the channels you use for information about data residency in their applications. Native channels like email and SMS, which use Twilio, are not data resident.
19+
>
20+
> Twilio is GDPR compliant, and has [Binding Corporate Rules](https://www.twilio.com/legal/binding-corporate-rules){:target="_blank"} to ensure that data is protected when it's transferred between countries.
21+
1722
## Before you begin: overview and task checklist
1823

1924
You’ll set up Twilio Engage in four stages:
@@ -233,7 +238,7 @@ To finish setting up your Messaging Service, you’ll now [configure an event we
233238

234239
1. Switch to the browser tab or window with your Engage workspace.
235240
2. Navigate to **Engage > Engage settings > Channels**. Under **SMS Service with Twilio**, click the **Get Started** button.
236-
3. The **Set up and valide your Twilio account** overlay appears (pictured below). Click the **Copy webhook URL** button. Your computer copies the URL to your clipboard.
241+
3. The **Set up and validate your Twilio account** overlay appears (pictured below). Click the **Copy webhook URL** button. Your computer copies the URL to your clipboard.
237242

238243
![Engage webhook URL](images/engagewebhook.png "Engage webhook URL")
239244

@@ -285,6 +290,12 @@ You'll now create a messaging service to connect your number to Engage:
285290

286291
Your WhatsApp messaging service is now created.
287292

293+
## Regional Segment
294+
295+
You can use Engage Premier on [Segment's regional infrastructure in the EU](/docs/guides/regional-segment/). Twilio Engage ensures data residency in the EU, but the channels you connect to, may not guarantee the same level of data residency. Check directly with the providers of the channels you use for information about data residency in their applications. Native channels like email and SMS, which use Twilio, are not data resident.
296+
297+
Twilio is GDPR compliant, and has [Binding Corporate Rules](https://www.twilio.com/legal/binding-corporate-rules){:target="_blank"} to ensure that data is protected when it's transferred between countries.
298+
288299
## Next steps
289300

290301
With configured accounts and services for all platforms, you’ve completed Engage onboarding and are ready to create and send campaigns to your users.

src/engage/quickstart.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,9 @@ This guide walks you through the set up process for a simple Engage space, which
1010
> success ""
1111
> The first four steps in this guide also apply to Unify set up. To learn more, visit the [Unify Onboarding Guide](/docs/unify/quickstart).
1212
13+
> info "Regional Segment"
14+
> Engage Foundations is available on Segment's regional infrastructure. For more information, see the article [Regional Segment](/docs/guides/regional-segment/).
15+
1316
## Engage configuration requirements
1417
> info ""
1518
> Engage requires both [Connections](/docs/connections/) and [Unify](/docs/unify/).

0 commit comments

Comments
 (0)