Dispatch Walkthrough: Complete Guide for All 8 Episodes

Dispatch doesn’t ease you in. It throws you straight into the chair, lights blinking, radios crackling, and a city that will absolutely burn if you hesitate. This is a dialogue-driven management thriller where every sentence is a lever and every second costs something. If you’ve ever reloaded a save because one bad line nuked a relationship or locked you out of an ending, this guide is built for you.

At its core, Dispatch is about control under pressure. You’re not swinging swords or min-maxing DPS, but the tension hits just as hard because the game tracks everything. Who you trust, how fast you react, and what information you prioritize all feed into branching outcomes that span all eight episodes. Miss a beat early, and the ripple can haunt you hours later.

How Dispatch’s Core Loop Actually Works

Each episode is structured around a series of escalating incidents handled through dialogue, timed decisions, and resource allocation. You’re juggling incoming calls, field agents, political pressure, and incomplete intel, often all at once. Think of it like turn-based strategy disguised as a conversation, where dialogue options are your abilities and information is your currency.

Conversations aren’t just flavor text. Dialogue choices can unlock new branches, close off entire investigation paths, or subtly shift a character’s loyalty meter without telling you outright. The game rarely telegraphs which option is “right,” and that ambiguity is the point.

Time Pressure Is the Real Final Boss

Dispatch’s most important mechanic is invisible: the clock. Many choices are timed, and hesitation is itself a decision. Letting the timer expire often produces a unique outcome, not a default fail state, and sometimes those outcomes are worse than choosing poorly.

Crucially, time pressure stacks. Spending too long extracting details from one caller can cause another situation to escalate off-screen. There’s no I-frame for indecision here; the city keeps moving whether you do or not.

Choice Weight, Consequences, and Long-Term Payoff

Not all choices pay off immediately, and that’s where most players get burned. Some dialogue options are long-game investments that won’t show value until two or three episodes later. Others give short-term stability but quietly poison future alliances.

Relationships function like hidden stats. Characters remember how you treat them under stress, not just what you say when things are calm. A supportive response during a crisis can outweigh multiple neutral interactions later, while a single ruthless call can permanently shift how that character responds in future episodes.

This walkthrough assumes you want to see everything Dispatch has to offer. That means tracking missable interactions, deliberately taking suboptimal paths when required, and understanding when to let situations fail to unlock unique scenes or endings. From here on, every episode will be broken down with spoiler-aware precision so you always know what a choice costs, and what it can unlock if you’re willing to commit.

Episode 1: First Shift — Tutorial Choices, Early Trust Flags, and Hidden Dialogue

Episode 1 is framed as onboarding, but treating it like a throwaway tutorial is the fastest way to lock yourself out of content. First Shift quietly establishes how Dispatch measures competence, empathy, and authority, and those metrics start ticking the moment the first call comes in. Every response here teaches the game how you play, and it adjusts future friction accordingly.

This episode has more hidden dialogue than any other early chapter, mostly because the game expects players to rush. If you slow down strategically, probe optional lines, and occasionally let timers burn, you’ll surface character beats that never reappear on a clean, “efficient” run.

The Opening Briefing: Your First Trust Check

The initial briefing with Central isn’t just flavor text; it’s your first relationship calibration. When prompted about readiness, choosing a confident but qualified response raises Central’s internal trust flag without pushing you into the “reckless” category. Overly cocky answers trigger a subtle skepticism modifier that shows up later as shorter response windows.

If you instead pick the cautious option and ask for clarification, you unlock an extra line where Central explains dispatch prioritization logic. That explanation never repeats, and it directly foreshadows Episode 3’s overload scenario. Completionists should always take this option at least once.

Letting the timer expire here produces a unique silence beat. Central fills the gap with a passive-aggressive acknowledgment that slightly lowers rapport but unlocks a hidden achievement flag tied to non-response behavior.

Call One: The Domestic Disturbance Tutorial That Isn’t

Your first live call appears straightforward, but it’s designed to test whether you default to procedure or people. Pushing for location and compliance advances the call cleanly, but it also locks you out of the caller’s optional backstory thread. That thread pays off in Episode 6 if preserved.

To fully exhaust the dialogue tree, ask about immediate danger before requesting identifying details. This keeps the caller talking longer, increasing time pressure elsewhere, but unlocks two unique emotional responses that boost your Empathy stat. Empathy is invisible, but it heavily influences whether civilians volunteer information later in the game.

