checking…
Built by
Overview
Latest releases
| When (ET) | SDR | Released by | Sequence | Leads | Where they got to |
|---|---|---|---|---|---|
| Loading… | |||||
Enroll
1Refresh
2Choose who
The standing rules are already applied
Has a phone or mobile number and an email address; lead status and lifecycle stage on the allowed list; called fewer times than the threshold; not on the suppression list.—
match
What was actually applied
Show the exact query this produced
| Contact | Phone | Mobile | Company | Job title | Owner | Campaign | Apollo list | Lead status | Lifecycle | Our calls | Last call (ET) |
|---|---|---|---|---|---|---|---|---|---|---|---|
| Press Count them to see who matches. | |||||||||||
Scroll sideways for phone, mobile, job title, Apollo list, lifecycle and last call. The name column stays put.
3Choose where they go
Pick the sender first
The sequence list is whatever that HubSpot user can reach. The property is optional, and is written only onto contacts HubSpot accepted.4Push
Release history
One row per push. Open a row to see every contact in it.
| When (ET) | SDR | Released by | Sequence | Leads | Where they got to |
|---|---|---|---|---|---|
| Loading… | |||||
| Who | Sequence | Sender | State | Tries | Reason | Queued |
|---|---|---|---|---|---|---|
| Search for someone above. | ||||||
← All releases
| Who | SDR | State | Tries | Why, if it did not go | Sent | Confirmed |
|---|---|---|---|---|---|---|
| Loading… | ||||||
Contact upload
A file of contacts, mapped to HubSpot properties and attached to the company you name. No company is ever created.
1Choose the file
What the file needs
A header row and one contact per line, saved as CSV. Every row needs an email address and a primary associated company id — the company's Record ID in HubSpot. Rows missing either are listed back to you and never sent. A company id that no longer exists in HubSpot fails that row: nothing here ever creates a company.2Map the columns
How the map works
Every column in your file is listed against every contact property in the portal. What you choose is remembered, so the next upload of the same export needs no mapping at all. Two columns are not properties and are chosen separately: the email, and the company id the contact is attached to.| Column in your file | First value | HubSpot property |
|---|
3What will happen
| Row | Company id | State | HubSpot id | Reason | |
|---|---|---|---|---|---|
| Loading… | |||||
Recent uploads
| When (ET) | File | By | Rows | Created | Updated | Failed | State |
|---|---|---|---|---|---|---|---|
| Loading… | |||||||
Lead tracker
How many leads were assigned to each SDR, and on what day.
Leads assigned per day
By SDR
Days counts only the days that SDR was assigned anything.
| SDR | Leads | Share | Days | Avg/day | Top lead statuses |
|---|---|---|---|---|---|
| Loading… | |||||
Lead status
Where the leads assigned in this range have got to.
Status comes straight from HubSpot’s Lead Status on the contact.
| Status | Leads | Share | By SDR |
|---|
Day by day
The same numbers as the chart, readable without colour.
Settings
The master switch
What the switch does
Off means nothing is sent and the queue waits. Confirmation still runs either way — it only reads HubSpot.Limits in force
| Loading… |
You
| Loading… |