Worker App Support Escalation: Restore Access, Verify Records

Assign one case owner and separate recovery from correction

Use the support case recovery record below as your shared operating artifact. It is an editorial template, not a native Teambridge feature or an official Teambridge support procedure. Keep it in an approved location with access limited to the people handling the case.

Operations owns the case through closure. The supervisor approves temporary arrangements, while the account administrator, scheduler, or time approver handles the relevant investigation and authorized changes.

Recovery record field	What to enter
Case ID and worker reference	Unique case reference and approved worker identifier
Affected work	Shift reference, work date, site, and affected time record if applicable
Symptom	Failed task, exact error if available, and first observed time
Operational deadline	Next affected shift, workaround expiry, or relevant payroll cutoff
Evidence	Timestamps, observed behavior, and restricted evidence links
Operations owner and backup	Named people accountable for coordination and worker updates
Technical responder	Investigator, acceptance time, and next response commitment
Authorized record owner	Person permitted to approve or change the affected record
Temporary workaround	Approved alternate arrangement and approving supervisor
Workaround expiry	Time the arrangement must be renewed, replaced, or ended
Task recovery status	Unresolved, temporarily supported, or restored, with evidence
Correction status	Pending, saved awaiting approval, verified, or no change required
Verification evidence	Worker task test, saved record check, approval, and duplicate check where relevant
Next worker update	Owner, channel, and promised update time
Closure	Verification time, worker notification, and remaining exceptions

Keep recovery and correction in separate fields even when the same person investigates both. If no record change is needed, record what was checked and why the existing record is correct. Do not leave the correction field blank and assume that means resolved.

Restored app use is a recovery event. Verified records are a separate closure requirement.

Route the symptom before escalating a suspected app defect

Start with the failed task rather than the worker's diagnosis. “The app is broken” could mean an account problem, an assignment that was never saved, or a clock action that did not produce the expected record.

Route each symptom to the person who can inspect its source:

• Account access: The account administrator checks the intended account and configured access.
• Missing shift: Scheduling checks the authoritative assignment and relevant visibility configuration.
• Time capture: The time approver checks existing entries and the evidence needed for any correction.

Operations retains worker communication across these routes. A handoff counts as accepted only when the recipient acknowledges ownership and supplies a next update time. Forwarding a message is not acceptance; if no one accepts, the operations owner uses the designated backup or manager escalation path.

This distinction is consistent with the narrow example of When I Work's troubleshooting resources, which organize help around different symptoms. Its mobile time clock guide also distinguishes actions that require manager or administrator privileges. That supports routing by task and authority, not a claim about every vendor's support process.

Prioritize by the next operational consequence. A worker unable to access an imminent assignment needs a faster decision than a resolved display issue with no remaining record discrepancy. Agree escalation intervals locally, record the deadline, and never present those intervals as vendor response guarantees.

Recover account access without borrowing credentials

The account administrator should investigate the intended worker account using the organization's approved identity verification and recovery procedures. Required access belongs to the administrator authorized to inspect or change that account, not to whichever supervisor happens to receive the message.

While access remains unresolved, the supervisor may verify identity and assignment through an authorized alternate channel. That can support an approved arrival arrangement. It does not restore the account, grant additional permissions, or justify borrowing another worker's credentials.

For an unresolved technical issue, send the responder a compact evidence package:

• Time of failure, including the time zone.
• Device, operating system, and app version where available.
• Exact failed task, error text, and reproduction steps.
• Appropriately redacted screenshots and the affected record references.

Never collect passwords in the case record. Restrict screenshots to what the responder needs, and remove unrelated worker information before sharing them.

The Teambridge mobile app page describes worker access to schedules, time tracking, messages, and other tools shaped by roles, permissions, and workflows. It does not establish a specific account recovery sequence. Use verified organizational or product documentation for the actual recovery action rather than inventing interface instructions.

Pass the access check only when the worker can enter the correct account and perform the originally affected task. A login screen disappearing is insufficient. If the account opens but the assignment remains missing, keep the case open and route that remaining symptom to scheduling.

Confirm the assignment before treating a missing shift as a display problem

The scheduler first checks whether the authoritative schedule contains the intended assignment for the correct worker, date, time, and site. Then check the relevant visibility configuration using documented procedures. This sequence is an operating recommendation, not a claim that every missing shift has a permissions cause.

Teambridge's documented role and workflow dependent mobile experience makes those configuration checks relevant. It does not prove why a particular shift is absent, or that refreshing the app will resolve it.

If the assignment is confirmed, the supervisor may communicate approved reporting instructions through an authorized alternate channel. Save the instructions, approving supervisor, expiry, and next update in the recovery record. The worker should know where to report and when to expect confirmation that normal app access is usable.