There’s a hidden failure state here as well. If you interrupt the caller twice and then choose a neutral response, they hang up. This counts as a resolved call mechanically, but it flags you as dismissive, which affects how similar callers behave in Episodes 2 and 4.

Timer Manipulation and the First Off-Screen Consequence

While handling Call One, a secondary alert begins ticking silently. If you fully exhaust all optional dialogue and let the clock dip into the red, that alert escalates off-screen. You won’t see the result immediately, but Episode 2 will reference it in a passing line that many players never hear.

Optimizers aiming for full narrative coverage should deliberately allow this escalation on one run. It unlocks a later debrief exchange that reveals how Dispatch’s simulation handles unattended crises, and it slightly alters Central’s tone toward you for the next two episodes.

Conversely, resolving Call One quickly prevents the escalation but closes off that entire branch permanently.

Call Two: Authority Versus Support

The second call introduces your first explicit authority check. You’re given a choice between issuing direct instructions or validating the caller’s emotional state before acting. Issuing commands improves your Authority stat but reduces the likelihood of callers improvising solutions later.

The optimal path for long-term flexibility is to acknowledge emotions first, then pivot to instructions. This hybrid approach isn’t obvious, but it raises both Authority and Empathy by small amounts. It also unlocks a hidden line where the caller explicitly thanks you, which is tracked internally.

Ignoring the emotional option entirely brands you as efficient but cold. That label matters more than the raw stats and changes how certain NPCs describe you when you’re not in the room.

The End-of-Shift Debrief: Locking in Your Trajectory

The episode closes with a short debrief that most players mash through. Don’t. This is where Episode 1 crystallizes into long-term consequences. When asked to self-assess, choosing “handled what I could” is the most balanced response and avoids extremes.

If you take full credit, you gain Authority but lose a hidden Safety margin that tightens timers later. If you deflect blame, Central flags you as unreliable, which reduces future informational transparency during briefings.

There’s also a missable line here if you remain silent until the timer expires. Central fills in your evaluation for you, and while it’s harsher than any selectable option, it unlocks a unique internal monologue in Episode 5 that only triggers if this flag is set.

Episode 1 doesn’t end with a bang, but it quietly writes the rules your version of Dispatch will follow. From here on, the game stops teaching and starts testing, and every trust flag you set during First Shift comes back when the stakes are real.

Episode 2: Lines of Fire — Branching Emergencies, Priority Routing, and Character Alignment

Episode 2 picks up immediately after the systems Episode 1 quietly locked in. Timers are tighter, caller behavior is less forgiving, and Central stops explaining why things matter. This is the episode where Dispatch reveals its real hook: you’re no longer solving problems, you’re deciding which problems are allowed to exist.

Every choice here feeds into a priority-routing matrix that follows you for the rest of the game. Who you save, who you stall, and who you reroute defines not just outcomes, but how the city learns to use you.

Opening Briefing: Reading Between the Lines

The opening briefing seems routine, but the wording changes based on your Episode 1 debrief flag. If you were flagged as efficient, Central frames the day around throughput. If you leaned empathetic, the language shifts toward damage control and public perception.

When given the chance to ask a clarifying question, always do it. This doesn’t consume time and quietly increases your Information Access stat, which directly affects how much context you get during overlapping calls later. Skipping it saves nothing and closes off several mid-call prompts.

Call One: The Warehouse Fire and Silent Timers

The first emergency is a warehouse fire with incomplete data and a deceptively generous timer. The critical decision isn’t which unit you send, but whether you probe for more details or dispatch immediately.

Probing reveals that the building is technically unoccupied but adjacent to an illegal housing block. This information only appears if you ask two follow-ups in a row, which most players won’t do under pressure. Sending fire services immediately prevents spread but guarantees civilian casualties off-screen, which counts against a hidden Public Trust modifier.

The optimal route is to stall for information, then reroute a smaller unit to the adjacent structure first. This delays suppression slightly but unlocks a later commendation in Episode 4 when the housing block becomes politically relevant.

Priority Split: When Two Calls Compete

Midway through the warehouse fire, a second call interrupts: a domestic dispute escalating toward armed violence. This is the first true priority split, and the game does not pause the initial timer.

Handling both perfectly is impossible without prior flags. If you earned the balanced self-assessment in Episode 1, you get an extra dialogue beat that buys you time. Use it to assign a holding pattern to the fire response while you de-escalate the domestic call.

