| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 0 | 1 | -100.0% |
| Nuevas | 0 | 1 | -100.0% |
| Link sent | 0 | 0 | — |
| Calls booked | 1 | 0 | — |
| Booked/Link % | — | — | — |
| Booked/Activas % | — | 0.0% | — |
| Booked/Nuevas % | — | 0.0% | — |
| Revenue variable | $0.00 | $0.03 | -100.0% |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 0 | 0 | 0 | 1 | — | — | — |
| Semana anterior (7d) | 1 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 06-02 | 0 | 0 | 0 | 1 | — | — | — |
| 06-01 | 0 | 0 | 0 | 0 | — | — | — |
| 05-31 | 0 | 0 | 0 | 0 | — | — | — |
| 05-30 | 0 | 0 | 0 | 0 | — | — | — |
| 05-29 | 0 | 0 | 0 | 0 | — | — | — |
| 05-28 | 0 | 0 | 0 | 0 | — | — | — |
| 05-27 | 0 | 0 | 0 | 0 | — | — | — |
| 05-26 | 1 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 05-25 | 0 | 0 | 0 | 0 | — | — | — |
| 05-24 | 0 | 0 | 0 | 0 | — | — | — |
| 05-23 | 0 | 0 | 0 | 0 | — | — | — |
| 05-22 | 0 | 0 | 0 | 0 | — | — | — |
| 05-21 | 0 | 0 | 0 | 0 | — | — | — |
| 05-20 | 0 | 0 | 0 | 0 | — | — | — |
| BP | Sev | Estado | Detalle |
|---|---|---|---|
| BP-1 | HIGH | PASS | Template compliance meta.md declares template `universal_dm`, which requires 16 sections per the template spec. system.md contains only 8 sections (Identidad, Voz, Flujo, Gate A, Keywords, Calibración, NO_RESPONSE, Principios, Tabla de Calibración). Missing: Knowledge Base integration, Entry Types & Routing, Path Routing, Path-Specific Logic, Non-Fit Fallback, Qualification Scorecard, Show-Up Protection, Follow-Up Logic, What to Never Do, Links Reference Table. evidence (3)
|
| BP-2 | MEDIUM | FAIL | Example coverage and cap (7 base scenarios + conditional, ≤20 total) examples.md contains only 1 example (price inquiry shortcut). Required: ≥6 of 7 base scenarios (happy path, resource/link delivery, objection handling, graceful disqualification, emotional/sensitive lead, re-engagement, off-topic question) plus conditional scenarios (keyword trigger, price objection). Current count is 1/20; missing 5+ base scenarios and both conditionals. evidence (2)
|
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md contains no self-contradictions. Paso 0 (connection, 2-3 questions) and Paso 1 (minorista/mayorista classification) are sequential, not conflicting. Gate A (escalation for grave cases) is an explicit exception to the normal flow, documented in its own section. Hard Invariants section is absent but does not contradict stated rules. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions system.md Paso 0 states 'conversación breve de 2-3 preguntas' (2-3 questions) before moving to sales questions. keywords.json declares 14 keywords with match_type 'any_mention' or 'isolated_word' and condition 'contextual', meaning they fire on first user message. This creates a contradiction: Paso 0 requires 2-3 connection questions before any keyword-triggered response, but keywords.json allows immediate keyword matching on the first message, bypassing Paso 0 entirely. evidence (3)
|
| BP-6 | MEDIUM | N/A | Voice consistency across examples Only one example exists in examples.md, so voice consistency cannot be assessed across multiple examples. Rule requires ≥2 examples to evaluate. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) Paso 5 (Coordinación de entrega) instructs the agent to 'le pasás el alias para transferir' (pass the payment alias) without an explicit guard clause. The action is guarded only implicitly by the prior steps (Paso 4 cierre, Paso 5 confirmation), but no inline condition states when the alias should be sent. The agent could send the alias prematurely if the lead has not confirmed product/price or zone. evidence (2)
|
| BP-8 | HIGH | PASS | No stale version language in examples Ejemplo 1 uses current flow language ('¿El combo o algún producto en particular?', 'El combo sale $75.000', 'te paso el alias y coordinamos la entrega') that matches system.md's Paso 4 and Paso 5 instructions. No stale or outdated phrasing detected. |
| BP-9 | MEDIUM | FAIL | No duplicated instructions The instruction 'al cerrar cada venta, mencionalo brevemente' (mention follow-up at close) appears in both system.md Principios (item 6) and program.json post_sale.agent_must_mention_at_close. This is a duplicated instruction in two canonical locations. The rule should have a single home; the other should be a cross-reference. evidence (2)
|
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, flow, conversational style) is expressed via Voz section and Principios (items 1–10), with examples demonstrating tone. Hard rules (prices, Gate A criteria, envío zones) remain as rules in Knowledge Base and program.json. The balance is appropriate. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 101 lines |
| 6d | 1.2 | FAIL | 1 examples (target 10, min 7) |
| 6e | 1.3 | WARN | 10 principles (target ≤7) |
| 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 | WARN | 3 em-dash(es) in 2 file(s); likely incidental |
| 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 | PASS | all 14 keyword(s) consistent across keywords.json + system.md (no DB) |
| 6s | Hygiene | PASS | no expired dates in live SDK |
| 6t | Coverage | WARN | 10/10 principle(s) without example: #1 Recomendá siempre del catálogo, #2 Escuchá antes de vender, #3 Mencioná el precio con, #4 Cerrá en el chat, #5 Si pregunta algo que |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-06-02 | communication breakdown and strategy gaps | escalation, team-dynamics, communication |
| 2026-06-02 | facebook account reconnection blocked | technical-issue, facebook-integration, blocker |
| 2026-06-01 | weekly metrics pura sanacion low volume | metrics, sales, conversion, low-volume, lead-quality |
| 2026-06-01 | video training materials requested | training, learning, resources |
| 2026-06-01 | weekly report pura sanacion low volume | metrics, conversion, traffic, action-item |
| 2026-05-29 | follow up workflows configuration | follow-up, workflows, configuration |
| 2026-05-29 | price increase required | pricing, prompt-update, action-item |
| 2026-05-28 | pricing query flow redesign deployed | sales-flow, pricing, deployed, conversation-design |
| 2026-05-28 | agent response length reduction | prompt-iteration, ux, deployment |
| 2026-05-28 | feedback routing to ninjo bot | process, communication |
| 2026-05-28 | follow up automation scope clarification | workflow, automation, scope, pending-decision |
| 2026-05-28 | welcome message followup implementation | followup, workflow, scope-clarification |
| 2026-05-28 | agent message length feedback deployed | ux, feedback, deployed |
| 2026-05-28 | pricing flow combo price deployment | pricing, conversational-flow, deployment |
| 2026-05-27 | facebook fanpage recreation reconnection | facebook, infrastructure, blocker |
| 2026-05-26 | whatsapp agent duplication and deployment | deployment, whatsapp, agent-setup, multi-channel |
| 2026-05-26 | dm template lead filtering strategy | lead-filtering, dms, strategy, workflow |
| 2026-05-26 | unified message control across channels | operations, inbox-management, multi-channel |
| 2026-05-26 | dm template and lead filtering strategy | campaign-setup, lead-quality, messaging-template |
| 2026-05-26 | whatsapp agent deployment multi channel | deployment, whatsapp, multi-channel, agent-setup |
Sin pendientes en el checklist ✅
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | sí | “no está funcionando esto / no hay embudo. No hay estrategia! No hay reuniones. No hay comunicación ni fluida ni no fluida! / No contestan. Nadie. Mando mjes a todos y no contestan” |
| Queja constructiva (accionable) | sí | “no hay embudo. No hay estrategia! No hay reuniones. No hay comunicación ni fluida ni no fluida!” |
| Señal | Cita textual | Fecha |
|---|---|---|
| Frustración fuerte: falta de estrategia, reuniones y comunicación interna | “no hay embudo. No hay estrategia! No hay reuniones. No hay comunicación ni fluida ni no fluida!” | 2026-06-02 |
| Sensación de abandono: nadie responde sus mensajes | “No contestan. Nadie. Mando mjes a todos y no contestan” | 2026-06-02 |
| Declaración de que nada funciona | “no está funcionando esto” | 2026-06-02 |
| Engagement activo: Joe solicita materiales de capacitación (señal de compromiso) | “None” | 2026-06-01 |
| Engagement activo: Joe define y valida flujo de precios con Ninjo | “None” | 2026-05-28 |
| Engagement activo: Joe toma decisión de subir precios e inicia el proceso | “None” | 2026-05-29 |
| Joe acepta el circuito de feedback (observa → reporta → itera) | “None” | 2026-05-28 |
Sin cambios pendientes en el checklist ✅