If no assignment is confirmed, return the staffing decision to scheduling. Do not tell the worker to report merely because they remember seeing a shift or received an earlier message. If scheduling creates or changes an assignment, an authorized scheduler must save the decision in the authoritative schedule.

Verification requires the saved assignment and worker visible shift to agree. If the schedule is correct but the worker still cannot see the assignment, temporary reporting instructions may remain active, but the task recovery status stays unresolved or temporarily supported.

Preserve time evidence without calling it an approved timecard

When a clock action fails, the supervisor should record observed work times and supporting context through an approved alternate channel. Identify who observed the work and distinguish actual observations from times reported later by the worker. Scheduled start time is not automatically actual start time.

For covered nonexempt employees in the United States, the Department of Labor's Fact Sheet 21 identifies hours worked each day and total hours worked each workweek among required records. This supports preserving actual work evidence. It does not prescribe the approval chain in this playbook.

Before entering a correction, the authorized time approver checks whether a punch already exists. Repeat that check before closure if a delayed entry could have appeared during investigation. This prevents the proposed manual correction from silently duplicating an existing entry.

Use the documented correction process in the system holding the authoritative time record. The approver needs permission to make the relevant change and complete the applicable approval step. After saving, inspect the resulting record rather than treating an unsaved edit or success message as sufficient evidence.

Verification requires a saved record matching the approved evidence, no duplicate entry, and completion of the applicable approval step. If the approver lacks access or the save fails, leave correction pending and escalate to the authorized administrator. Keep the relevant payroll deadline visible without assuming that an app recovery also resolves payroll consequences.

The Teambridge platform page describes configurable records, permissions, workflows, and approval points. Those capabilities do not establish automatic support routing, a ready made escalation system, or the exact time correction behavior in your configuration. Confirm implementation details before using this playbook against live records.

Hypothetical case A17 stays open after login succeeds

The following completed record is hypothetical. Assume a confirmed 07:00 assignment, an identity verified worker, a supervisor who can observe actual work, and authorized responders available during the shift. All times illustrate the proposed workflow, not customer results or Teambridge response commitments.

Recovery record field	Completed hypothetical case A17
Case ID and worker reference	A17; restricted worker reference W17
Affected work	Confirmed 07:00 assignment; start time entry affected
Symptom	Account access failure reported at 06:55
Operational deadline	07:00 shift start; temporary arrangement expires at 07:30
Evidence	Redacted access error and supervisor observation of work beginning at 07:03
Operations owner and backup	Assigned operations coordinator; duty operations manager as backup
Technical responder	Account administrator accepts at 06:58; next response due at 07:20
Authorized record owner	Time approver responsible for the affected start entry
Temporary workaround	Supervisor approves alternate arrival check and records observed 07:03 start as evidence
Workaround expiry	07:30; supervisor must reassess if unresolved
Task recovery status	Login succeeds at 07:18; affected task checks completed at 07:26
Correction status	Pending at 07:18; approved 07:03 start saved at 07:24 after checking for an existing punch
Verification evidence	At 07:26, correct account access, assignment visibility, saved start entry, approval, and absence of duplication checked
Next worker update	Operations update through the approved alternate channel due at 07:20 and delivered then
Closure	Worker informed at 07:26; case closed with no remaining exception in the assumed scope

At 07:18, closing this hypothetical case would be premature. Login has succeeded, but the observed 07:03 start still lacks a confirmed correction. Operations keeps that discrepancy visible while the time approver investigates.

At 07:24, the hypothetical time approver confirms there is no existing punch and saves the approved start entry. Operations then completes the task and record checks at 07:26, informs the worker, and closes the case. The alternate arrival check supported work temporarily; it never substituted for the saved time record.

Review unresolved corrections before they outlive the workaround

Put the workflow into service with a short implementation sequence:

1. Name the owner and backup. Assign operations coverage for worker updates and identify authorized account, scheduling, and time responders.
2. Agree local response targets. Define acceptance and update expectations around shift starts, workaround expiry, and relevant payroll cutoffs.
3. Test all three routes. Use controlled cases to confirm authorized access, saved changes, worker task verification, and escalation when a responder cannot complete an action.
4. Approve the evidence standard. Require task recovery and record verification evidence before closure, including an explicit finding when no record change is necessary.

During the affected shift, review urgent open cases and workarounds approaching expiry. Before the relevant payroll cutoff, review pending time corrections with the time approver. Weekly, review repeated causes and reopened cases to identify where routing, configuration, or verification needs attention.

Measure elapsed time from report to owner acceptance, temporary recovery, and verified correction separately. Also track overdue corrections and reopened cases. Set performance targets after observing your operating conditions rather than importing an unsupported benchmark.

A closure is valid only when every required check has evidence. If a workaround expires, the supervisor must reassess the arrangement while operations keeps the unresolved work visible. Start with the recovery record and test the three routes before rollout; do not let a working login become permission to forget an incorrect record.