Loading...
Loading...
Loading...
No, Tempo does not store any PII information on the agent’s personal mobile phone.
Yes, Tempo uses the following protocols to control user authentication:
Yes, Tempo for iOS uses platform-specific APIs to securely store the user’s authorization and refresh tokens. Tempo’s login credentials or the SSO is shared with the user along with the Genesys Cloud platform’s settings.
Tempo supports the basic authentication and OAuth integration. Any SSO support for Tempo has to come from the platform and authorization libraries. Tempo uses a web-based login screen, which the agents can use to access Tempo.
No. Genesys Cloud uses a single authentication infrastructure across all clients, which includes the web app, desktop app, and mobile applications like Tempo. They authenticate against the same platform using OAuth tokens, and all access the same backend APIs.
This means that features like IP allowlisting, SSO, and MFA policies are applied consistently, regardless of how the user logs in. If IP restrictions are in place and a mobile device’s IP is not allowlisted, the user will not be able to access Genesys Cloud through Tempo either.
No, Tempo for iOS does not send any data to third-party sites.
Genesys Tempo uses the automated crash reporting feature to collect generic data and a stacktrace. It uses non-fatal logging to log certain internal errors that are not expected. When we use non-fatal logging, we only include a stacktrace, which is an error message. PII is not included in the report.
Yes, Tempo uses TLS 1.2.
Tempo stores authentication data in the appropriately secure OS mechanism, while user preferences are stored using the appropriate OS preference API.
No, Tempo does not access any internet sites to provide functionality.
Yes, Tempo prevents any unmanaged applications from accessing the data.
No, the data in the mobile application is based on the web APIs.
No personal information is stored locally; only app-related settings are stored using the operating system’s secure preference APIs, such as preferences like enabling notifications. Authentication and refresh tokens are stored securely using platform-specific APIs, including the user ID.
Yes, Tempo supports FedRAMP compliance.
You can view your possible shifts for the days you do not have a published schedule, if you have the appropriate permission.
Navigate to the Settings page and use the Submit Feedback option to submit user feedback.
You can view your time balances on Genesys Tempo when you create time-off requests.
Click the Time-Off Balances icon to view the time-off categories along with the corresponding time-off balances.
Error message: The HRIS time-off integration is misconfigured. Contact your supervisor for additional support.
You see this message as HRIS time-off integrations are currently available only on the desktop version and not on Tempo. The issue does not impact existing functionality. You can see the HR system accrual balances on Tempo starting October 2023.
Yes. Genesys Tempo for iOS and Collaborate for iOS have independent logins.
You see the Error Getting User message if you are inactive and your administrator configures an inactivity timer for Genesys Cloud log in instances.
No. Currently, Genesys Tempo is only supported on iPhones. Genesys plans to support iPads in a later release.
You see the Missing Management Unit message if you are not assigned to a management unit. Contact your supervisor or your Genesys Cloud Administrator to inform them about the issue.
Tap Settings. Then tap FAQ.
You can also view the FAQs on the Genesys Cloud Resource Center.
Genesys Tempo includes schedule notifications when a schedule is added, changed, or removed. Also, Genesys Tempo provides time-off request notifications for approved or denied requests. Configure notifications in your device’s Settings application on your device.
To notify your manager that you are running late, to the upper right, tap Running late .
You can submit a running late request for your next work activity, such as, Meeting, On Queue, Off Queue or Training Activity Categories. If you submit a running late request before and activity that has the Activity Category Break or Meal the request will take effect as the beginning of the next scheduled work activity.
After you submit a running late request, you cannot submit another one for the same activity. The icon is enabled when there is a work-time activity within the next four hours and the activity cannot have a running late request applied already. Also, the icon is disabled after submitting five late explanations per day.
To trade a shift from the daily view, tap Trade or Drop.
You can use the same process from the weekly view.
To browse the available upcoming shifts, to the upper right, tap arrow .
No, Tempo does not send any data to third-party sites for processing. It uses Google Firebase to support app functionality, such as crash reporting. Firebase processes data only on behalf of Genesys and does not use it for its own purposes.
Genesys Tempo is a application that enables agents to perform the scheduling tasks.
At the bottom of the screen, tap Time Off. Then, to schedule a time-off request, to the upper right, tap Add .
Tap Time Off. The Summary tab appears. This tab displays your pending requests, any approved requests for this week, and your upcoming approved requests.
To see all of your requests, tap All Requests.
The following statuses are possible:
| Request Status | Definition |
|---|---|
| Pending | The request is awaiting manual intervention from an administrator. |
| Approved | Either an administrator or the system approved the request. When an administrator approves, the update is done manually and when the system approves, the update is done automatically based on auto-approval rules. |
Canceled | The request is canceled. |
| Denied | Administrator denied the request manually. |
| Waitlisted | The system could not approve the request automatically because it is waiting on limit availability. If availability appears before the waitlist window closes, the system auto-approves the request. |
Advance Time Elapsed | The request was not auto-approved because configured advance time for the waitlist has elapsed. |
Invalid Daily Duration | The system could not approve the request automatically because the daily duration that the agent requested does not comply with the agent’s scheduled hours. If the agent is not scheduled currently, the system checks the duration against the work plan to which the agent is associated. For work plan rotation, the system also chooses the correct work plan according to time-off request dates and assigned rotation. Note: If an agent is not currently scheduled to work, and is not associated with a work plan, then the time-off request is not automatically approved. The request remains in Pending status and requires an administrator’s manual intervention. |
| Outside Shift | The system could not approve the request automatically because it is not compatible with any work plan shift. |
Removed from Waitlist | Request is no longer associated to a waitlist. For example, when an agent moves to another management unit and there is no matching time-off plan set up for auto-approval in another management unit. |
| Auto Approved | Request is auto-approved by the system. |
| Insufficient Balance | Request is not auto-approved due to insufficient balance in the selected time-off type. |
| Pending – Restricted Activity Code | The system prevents auto-approval of requests when particular activity codes are present in the published schedule. These activity codes are selected as restricted activity codes. |
Currently, Genesys Tempo does not support the ability to create time-off requests with non-continuous dates. You can use the web app to create a time-off request with non-continuous dates.
You can use Genesys Tempo to view time-off requests with non-sequential dates.
When you log on to Tempo, the following indicators are possible:
| Pending Message | Definition |
|---|---|
| Your request is waitlisted. You are third in line on the waitlist. | Request duration and all other checks have passed. Currently, limits are not available on the dates selected. The system approves the request automatically when limits become available. |
| Your request was not auto-approved because the configured advance time for waitlist has elapsed. | The request is expired and the system cannot approve it automatically. |
| Your request was not auto-approved because the daily duration specified is not compatible with the scheduled or planned shift duration. | Requested duration did not pass the check against a published schedule or, if none exists, the work plan to which the agent is associated. The request requires manual intervention from an Admin for approval or denial. |
| Your request was not auto-approved because the partial day paid request is not compatible with any planned shift. | Requested partial day did not pass the check against a published schedule or, if none exists, the work plan to which the agent is associated. The request requires manual intervention from an Admin for approval or denial. |
With the current version, the permission check occurs when you log in or restart the app. If you log in before your access is disabled, you can continue to use the app until you restart the it. When you restart the app, a message informs you that your access is revoked.
To access latest update, make sure that your device includes the minimum supported versions: Android 7 (sdk 24) or iOS 13.
You can find a list of FAQs for Genesys Tempo for iOS here.