Support queues for collaboration platforms are remarkably repetitive: a dozen problems generate most tickets, and most of those have user-side fixes that take under five minutes. This chapter is the page to read before opening a ticket — and the page support desks should link in their auto-reply.
Sign-In Loops and Expired Sessions
The classic symptom: the sign-in window reappears forever after entering correct credentials. Causes, in order of frequency: a stale cached token, a clock drift of more than a few minutes, or a conditional-access rule blocking the device. Fix sequence: sign out completely, correct the system clock, restart, sign in again. If the loop persists on one device but not another, the device's compliance state is the suspect — that is an escalation, with the device name in the ticket.
"The File Disappeared"
Almost never deleted; usually moved, renamed, or filtered. Check in order: the channel's file library search (renames break mental bookmarks), the recycle bins — both the library's and the tenant's, where admins can restore — and the view filters, which silently hide file types. If a sync client is involved, compare the local folder against the web view; the web view is the source of truth, and local absence is a sync fault, not data loss.
Notifications That Went Silent
- Confirm the channel is still followed; unfollowing survives app reinstalls and surprises people months later.
- Check the OS-level notification permission for the app — operating-system updates reset it more often than anyone admits.
- Review do-not-disturb and quiet-hours schedules, including calendar-driven automatic statuses.
- On mobile, verify battery-optimisation is not freezing the app in the background.
Audio and Video Failures in Calls
Diagnose in layers: device selection first (the app may have grabbed a monitor's nonexistent microphone), then OS permissions, then network. The in-app call health panel distinguishes them — device problems show no input level, network problems show packet loss. When a whole office degrades at once, it is the network path, and the call health export is exactly what your network team needs.
The universal reset, and its limits
Clearing the app cache resolves a surprising share of rendering and sync oddities without touching your data — cache is regenerable, settings and history are not. What cache clearing never fixes: permission problems, retention behaviour, and anything another user also experiences. If two people see it, stop local troubleshooting and escalate; you are now witnessing a tenant issue.
Sync Conflicts and Duplicate Copies
Conflict copies appear when two devices edit offline and reconcile badly. Prevent by letting sync finish before shutting laptops; recover by comparing the conflict copy against the current version in the web editor and merging by hand — never by deleting either file first. Recurring conflicts on one folder usually mean two sync clients claim it; audit what is syncing what.
Writing a Ticket That Gets Fixed
- One sentence of symptom, one of expected behaviour.
- Who else is affected, and since when.
- What you already tried, so support starts at step four, not step one.
- Screenshots with timestamps; for calls, the call health export.
That closes the handbook: twenty-four chapters from first sign-in to lifecycle retirement. Keep it bookmarked — the interface will change, but the habits inside these pages age slowly.
