Your lists, imported by CSV and organized for dialing

Lists enter through a CSV workflow: a file from a list vendor or an export from your CRM, uploaded to the list you choose. Headers are normalized and each row's phone number is validated and standardized, because a queue is only as good as its numbers. Rows without a usable number are rejected.

There is no native CRM or list-vendor integration, and that is a choice rather than a gap. A CSV is a file you can inspect, test with synthetic records in the sandbox, and confirm separately before production. An integration would move that verification out of your hands.

A completed import is not a release decision. The permission review, registry scrub and eligibility check happen before the list reaches a session, and they belong to your business. Import is plumbing; release is judgment.

Once imported, leads organize into lists, groups and ponds. The sidebar shows live counts per group, and the count matches what the signed-in role can actually access, so an operator is never surprised by a queue they cannot dial.

Session setup then slices the work: pick lists, statuses and ponds, or name up to 200 specific leads. The dialer queues exactly that slice, applies quiet hours, DNC and caps per lead, and skips anything that fails a gate with a recorded reason.

For data leaving the workspace, an admin CSV export of the lead table covers audits, migrations and departures. Import and export are both explicit, file-based actions, so data moves when you move it.