KyntloOutbound engine · Ahmed

Weekly outbound review

Every Sunday, before the first send: read deliverability and replies for the week, then raise, hold or cut the caps. Thirty minutes, one page, one decision per inbox.

OwnerAhmed · with Boush
TaskA11 step 3
WhenSunday, before 9am
Version1.0 · 11 Oct 2026
Outbound engine1 Sales quotas2 Batches into the engine3 Weekly reviewRelatedCold outreach playbookCold outreach status
What to read

The eight numbers

Opens are not on the list: privacy features make them unreliable, and the Engine judges messages on replies. Reply rate and positive share use the thresholds in the Acquisition Engine.

MetricHow it is countedWhere to read itHealthyAlarm
SentEmails, WhatsApp, DMs, dials, per inbox and per channelSequence tracker; conversationsMatches the quotaUnder quota 2 days running
Bounce rateHard bounces / emails sent, worst single dayEmail stats per inboxUnder 2 percent every dayOver 2 percent any day; over 5 percent is a cut
Spam complaintsComplaints / emails deliveredGoogle Postmaster Tools for the outreach domainUnder 0.1 percent0.3 percent or more
Reply rateFirms that replied / firms that got at least email 1Reply log; AE Reply Class6 to 12 percentUnder 3 percent
Positive sharePositive or curious replies / all repliesAE Reply ClassOver 40 percentUnder 25 percent
Audits bookedNew calls on the audit calendar from outboundAudit calendarWeekly quota met0 for 2 weeks with replies coming in
UnsubscribesUnsubscribes / deliveredEmail statsUnder 1 percentOver 2 percent
Ready recordsRecords tagged ae: gate-ready not yet startedContacts view2 weeks of new sequences or moreUnder 1 week
Volume follows health

Raise, hold or cut

Caps move once a week, on Sunday, never in the middle of the week except to stop. The bounce halt during the week is automatic: over 2 percent on a day stops that inbox for the rest of the day.

If last weekDecisionDo this
Clean: no day over 2 percent bounce, complaints under 0.1 percent, reply rate 3 percent or moreRaise+10 per inbox per day, up to the ceiling of 50
Any day bounced 2 to 5 percentHoldVerify every address in the next batch before it is released
Complaints 0.1 to 0.3 percentHoldCheck the unsubscribe link, the targeting and the first line
Any day over 5 percent bounce, or complaints 0.3 percent or moreCutHalve the cap, rest the inbox 2 days, check the domain records and the list source
Reply rate under 3 percent, delivery cleanHoldSecond week in a row: the message or the wedge is wrong. Rewrite before the next wave; more volume will not fix it
Reply rate 3 to 6 percentRaise allowedTest one message change this week
Positive share under 25 percentRe-scoreThe wrong firms are replying. Re-score the next batch before release
Fill in, read the answer

Decide the cap

Put in last week's numbers for one outreach-domain inbox. The answer follows the rules above. In Phase 0 the normal inbox stays at 15 whatever the answer: raising it is not allowed.

Fill in the first three boxes
Sunday, 30 minutes

Run the review

  1. Pull the eight numbers for the week, Sunday to Thursday, per inbox and per channel.
  2. Put each inbox through the cap rules. Write one decision per inbox: raise, hold or cut.
  3. Update the Cap custom values in Client Zero and, if the phase changed, Quota Phase and the knowledge base FAQ.
  4. Read every reply of the week in full. Copy the two most common objections into the reply log.
  5. Check ready records. Under 2 weeks of supply: order the next batch today.
  6. Fill in the template below and post it to the team. Then send.
Copy, fill, post

The review template

Tokens in pink are filled in each week. The reviewer's name follows the sender dropdown on the cold outreach pages.

Weekly outbound review
Weekly outbound review - week of {{week_start}}
Phase: {{phase}}   Reviewed by: {{sender}}

SENT  email {{emails}} | WhatsApp {{wa}} | DM {{dm}} | dials {{dials}}
Quota met on {{days_met}} of {{send_days}} send days

DELIVERY
Worst-day bounce: {{bounce}} percent   Complaints: {{complaints}} percent
Unsubscribes: {{unsubs}}

REPLIES
Reply rate: {{reply_rate}} percent (last week {{reply_prev}})
Positive share: {{positive}} percent
Audits booked: {{audits}} against a quota of {{audit_quota}}

DECISION PER INBOX
{{inbox_1}}: {{raise_hold_cut}} -> new cap {{cap_1}}
{{inbox_2}}: {{raise_hold_cut}} -> new cap {{cap_2}}

TOP OBJECTION THIS WEEK
"{{verbatim}}"

NEXT
Ready records left: {{ready}} ({{weeks}} weeks)
Next batch ordered: {{yes_no}}
One change being tested: {{change}}
Plain hyphens only if this is pasted into Kyntlo.
Week 0

Baseline, 11 Oct 2026

The first review has nothing to read yet. This is the starting line the first real week will be compared with.

MeasureNowWhy
Emails sent0Day 0 not run, so email 1 cannot be written
WhatsApp sent0Follows email 1
Bounce rate-Nothing sent
Reply rate-Nothing sent
Audits booked0Audit calendar, 1 Sep to 31 Oct, no bookings
Email campaigns0None in Client Zero
Outreach workflowNoneOne draft, Personalized Outreach Generator, is not an outreach sequence
Outreach domainNoneNot bought; msg.kyntlo.com is in warm-up for marketing
Ready records037 at the Day 0 gate, 2 on hold

First real review: Sunday 25 Oct, if Day 0 runs on 13 Oct and wave 1 email 1 goes on 18 Oct. That week is the phase-zero test: 2 to 3 replies from 15 means scale, 1 means retarget, 0 means change the wedge.

Once a month

Domain health

DMARC. After 30 clean days on a sending domain, move the policy from none to quarantine. Read the aggregate reports first.

Records. SPF, DKIM and DMARC still pass on every sending domain. msg.kyntlo.com is set up; the outreach domain needs the same before warm-up starts.

List hygiene. Suppress contacts with no open in 90 days from marketing sends. Cold records closed at day 21 come back only through the 90-day re-score.

Placement. Send one message from each inbox to a test address on each major mail provider and check it lands in the inbox, not spam.