Portal command lock
Support
Support should feel like guided resolution with context already attached, not a generic help screen.
Primary command surface
Dashboard
Best next step
Choose the support path tied to the live blocker so the right team can act without re-explaining the situation.
Guided resolution

Resolve blockers without losing context

Users should know which path to open, why it matters now, and what resolution outcome to expect after they ask for help.

Now
Open the right support path
Support works best when users do not have to translate the blocker twice.
Expected outcome: Lower resolution time
Today
Preserve journey context
The most trustworthy support experience already knows where the user is stuck.
Expected outcome: Less repetitive back-and-forth
Primary job
Route the blocker
Need
Context attached
Next step
Open correct path
Outcome
Faster resolution
Blocker visibleOwner visibleExpectation visibleResolution visible
Route-owned brief

Escalate missing stipend ticket

The case gains urgency before timing drift widens the loss.

Blocked action: The issue is still blocking payout confidence.
Readback after action: The case gains urgency before timing drift widens the loss.
escalate-nowThe issue is still blocking payout confidence.Score 56
Top action
Escalate missing stipend ticket
Why now
The issue is still blocking payout confidence.
Readback
The case gains urgency before timing drift widens the loss.
Next route
/pay
Credalyst Portal · Canonical staffing journey

Support

Route blockers into help with the right staffing context already attached.

Status: Support ready

Journey command surface

Owner: Support · SLA: Now

Why this surface exists

Support ensures blockers can be resolved with context, status, and ownership visible.

Ownership and SLA

Owner: SupportSLA: NowNext action visible

Support continuity

  1. Blocker identified
    Owner: SupportSLA: Closed
  2. Owner attached
    Owner: SupportSLA: Closed
  3. Resolution path openedOpen the right help path
    Owner: SupportSLA: Now
Context-aware help

Route blockers into help with the right staffing context already attached.

This portal command surface is no longer a thin route wrapper. It now carries intelligence, next actions, system memory, trust posture, and a direct bridge into the canonical opportunity workspace.

Intelligence visibleSystem memory preservedTrust layer visiblePremium portal shell
System memory
5 signals
Decision stage
Support ready
Confidence
98%
Next best action
Open the right help path
Portal command lock
Support
This route now specializes in one decision job and should never compete with dashboard as the portal home surface.
Primary command surface
Dashboard
Best next step
Open the right help path
Live opportunities
3
Primary owner
Support
System memory
5 signals
Trust posture
4 checks
Score
100/100
Risk
Moderated
Prediction
6 likely matches
Next best action
Open the right help path
Consequence if delayed
The system will keep surfacing the same blocker until the guided action lands.
Route-owned brief
Escalate missing stipend ticket
Escalate the missing stipend ticket before the current payout window closes.
Blocked action: The issue is still blocking payout confidence.
Consequence: The case gains urgency before timing drift widens the loss.
Readback after action: Readback after action: The case gains urgency before timing drift widens the loss.
Immediate next action
Open the right help path
Intelligence
Signal 1
Support opens with blocker context already preserved.
Signal 2
The user does not have to restate the same work journey from scratch.
Signal 3
Critical issues can bridge directly into trust, status, or the live opportunity workspace.
Decision intelligence
Score
Score blends visible intelligence signals, trust posture, and memory continuity into one operating read.
Risk
Risk now stays visible before the clinician or team commits the next move.
Prediction
Projected match movement over the next 21 days based on current trust and intelligence coverage.
Next best action
Each module now points to a committed next move instead of acting like a detached side route.
Why the score holds
Coverage
The workspace now shows intelligence, memory, and live opportunities in one operating frame.
Trust posture
Trust checks stay visible alongside the decision surface instead of being hidden in another route.
Action clarity
The next best action now exits directly into canonical opportunity flow.
Opportunity models
WorkOpportunity
The clinician-side opportunity that carries match score, trust posture, pay summary, schedule shape, and next actions. Owner: Credalyst Portal
SystemOpportunity
The operator-side opportunity that carries stage, estimated value, installed modules, missing modules, and expansion timing. Owner: GrowthOS
Revenue conversion path
Site discovery
Public proof, ROI, and workflow narrative qualify the buyer before a generic sales handoff happens. CTA: Qualify facility demand
Portal decision
The portal can hold timeline, next actions, trust posture, and buyer-visible signals without resetting context. CTA: Review the command workspace
Growth execution
GrowthOS turns the qualified buyer into a SystemOpportunity with stage, estimated value, and expansion pressure. CTA: Advance the system queue
System memory
Last touch
Support context attached
Last action
Open the right help path
Last outcome
Blocker routed with context
Prior owner
Support
History depth
4 support checkpoints
Action density lock
Next action
Open the right help path
Expected effect
Progress moves faster because the system narrows the safest high-value move.
Consequence if delayed
Stage progress slows and trust/readiness drift gets worse.
Why now
Support opens with blocker context already preserved.
Last touch
Support context attached
Last outcome
Blocker routed with context

Canonical links