# FlowPilot — Suggested Fix → Resolve CTA merge (Option A)

Option A — Suggested Fix merges into the Resolve CTA
Three versions of the same task lane. Today keeps Suggested Fix as a separate card that gets pushed down by a long facts list. Option A (armed) deletes the card — the Resolve button at the bottom becomes the proposal. Option A (waiting) is what the same bar looks like before the AI emits a proposal.
Today
Baseline
What we know · 5 facts
User cannot authenticate to Outlook; repeated 401s from Exchange Online.
promoted 14:02 · from ticket
Cached credentials in Credential Manager reference a prior tenant the user migrated off six months ago.
promoted 14:07 · from chat
MFA prompt appears then fails silently — no authenticator notification, no error code surfaced to the user.
promoted 14:11 · from chat
Other devices under same account authenticate successfully, isolating the problem to this workstation.
promoted 14:14 · from chat
Office 365 client last updated three weeks ago; local profile not recreated since migration.
promoted 14:18 · from chat
Suggested fix · 94% confidence
Clear cached credentials + rebuild Outlook profile
Remove stale entries from Credential Manager referencing the prior tenant, then rebuild the local Outlook profile so the client re-authenticates cleanly against the current tenant.
✓ Matches an existing Script Library template — click to use
Baseline problem. The Suggested Fix card sits after What-we-know. With 5+ facts (common by mid-session) it's below the fold. The generic Resolve button at the bottom doesn't surface what would be resolved, so the engineer has to scroll up, read the card, then scroll back down to act.
Option A — armed
Proposal ready
What we know · 5 facts
User cannot authenticate to Outlook; repeated 401s from Exchange Online.
promoted 14:02 · from ticket
Cached credentials in Credential Manager reference a prior tenant the user migrated off six months ago.
promoted 14:07 · from chat
MFA prompt appears then fails silently — no authenticator notification, no error code surfaced to the user.
promoted 14:11 · from chat
Other devices under same account authenticate successfully, isolating the problem to this workstation.
promoted 14:14 · from chat
Office 365 client last updated three weeks ago; local profile not recreated since migration.
promoted 14:18 · from chat
What changes. The Suggested Fix card is gone. Its content moved onto the Resolve button, which is always in view. One click = accept the fix + open the existing `ResolutionNotePreview` popover pre-filled. No card-then-button two-step.
Option A — waiting
No proposal yet
What we know · 2 facts
User cannot authenticate to Outlook; repeated 401s from Exchange Online.
promoted 14:02 · from ticket
Cached credentials in Credential Manager reference a prior tenant.
promoted 14:07 · from chat
Before confidence threshold. Same slot, disabled state. Amber pulse signals the AI is still reasoning. Below threshold or no proposal yet → same visual — the engineer can still use Escalate at any time.

#### Why this helps discoverability

- Proposal is in the place the engineer looks to act, not in the scrolling lane above.
- Resolve bar is already sticky at the bottom — no new sticky patterns needed (preserves the `8879f96` fix).
- Accepting a fix and resolving the session collapse into one click instead of two.

#### What you give up

- No space for secondary info on the button (reasoning, alternative fixes). Would need an expand/chevron or hover tooltip.
- No standalone "dismiss this fix" affordance — need to decide where dismiss/reject lives (chevron menu? secondary button?).
- If the AI proposes multiple candidates, only the top one fits the button. Need a "▾ 2 other candidates" menu.