Reply operations · KoraMD affiliate acquisition

The campaigns can run at 500. Every reply stays human-approved.

Tier 3 is explicitly saved at 500 emails per day. The native Reply Agent is active in Human-In-The-Loop mode, and this cockpit keeps external sending blocked until Kora approves the library, guardrails and account connections.

Campaign healthy Tier 3 saved at 500/day Unibox audited Reply Agent active in HITL Library ready for review External sends gated
The live snapshot could not be loaded. The operating rules and response library remain available below.
Leads live10,062Tier 2 and Tier 3
Sent total1,193200 sent today
Contacted7087.0% of list
Replies70.70% reply rate
Bounce1.01%alarm at 3%
Inboxes25/25500/day shared ceiling
Parallel activation plan

We build while Kora approves.

The full reply operating system moves forward on two lanes at once. This keeps the build moving while Austin and Michael complete the final approvals.

Foundation ready now

Campaign capacity, the native HITL agent, inbox surface, triage logic and operating cockpit are already in place.

✓ Campaigns live ✓ 25 inboxes ✓ Tier 3 at 500/day ✓ Unibox receiving ✓ Native HITL agent active ✓ Replies classified ✓ Business-day monitor live ✓ Cockpit live

What Juan has prepared

Monitoring live
  • Match every Unibox reply to the right response
  • Preserve opt-out, automatic reply and claim guardrails
  • Monitor Slack, Unibox and campaign health five times during the business day
  • Use the existing native Reply Agent in Human-In-The-Loop mode with Autopilot off
  • Disable automatic and out-of-office handling, then load only the approved Mycelium guidance
  • Post each inbound message and draft into Slack after Kora authorizes the connection
  • Add approve and edit controls for Austin and Michael
  • Send through the original Instantly thread only after approval
  • Route interested responders into GoHighLevel and prove the complete flow

What Kora approves in parallel

Ready for Kora
  • Final signoff on the complete response library
  • Confirm Austin and Michael as Slack approvers
  • Email Outreach Hyper Growth is active for the 10,062-lead live base
  • Add Reply Agent credits and confirm the monthly budget
  • Have a Kora admin authorize the Slack connection
  • Connect Kora's HighLevel account and confirm the partner pipeline stage
Delivery window2 to 3 business days after account access and approvals
CalibrationFirst 25 replies validate copy and routing
Permanent gateJuan plus Austin or Michael approve every reply

Activation preflight

Every external message is blocked by default. Client messages and lead replies require exact approval before send.

Hyper Growth: 25,000 contacts · 125,000 emails 0 of 125 pilot credits
PendingComplete response library
PendingSlack approvers
ReadyEmail Outreach capacity
PendingInstantly pilot credits
PendingSlack authorization
PendingGoHighLevel connection
ReadyApproval-bound delivery contract
PendingReply Agent configuration
PendingOriginal-thread proof
PendingGoHighLevel routing proof

Current reply queue

The public cockpit only stores aggregate counts. Names, email addresses and message bodies stay inside Instantly.

Unibox triage

Actionable threads receive a draft. Automatic replies and opt-outs never receive an automated response.

12threads received
4need action
2positive or question
1contact redirect
4opt-outs
4automatic replies

Kora approvals in parallel

Mike's positioning is aligned. The complete library and account access can close while the integration is built.

  1. 1
    Approve the final libraryReview the exact replies below and confirm the complete operating set.
  2. 2
    Outreach capacity is closedHyper Growth is active with room for 25,000 contacts and 125,000 emails. Tier 3 is explicitly saved at 500 per day.
  3. 3
    Fund the Reply AgentRecommended: Growth Credits at $47 per month, with 1,500 credits for up to 300 generated replies.
  4. 4
    Approve guardrails and connectionsConfirm Austin and Michael, disable automatic handling, load approved guidance, then connect Slack and the approved HighLevel stage.

Recommended workflow

Start with a 25-reply calibration batch. Every external reply remains Human-In-The-Loop: Juan approves the exact English and Portuguese copy, then Austin or Michael confirms it for Kora before anything is sent.

01 · ReceiveReply lands in Unibox

Instantly stops the campaign follow-up for that lead.

02 · ClassifyIntent is detected

Positive, question, redirect, negative, opt-out or automatic.

03 · DraftKora-approved language only

Use up to $150 per referred patient and the approved partner proof line. Never reuse the legacy $200 language.

04 · ApproveAustin and Michael copied

Slack shows the inbound reply and the proposed response.

05 · RouteSend and update CRM

Interested leads move toward GoHighLevel for closing.

Response library

English is the client-facing copy. Portuguese is the exact operating translation for Juan. Mike's positioning and Austin's compensation direction are aligned. The complete library is ready for final Kora signoff.

Automation guardrails

These rules protect deliverability, compliance and the relationship with each lead.

Agent may prepare

  • Draft answers to program questions using approved language
  • Prepare a respectful close for negative replies
  • Flag contact redirects for record updates
  • Notify the Mycelium Slack channel with the inbound reply and draft
  • Route approved positive replies toward GoHighLevel

Agent may not do

  • Send a reply without human approval
  • Reply to opt-outs or automatic messages
  • Repeat the legacy $200 and Net 60 language from quoted campaign history
  • Invent compensation, proof, medical or clinical claims beyond the approved library
  • Purchase credits or authorize Slack without Kora approval

Ready to connect

The campaigns have a verified 500-per-day ceiling and the native HITL agent is active. Kora can approve the complete library, guardrails, credits and account connections in parallel. After the first end-to-end proof, the 25-reply calibration batch begins. Dual approval remains mandatory for every external reply.

Monitoring live · activation gated