Skip to content

Commit a1c6acd

Browse files
committed
[netlify-build]
1 parent 6491c21 commit a1c6acd

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/unified-profiles/connect-a-workspace.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ If you already have a Segment workspace, you can use a new or pre-existing [Segm
2020
## Step 1: Set up your Unify space
2121

2222
> success ""
23-
> This section is about setting up a new Segment Unify space to link to Twilio Flex. If you have an existing Segment Unify space you'd like to use, proceed directly to [Step 2: Connect your data to Unify](#step-2-connect-your-data-to-unify). If your Unify space includes a Salesforce source, RETL source, and a Segment Profiles destination already configured, proceed directly to [Step 3: Connect Flex to your Unify space](#step-3-connect-flex-to-your-unify-space).
23+
> This section is about setting up a new Segment Unify space to link to Twilio Flex. If you have an existing Segment Unify space you'd like to use, proceed directly to [Step 2: Connect your data to Unify](#step-2-connect-your-data-to-unify). If your existing Unify space includes a Salesforce source, RETL source, and a Segment Profiles destination, proceed directly to [Step 3: Connect Flex to your Unify space](#step-3-connect-flex-to-your-unify-space).
2424
2525
Segment recommends creating a development or sandbox Unify space, verifying that your profiles appear as you would expect, and then creating a production Unify space.
2626

0 commit comments

Comments
 (0)