How a prospecting batch becomes sends: the gates a record passes, the tags that show where it is, the caps per channel, the send schedule, and what the outreach workflow must do once it is built.
The niche-1 batch is connected to the engine as data: every record is tagged with its batch and its gate. It is held at the Day 0 gate, so nothing sends.
Done on 11 Oct. All 39 records got ae: batch-2026-09-niche-1. The 37 sendable records got ae: gate-day0-pending. The 2 holds keep ae: hold and no gate tag. Every record is still DND, as imported.
8 sheet records are not in Client Zero. 6 are tier C (3 in wave 3 and 3 WhatsApp-first) and 2 are holds. Load the 6 only if they still pass the gates after Day 0; the 2 holds stay out until the sheet note on each is resolved.
Signal Score, tier, niche, wave. Tagged ae: batch-month-niche.
Form submitted, reply timed, consent basis set, suppressions checked.
Tag ae: gate-ready, DND lifted for email only, sequence start set.
Inside the caps and the send window. Tag ae: in-sequence.
Sequence stops, AE Reply Class set, answered from kyntlo.com.
Audit booked, no, or no reply by day 21. Tag ae: closed.
A record enters the engine only when all six are true. The same rules are in the knowledge base so the agent applies them too.
| # | Gate | Where it is checked | Pass when |
|---|---|---|---|
| 1 | Scored and tiered | AE Tier, AE Wave, AE Track = Engine | Tier and wave are set; Build-track records never enter |
| 2 | Reachable | Email, or tag ae: wa-opener | A published business email. No email means the WhatsApp-first cohort, 5 a day |
| 3 | Lawful basis | Consent Basis | legitimate interest · public business contact |
| 4 | Day 0 logged | AE Day 0 Submitted, AE Day 0 Reply Hours, AE Day 0 Display | Form submitted on their own site and the reply time or silence recorded after 72 hours. Email 1 is built on this |
| 5 | Suppressions | Tags and DND | Not a customer, partner, past bounce or unsubscribe; one firm per domain |
| 6 | Released | Tag ae: gate-ready | Ahmed checked 1 to 5 and lifted DND for email only |
The left column is what applies today. The right is the ceiling once the outreach domain is warm and the agent is signed off. Values live in Client Zero as Cap custom values.
| Channel | Phase 0, now | Agent live, after warm-up | Rule |
|---|---|---|---|
| 1 normal inbox, 15 a day including follow-ups | Outreach domain only, 20 a day per inbox, +10 a week, ceiling 50, 2 to 3 inboxes | Over 2 percent bounce on a day stops that inbox for the day | |
| Business app, 5 to 8 a day | API, 30 to 40 new conversations a day per number | Only after email 1. Never cold | |
| Instagram DM | By hand, inside the touchpoint quota | By hand, inside the touchpoint quota | Only to firms with an active feed; one specific, true detail |
| Voice | 0 | 40 dials a day, A tier only | Registered line first. Never a second dial after a decline |
Domains. kyntlo.ai is the brand and never sends. kyntlo.com is for human replies. msg.kyntlo.com is marketing to people who opted in, and is in warm-up. Cold outreach from the agent goes from a separate outreach domain, warmed for 5 weeks first.
Every email. One-click unsubscribe, replies routed to a human on kyntlo.com, plain text as in the A06 templates. Move DMARC from none to quarantine after 30 clean days.
The sheet's Send schedule tab still shows September dates that have passed. This is the same plan moved to the earliest dates if Day 0 runs on Tuesday 13 Oct. If Day 0 moves, every date moves with it.
| Earliest date | What goes out | Volume | Gate before it runs |
|---|---|---|---|
| Tue 13 Oct | Day 0: submit every form on the timing log | 43 forms | None. This is first |
| Fri 16 Oct | 72-hour clock closes; log silence as silence | - | Every row has a reply time or no reply |
| Sun 18 Oct | Wave 1 · email 1 | 15 | Day 0 complete; wave 1 re-ranked, the slowest responders lead |
| Tue 20 Oct | Wave 1 · WhatsApp 1 to non-repliers | max 8 | Only firms that got email 1 |
| Wed 21 Oct | Wave 1 · email 2, same thread | 15 | - |
| Thu 22 Oct | WhatsApp-first cohort opens | 5 a day | The records with no published email |
| Sun 25 Oct | Wave 1 · email 3, and wave 2 · email 1 | 15 + 10 | Read wave 1: 2 to 3 replies means go; 0 means change the wedge |
| Sun 1 Nov | Wave 3 · email 1 | 10 | Rewrite the two weakest messages first |
Over the phase 0 cap? Sun 25 Oct puts 25 emails on one day, over the 15 cap. Split it: wave 1 email 3 on Sunday, wave 2 email 1 on Monday 26 Oct.
At about 38 percent from scraped to sequence, this is how many records each phase needs. A batch is ordered on Sunday when ready records will run out within 2 weeks.
| Phase | New sequences / day | Ready records / week | Scraped / week |
|---|---|---|---|
| 0 · Manual bridge | wave days | 37 | This batch; runs out after wave 3, around 1 Nov |
| 1 · week 1 | 8 | 40 | 105 |
| 1 · week 2 | 12 | 60 | 158 |
| 1 · week 3 | 16 | 80 | 211 |
| 1 · week 4 | 20 | 100 | 263 |
| 2 · Full run | 27 | 135 | 355 |
The next batch is needed before the agent is. Niche 1 has 37 sendable records in Client Zero. Once wave 3 goes, there is nothing left to send. The next niche-1 or niche-2 batch should be scraped and scored in October so Day 0 can run on it before November.
Workflows cannot be created through the connection used here, so this is the spec for Boush and Keroles to build in Kyntlo. Ahmed signs it off before it sends.
ae: gate-ready added, on a send day, inside the Send Window.ae: replied, and notifies Ahmed.ae: closed.ae: closed, set Last Contact Date, and leave the record for the 90-day re-score.Sends to a record with ae: gate-day0-pending or ae: hold.
Sends from kyntlo.ai, kyntlo.com or msg.kyntlo.com.
Opens a WhatsApp conversation with someone who has not had email 1.
Sends outside Sunday to Thursday, 9am to 9pm Gulf time, or in the first week of Ramadan.
Crosses a cap to hit a quota.
Keeps sending after a reply, a bounce or an unsubscribe.