Call operations
Write a handoff note for a shared front-desk tablet
A shared-tablet handoff note format for front-desk call teams, with fixed fields, privacy rules, update timing, and a shift-end check.

Table of contents
A shared tablet at the front desk is convenient and risky at the same time. The next agent can see the note, but so can a visitor standing at the counter. The note also tends to grow during a busy shift until it becomes a wall of text that nobody reads. A fixed format keeps the handoff short, private, and useful.
Key takeaways
- Use five fixed fields instead of a blank notepad.
- Keep caller names and numbers out of the always-visible screen.
- Update the note at the moment of handoff, not at the end of the day.
- Lock the tablet when it is not in use and clear old notes at shift end.
- Review one week of notes to find fields that are routinely empty.
Decide what belongs in the note
The handoff note should carry only what the next agent needs to act. Open callbacks, promised times, urgent call types, and anything that changed since the morning belong there. General office news does not. A note that includes everything becomes a second inbox and stops being read.
Write the purpose at the top of the template so the team knows the boundary. "This note is for calls that need action in the next eight hours" is a clear limit. Anything longer belongs in the case record or the team message channel. The tablet is a bridge between shifts, not an archive.
Use five fixed fields
Start with five fields: open callback, promised time, caller request, owner, and status. Each field should be short enough to read at a glance. The owner field names the person who will act, not the person who wrote the note. The status field uses three values such as open, waiting, and done.
Fixed fields make the note predictable and easier to audit. They also stop the writer from burying a deadline in a paragraph. If a field does not apply, leave it blank rather than writing "none" in every row. The template should fit on one screen without scrolling.
Keep private details off the visible screen
A tablet facing the counter can expose a caller's name to the next visitor. Use a case number or initials in the visible row and keep the full details behind a login. Turn on the screen lock and set it to engage after a short idle period. The person at the counter should never see a phone number or a medical detail.
Staff should also avoid reading the note aloud when a visitor is nearby. A quiet handoff is part of the same privacy rule. If the next agent needs a detail, open the case record on a protected screen. The medical message standard offers related guidance for sensitive intake.
Update at the moment of handoff
The note should change when the promise changes. If the caller is told two o'clock, the note should show two o'clock before the agent leaves the desk. Waiting until the end of the shift creates a gap where the next caller hears a different story. The update is part of the call, not an administrative extra.
Use a timestamp beside each change so the next agent knows how fresh the note is. A note from four hours ago may already be out of date. If the caller calls again, the agent can see whether the promise was kept. The timestamp also helps the shift lead spot a note that has not moved all day.
Avoid free-text sprawl
A short free-text area is useful for context that the fields cannot hold. Limit it to two sentences and require a plain description of the next action. A note that says "caller upset" without an action gives the next agent nothing to do. A note that says "caller upset about a missed delivery, needs a call before noon" is actionable.
Do not use the free-text area for opinions about the caller. Labels such as difficult or demanding follow the caller into the next interaction. Describe the behavior and the requested outcome instead. The next agent can decide how to respond without inheriting a judgment.
Check the note at shift end
The outgoing agent should read the note aloud to the incoming agent in under two minutes. The incoming agent confirms each open item and asks one question. Both agents then clear the rows that are done. The spoken check catches a note that looks complete but is missing a time.
The shift lead should review the note once a week for empty fields and stale rows. A field that is always blank may not be needed, and a field that is always full may be too broad. Change one field at a time and watch whether the handoff gets shorter. The overnight notes review shows how to check notes before the queue opens.
A shared tablet works when the note is treated as a handoff tool rather than a diary. Five fields, a short timestamp, and a spoken check are enough for most front desks. Clear the screen at the end of the shift and lock it when it is not in use. The format should make the next action obvious in seconds.