Choosing to fully commit to one call locks the other into an automated resolution. Automation always resolves worse than player input, and NPCs will reference that failure later. Even partial engagement is better than none.

Call Two: De-escalation Versus Control

The domestic dispute tests your alignment more aggressively than anything so far. You can assert authority, appeal emotionally, or deflect responsibility to law enforcement protocols.

Pure authority resolves the call fastest but adds an Aggressive Control flag that certain characters will react to negatively in Episodes 6 and 7. Pure empathy risks escalation if your Authority stat is already low. The best path is to establish control, then immediately validate the caller’s fear.

This sequence unlocks a rare outcome where the caller stands down without police intervention. It’s one of only three non-lethal resolutions tracked for the true pacifist ending, even though the game never labels it as such.

Character Alignment: Central Is Watching

Episode 2 is where Central stops being a neutral interface and starts acting like a character. Your routing decisions subtly change its tone, pacing, and even how much slack you’re given on timers.

If you consistently prioritize human outcomes over infrastructure, Central becomes more conversational but less forgiving of mistakes. If you prioritize efficiency, it feeds you cleaner data but cuts off optional dialogue. Neither path is strictly better, but mixing them causes friction that manifests as delayed prompts later.

Pay attention to when Central interrupts you. Those interruptions are alignment checks, not flavor text.

End-of-Episode Choice: Owning the Fire

The episode closes with a direct question about the warehouse fire’s outcome. This isn’t about truth, it’s about framing.

Admitting uncertainty preserves flexibility and keeps both Authority and Empathy stable. Claiming success boosts Authority but permanently closes an investigative branch in Episode 3. Deflecting responsibility increases Empathy but marks you as politically cautious, which affects how external agencies treat you.

There is also a hidden fourth outcome if you let the timer expire without answering. Central records the silence as deliberate, unlocking a confrontational exchange in Episode 6 that only appears if you’ve avoided accountability twice.

Episode 2 doesn’t punish mistakes immediately. Instead, it teaches the city how to lean on you, push back against you, or work around you. From here on, Dispatch remembers not just what you did, but why you did it.

Episode 3: Fault Lines — Moral Trade-Offs, Escalating Consequences, and Missable Calls

Episode 3 is where Dispatch stops pretending your choices are isolated. The game starts chaining consequences across calls, timers, and even UI interruptions. If Episode 2 taught the city how to react to you, Fault Lines tests whether you understand the rules you’ve been training it to follow.

This episode also introduces the first truly missable calls in the campaign. Not optional outcomes, but entire conversations that simply never appear if your stats, prior framing, or response cadence are off by even a few seconds.

Opening Call: The Transit Platform Standoff

The episode opens with a stalled mag-rail platform and a jumper threatening to step off the edge. The critical mistake here is treating this like a pure Empathy check. It’s not.

If you claimed success at the end of Episode 2, Authority starts artificially inflated, and the caller reacts defensively to direct commands. The optimal path is to ask procedural questions first, then pivot into validation once the timer hits the second tick. This lowers aggro without triggering Central’s override warning.

Choosing to immediately reassure the jumper feels right but hard-locks the outcome into police intervention unless your Empathy is already capped. The cleanest non-lethal resolution requires controlled pacing, not emotional speed.

Timer Manipulation and the First Hidden Call Window

Midway through the platform call, Central briefly flags a power fluctuation elsewhere in the district. This is not flavor text.

If you acknowledge the alert without switching focus, a hidden maintenance call becomes available three minutes later. Miss it, and the game quietly reroutes that thread into a catastrophic failure in Episode 5.

To unlock it, you must finish the platform call with at least one timer segment remaining. Rushing for a fast resolution closes the window entirely. This is the first time Dispatch rewards restraint over efficiency.

The Maintenance Worker Dilemma

The maintenance call presents a worker trapped between sealing a breach or evacuating nearby residents. This is the episode’s core moral trade-off, and it’s deliberately framed to punish stat-chasing.

Telling the worker to seal the breach boosts Authority and prevents short-term casualties, but it permanently damages your Empathy scaling. More importantly, it alters how civilian callers describe you later, using colder, procedural language.

Ordering an evacuation preserves Empathy but creates cascading infrastructure failures. Those failures are not immediate, but they stack hidden penalties on future response timers, making later calls less forgiving.

Central Pushback and Alignment Friction

No matter what you choose, Central interrupts during this call. This interruption is an alignment stress test.

