Projects overview
A project is the main container for day-to-day work. Instead of mixing every client into one list, you give each campaign or client its own project with its own tables, spinners, and outcomes.
Why projects exist
Section titled “Why projects exist”- Keep data and automation for Client A separate from Client B.
- Apply different modules (Outreach vs Call Analyzer).
- Scope analytics and records to one body of work.
Screenshot needed
Inside a project — left project nav (Data tables, Spinners, Jobs, Records, Settings).
Where: Open any project
Save as:
src/assets/screenshots/15-project-nav.pngProject types
Section titled “Project types”Outreach
Section titled “Outreach”Use for contact lists and multi-channel automation: WhatsApp, SMS, email, voice, AI drafting, dispositions. The Records page shows outreach outcomes (who, what happened, when).
Call Analyzer
Section titled “Call Analyzer”Use for post-call work: recordings, transcription, tags, QA scores, summaries. The Records page shows analyzed calls.
You choose the type when you create the project. That choice shapes which menu items and processors you see.
What lives inside a project
Section titled “What lives inside a project”| Area | Contents |
|---|---|
| Data tables | Source contacts or call rows |
| Spinners | Pipelines |
| Jobs | Runs of those pipelines |
| Records | Outcomes for ops |
| Settings | Project-level options |
| PCA pages | Setup, tags, QA (analyzer projects) |