Handling Emergencies: Grace & In-Session Exits
[MANDATORY PLATFORM STANDARD]
Aleksandra
Last Update 3 months ago
We understand that life happens, and emergencies can occur at any time – sometimes even during a live session! This policy covers how Yo! handles these unexpected events, from unforeseen circumstances that lead to grace cancellations, to actual emergencies that might require you to leave a session early.
1. Covering Unforeseen Events: Grace Cancellations
We understand that life happens and emergencies can occur. The Grace Cancellations built into the system (as detailed in our Reliability System: Cooldowns & Grace Cancellations policy) are designed to cover these very situations—whether it's a sudden illness, a tech problem, or any other unforeseen event.
The system automatically gives you a buffer of 3 Reported and 1 Unreported cancellations each pay cycle that do not trigger immediate cooldowns. There is no need to contact support or provide documentation for these. As an independent professional, you are responsible for managing your schedule and using this built-in buffer wisely.
2. Handling In-Session Events
We understand that emergencies can happen during a live session. Here is how the platform handles these rare situations.
The Correct Way to Leave a Session: If you must leave a session early for a personal emergency, the only correct way to do so is by using the 'Leave' button inside the Yo! Zone.
Failing to use this button (for example, by closing the browser tab or shutting down your computer) is a violation of our standard procedure. This may result in the session being processed incorrectly, which could impact your metrics and payment.
💡How the System Handles Your Early Departure: The automatic outcome of your departure is determined by your total time present in the session.
➡️A Note on Punctuality: The 20/40-minute markers mentioned below refer to your actual time present in the session. The 2-minute grace period for lateness is for entry only; any time you arrive late will delay the moment you reach these presence milestones.
⭐If you must leave EARLY (before reaching a presence time of at least 20 minutes for 25-minute sessions and 40 minutes for 50-minute sessions):
Politely inform the yoser. We suggest saying something like: "I'm very sorry, but due to an unforeseen emergency, I need to leave our session now. Our system will process the final status of the session, and you will be notified of the outcome on your dashboard and via email shortly. Thank you for your understanding."
Use the 'Leave' button to exit the Yo! Zone.
Outcome: The system will automatically end the session 5 minutes after you leave. The session will be tagged as a Reported Cancellation and will count towards your reliability metrics. The yoser will receive their ticket back.
Disclaimer: To avoid providing incorrect information, you should never state what will happen with the yoser's tickets. Our system will handle all notifications. If the yoser has questions, they should be directed to Yoser Support.
⭐If you must leave LATE (after reaching a presence time of at least 20 minutes for 25-minute sessions and 45 minutes for 50-minute sessions):
A Note on the "45-Minute" Mark for 50-Minute Sessions: You might wonder why this rule applies after 45 minutes, not 40 (the 80% mark). This is due to a platform rule: if you leave for 5 consecutive minutes at any point before the 45-minute mark, the session is automatically canceled by the platform as a Reported Cancellation. Our special "Late Departure" policy below only applies in the final 5-minute window where that automatic cancellation can no longer occur.
We don't expect this scenario to happen, especially with so little time left to finish the session. Even so, it's important to understand the impact of this action.
Because the yoser received the majority of the service, their ticket will not be replaced. However, leaving early still breaks their fair expectation of a complete session, which can damage your reputation with that yoser and your overall reliability of the Yo! platform.
For this reason, this action must be treated as a last resort for true emergencies only. If it happens, here is the proper procedure:
Politely inform the yoser. Using the same script as above is the safest way to manage expectations.
Use the 'Leave' button to exit the Yo! Zone.
Outcome: To be fair while maintaining quality standards, the system handles this as follows:
The first time this occurs within a pay cycle, the session's status will remain Finished.
For any subsequent occurrences in the same cycle, the session's status will be automatically re-tagged as a Reported Cancellation.