If you’ve been consistent in Episode 2, Central’s objection is advisory. If you mixed priorities, it becomes corrective, briefly locking out one dialogue option. That lockout is permanent for the rest of the episode.

Pushing back against Central here increases a hidden Resistance flag. This flag doesn’t pay off until Episode 7, but missing it locks you out of one of the game’s most confrontational endings.

Missable Call: The Unlogged Emergency

After resolving the maintenance dilemma, do not immediately fast-forward. Let the interface idle until Central prompts you again.

If your Authority is below average and you admitted uncertainty in Episode 2, an unlogged call slips through. It’s a civilian reporting “nothing urgent,” which is a lie the game expects you to catch.

Pressing for details unlocks a domestic crisis chain that never reappears if dismissed. Ignoring it counts as a silent failure, one of only two in the game that permanently lower your maximum Empathy.

End-State Consequences Moving Forward

Episode 3 doesn’t end with a clean capstone choice. Instead, it recalibrates the entire system around you.

Your response pacing now affects how long Central waits before intervening. Civilian callers adjust their language based on whether you favored systems or people. Most importantly, the game starts remembering what you didn’t answer, not just what you did.

From here on, Dispatch stops asking whether you made the right call. It starts asking who you’re willing to leave unheard.

Episode 4: Pressure Point — Relationship Locks, Soft-Fail States, and Diverging Paths

Episode 4 opens without a cooldown. Calls stack immediately, timers are tighter, and Central’s tolerance is visibly thinner. This is the moment where the game stops flexing its systems and starts enforcing them.

Everything you carried out of Episode 3 is now live. Authority, Empathy, Resistance, and pacing penalties all feed into hidden thresholds that determine which characters will still engage with you honestly.

Opening State Check: The Invisible Gate

Before the first full call even resolves, the game runs a silent state check. This determines whether Episode 4 operates in Open, Restricted, or Locked mode for relationships.

You’ll know you’re Restricted if Central prefaces the first call with procedural language instead of context. Locked mode is harsher: one ally simply does not chime in at all, and you cannot recover that channel this episode.

If you hit Locked, do not reload unless you are chasing a perfect run. The episode still has unique content in this state, including outcomes you cannot see otherwise.

Relationship Locks Explained

Episode 4 is where relationship meters stop being flexible. Two key characters can hard-lock based on how you respond during the “multi-caller overlap” scenario roughly ten minutes in.

Prioritizing speed over clarity locks the Analyst path. You’ll still get data, but it becomes delayed and partial, effectively a DPS nerf to your decision-making. Prioritizing reassurance over resolution locks the Field Liaison, cutting off future warnings about physical escalation.

You can only keep one fully open. Trying to split the difference triggers a soft-fail variant where both remain present but unreliable.

The Multi-Caller Overlap: The Core Test

This is Episode 4’s signature sequence. Three calls come in with overlapping timers, and the UI intentionally obscures one urgency indicator.

The optimal play is not to chase the loudest caller. The quiet line has the shortest failure window, and letting it expire creates a cascading morale penalty that bleeds into Episodes 5 and 6.

Pausing to ask clarifying questions here costs time but raises Trust. If your Trust is already high, those pauses gain I-frames against Central interruptions. If it’s low, Central overrides you mid-sentence.

Soft-Fail States and Why They Matter

Episode 4 introduces soft-fails that do not end calls or flash warnings. They feel like success, but they hollow out future options.

A prime example is resolving the transit hostage situation without escalation. If you do this by deferring entirely to protocol, you succeed tactically but lose narrative leverage. Later characters will reference this as “handed off,” not “handled.”

Soft-fails stack. Two in this episode permanently cap one relationship meter below its maximum, even if you play perfectly afterward.

Diverging Paths: Command vs. Mediation

Midway through the episode, Central forces a framing choice. You are either asked to “take control” or “keep people talking.”

Command path grants faster timers, clearer UI pings, and fewer civilian interruptions. It also spikes Resistance gain but bleeds Empathy every time you cut someone off.

Mediation path slows everything down. You gain more dialogue branches, including optional de-escalation checks, but response windows shrink and RNG on civilian compliance increases.

Neither path is better. They lead to different endings, and Episode 4 is the point of no return for which philosophy defines your dispatcher.

Missable Interaction: The Personal Line

After resolving the second major incident, do not immediately advance time. Let the board idle.

If you maintained at least one open relationship, a personal line opens off-grid. This call never logs, never affects stats directly, and exists purely for character bonding.

