Sign in with your Renaissance Google account to log a booking.
| Time (ET) | Status | Lead | Business | Partner | CC address | By |
|---|---|---|---|---|---|---|
| Loading | ||||||
Paste or type a phone number or an email address — instantly see whether it submitted a funding web form. Phone matching is on the last 10 digits, so +1 / dashes / spaces don't matter; email has to match exactly.
Search your bookings to edit or delete — or pick a date to see every booking that day.
Account-grain, independent of campaign attribution: sends from the per-account daily actuals, replies from the reply drain keyed on the sending account. The drain runs ~75–80% of the Instantly analytics count, so read reply rate here as a ranking, not a level.
A campaign is tied to a sender in this order: the infrastructure registry, then the sending accounts that carried its replies, then the convention in its name. Anything left over is shown as Unmeasured rather than dropped.
Emails sent is the true daily count. Lead-grain rows is how much of that day we can read mailbox-by-mailbox; on a day below 50% the lane split is carried on each campaign\'s mix from the rest of the window.
daily_limit of every
SEND-READY account carrying one of the six infra parent tags: Reseller · Outreach
Today · MilkBox · MailIn · MailIn SMTP · Koldify. Send-ready = Instantly status == 1
(so never paused, never in a connection / soft-bounce / sending error state) and carrying no
status_message — the second half matters because an inbox whose OAuth has permanently
failed still reports status == 1 while being physically unable to send.
Not every workspace carries every lane — which lanes a workspace holds on the day you are
looking at is what the per-workspace breakdown below shows, and the sub-heading names the
workspaces on the Koldify lane that day. Each account contributes its own configured limit;
nothing is ever averaged or multiplied out across a pool.
Deduped by email, so an account on two lanes is counted once in the workspace total. Warm-up volume is
a separate quota and is never counted. (Sam's spec, 2026-08-28. Maxify is excluded entirely.
Google Panel and Microsoft Panel are still censused but are NOT counted here — which is why this
tab's fleet total will not reconcile to the Infra tab's, where Google Panel IS counted.)
rest_windows.json and cover past days too, so turning one on corrects the whole
week on the next hourly publish. (Sam, 2026-09-17: "we were resting then, so it shouldn't
be added. It's incorrect to say that it should have sent 224,000.")/campaigns/analytics/daily with no campaign_id), split into lanes by the
per-campaign rows. ⛔ A per-campaign sum is not the workspace total — it drops every campaign
deleted or renamed out of the window. That hole was worth 560,103 sends on 08-27 in F5 alone
(rendered 110,045; the workspace actually sent 670,148). Volume the listed campaigns cannot account
for now appears as its own unattributed lane instead of vanishing — and it is not simply
deleted campaigns: F5's campaign list is complete and its lifetime per-campaign totals are
smaller than four days of its workspace sends, while two independent Instantly aggregates
(workspace-grain daily and the analytics overview) agree with each other to the digit. Instantly's
per-campaign breakdown is incomplete at the source, so the residual is parked, never proportioned
across the real lanes. A campaign
bound to two infra parent tags cannot be split truthfully at campaign grain, so it is reported
separately rather than proportioned.Messages sent per meeting booked. Lower is more efficient.
What each loop-in costs us to produce, and what it sells for.
Every business-funding web-form fill, and which partners it went to.
Cold email, month over month.
Add a new dropdown value (e.g. a new advisor). It's available across the form immediately, for everyone.
Choose which columns to include. Save a set as a template to reuse it; the last set you exported is remembered automatically.