Outreach outcomes
For Outreach projects, Records is the operations screen. It is not a copy of your data table.
What you see in the list
Section titled “What you see in the list”| Column | Meaning |
|---|---|
| Status | completed, failed, waiting, … |
| Contact | Metadata fields joined on one line |
| Outcome | Best operational result (disposition, AI text, message id, …) |
| Spinner | Which pipeline ran |
| When | Completion time |
Rows stay one line tall. Long text is truncated with an ellipsis.
Screenshot needed
Records list with compact rows and detail panel open.
Where: Project → Records
Save as:
src/assets/screenshots/09-records-outcomes.pngDetail panel
Section titled “Detail panel”Click a row to open details below the table:
- Metadata (pipeline input) — only configured metadata fields
- Outreach outcome — disposition, AI reply, channel references (not internal log noise)
- Actions: Pipeline journey (debug) and Close
Why this design
Section titled “Why this design”At high volume, supervisors need:
- Who
- What happened
- When
They do not need every intermediate log field in the grid. Debug timelines stay one click away.
Source data
Section titled “Source data”Browse imports under Data tables, not Records.