Lists & Pipeline | Audienti

Purpose

Lists and pipeline views keep prospect work organized after prospects enter Audienti. Use them to control intake, ownership, routing, review, nurture, and rejection states.

Queue mode orientation

Prospect queue, list, and pipeline modes shown as three operating views — Use queue for next actions, list for scoped review, and pipeline for stage movement.

Steps

Use lists for clear intake groups: imports, webhook endpoints, campaigns, or nurture pools.
Use queue mode when the next action matters more than the source list.
Use pipeline mode when ownership and stage movement are the priority.
Use rejection and nurture states deliberately so operators do not re-review the same bad fit.

Verification

Every active list has a current owner and clear source.
Pipeline stages reflect the prospect's real operating state.
Assigned-user filters match the operator responsible for next action.
Nurture and rejected prospects leave the active review path.

Common mistakes

Using lists as permanent storage instead of operating groups.
Leaving stale prospects in active pipeline stages after they should be nurtured or rejected.
Assigning prospects without confirming the owner can take the next action.