End-to-end journey

BRD process map — phases highlight as the workflow progresses.

Go to Console

Live event stream — ISS-2041

Open issue →

DATADOGBancolombia · B&M · Bank Deposit · latency > 90m01:25 PM
REGISTERIssue ISS-2041 registered — 23 affected · ETR 3h02:42 PM
NOTIFY12 B&M customers SMS'd new ETA02:43 PM
AGENTCare Agent opens order us100000003 — sees issue context02:47 PM
UPDATEIssue ETA pushed +3h — 11 customers re-notified03:31 PM

Phase 2 detail

Register Delay

Phase 2Three-step wizard

What happens

Transmissions agent opens the Register Delay wizard, defines the affected scope (correspondent, stage, entry method, delivery method, start and end time — both required), previews the matched orders, then confirms an Estimated Time to Resolution.

Who's involved

Transmissions agent.

Inputs

•Correspondent #
•Stage (Pre/Post-Sent)
•Entry & Delivery method
•Affected time range (start + end)
•ETR (hours + minutes)

Outputs

•Issue draft → atomic commit on Register

Rules & guardrails

•Nothing is persisted until 'Register' is pressed.
•Cash Pickup is excluded from the entire flow, both stages.
•Office Pick Up is disabled when stage = Post-Sent (money already available for pickup).
•Overlap with an open issue (same correspondent + stage + delivery) shows a warning and excludes the already-covered orders.
•ETR is captured in the confirm modal, not during scoping.

End-to-end journey

Detection

Register Delay

Issue created

NOTIFY dispatch

Customer surfaces

Resolution

Live event stream — ISS-2041