Merge branch 'master' into develop

stayseesong · web-flow · commit 885007626c90 · 2023-06-13T10:02:18.000-07:00
diff --git a/src/_data/sidenav/main.yml b/src/_data/sidenav/main.yml
@@ -410,6 +410,8 @@ sections:
       title: Email Campaigns
     - path: '/engage/campaigns/sms-campaigns'
       title: SMS Campaigns
+    - path: '/engage/campaigns/broadcasts'
+      title: Broadcasts
     - path: '/engage/campaigns/whatsapp-campaigns'
       title: WhatsApp Campaigns
   - path: '/engage/analytics'
diff --git a/src/engage/campaigns/broadcasts.md b/src/engage/campaigns/broadcasts.md
@@ -0,0 +1,90 @@
+---
+title: Broadcasts
+plan: engage-premier
+---
+
+> info ""
+> Broadcasts are in public beta.
+
+Broadcasts are one-time email or SMS campaigns that you can send with Twilio Engage. Use broadcasts for single, one-off occasions like the following:
+
+- **Special events**, like webinars or conferences
+- **Offers**, like product discount codes
+- **Newsletters** that you want to send on a specific date
+
+For more on the different types of Engage campaigns, read [Audiences, Journeys, and Broadcasts](/docs/guides/audiences-and-journeys/).
+
+On this page, you'll find step by step instructions for how to create a broadcast.
+
+## Create and send an email broadcast
+
+Follow these steps to create an email broadcast:
+
+1. Navigate to **Engage > Broadcasts**, then click **+ Create broadcast**. 
+2. From the **New broadcast** page, choose **Email**.
+3. Add a name and description, then click **Choose recipients**.
+4. Click **Add condition** to add users who will receive your campaign, then click **Build**.
+    - To send a message to a pre-built audience, choose `Part of an Audience`, then select the audience.
+5. Select **Build a new email** or use an email template, then click **Continue**.
+6. Fill out the **Email settings** fields, choose your email editor, then click **Continue**.
+7. Configure your email, then click **Continue**.
+8. On the **Review and schedule** page, confirm your broadcast's settings.
+9. Schedule your broadcast:
+    - To send your broadcast immediately, select **Send now**, then click **Send now ->**. Confirm a final time by clicking **Send** in the popup.
+    - To send your broadcast later, select **Schedule**, then enter the date, time, and time zone for your scheduled broadcast. Click **Schedule ->**, then confirm by clicking **Schedule** in the **Schedule message** popup.
+
+
+## Create and send an SMS broadcast
+
+Follow these steps to create an email broadcast:
+
+1. Navigate to **Engage > Broadcasts**, then click **+ Create broadcast**. 
+2. From the **New broadcast** page, choose **SMS**.
+3. Add a name and description, then click **Choose recipients**.
+4. Click **Add condition** to add users who will receive your campaign, then click **Build**.
+    - To send a message to a pre-built audience, choose `Part of an Audience`, then select the audience.
+5. Select **Build a new SMS** or use an SMS template, then click **Continue**.
+6. Choose a messaging service, enter your message into the body field, and add any merge tags. 
+7. Test your SMS, then select **Review and schedule**.
+8. On the **Review and schedule** page, confirm your broadcast's settings.
+9. Schedule your broadcast:
+    - To send your broadcast immediately, select **Send now**, then click **Send now ->**. Confirm a final time by clicking **Send** in the popup.
+    - To send your broadcast later, select **Schedule**, then enter the date, time, and time zone for your scheduled broadcast. Click **Schedule ->**, then confirm by clicking **Schedule** in the **Schedule message** popup.
+
+### Cancel a scheduled broadcast
+
+Follow these steps to cancel a scheduled broadcast:
+
+1. Navigate to **Engage > Broadcasts > Scheduled**. 
+2. Select the scheduled broadcast you want to cancel.
+3. From the broadcast overview tab, click **Unschedule**.
+4. In the popup, click **Unschedule** to confirm.
+
+Unscheduled broadcasts revert to draft status and can be found under the Drafts tab of the Broadcasts page.
+ 
+## Working with broadcasts
+
+Keep the following information in mind as you work with broadcasts.
+
+### SMS segments
+
+SMS broadcasts longer than 160 characters are split into segments and then joined together by the recipient's device. As a result, you can send SMS broadcasts longer than 160 characters, but each 160-character segment is billed individually. 
+
+For more on message segments, view [SMS character limits](https://www.twilio.com/docs/glossary/what-sms-character-limit){:target="_blank"}.
+
+### Scale and throughput
+
+The following table lists geographic availability, scale, and speed details for email broadcasts and [short code SMS](https://support.twilio.com/hc/en-us/articles/223182068-What-is-a-Messaging-Short-Code-){:target="_blank"} broadcasts:
+
+| Broadcast type | Availability                            | Throughput                                                                 |
+| -------------- | --------------------------------------- | -------------------------------------------------------------------------- |
+| Email          | All countries where Engage is available | 1 million per hour                                                         |
+| SMS short code | US, Canada, UK                          | 360,000 per hour                                                            |
+
+Long-code message throughput depends on a number of factors, including your [10DLC trust score](https://support.twilio.com/hc/en-us/articles/1260803225669-Message-throughput-MPS-and-Trust-Scores-for-A2P-10DLC-in-the-US){:target="_blank"}. 
+
+Segment recommends that you use short code phone numbers for SMS broadcasts sent to more than 5000 recipients.
+
+## Broadcast analytics
+
+Engage tracks analytics for both email and SMS broadcasts. For more information on Engage analytics, view [Analytics Overview](/docs/engage/analytics/).
diff --git a/src/engage/images/broadcasts.png b/src/engage/images/broadcasts.png
diff --git a/src/guides/audiences-and-journeys.md b/src/guides/audiences-and-journeys.md
@@ -1,15 +1,15 @@
 ---
-title: Audiences and Journeys
+title: Audiences, Journeys, and Broadcasts
 plan: engage-foundations
 ---
 
-Audiences and Journeys are fundamental to [Twilio Engage](/docs/engage/). Both let you segment your users, send them personalized content, and show them ads from platforms like Facebook or Google.
+Audiences, Journeys, and Broadcasts are fundamental to [Twilio Engage](/docs/engage/) and let you segment your users, send them personalized content, and show them ads from platforms like Facebook or Google.
 
-In this guide, you’ll learn how to choose between an Audience and a Journey for a number of marketing use cases across the customer lifecycle.
+In this guide, you’ll learn how to choose between an Audience, a Journey, and a Broadcast for a number of marketing use cases across the customer lifecycle.
 
 ## Back to basics
 
-First, consider the following definitions for an Audience and a Journey.
+First, consider the following definitions for an Audience, Journey, and Broadcast.
 
 ### Audience
 
@@ -23,39 +23,45 @@ A [Journey](/docs/engage/journeys/) is a logic-driven workflow that progresses u
 
 As with Audiences, Segment can sync users to Destinations at designated points in the Journey. Unlike an Audience, a Journey can send users to Twilio Engage’s [native email and SMS channels](/docs/engage/campaigns/).
 
+### Broadcast
+
+A [Broadcast](/docs/engage/campaigns/broadcasts) is a one-time SMS or email campaign sent to a group of users. Whereas Segment continously updates Audience membership, Segment only calculates the users who will receive your Broadcast once. Marketers commonly use Broadcasts for newsletters, promotional campaign, and events.
+
 ## Engage and the customer lifecycle
 
-The customer lifecycle provides a helpful framework for thinking about Audiences and Journeys.
+The customer lifecycle provides a helpful framework for thinking about Audiences, Journeys, and Broadcasts.
 
 ![A flow chart of the digital marketing lifecyle](images/digital_marketing_lifecyle.png "Digital Marketing Lifecycle Funnel")
 
-Engage Audiences tend to be most effective at the top of the customer lifecycle funnel, where brand awareness and discovery occurs.
+Audiences and Broadcasts tend to be most effective at the top of the customer lifecycle funnel, where brand awareness and discovery occurs.
 
 A Journey becomes a better option as customers progress down the funnel, where a more complex strategy involving messaging, social ads, and newsletters helps move customers closer to conversion.
 
-## Choosing between an Audience and a Journey
+## Choosing between Audiences, Journeys, and Broadcasts
 
 With the customer lifecycle in mind, use the following table as a starting point for selecting an Audience or Journey for common marketing use cases:
 
-| Use Case                                        | Audience or Journey |
-| ----------------------------------------------- | ------------------- |
-| I want to send email and SMS campaigns.         | Journey             |
-| I only have one intended touchpoint.            | Audience            |
-| I need branching logic.                         | Journey             |
-| I want to run A/B tests.                        | Journey             |
-| I want to re-target customers with the same ad. | Audience            |
+| Use Case                                         | Audience, Journey, or Broadcast |
+| ------------------------------------------------ | ------------------------------- |
+| I want to send email and SMS campaigns.          | Journey or Broadcast            |
+| I want to send a one-time email or SMS campaign. | Broadcast                       |
+| I only have one intended touchpoint.             | Audience or Broadcast           |
+| I need branching logic.                          | Journey                         |
+| I want to run A/B tests.                         | Journey                         |
+| I want to re-target customers with the same ad.  | Audience                        |
+
 
 While these suggestions will work for most use cases, you may need to consider other factors before you implement your own campaign. Asking the following questions will help you identify the right approach.
 
 ### Over the course of a campaign, how many touchpoints do I want to create?
 
-Audiences work best for single, one-off messages or touchpoints. If you need a campaign with time delays and branching logic, opt for a Journey.
+Audiences and Broadcasts work best for single, one-off messages or touchpoints. If you need a campaign with time delays and branching logic, opt for a Journey.
 
 For example, an Audience works well if you want to show a single ad when a user abandons a cart. If, however, you want to show an ad, wait several days, then send the user an email if they’ve not completed their purchase, go with a Journey.
 
 ### Do I want to use Engage Premier Channels like SMS and email?
 
-All messaging through [Engage Premier Channels](/docs/engage/#market-to-customers-with-engage-premier-and-channels) takes place in Journeys. If you’d like to send an SMS or email campaign to a customer, use a Journey.
+You can message users with [Engage Premier Channels](/docs/engage/#market-to-customers-with-engage-premier-and-channels). If you’d like to send an SMS or email campaign to a customer, use a Journey.
 
 ### Do I need branching logic?
 
@@ -73,4 +79,4 @@ Audiences, on the other hand, admit users whenever they meet the Audience’s cr
 
 ## Putting it together
 
-With this guidance in mind, take your next steps with Engage by learning [how to build a Journey](/docs/engage/journeys/build-journey/) and [work with Engage Audiences](/docs/engage/audiences/).
+With this guidance in mind, take your next steps with Engage by learning [how to build a Journey](/docs/engage/journeys/build-journey/), [work with Engage Audiences](/docs/engage/audiences/), and [send a Broadcast](/docs/engage/campaigns/broadcasts/).
diff --git a/src/privacy/hipaa-eligible-segment.md b/src/privacy/hipaa-eligible-segment.md
@@ -4,6 +4,7 @@ title: HIPAA Eligible Segment
 
 Segment is a HIPAA eligible platform, and meets the data privacy and security requirements of healthcare customers and their stakeholders. For more information about Segment becoming HIPAA eligible, see the [announcement blog post](http://segment.com/blog/segment-for-healthcare){:target="_blank"}.
 
+
 ## Business Associate Addendum
 
 > info ""
@@ -18,4 +19,16 @@ Ensure your Workspace is eligible for HIPAA before you configure and send any pe
 1. In your Workspace, navigate to **Settings > Workspace Settings**.
 2. On the **General Settings** tab, ensure that the HIPAA badge appears. This badge confirms that the Workspace is HIPAA eligible. ![HIPAA Eligible](images/hipaa-eligible.png)
 
-With the BAA signed and Workspace confirmed as eligible, you can start building. For more information about starting a HIPAA compliant implementation, see Twilio's [Architecting for HIPAA on Twilio](https://twil.io/architecting-for-hipaa){:target="_blank"}, which outlines the shared responsibilities and requirements for building and maintaining HIPAA-compliant workflows in Segment.
+With the BAA signed and Workspace confirmed as eligible, you can start building. For more information about starting a HIPAA compliant implementation, see Twilio's [Architecting for HIPAA on Twilio](https://twil.io/architecting-for-hipaa){:target="_blank"}, which outlines the shared responsibilities and requirements for building and maintaining HIPAA-compliant workflows in Segment.
+
+## HIPAA Auditing
+Segment maintains audit logs of every read and update action a user performs in the Segment app that may involve PHI/PII. 
+
+Data captured in the HIPAA audit logs includes:
+ - `workspace_id`: unique identifier of the workspace
+ - `actor_user_id`: unique identifier Segment assigns to the logged in user
+ - `event_type`: The action performed by the user. For example, `Source Debugger Raw Viewed`, `Destination Filter Modified`, or other events
+ - `end_user_id`: Segment sometimes assigns this unique identifier to an end-user, event, audience, or journey, depending on the event type
+ - `timestamp`: Time in UTC when the action occurred
+
+These logs can be provided upon request. For specific requests, please reach out to [friends@segment.com](mailto:friends@segment.com){:target="_blank"}.
