The boss performance review is the end-of-day evaluation. It can show earnings and individual performance, replay parts of calls, comment on what players said and announce content for later workdays. Check the actual quota and final result rather than deciding you failed because the boss insulted your conversation.
Missing the daily quota can lead to firing. A high individual grade or a funny replay is not a substitute for checking the team outcome. The exact scoring formula, replay-selection rules and complete consequences are not established for every current build.
Reach the review from the workday
Use the current day-ending or clock-out control when you are ready to finish the shift. Follow any group instructions displayed in your build, then move into the review sequence and use the seating or interaction prompt provided there.
Do not assume that ending a day submits unfinished app actions. Check your credited earnings before leaving a call. A caller agreeing to pay is not the same as a completed transaction, and the review evaluates the result the game has recorded.
Read the result in separate parts
The review can mix several kinds of information into one sequence. Keep them separate so a joke or an individual grade does not obscure the outcome.
| Review element | What to use it for |
|---|---|
| Earnings or quota result | Determine what the workday actually achieved. |
| Individual performance labels or grades | Compare player contributions without assuming they guarantee team success. |
| Replayed call audio | Hear selected parts of the conversation. |
| Boss commentary | Understand the game’s response to that dialogue; it is not a complete scoring formula. |
| Later-content announcement | Check what to look for in the next workday or shop. |
A successful payment can still receive mocking commentary. The review’s tone is deliberately harsh, so praise or insults alone are poor completion checks. Read the displayed or announced outcome.
Understand why calls are replayed
The review can replay portions of player and caller dialogue, including teammates’ calls in co-op. That can make a successful interaction sound awkward when a small fragment is isolated from the full conversation.
Do not infer a universal rule from one replay. The available information does not establish that every call is reviewed, that every selected line changed a score, or that the boss’s criticism explains the whole calculation.
If you want to improve the next shift, use the replay to notice a concrete issue you can check: a contradictory story, an unclear request, an unrelated demand or a voice-transcription misunderstanding. Then compare that with the task’s actual outcome. A joke that sounded strange can still have completed a payment, while a smooth conversation can still leave an app step unfinished.
Check whether the day passed
Use the final quota or workday result to determine whether the run advances. The game’s stated consequence for failing the daily quota is firing. There is no verified rule that a particular individual grade alone causes firing, nor a complete current formula tying every insult to a numerical penalty.
If the outcome surprises you, inspect what you can verify: whether the team target was covered, whether transactions were credited and whether any incident interrupted the workday. Do not adopt a character’s improvised explanation or a player’s guess as a confirmed reason.
A strong personal contribution can coexist with a failed overall result. Keep that distinction in mind when reviewing a co-op day, especially if the sequence highlights only one player at a time.
Follow later-content announcements
The boss can announce new scams or tools for upcoming workdays. Note the item and timing, then inspect the current shop when it becomes available. Some listings can be free claims, while others have a price.
An announcement is not proof that the app has already appeared on your desktop. Check the listing, complete any required claim or purchase, and confirm that the task is accessible before using it in another call.
Unlock schedules have changed across builds, so the current review is more useful than an old fixed calendar. This page does not assign particular scams to universal numbered days.
Recognize a technical review interruption
Official hot fixes address boss-review timeout errors, including cases involving pausing or replacing a replay. If the sequence stalls, check that the game is updated before interpreting the delay as a normal gameplay outcome.
A fix announcement does not guarantee that every future stall is solved. Distinguish an unresponsive review from the boss still playing a recording or speaking. If a problem continues, record the point where the sequence stopped and whether it followed a pause or replay change; those details are more useful than treating the stall as a hidden score penalty.
Complete the review when the game’s controls allow it, then check the next workday state. That confirms the transition more clearly than the boss’s tone or one isolated performance label.