Don’t Pick Up

You slide the back panel off a cracked handset, and a folded receipt falls onto the counter — a name, an address, a date that doesn’t match the intake form in front of you. In Don’t Pick Up, that half-second of hesitation is the entire game.

Life as a Device Repair Associate in Don’t Pick Up

Every shift starts the same way: a stack of broken phones, a supervisor’s checklist, and a form that expects you to fill it out without asking why. As a Device Repair Associate, your job description sounds mundane on paper — open the case, replace the part, close it back up — but the game keeps stretching that routine until it snaps. The workshop is clean, the lighting is even, and nothing about the room tells you that anything is wrong. That’s the point.

What makes the role interesting is how little control you actually have over what lands in front of you. Some devices are ordinary. Others contain messages, photos, or recordings that weren’t meant for a repair counter. You can’t skip them, and you can’t un-see them once the screen lights up.

The tension in Don’t Pick Up isn’t built from monsters jumping out of vents. It’s built from paperwork you’re not sure you should be signing.

The Daily Directives and Why They Change

Each morning brings a new set of regulations, and they’re never framed as suggestions. One day you’re told to report any device with foreign language text. The next, that same rule has quietly vanished and been replaced with something stricter. Yesterday’s directive does not excuse today’s mistake, and the game is blunt about that.

This constant rewriting is where the game turns from a repair sim into something closer to a survival test. You’re not just fixing phones — you’re trying to keep pace with a system that shifts its own rules while pretending it hasn’t.

Players who treat the directives as background flavor tend to get caught out fast.

What Beginners Get Wrong Behind the Repair Bench

The most common early mistake is speed. New players rush through intake, assuming the danger is external — a jump scare, a knock at the door — when the real risk is procedural. Missing a required check, skipping a report, or handling a flagged device the wrong way carries consequences that surface much later, not immediately.

The second mistake is emotional: reading too much into a device out of curiosity rather than obligation. It’s tempting to dig for the full story behind every scrap of sensitive information you uncover, but Don’t Pick Up rewards discretion over nosiness far more often than it rewards digging.

• Rushing intake without confirming the daily directive first
• Treating every device the same way regardless of what’s found inside
• Ignoring supervisor guidance because it feels repetitive
• Reporting everything reflexively instead of weighing who it affects

Handling Sensitive Information Without Getting Flagged

Discretion is the actual skill the game is testing. What you choose to report, what you quietly set aside, and what you never mention again all feed into how the city’s political crisis outside your window keeps escalating — or doesn’t. There’s no clean way to play it safe; every option costs someone something.

Community discussion around early builds already leans toward calling this the game’s most divisive element: some players find the ambiguity thrilling, while others want clearer feedback on whether a choice was “correct.” Don’t Pick Up seems content to leave that discomfort unresolved.

By the time regulations start contradicting each other outright, most players stop trying to be perfectly compliant and start making calls based on gut instinct instead.

The Different Endings Waiting Inside Don’t Pick Up

Endings are built from the accumulation of small decisions rather than one dramatic final choice. Who you served, what you reported, and what you buried all get tallied quietly in the background, which means two players who think they played “the same way” can land in completely different places.

This is where the simulation angle really pays off — nothing about the ending screen explains itself, and players often have to trace back through earlier shifts to understand why things turned out the way they did.

That ambiguity is deliberate, and it’s a big part of why the game invites replaying.

What happens if you ignore a daily directive in Don’t Pick Up?

Ignoring a directive doesn’t trigger an instant game over. Instead it quietly logs as non-compliance, which surfaces later through supervisor reviews or shifts in how the story treats your Device Repair Associate.

Does every phone in Don’t Pick Up contain a story?

Not every device is significant — some repairs really are routine. Part of the challenge is learning to tell which phones matter and which are just work, without a reliable indicator either way.

Can you get a good ending in Don’t Pick Up?

There isn’t a single “good” ending flagged by the game. Outcomes reflect the pattern of choices you made about who you protected and what you reported, so what counts as good depends on what you prioritized.

Don’t Pick Up turns a repair counter into one of the more uncomfortable workplaces in recent horror games, precisely because nothing about it looks dangerous until the daily directives start contradicting each other and you’re the one holding the last flip phone with someone’s name written inside the case.