| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 11 | 10 | +10.0% |
| Nuevas | 0 | 0 | — |
| Link sent | 0 | 0 | — |
| Calls booked | 0 | 0 | — |
| Booked/Link % | — | — | — |
| Booked/Activas % | 0.0% | 0.0% | +0.0pp |
| Booked/Nuevas % | — | — | — |
| Revenue variable | $0.00 | $0.00 | — |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 11 | 0 | 0 | 0 | — | 0.0% | — |
| Semana anterior (7d) | 10 | 0 | 0 | 0 | — | 0.0% | — |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 06-01 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 05-31 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 05-30 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 05-29 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 05-28 | 0 | 0 | 0 | 0 | — | — | — |
| 05-27 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 05-26 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 05-25 | 2 | 0 | 0 | 0 | — | 0.0% | — |
| 05-24 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 05-23 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 05-22 | 0 | 0 | 0 | 0 | — | — | — |
| 05-21 | 0 | 0 | 0 | 0 | — | — | — |
| 05-20 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| 05-19 | 1 | 0 | 0 | 0 | — | 0.0% | — |
| BP | Sev | Estado | Detalle |
|---|---|---|---|
| BP-1 | HIGH | PASS | Template compliance Agent declares 'conversational' template. system.md contains all required Tier 2 sections (Identity, Voice, Flow, Calibration, Principles, Tools) plus supporting files (knowledge_base.md, examples.md, objections.md, keywords.json, resources.json, program.json, personal_story.md, case_studies.json). Structure matches the conversational template's 3-tier design. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base scenarios + conditional, ≤20 total) examples.md contains 14 examples covering: happy path (Ex 1), resource delivery (Ex 1, 3), objection handling (Ex 6), disqualification (Ex 4, 5, 14), emotional/sensitive (Ex 5), re-engagement (Ex 8), off-topic (Ex 10), plus keyword trigger (Ex 3: APPROACH), price objection (Ex 6), and edge cases (Ex 11, 12, 13). Total count is 14, under the 20-example cap. |
| BP-3 | HIGH | PASS | Examples align with the flow All 14 examples follow the stated flow (Open → Discover → Dig → Connect → Resource → Bridge → Close) or explicitly skip steps for hot leads (Ex 2). Each example reaches a terminal state (link sent, NO_RESPONSE, or application submitted). No example ends mid-flow. |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md states 'Always get consent before sending any link or resource' with an explicit exception: 'Exception: hot leads who explicitly ask for the link.' This is a single rule with a documented carve-out, not a contradiction. The Flow section also notes 'If a keyword was sent (APPROACH, etc), adjust the resource to match the keyword topic,' which is consistent with keywords.json's keyword-specific paths. No shared precondition produces conflicting outputs. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions keywords.json declares `send_without_permission: true` for 'talk' and 'places' keywords. system.md's Principle 6 explicitly documents an exception category ('Exception: hot leads who explicitly ask for the link') and Flow notes 'If a keyword was sent (APPROACH, etc), adjust the resource to match the keyword topic.' These are different preconditions: keyword-triggered immediate delivery (keywords.json) vs. standard DM flow (system.md). Example 3 demonstrates the APPROACH keyword path with consent-based delivery, showing both rules coexist. The 'talk' and 'places' keywords operate under a separate, operator-configured exception pathway already acknowledged in system.md. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All 14 examples use the same persona: casual, lowercase, no periods, no emojis, direct tone ('whats up man', 'i hear you man', 'no worries man'). Vocabulary and phrasing are consistent across all scenarios (happy path, objections, disqualifications, edge cases). No jarring tonal shifts. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions (sending links, qualifying, closing) are guarded. Principle 6 states 'Always get consent before sending any link or resource. Exception: hot leads who explicitly ask for the link.' The Calibration section defines 'Hot' as '(I want coaching, how do I sign up, wheres the link)' — a clear guard. Example 2 demonstrates the hot-lead exception firing correctly. The keyword-triggered paths in keywords.json ('talk', 'places' with `send_without_permission: true`) are operator-configured exceptions, already documented in system.md's Flow section. No action is unguarded. |
| BP-8 | HIGH | PASS | No stale version language in examples All examples use current language from system.md: 'whats up man', 'where you from', 'whats your dating life like', 'gameplan call', 'application link', 'NO_RESPONSE'. Closing CTAs match the current flow ('fill it out and let me know', 'ill take a look and follow up with you soon'). No stale or outdated phrasing detected. |
| BP-9 | MEDIUM | PASS | No duplicated instructions Each behavioral instruction has a single canonical home. Principles are stated once in system.md; examples demonstrate them without restating. objections.md provides handling scripts without duplicating flow rules. keywords.json notes reference the flow without copying it. No instruction appears in two places with similar prose. |
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, flow, conversation style) is expressed via Principles (6 principles on consent, pricing, repetition, etc.) and 14 worked examples. Hard rules are reserved for factual constraints ('English only', 'no minors', 'max 30 words per message', 'no periods'). The balance favors principles and examples over prescriptive rules. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 81 lines |
| 6d | 1.2 | PASS | 14 examples |
| 6e | 1.3 | N/A | no Principles section |
| 6g | PAT-006 | WARN | non-STEP-0 keyword handling |
| 6h | Anti-pat | PASS | no 'burbuja' |
| 6i | Anti-pat | PASS | no HTML comments |
| 6j | Anti-pat | FAIL | 48 em-dashes across 1 file(s); first: system.md:30 |
| 6k | PAT-006 | PASS | no tool syntax leak |
| 6l | Resources | PASS | no placeholder URLs |
| 6m | Hygiene | PASS | no audit metadata in prompt files |
| 6n | PAT-008 | PASS | URL forms consistent across files |
| 6q | PAT-001 | PASS | no instruction duplication into examples.md, keywords.json, program.json, resources.json |
| 6r | Keyword-drift | FAIL | 1 in keywords.json + recent digest, never named in system.md: ['action']; (3 stale drift entr(ies) ignored — no recent digest mention) |
| 6s | Hygiene | PASS | no expired dates in live SDK |
| 6t | Coverage | N/A | no Principles or Flujo section found in system.md |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-05-18 | critical zero activity week may 11 17 | funnel-metrics, alert, zero-activity |
| 2026-05-18 | weekly report may 11 17 zero activity | reporting, funnel-metrics, alert |
| 2026-05-18 | weekly funnel report zero activity may 11 17 | automated-report, funnel-metrics, alert |
| 2026-05-11 | weekly funnel report may 04 10 zero activity | reporting, funnel-metrics, alert |
| 2026-05-04 | low activity reactivation sprint proposal | activity, engagement, content-funnel, proposal |
| 2026-04-29 | instagram reconnection required agent setup | agent-setup, instagram, account-access, action-required |
| 2026-04-27 | weekly performance report apr20 26 | performance, metrics, bookings, funnel |
| 2026-04-27 | weekly survey request ninj checkin | survey, feedback, communication |
| 2026-04-22 | quarterly agent improvement call | agent-performance, optimization, feature-planning |
| 2026-04-22 | instagram reconnection request | account-management, platform-integration |
| 2026-04-21 | weekly funnel report apr 13 19 qualification and mid funnel | funnel-analysis, conversion, qualification, action-items |
| 2026-04-21 | no response dane garingan contact issue | no-response, contact-issue |
| 2026-04-16 | no response lead alerts automated | automated-notification, lead-status |
| 2026-04-15 | operator channel command syntax clarification | operator-commands, documentation, ux |
| 2026-04-15 | evan makris chatbot disable confirmation | chatbot-control, contact-management, operational |
| 2026-04-14 | lead magnet inventory and typeform cleanup | lead-magnets, cta-links, typeform, action-item |
| 2026-04-13 | notifications summary | automated, notifications, no-response |
| 2026-04-07 | typeform links unresolved | typeform, links, cta, unresolved |
| 2026-04-05 | story responses off fix deployed | story-replies, platform-config, bug-fix, trigger |
| 2026-04-02 | action cta live confirmed | cta, action-keyword, live, confirmation |
Sin pendientes en el checklist ✅
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | sí | “CRITICAL: AI too obvious, overselling, responses too long” |
| Es queja | sí | “responses too long (3 paragraphs for 1 line)” |
| Queja constructiva (accionable) | sí | “Lloyd wants explicit rejection message / DEACTIVATE keyword in chat to stop agent on specific conversations” |
| Señal | Cita textual | Fecha |
|---|---|---|
| Crítica recurrente y crítica: respuestas muy largas, tono robótico, overselling | “responses too long (3 paragraphs for 1 line)” | 2026-03-21 |
| Escalación crítica por AI demasiado obvia | “CRITICAL: AI too obvious, overselling, responses too long” | 2026-03-19 |
| Señal positiva: Lloyd confirma mejora de calidad tras fix | “responses are shorter / So yes it is better” | 2026-03-26 |
| Queja accionable: agente sigue enviando links Typeform obsoletos | “Typeform links still being sent in some paths” | 2026-04-07 |
| Dolor recurrente: agente messaged Lloyd's personal friends | “Agent messaging Lloyd's personal friends — recurring pain point” | — |
| Queja con solución propuesta: geo-blocking insuficiente, lead de India llegó a booking | “Lloyd wants explicit rejection message” | 2026-03-25 |
| Feature request fuerte: kill-switch por conversación | “DEACTIVATE keyword in chat to stop agent on specific conversations” | 2026-03-28 |
| Problema crítico sin resolución confirmada: cero actividad dos semanas consecutivas | “Zero activity week of May 11–17 requires immediate investigation (agent status, lead flow, configuration)” | 2026-05-18 |
| Queja por story replies irrelevantes, cliente tomó acción directa | “Story responses now disabled (April 6) after Lloyd flagged irrelevant replies” | 2026-04-06 |
Sin cambios pendientes en el checklist ✅