Choosing to stay professional ends it quickly. Engaging, even briefly, flags a future interruption in Episode 6 that can save a life outright.

End-of-Episode Locks and What Carries Forward

Episode 4 ends by sealing at least one door. You will lose access to a character perspective, a dialogue tone, or a tactical shortcut, depending on your choices.

From here forward, the game assumes intent. It no longer tests what you value; it reacts to what you’ve already proven you’ll sacrifice.

If Episode 3 taught the system how you think, Episode 4 teaches it who you will protect when everything breaks at once.

Episode 5: Breaking Protocol — Major Branch Split, Irreversible Decisions, and Outcome Tracking

Episode 5 is where Dispatch stops asking what you want to do and starts locking you into who you’ve become. The systems introduced earlier now collide at once: relationship meters, protocol tolerance, and incident load all spike together.

If Episode 4 sealed doors, Episode 5 burns the map behind you. Every major decision here is tracked, remembered, and referenced in future incidents, sometimes hours later in real time.

The Protocol Override Moment (This Is the Point of No Return)

Early in the episode, Central issues a live directive that directly contradicts on-the-ground intel. You are given a narrow response window with three options: comply immediately, request delay, or override protocol.

Complying preserves Command Trust but permanently disables one high-empathy dialogue tone for the rest of the game. This is the safest mechanical choice but the coldest narratively.

Requesting delay triggers a skill check based on prior Mediation usage. Pass it, and you buy time without penalty. Fail it, and Central flags you as unreliable, increasing future response timers by roughly 10 percent.

Overriding protocol is irreversible. You gain access to the Rogue Dispatcher state, unlocking unique dialogue options in Episodes 6–8, but Central will actively work against you from this point forward.

Branch Fallout: How the Game Starts Treating You Differently

Once the protocol decision is made, the episode restructures itself. Incident order changes, call frequency shifts, and even background chatter updates to reflect your status.

Command-aligned players get cleaner UI and fewer overlapping calls, but civilian NPCs become less cooperative across the board. Expect more resistance checks and fewer second chances.

Rogue or delay-focused players deal with cluttered boards and overlapping emergencies, but unlock extra human moments. These often look like flavor, but several double as hidden stabilizers that prevent hard fails later.

Critical Incident: The Dual-Site Emergency

Mid-episode introduces the dual-site emergency, forcing you to triage two active crises with shared resources. You cannot fully resolve both. The game does not hide this from you.

Saving the high-visibility site boosts Public Confidence and locks in a late-game assist from Central if you stayed compliant earlier. The cost is a relationship hit with a key recurring character.

Prioritizing the low-visibility site does the opposite. You gain deep loyalty with that character, unlocking an optional Episode 7 route, but Public Confidence takes a permanent hit that affects ending thresholds.

Hidden Failure States and Soft-Fail Tracking

Episode 5 introduces invisible failure flags. These are not mission fails but narrative fractures that quietly stack.

Interrupting three or more civilian calls, regardless of success, flags you as dismissive. This caps one empathy-based ending unless countered by a specific Episode 6 interaction.

Letting a timer expire, even on a non-critical call, marks procedural negligence. Do this twice, and you lose access to a late-game override option entirely.

Missable Relationship Pivot: Breaking or Reinforcing Trust

After the dual-site emergency, a trusted contact reaches out directly. This interaction only appears if you have not maxed or bottomed their meter yet.

Deflecting responsibility preserves professionalism but freezes the relationship where it stands. You cannot advance it later.

Admitting doubt or ownership, even briefly, reopens growth and enables a unique callback in Episode 8. This is one of the few chances to reverse earlier damage.

End-of-Episode State Check: What Episode 5 Locks In

By the end of Episode 5, the game finalizes three hidden values: Central Alignment, Civilian Trust, and Personal Conviction. You can still influence them, but you can no longer change their direction.

The episode closes without a traditional cliffhanger. Instead, Dispatch records what you were willing to break when the rules stopped working.

From here on, the system doesn’t challenge your decisions. It tests whether you can live with them.

Episode 6: Fallout — Reputation States, Character Fates, and Optional Scene Recovery

Episode 6 is where Dispatch stops being subtle. The hidden values locked at the end of Episode 5 now surface as tangible reputation states, and the game starts enforcing consequences instead of hinting at them. You are no longer shaping direction; you are navigating damage.

This episode is structurally quieter but mechanically brutal. Nearly every scene is reactive, pulling from choices you made hours ago and daring you to either double down or attempt controlled recovery.

