Sales Quotas
Kyntlo Outbound engine · Ahmed Sales quotas Once the agent is sending, the job stops being send the emails and becomes own the numbers. These are the daily numbers Ahmed owns, the caps they sit inside, and how they step up as the engine earns the right to send more. Owner Ahmed · support Boush Task A11 · P1 Phase now 0 · manual bridge Version 1.0 · 11 Oct 2026 Outbound engine 1 Sales quotas 2 Batches into the engine 3 Weekly review Related Cold outreach playbook Cold outreach status Assigned 11 Oct 2026 Today's quotas These are live in Client Zero as custom values. They are Phase 0 numbers: the agent is not built yet, so Ahmed still sends by hand, from his normal inbox, inside the phase-zero limits. Touchpoints 15 per send day, all channels Follow-ups 10 of the 15, per send day Audits booked 1 per week Email cap 15 per day, 1 inbox WhatsApp cap 8 per day, Business app Voice 0 no registered line yet The numbers are set, the sending is not. As of 11 Oct no niche-1 message has gone out: Day 0 has not been run, so 0 of 43 forms are logged, and email 1 cannot be written without each firm's own result. The quotas start counting on the first send day after Day 0 is logged. Quota is a floor, cap is a ceiling. A quota is the activity Ahmed is accountable for on a send day when there are enough ready records. A cap is a hard limit that is never crossed, whatever the quota says. Anything over the cap waits for the next send day. So everyone counts the same way Definitions Term Counts Does not count Touchpoint Any outbound message to a prospect: an email, a WhatsApp message, an Instagram DM, a dial that connects. First touches and follow-ups both count. Replies to someone who wrote back. Internal notes. Day 0 form submissions (those are research, logged separately). Follow-up Touch 2 onwards in the sequence to a firm that has not replied: email 2 to 5, WhatsApp 1 and 2, the Instagram DM, the day 18 new angle. Answering a reply. That is never capped, never counted against the quota, and is done within 2 working hours. Audit booked A call on the audit calendar (the Audit Call Link) with a decision-maker at a prospect firm, booked from outbound. Calls with partners, existing clients, or inbound leads. A booking that is cancelled before it happens. Send day Sunday to Thursday, 9am to 9pm Gulf time. Friday, Saturday, public holidays, and the first week of Ramadan. Derived, not guessed Where the numbers come from The full-run quotas are the Acquisition Engine's monthly funnel turned into a send day. The early quotas are the same rates applied to what the caps allow. Engine step Per month Note Scraped per month 1,550 Engine target, all niches Into a sequence (about 38 percent) 590 the rest fail a gate Engagements (8 percent) 47 the fragile number Meetings, here audits booked 14 about 3 a week Discoveries 10 Pilots 6 Signed 3 per month New sequences per day. 590 a month over about 22 send days is 27 a day . Touchpoints per day. Each sequence has 5 emails, 2 WhatsApp messages and 1 Instagram DM over 21 days. Once the pipe is full, 27 new a day means about 135 emails a day: that needs 3 warmed inboxes at their 50 ceiling. Audits per week. 14 meetings from 590 sequences is 2.4 percent. Weekly audits = new sequences that week x 0.024, rounded, with a 2 week lag. Phase 0. The phase-zero test is 15 emails. 2 to 3 replies means scale, 1 means retarget, 0 means change the wedge. With 37 sendable firms in this batch, 1 audit a week is the honest target. Earned, one week at a time The ramp Each row is a phase. A row only unlocks when its gate in the second table is met and the Sunday review says raise. Touchpoints are set at 80 percent of the combined email and WhatsApp caps; follow-ups are touchpoints minus new sequences. Phase Inboxes x cap Email / day WhatsApp / day Voice / day New seq. / day Touchpoints / day Follow-ups / day Audits / week 0 · Manual bridge now 1 x 15 15 8 0 15, 10, 10 on wave days 15 10 1 1 · Agent, week 1 2 x 20 40 15 0 8 44 36 1 1 · Agent, week 2 2 x 30 60 20 0 12 64 52 1 1 · Agent, week 3 2 x 40 80 30 0 16 88 72 2 1 · Agent, week 4 2 x 50 100 30 0 20 104 84 2 2 · Full run 3 x 50 150 40 per number 40, A tier 27 152 125 3 Phase Gate to enter 0 · Manual bridge Day 0 logged for the wave. Normal inbox, WhatsApp from the Business app. 1 · Agent, week 1 Outreach domain warmed for 5 weeks; the B23 workflow signed off by Ahmed; phase 0 read: 2 to 3 replies from the first 15. 1 · weeks 2 to 4 The Sunday review says raise. WhatsApp moves to the API number. 2 · Full run Third inbox warmed; reply rate inside 6 to 12 percent. Voice only once a registered line and an A tier exist. WhatsApp follows email. Only firms that got email 1 first, never cold. 30 to 40 new conversations a day per number on the API, 5 to 8 a day from the Business app. When the queue is bigger than the cap, the rest roll to the next send day. Voice waits. 40 dials a day, A tier only, 9am to 9pm, and never a second dial after a decline. There is no registered line and no A tier today, so the voice quota is 0. Where they live Assigned in Client Zero 14 custom values hold the quotas, caps and thresholds, so the agent and every workflow read one source. Change a number there and everything that uses the key follows. Custom value Key Value on 11 Oct Quota Owner {{ custom_values.quota_owner }} Ahmed Quota Phase {{ custom_values.quota_phase }} Phase 0 - manual bridge, agent not live Quota Daily Touchpoints {{ custom_values.quota_daily_touchpoints }} 15 Quota Daily Follow-ups {{ custom_values.quota_daily_followups }} 10 Quota Weekly Audits Booked {{ custom_values.quota_weekly_audits_booked }} 1 Cap Email Per Inbox Per Day {{ custom_values.cap_email_per_inbox_per_day }} 15 Cap Sending Inboxes {{ custom_values.cap_sending_inboxes }} 1 Cap WhatsApp Per Day {{ custom_values.cap_whatsapp_per_day }} 8 Cap Voice Dials Per Day {{ custom_values.cap_voice_dials_per_day }} 0 Cap Bounce Halt Percent {{ custom_values.cap_bounce_halt_percent }} 2 Reply Rate Target {{ custom_values.reply_rate_target }} 6-12 percent healthy, alarm under 3 percent Positive Reply Share Target {{ custom_values.positive_reply_share_target }} over 40 percent healthy, alarm under 25 percent Send Window {{ custom_values.send_window }} Sunday to Thursday, 9am to 9pm Gulf time Quota Review Day {{ custom_values.quota_review_day }} Sunday, before the first send To change a quota. In Kyntlo open Client Zero, go to Settings, then Custom Values, search for Quota or Cap, edit the value, save. Change Quota Phase in the same sitting so the two never disagree. Plain hyphens only: the platform rejects the long dash. The agent's copy. The same rules are written as 3 FAQs in the knowledge base A06 Outbound copy and rules: the current quotas and caps, the entry gates, and the weekly cap rules. Update the FAQ when a phase changes. Supervising, not sending Ahmed's send day From the day the agent is live, this replaces sending the weekly 50 by hand (A02). In Phase 0 the same checklist applies, with Ahmed doing the sends himself. 9am, before the first send Open the gate view: contacts tagged ae: gate-ready . Is there enough for today's new sequences? Check yesterday's bounces. Over 2 percent on any inbox means that inbox does not send today. Confirm the counters reset: emails per inbox, WhatsApp, dials. Through the day Every reply answered within 2 working hours, from a human inbox on kyntlo.com. Classify each reply in AE Reply Class. A positive reply gets the audit link the same day. Stop the sequence for anyone who replied, unsubscribed or bounced. Before 9pm Log the day: touchpoints sent, follow-ups sent, replies, audits booked. Under quota? Write one line why: no ready records, cap hit, or the engine stopped. Anything odd goes to Boush the same evening, not on Sunday. Sunday Run the weekly review before the first send. Raise, hold or cut the caps, then update the custom values and Quota Phase. Order the next batch if ready records will run out within 2 weeks. Honest limits What is not done yet Nothing enforces the quotas yet. They are stored as values; no workflow counts sends or stops at a cap. That needs the outreach workflow, which has to be built by hand in Kyntlo (B23, Boush and Keroles). Until then the caps are a rule Ahmed follows. No sends, so no actuals. Day 0 has not been run, no niche-1 email has gone out and no audit has been booked on the audit calendar since 1 Sep. The first real numbers arrive in the first week after Day 0. No outreach domain. Playbook 02 keeps cold outreach off kyntlo.ai, kyntlo.com and msg.kyntlo.com. The separate outreach domain still has to be bought and warmed for 5 weeks, so Phase 1 cannot start before then. Quotas are per person, the values are per account. Client Zero has one set of values. If a second sender joins, split the quotas in this page and add a suffix per person. Kyntlo · Own Tomorrow · Internal. A11 · owner Ahmed, support Boush. Built 11 Oct 2026 from the Acquisition Engine and Playbooks 01 to 03 v2.1. Version 1.0.