Broadcasts are created by Global Users or Team Admins and are generally sent from the OurPeople Console. Broadcasts can be sent immediately or scheduled to be sent at a later date and time.
Don't know what Broadcasts are? Please read the Broadcast Overview documentation.
To create a Broadcast:
STEP 1: From the Navigation menu, select Broadcasts or click the "Create Broadcast" Quick action.
STEP 2: Click the Create button.
The Create Broadcast screen will load. Click the Add Content button to bring down another menu with all of the cards you can create.
STEP 3: Click the content you want to create
In the above example, the Team Admin dragged in a Text card. This is limited to 700 characters, so as the message is typed, the number will count down automatically. Clicking Normal will display a dropdown menu of text formatting options.
Dependent on the type of communication, the Team Admin or Global User has a number of Broadcasts cards at the bottom of the screen. There are a number of different types and further documentation on each can be viewed at the below links:
STEP 4: Type your Broadcast Content
Note: The Title of the Broadcast is visible at the top of the screen. In this example, the first line of the message has automatically been added as the Broadcast Title. This can be changed by clicking on the title box.
Over to the top right of the card are shortcut keys to help Copy a card or Delete a card from the Stack.
You have the option to Add Content into the build if required, this creates a Stack. Add more Cards as desired by clicking on Add Content and choosing from the drop-down.
Stacks are limited to a maximum of 30 cards.
All cards can be added as a single broadcast but multiple broadcast cards sent together, will automatically create a "Broadcast Summary" card beneath the Add Content button. (pictured above)
STEP 6: When all content has been added to the Build, click the Continue button.
Progress to Creating a Broadcast Step 2: Define Audience
Don't know what Broadcasts are? Please read the Broadcast Overview documentation.
Comments
0 comments
Article is closed for comments.