Opening record detail
On the Records page, clicking a row does not open the full debug timeline. It opens a detail panel below the table so you can review one contact without leaving the list.
That design is intentional: supervisors scan many rows; builders open the journey only when something needs investigation.
What Records is for
Section titled “What Records is for”Records answers day-to-day operations questions:
- Who was contacted?
- What happened?
- When?
- Which spinner ran?
It is not a copy of your data table, and it is not the primary debug screen.
src/assets/screenshots/09-records-outcomes.pngHow to open detail
Section titled “How to open detail”- Open the project → Records.
- Click any row in the list.
- A detail panel appears below the table (the list stays visible above).
Rows stay one line tall. Long text is truncated with an ellipsis so the grid stays scannable. Full text lives in the panel.
src/assets/screenshots/35-records-detail-panel.pngWhat the detail panel shows
Section titled “What the detail panel shows”| Section | Purpose |
|---|---|
| Metadata (pipeline input) | Only configured metadata fields — the contact context that entered the run |
| Outreach outcome | Disposition, AI reply, channel references — operational results, not internal log noise |
| Actions | Pipeline journey (debug) and Close |
You get enough context to act (follow up, coach, escalate) without loading every step event for every click.
What does not happen on click
Section titled “What does not happen on click”Clicking a row does not:
- Open the pipeline journey drawer automatically
- Navigate away from Records
- Load the full source CSV row from Data tables
Journey is one deliberate click away when you need it. See When to use the journey.
Why the panel sits below the table
Section titled “Why the panel sits below the table”At high volume, operators compare contacts side by side in the list while reading one person’s detail. A full-page takeover or an instant journey drawer would interrupt that flow.
The pattern is:
- Scan the list (status, contact, outcome, spinner, when)
- Select a row for more detail
- Open journey only if the outcome is wrong, failed, or unclear
Success looks like
Section titled “Success looks like”- You can review a contact in a few seconds without leaving Records
- Metadata and outcome are easy to tell apart
- The list remains visible so you can move to the next row quickly
- Journey stays optional, not the default click target
Common problems
Section titled “Common problems”| Problem | What is going on | What to do |
|---|---|---|
| “Click does nothing useful” | Expecting journey or full CSV | Read metadata + outcome in the panel; use Data tables for source data |
| Detail looks incomplete | Metadata fields not set, or step wrote no outcome | Fix metadata / spinner, then run again |
| Need step-by-step errors | Detail is ops-focused by design | Click Pipeline journey |
| Lost the list context | Looking for a modal or new page | Scroll — panel is below the table |
Closing the panel
Section titled “Closing the panel”Use Close on the panel, or click another row to switch focus. Closing does not delete anything; it only hides the detail view.