Reputation States Explained: Where the Game Places You

At the start of Episode 6, Dispatch assigns you one of three internal reputation states: Trusted Operator, Questioned Asset, or Operational Liability. The game never names these on-screen, but the dialogue, UI prompts, and call pacing make it clear which lane you’re in.

Trusted Operator comes from high Central Alignment and stable Civilian Trust. You’ll get shorter response timers, fewer overlapping calls, and one extra dialogue option per major interaction. This is effectively the game playing fair.

Questioned Asset is the most common state and where most players land. Calls stack faster, supervisors interrupt more often, and you’ll see passive-aggressive phrasing that limits how much emotional ground you can cover in a single response.

Operational Liability is the danger zone. Triggered by low Public Confidence or stacked negligence flags, this state introduces hard restrictions, including forced call prioritization and the removal of at least one “de-escalate” dialogue branch.

Character Fates Begin to Lock

Episode 6 is the first time character outcomes can hard-lock without a death or dramatic failure. Several recurring contacts now check your reputation state before deciding how much of themselves they reveal.

If you’re a Trusted Operator, a key civilian contact follows up on an unresolved Episode 4 thread, allowing you to steer their long-term outcome toward recovery instead of withdrawal. Miss this, and their fate defaults off-screen.

In Questioned Asset, that same character still appears, but only in a truncated exchange. You can prevent the worst outcome, but you cannot secure their best ending without a recovery flag later in the episode.

Operational Liability cuts this character entirely. Their story resolves through a third-party report in Episode 7, and you lose all influence over it.

The Fallout Call: One Choice, Three Permanent Outcomes

Midway through Episode 6, you’ll receive a mandatory call flagged internally as the Fallout Check. It’s framed as routine, but it is one of the most important conversations in the game.

Taking responsibility, even if you weren’t directly at fault, increases Personal Conviction and clears one Episode 5 dismissal flag. This is the only way to reopen empathy-based endings if you were previously capped.

Deflecting blame preserves Central Alignment but permanently closes one character reconciliation path. This locks out a specific Episode 8 ending variant tied to mutual accountability.

Attempting to stay neutral triggers RNG-weighted dialogue. If your Civilian Trust is below the midpoint, this choice almost always resolves against you, making it the riskiest option for completionists.

Optional Scene Recovery: What Can Still Be Fixed

Despite the title, Episode 6 does allow limited recovery, but only if you know where to look. Two optional scenes exist, both entirely missable.

The first is a late-shift callback that only triggers if you manually review a previously resolved log instead of advancing time. This scene can remove one negligence mark, but only if you choose the least efficient response option.

The second is a private channel conversation unlocked by maintaining silence during a supervisor interruption earlier in the episode. Speaking at all, even to comply, skips this scene entirely.

Neither scene improves your reputation state directly. Instead, they prevent further degradation, which is crucial if you’re aiming for high-variance endings.

Why Episode 6 Feels Unfair by Design

Dispatch intentionally limits player expression here. Dialogue options shrink, timers tighten, and emotional reads become harder. This isn’t a difficulty spike; it’s a thematic one.

The game wants you to feel the weight of accumulated decisions without the safety net of optimal play. If you’re struggling to “play perfectly,” that’s the point.

Episode 6 doesn’t ask whether you made the right calls. It asks whether you’re willing to own them when the system stops forgiving you.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Episode 7: Endgame Setup — Final Choice Matrix, Ending Requirements, and Save Scumming Tips

Episode 7 is where Dispatch stops pretending your choices are flexible. Almost every dialogue here is a soft lock, hard lock, or multiplier for Episode 8 outcomes. If Episode 6 tested whether you’d accept responsibility, Episode 7 tests whether your entire playthrough is internally consistent.

This episode has fewer conversations, but every one of them modifies invisible flags that directly map to endings. Think of Episode 7 less as story progression and more as endgame routing.

The Three Core Axes That Decide Your Ending

By the time Episode 7 begins, the game is evaluating you on three hidden axes: Personal Conviction, Institutional Alignment, and Civilian Trust. Episode 7 doesn’t build these from scratch; it amplifies or collapses them.

Personal Conviction is checked first. If it’s below the soft threshold, several “strong stance” dialogue options will appear selectable but silently fail, defaulting to weaker variants.

Institutional Alignment determines which authority figures will support you in Episode 8. Falling below neutral doesn’t cause an instant fail, but it forces adversarial framing later.

