Follow the caller’s path

This specimen uses fictional records and demonstrates the proposed visual system. Select a flow step to update its inspector. Application operations are disabled; these controls do not publish, deploy, or place calls.

Account context

Flow editor

The current app uses a tree with a selected-step inspector. The start step and each outcome should be legible. On narrow screens, this specimen places the inspector below the tree. A production editor also needs an accessible alternative to any graph-only interaction.

Publication

Publishing creates an immutable revision. Show the version number, validation state, and consequence. A successful publication message should offer deployment as a separate next step.

Phone route

Name the number, route, and published revision being activated. The current app exposes both deployment and rollback. A ready deployment is a prerequisite for rollback; do not show an available rollback based only on a publication existing.

Call history

Durations use tabular numerals. Keep an individual call result distinct from the complete session or media availability. Show timezone and the actual recording state in the application.

Voicemail

Recording and transcription have their own states. If audio is missing, explain it rather than drawing a fake player. Keep the original recording available when a transcript exists.

Use in the application

Preserve the existing Rails account scope, form methods, and controller behavior when adopting these patterns. Replace the specimen’s local JavaScript with the application’s normal Stimulus controllers. Test tree navigation and inspectors with a keyboard, long names, missing media, empty data, validation failures, and narrow viewports.