The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →The Delamain phone bug in Cyberpunk 2077 is one of those issues that feels small until it blocks a full quest beat: you get a missing call, a phone prompt that never completes, or the Delamain interaction behaves like it’s frozen mid-state.
This guide gives you a reliable, repeatable fix. It’s built around resetting the quest/phone state the game actually relies on—then validating it quickly—so you don’t waste hours trying random resets.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Cyberpunk 2077: Ultimate Edition- Nintendo Switch 2 | $62.99 | Buy on Amazon |
| 2 |
|
Cyberpunk 2077 - PlayStation 4 | $25.00 | Buy on Amazon |
| 3 |
|
BANDAI NAMCO Entertainment Cyberpunk 2077 (Ultimate Edition) | $64.00 | Buy on Amazon |
| 4 |
![Cyberpunk 2077: Ultimate Edition - Nintendo Switch 2 [Digital Code]](https://m.media-amazon.com/images/I/41R5kouU7PL._SL160_.jpg)
|
Cyberpunk 2077: Ultimate Edition - Nintendo Switch 2 [Digital Code] | $69.99 | Buy on Amazon |
| 5 |
|
The World of Cyberpunk 2077 | $32.47 | Buy on Amazon |
As an Amazon Associate I earn from qualifying purchases.
What the Delamain phone bug usually is
Players typically see one of these patterns during Delamain-related story or side progress:
- Phone not triggering: the Delamain call/prompt doesn’t appear when it should.
- Prompt loops: you get repeated notifications, but the interaction never completes.
- UI/interaction freeze: the phone opens, but selecting the Delamain item or continuing the call does nothing.
- Quest stage desync: the world looks right, but the quest behaves like you never reached the call.
Most of these come from the game saving while the phone/quest state machine is mid-transition, then resuming into an inconsistent state. The solution is to force the game to re-initialize that state cleanly.
#1 Best Overall
- Explore all of Night City’s extremes — From V’s rise as a cyberpunk mercenary in Night City to their journey into the shadowy world of spies in Dogtown, dive into the full story and carve your own path through it.
- Meet unforgettable characters — Forge relationships with a rich cast of characters all with their own dreams, tragedies, and tales to tell, including Keanu Reeves as rockerboy Johnny Silverhand and Idris Elba as secret agent Solomon Reed.
- Explore one of the most immersive cities in video games — Experience a breathtaking city of the dark future at home or on the go with the power of Nintendo Switch 2! Customize your journey from the very first steps with performance and quality mode.
Prerequisites and what you should not do
- Back up your save. If you can, keep a manual save before you attempt fixes.
- Disable mods temporarily (if applicable). Script mods are a common reason quest/phone triggers don’t fire correctly.
- Don’t spam loads. Repeated reloads on the same broken state can “bake in” the issue across autosaves.
- Know your platform. The best approach differs slightly between PC, PlayStation, and Xbox.
The most reliable fix (proven workaround): quest-state reset via a hard reload
This workaround forces Cyberpunk 2077 to fully reinitialize the quest and phone systems, rather than just doing an in-menu quick reload that may preserve the bugged state.
Do it in order. If you skip steps, you’ll often get the same broken behavior again.
PC (GOG/Steam) steps
- Exit to desktop: From the in-game pause menu, choose Exit Game (not just “Resume”).
- Stop background processes: Open Task Manager and fully end Cyberpunk 2077 (and any launcher processes still running).
- Do a clean relaunch: Start the game fresh.
- Load a manual save made earlier than the moment the bug started. If you only have autosaves, load the oldest autosave you can find.
- Trigger the call without fast-travel spam: Walk to a neutral area near where the call would normally trigger and wait/cycle time if your game objective requires it. Avoid fast traveling immediately after loading.
- Let the phone state reinitialize: Once the phone prompt appears (or should appear), do not open/close the phone repeatedly. Accept the call, then proceed normally.
If it still fails, continue to the checklist section. On PC, also check mods and files (those are the usual “why it didn’t fix” causes).
PlayStation 5 / PlayStation 4 steps
- Fully close the game: Press the PS button > highlight Cyberpunk 2077 > press Options > Close Game.
- Reboot the console: Hold the power button on the PS unit until you get the restart option, then restart.
- Launch Cyberpunk 2077 fresh.
- Load the oldest relevant save: Use the save that predates the first broken phone behavior.
- Wait in place: Stand in a stable area (not mid-transition). If you’re supposed to receive a call upon entering/leaving an area, follow that route once—don’t repeat entries rapidly.
- Complete the interaction once it fires: If the call triggers, follow the objective instead of backing out.
On PlayStation, “close game + restart console” matters because it clears cached session/streaming state that a simple in-menu reload can preserve.
Xbox Series X|S / Xbox One steps
- Quit the game completely: Press Xbox button > select the game > press Menu > Quit.
- Power cycle (quick restart): After quitting, turn the console off, wait ~30 seconds, then turn it back on.
- Start the game from the dashboard (not quick resume).
- Load an older manual save.
- Recreate the trigger once: Move normally toward the location that should cause the Delamain prompt to fire and wait there. Skip fast-travel loops.
- Handle the phone interaction: When the phone prompt appears, accept it and proceed.
If you’re using Quick Resume, the phone bug often persists because the game resumes in the exact stuck moment. Starting clean fixes that most times.
Rank #2
- Cyberpunk 2077 is an open-world, action-adventure story set in Night City
- Become a cyberpunk, an urban mercenary equipped with cybernetic enhancements and build your legend on the streets of Night City
- Take the riskiest job of your life and go after a prototype implant that is the key to immortality
If the hard reload doesn’t work: the “phone/quest blockers” checklist
If the quest-state reset didn’t fix it, the bug usually has a blocker: mismatched version, a mod, corrupted save data, or a UI desync. Use this checklist to isolate the cause quickly.
Mods, CET/Script mods, and save edits
Any mod that touches quest logic, phone UI, audio, or scripting can prevent triggers from updating correctly.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallOutdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware match- Disable all mods and start the game once clean.
- Remove script-heavy mods that modify phone, events, quests, or UI.
- If you used a save editor, revert to a save made before the edit.
On PC, the “hard reload” method above is usually enough only when the environment is stable. Mods are the most common instability source.
Game version and DLC checks
Cyberpunk 2077 frequently changes quest scripting and triggers across patches. If you recently updated (or changed DLC state), revert to a save consistent with that patch.
- Confirm your game version in the main launcher/boot screen.
- If you installed or enabled Phantom Liberty (or changed DLC status), ensure you’re testing with a save made under the same setup.
- Update both the base game and any platform components (Steam/Epic/GOG pack updates if applicable).
If you’re mid-quest while the patch changed, quest triggers can desync. The most reliable fix then is still: load an older save after the update, but before the phone bug first appears.
Rank #3
- THE ULTIMATE CYBERPUNK 2077 EXPERIENCE - Includes the critically acclaimed spy thriller expansion Phantom Liberty
- CREATE YOUR OWN CYBERPUNK
- Explore the city of the future – you decide when you want to go where and how to get there
- Decide how the story ends – your choices in the main game as well as in the spy thriller adventure Phantom Liberty lead to a complex web of consequences
Audio/input desync and phone UI stuck states
Sometimes the phone prompt exists, but the interaction doesn’t register (controller input focus, audio device hiccups, or UI state).
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →- Restart controller input: unplug/replug controllers (PC), or re-pair if needed (consoles).
- Cycle audio devices: switch output device on PC and then back.
- Close and reopen once: open phone once, attempt the interaction once, then stop spamming UI toggles.
Because you only want one clean trigger attempt, this is best done immediately after the hard reload method—not hours later.
Corrupt or overly-smeared saves
Over time, autosaves and manual saves can accumulate states that don’t cleanly recover (especially after crashes, alt-tabbing, or abrupt power loss).
- Load the oldest save you can reasonably live with.
- Avoid continuing from an autosave made right when the bug first occurred.
- Keep multiple backup saves so you can roll back one step at a time.
If every older save shows the same broken phone state, the blocker is likely mods/version rather than save corruption.
Verification: how to confirm the bug is fixed
You’ll know you fixed it when the Delamain interaction changes state in a way the game can’t fake.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errorsRank #4
- A Nintendo Switch Online membership may be required for online play. Please check the game detail page on Nintendo.com for membership requirements.
- 2025 CD PROJEKT S.A. All rights reserved. CD PROJEKT, the CD PROJEKT logo, the REDengine logo, Cyberpunk, Cyberpunk 2077, the Cyberpunk 2077 logo, Johnny Silverhand, the SAMURAI logo, Phantom Liberty and the Phantom Liberty logo are trademarks and/or registered trademarks of CD PROJEKT S.A. in the US and/or other countries. All other copyrights and trademarks are the property of their respective owners.
- The phone prompt reliably appears when expected (no looping notifications).
- Selecting/accepting the Delamain item triggers the correct quest step (objective updates in your journal).
- The game no longer stalls on the phone/UI interaction (you can proceed normally to the next objective).
If the objective updates but the world doesn’t react, that’s usually a different trigger problem than the phone bug. In that case, use the troubleshooting matrix below.
Troubleshooting matrix (symptom → what to try)
| Symptom | Most likely cause | What to try next |
|---|---|---|
| Phone call never triggers | Quest state preserved in stuck load | Do the hard reload: fully exit/close app, reboot console/stop background processes, then load an older manual save |
| Call triggers but selection does nothing | UI input focus desync | Restart game clean; attempt interaction once; swap audio/controller device; avoid repeated phone open/close |
| Looping notifications | Quest stage not advancing after phone state change | Disable mods; ensure same patch/DLC setup; load older save and proceed without fast-travel spam |
| Bug persists across all saves | Version/DLC mismatch or mod conflict | Update/verify files (PC) or reinstall (if needed); remove mods; test with a new clean run save just to confirm behavior |
| Only happens after crash/alt-tab/power loss | Corrupted runtime state | Use pre-crash save; avoid continuing from immediately post-crash autosaves |
Prevention: avoid triggering the bug again
- Save manually before entering mission trigger areas—especially during phone-call moments.
- Don’t rely on Quick Resume for quest-critical phone interactions.
- Limit fast travel immediately after a load when you’re waiting on a phone event.
- Keep your mod set stable while doing quest lines. If you must update mods, do it between play sessions and keep backups.
This is boring advice, but it works because it prevents the game from saving mid-transition—the exact condition that creates phone-state desync.
When to escalate (CDPR support and what to include)
If the hard reload + checklist still fails, you’re beyond “player-side workaround” and into “reporting a reproducible bug.”
When contacting support or posting to community channels, include:
- Your platform (PC Steam/GOG, PS5/PS4, Xbox Series X|S/One)
- Your current game version (exact patch)
- DLC status (e.g., Phantom Liberty installed/active)
- Whether mods are enabled, and which ones touch UI/quests/scripts
- What you tried (hard reload, older manual save, mod disable, reboot)
- A short description of the moment the Delamain phone prompt should trigger
FAQs
Will deleting the save file fix the Delamain phone bug?
It can, but it’s usually unnecessary and risky. Prefer loading an older manual save and doing the hard reload first. Deleting saves is last-resort when you confirm the issue persists across all prior saves.
Best Value
Does verifying game files on PC help?
It can help if files are damaged, but it won’t fix quest-state issues caused by a stuck phone interaction. If you’re on PC, do it after you’ve tried the hard reload and after you’ve disabled mods.
Can this happen only with certain DLC?
Yes. DLC can add content and scripting changes that affect how triggers progress. If you changed DLC state recently, test with saves made before the bug and make sure your version/DLC setup matches.
My phone prompt appears, but the quest won’t update. What now?
That’s often a quest-stage desync. Disable mods, load an older save from before the phone prompt first misbehaved, and repeat the interaction once after a clean restart (no fast-travel spam).
Can I fix it without loading an older save?
Sometimes a clean exit/reboot is enough, especially on consoles where Quick Resume preserves stuck states. But if your most recent save is already “stamped” with the bug, an older manual save is the fastest path.
Bottom Line
The most reliable way to fix the Cyberpunk 2077 Delamain phone bug is a controlled quest-state reset: fully exit/close the game, reboot if needed (consoles), load an older manual save, then trigger the phone interaction once in a stable area.
If that still fails, treat it like a blocker problem—disable mods, confirm version/DLC consistency, and avoid continuing from autosaves made during the stuck moment.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
Recommended Free Tools