Civilian Trust acts as a multiplier. High trust widens your ending pool; low trust compresses it into only failure-adjacent outcomes.

Final Choice Matrix: What Actually Matters

Episode 7 has four conversations that look cosmetic but aren’t. Each one sets or clears a single-use flag that cannot be overwritten.

The opening briefing choice decides your narrative posture. Assertive language boosts Conviction but drains Alignment. Procedural language does the opposite. The compromise option only works if both stats are already above midpoint; otherwise it resolves randomly.

Mid-episode, you’ll be asked whether to preemptively document a risk. Saying yes adds a hidden Transparency flag. Saying no preserves resources but locks you out of two Episode 8 resolutions tied to whistleblower logic.

The private channel exchange is the most punishing. Supporting the other operator raises Civilian Trust but applies a latent penalty if your Conviction is low, which can flip the support into perceived weakness later.

The final desk decision is a pure ending gate. This choice doesn’t change stats; it checks them. If you don’t meet the requirement, the game substitutes a downgraded version without telling you.

Ending Requirements Breakdown

There are five primary ending categories, each with internal variants. Episode 7 determines eligibility for all of them.

The Reconciliation ending requires high Civilian Trust and at least one cleared dismissal flag from Episode 5 or 6. Miss either, and the option never appears.

The Reform ending is Conviction-locked. You must have taken responsibility in Episode 6 and chosen at least one transparency-forward option in Episode 7.

The Institutional Victory ending requires positive Alignment and no Transparency flag. Even a single risk disclosure disqualifies it.

The Collapse ending is triggered automatically if Civilian Trust is critically low and you fail the final desk check. This can happen even with high Conviction.

The Quiet Exit ending is the fallback. If you don’t fully qualify for anything else, this is where the game pushes you.

RNG Checks and Fake Choices to Watch For

Episode 7 hides two RNG-weighted checks behind dialogue that looks deterministic. Both are influenced by Civilian Trust.

The “we’ll manage it internally” response has a 60/40 split if Trust is average, but becomes a guaranteed fail below that. The game never tells you this.

Similarly, the neutral response during the risk briefing only works if Conviction and Alignment are within five points of each other. Otherwise it randomly resolves toward your weaker stat.

Completionists should treat these as traps, not real options.

Optimal Save Scumming Strategy

If you’re chasing every ending, Episode 7 is the last safe place to branch saves. Do not rely on Episode 8 checkpoints.

Create a manual save before the opening briefing. This is the earliest divergence point for Conviction versus Alignment paths.

Create a second save before the mid-episode risk documentation choice. This single flag affects three endings and is faster to branch here than replaying Episode 6.

Avoid reloading during conversations. Dispatch seeds RNG outcomes when the scene loads, not when the choice is made. Reloading mid-dialogue often produces identical results.

If you’re manipulating Trust-based outcomes, reload to the start of the scene, not the choice prompt. That’s where the roll happens.

Common Mistakes That Lock Players Out of Endings

The biggest mistake is assuming Episode 7 will let you correct earlier play. It won’t. It only validates or punishes what you’ve already done.

Another frequent error is chasing balance. Trying to keep all stats even often drops them below thresholds that require commitment.

Finally, many players overvalue Institutional Alignment late. Episode 8 has fewer institutional protections than the game implies, making blind loyalty one of the riskiest endgame reads.

Episode 7 isn’t about making the right choice. It’s about making the choice your entire playthrough has been building toward.

Episode 8: All Endings Explained — Full Ending Breakdown, Variations, and Completion Checklist

Episode 8 is pure payoff. There are no training wheels, no hidden tutorials, and almost no room to pivot once the opening briefing locks in your final flags.

Everything here is a validation pass. The game tallies Conviction, Alignment, Civilian Trust, and three hidden Episode 7 flags, then routes you into one of eight core endings with minor dialogue variations layered on top.

If Episode 7 was about commitment, Episode 8 is about consequences.

How Episode 8 Decides Your Ending

Before breaking down each ending, it’s important to understand how Dispatch actually resolves its finale.

The opening briefing performs a silent evaluation using your highest stat, your lowest stat, and whether Civilian Trust is above or below 60. One Episode 7 document choice also acts as a hard gate for multiple endings.

There are no mid-episode stat swings large enough to override this. Dialogue in Episode 8 only changes tone, character fates, and epilogues, not the core ending path.

