Join the Beyond experts for tactical training on how to release Beyond to their Agents and how to take advantage of the classified Beyond functionality not available in Enterprise. Attendees will leave with the knowledge that allows them to accomplish their Beyond Roll-Out Mission.

1. Beyond Base Camp
Presented by:
Shawna Evans
Steve Patton

2. Agenda
• How Beyond implementations happen
• What to know before you begin
• What we need from you
• Recommendations for Beyond roll-out

3. How Beyond implementations happen
Beyond Implementation Data Conversion
1. Reach out to your Account Manager
- Be prepared to discuss your intended use of Beyond
2. TempWorks resources are assigned
3. Discuss roll-out plan

4. What to know before you begin
It’s up to you to decide how big or small of a project your
Beyond implementation is.
• Do you need custom reports to be included in Beyond?
• What task system do you plan on utilizing moving forward?
• What user base will be utilizing Beyond?
• How deep do you want to dive into security?
• How critical is the use of new Beyond functionality?
• Integrations – what is compatible with Beyond?

5. What we need from you
✓A list of mission critical Beyond reports
✓Define your unique groups of Agents
✓Sales Reps, Recruiters, Administrators
✓A further breakdown of Teams of Agents
✓Minnesota Recruiters, California Recruiters
✓Confirmation on how Beyond specific functionality will be
utilized

6. Defining Agent Groups

7. Security in
Beyond

9. Security - Permission
• Beyond accessible without being a member.
• Dictates what user can do in Beyond.
• Where defined roles come in.
• i.e. Admin, Recruiter, Sales, Payroll

10. Security - Reports
• Default groups exist.
• Flexible opportunity to
customize.
• Need mission critical custom
reports from Enterprise?

11. Security – Message Action Type
• New(er) functionality
• Message actions assigned Message action Type
• Group determines Read/Write capabilities.
• Ex. “Spy Compromised” message action with a type of “Sales” can be read-
only for unsecure group, but secure could create and edit the action.

12. Security – Document Type
• Read / Write / Delete
• Who Uploads?
• Who needs access?
• Who removes old documents?

13. Security – Customer Status
• Staffing Specialist vs. Sales
• Unchecked options will not be available in Beyond’s drop down.

14. Security – Custom Data
• Have classified
Custom data?
• Note again the
ability to deny read
and write access.

15. Security – Adding Members

16. Beyond Teams

17. Service Rep Team Structures
• Members of a branch
• Members of a role
• Regional based teams
• Strategic teams
• Executive teams
• Secret Intelligence Service (MI6)

18. Creating Teams in Beyond

19. Team Functionality
• Task Distribution
• Shared Dashboards
• Message Stream
• Tasks

20. Team Task Distribution

21. Team Dashboards
• Limit scope of Message
stream to only messages
logged by your team.
• See tasks that have been
assigned to your team.
• Can create multiple
custom dashboards and
bounce between them.

22. Status Change Workflow – Rule Request
You’ll need to define the following…
1. The record type that is being effected
2. What is required for a record status
3. Is the rule required?
4. At what hierarchy level does the rule exist?
5. What does the rule check for?

23. Status Change Workflow – Messages
You’ll need to define the following…
1. The record type that is being effected
2. What is required for a record status?
3. Can service reps edit the message?
4. Is it required to log the message?
5. What message action code should be used?
6. What message text should default?

24. Status Change Workflow – Tasks
You’ll need to define the following…
1. The record type that is being effected
2. What is required for a record status
3. Can service reps edit the task?
4. Is the task creation required?
5. Determine default task settings:
- Subject, Note, Priority, Tags, Due Days, Assigned Teams, Specific
Assigned Rep
6. What is the task hierarchy?
7. Is the task public or private?

25. Recommendations for a Beyond Roll-Out
Start small.
• Decide what is a must have vs. what is a nice-to-have
• Permissions? Must have.
• Status change workflows? Nice-to-have.
• Beta release Beyond to branch or role
• Atlanta Office goes live first
• Sales Execs. utilize Beyond first
• Collect feedback from users
• What do they love about Beyond? What do they miss from Enterprise?
• Share your feedback with us on the Beyond Community Hub!
• Live Beyond clients are invited access to the Beyond category of the Hub

26. Questions?