A GUIDED WORKFLOW
Follow an account decision from context to next step.
Follow a fictional account through shared context, Twin preparation, human review and governed follow-through.
Illustrative example · Fictional account scenario.
Source and action availability must be confirmed for the environment being evaluated.
Illustrative view
Illustrative example · Fictional account scenario
A fictional account, start to finish
Source and action availability must be confirmed for the environment being evaluated.
01 — THE SITUATION
An account review is approaching. A technical commitment is still open.
The account owner needs to understand whether a delayed integration milestone affects the customer's planned rollout.
The relevant story is spread across an account plan, a support issue, a project update and meeting notes.
02 — THE CONTEXT
Bring the permitted evidence into one review.
The account view relates the customer goal, the open commitment and the available technical updates. The source references remain visible.
One important question is unresolved: the latest support update does not establish whether the milestone can still be met.
SpineWorkspace · Key Workbench viewsIllustrative view · no live data
CSM Accounts Hub
Account 360
Account Health
CS Decision Log
Success Plans
03 — THE PREPARATION
Ask the Twin: “What needs attention before this review?”
Spine Twin · Example responsePrepared from permitted account context
The open integration milestone may affect the planned rollout. The available updates do not confirm a revised delivery date. I suggest asking the technical owner for a verified status before making a new customer commitment. I can prepare an internal follow-up for your review.
Human review · awaiting approval
The proposal keeps a possible impact separate from a confirmed delay and makes the missing evidence explicit.
04 — THE DECISION
Review the proposal and its scope.
The account owner checks the evidence and proposed follow-up. If the requested operation is supported, Runtime evaluates whether it can proceed and whether approval is required.
A change to the proposal's target or operation calls for an appropriate authority evaluation.
05 — THE FOLLOW-THROUGH
Keep the requested action and its result distinct.
If the operation proceeds, the work records its status and the result that can be observed. A request accepted by a source system remains pending until the relevant completion evidence is available.
The next account review can continue from the decision, the follow-up and any unresolved question.
A GUIDED WORKFLOW
The evidence, the decision and the outcome stay with the work.
Capabilities, availability and supported systems are confirmed per deployment during evaluation.
Illustrations are indicative. Source systems stay authoritative. Authority stays with people.