Think of Episode 8 as a boss fight where your build was locked hours ago.

Ending 1: Institutional Ascension

This is the default Alignment-dominant ending and the one most first-time players see.

You side fully with the system, endorse the final directive, and accept the official narrative without resistance. Civilian Trust being high softens public response, while low Trust turns this into a cold, authoritarian victory.

Key variation: If you approved the risk documentation in Episode 7, your character is publicly rewarded. If you didn’t, you still “win,” but you’re quietly sidelined in the epilogue.

Completion tip: This ending requires Alignment to be at least 15 points higher than Conviction.

Ending 2: The Loyal Executor

This is a harsher variant of Institutional Ascension triggered by low Civilian Trust.

The system survives, but public unrest escalates. Several supporting characters are reassigned or erased from the record entirely.

You’ll notice heavier use of static shots and truncated dialogue here. That’s intentional. The game visually reinforces how much control has been lost.

Missable interaction: A final conversation with the Analyst only appears if Trust is above 40, even though the ending still resolves negatively.

Ending 3: Conviction Breakthrough

This is the clean Conviction victory and arguably the game’s thematic “true” ending.

You reject the directive, expose the manipulated data, and force a structural reset. High Civilian Trust turns this into reform. Low Trust turns it into upheaval.

The final choice here is real, not cosmetic. Choosing to address the public versus internal leadership determines which characters remain in power during the epilogue.

Requirement: Conviction must exceed Alignment by at least 10, and you must have refused the Episode 7 risk document.

Ending 4: Pyrrhic Reform

This is the darker Conviction path and one many players stumble into accidentally.

You succeed in stopping the system’s worst outcome, but fail to replace it cleanly. Trust is low, resources are depleted, and the closing montage emphasizes instability.

Several players misread this as a failure ending. It isn’t. It’s a warning.

Optimization note: This ending is unavoidable if Conviction is high but Civilian Trust is below 35.

Ending 5: The Compromise Protocol

This is the balance ending and the hardest to reach intentionally.

Conviction and Alignment must be within five points of each other, and Civilian Trust must be above 60. Miss any of these thresholds and the game pushes you elsewhere.

You negotiate a hybrid solution that preserves the system while exposing its limits. It’s hopeful, but deliberately unresolved.

RNG warning: If Conviction and Alignment are too perfectly equal, the game sometimes re-rolls toward your weaker stat. Reload the scene if needed.

Ending 6: Silent Collapse

This ending triggers when all stats are middling or low.

You neither stop nor endorse the final directive decisively. The system fails quietly, without a villain or hero to blame.

There’s minimal dialogue and the shortest epilogue in the game. That’s the point.

Completionists often miss this ending because it requires resisting optimization. You have to play poorly on purpose.

Ending 7: Scapegoat Protocol

This is one of Episode 8’s most brutal outcomes.

Triggered by high Alignment, low Trust, and refusing public accountability in the final briefing, the system survives by sacrificing you.

Your character’s legacy is rewritten, and multiple scenes are framed from third-party reports instead of direct POV.

This ending unlocks unique codex entries that don’t appear anywhere else.

Ending 8: Total Severance

The rarest ending in Dispatch.

This requires high Conviction, very low Alignment, low Trust, and rejecting both the Episode 7 documentation and the Episode 8 emergency override.

You dismantle the system entirely and walk away. No reform. No replacement.

The final scene fades out without credits music, followed by a delayed epilogue text crawl. Many players think the game bugged here. It didn’t.

Completion Checklist for Episode 8

Use this checklist to ensure you’ve seen everything Episode 8 offers.

Unlock all eight endings, not just variations. Variants do not count toward completion.

Trigger at least one ending with high Trust and one with low Trust to see the full epilogue spread.

View the Analyst’s final conversation in at least two endings. Their dialogue changes significantly.

Read all post-credits codex updates. Several only unlock after specific endings.

Do not rely on Episode 8 autosaves. All meaningful branches must be prepared in Episode 7.

Final Thoughts and Last-Minute Advice

Dispatch doesn’t reward perfection. It rewards intent.

Episode 8 makes that clear by refusing to let you course-correct at the finish line. If your ending feels harsh, it’s because the game is reflecting how you played, not punishing you arbitrarily.

For completionists, this is a rare finale that respects your time. Every ending is deliberate, distinct, and mechanically earned.

Make your saves smart, commit to your choices, and let Dispatch finish the argument it’s been building since Episode 1.

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.