Lists and import
Lead lists arrive as CSV: upload, map, import, and the leads land in your workspace. Lists and groups keep a large file organized, and session filters pick which slice rings. There is no native CRM integration, by design, so your list stays a file you control and test.
Product interface, sample data. Phone: picking lists before a session.
4 steps, in the order they happen during a session.
Use ← → to step through.
Arrow keys move between steps. Lettered spots on the picture match the list under it.
Pick a list and upload a CSV. Headers are normalized, phones are required and converted to a standard format, and rows without a usable number are rejected rather than half-imported.
Upload a CSV into the open list List name and how many leads it holds Each row is a lead with a phone Lead groups sit in the sidebar with live counts, so operators pick a slice without building filters every session. Counts reflect what each role can actually access.
All leads you can access, with the count Named lists with a live count each Groups sit under the lists Session setup filters by list, lead status and lead list, up to 200 explicitly picked leads. The queue you release is the queue that gets dialed, nothing else.
This list is the one that will be dialed Only these lead statuses enter the queue Start dials the queue you just set An admin can export the lead table as CSV, which covers audits, migrations and moving your data elsewhere. Import and export both go through the file you control.
What the product does today. Plans from $29 per seat. Breeze, $29, is everything faster: continuous dialing and call notes. Three lines are Jetstream, $49.
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 a small file, 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 and groups. 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 lead lists, 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.
Straight answers. Anything else: email support.
Pick your plan and seats, check out, then set your password from the set-password email. Calling credit is optional at checkout, but you need credit to dial. Add it any time from your dashboard. Month to month. Pick your plan and seats, check out, then set your password from the set-password email. Calling credit is optional at checkout, but you need credit to dial. Add it any time from your dashboard.
