Re-engage
Audience: Support · QA · Engineering · Where in app: Build → Re-engage (/re-engage, settings) and Conversations → Re-engage (/re-engage/inbox, inbox) · Plan availability: wherever Agent K is available (not AppSumo) · Shipped: backend 76b4d9154, 40bb7fccc (2026-11-13); frontend 8975e6ce, 855a7c67
Re-engage is Agent K's lane for people who already know the business: dormant CRM leads (context.source: 'reactivation') and the business's own known website visitors ('knockid' — came back, highly engaged, went quiet). An imported list flagged context.import.known counts too (reEngage.isReEngage). Before Nov 2026 these were Agent K settings; the page reads and writes the same companies.ai_agent_k.re_engage subdoc, so nothing was migrated. CompanyController merges an incoming re_engage (and its writing) over the stored one, so a save from either page keeps the other's fields.
Settings (ai_agent_k.re_engage, lib/reEngage.js)
| Field | Default | Meaning |
|---|---|---|
returning_visitor | true | "A past visitor comes back" |
engaged_visitor + min_engagement | false, 70 (1–100) | "Someone is highly engaged on your site" — a visit's ms-sessions engagement score reaches it |
went_quiet | false | "Someone went quiet" |
revive_crm + dormant_days | false, 90 | "Revive forgotten CRM leads" — CRM reactivation feeder; turning it off also stops in-flight reactivation follow-ups (AgentKSequenceJob) |
max_per_day | 0 (0–500; UI 1–100) | re-engage leads started per company-day (reEngage.sentToday counts non-dismissed/failed nox_actions with a re-engage source); 0 = only Agent K's caps. AgentKPushService returns re_engage_daily_cap past it |
writing { tone, pitch, avoid } | '' | writingInstruction() → drafter instructions ("Tone: … What to offer… Never: …") |
use_history | true | contextFor() adds a brief: first interest, funnel stage + reason, earlier visits and pages, the last chat question, last reply, today's visit — "use it naturally, never say you tracked them" |
send_via | '' | '' same as Agent K · workflow the CRM workflow sends (push only) · crm Agent K sends via GHL Conversations · mailbox from the connected mailbox |
reEngage.senderFor(company, provider) layers send_via over mailboxRouting.senderFor: an impossible choice (mailbox not usable for agent_k, crm on a non-GHL provider) falls back to the CRM workflow (null), never to another sender. AgentKPushService and the sequence / auto-send jobs include companies whose re_engage.send_via is crm or mailbox even when Agent K itself is push-only. Customers are skipped while nox_funnel.customers.mode = 'stop_selling' (lib/customers), and the do-not-contact list applies.
Inbox lane
lib/agentKLeadQuery takes lane = prospect | reengage (40bb7fccc): list, counts and bulk runs split Agent K's new prospects from re-engage leads, and every lead is in exactly one. Frontend views/reengage/ReEngageInbox.vue mounts AgentKInbox lane="reengage" (Conversations → Re-engage, gated ai_agent_k.enabled + pages.agent_k); the Agent K inbox shows prospects only, and lead links route to the right inbox.
Page
views/reengage/ReEngage.vue — tabs Who / Writing / Sending / Next steps, explicit Save (PUT /company/:id { ai_agent_k: { re_engage } }). Menu item Build → Re-engage needs canViewAutomations + agentKAvailable; route meta settings.ai + pages.agent_k. The Sending tab's options depend on the live route (agentKRoute): GHL adds "through LeadConnector", a usable mailbox adds "from /automations?templates=reactivation.
Automation trigger
re_engage_sent { days, outcome } — see Automations. Touches are labelled by touchAttribution.inferForDraft: reactivation → Database Reactivation, knockid → Agent K Outreach.
Related
- Agent K — feeders, push, sequences, mailbox routing.
- Automations · Leads — Overview