Review — zapatas.us

← overview

ventana últimos 7d vs 7d previos · tz America/Argentina/Buenos_Aires · último cambio Ninjo: 2026-04-28 21:16 (deploy config, hace 36d)
6
Nuevas (7d)
prior 19
0
Calls booked
— de link
0
Link sent
0.0% de activas
$1
Revenue variable
26 msgs

Resumen — período vs período

Métricathis 7dprior 7dΔ
Activas1028-64.3%
Nuevas619-68.4%
Link sent00
Calls booked00
Booked/Link %
Booked/Activas %0.0%0.0%+0.0pp
Booked/Nuevas %0.0%0.0%+0.0pp
Revenue variable$0.91$1.54-40.9%

Funnel — semana actual vs anterior

PeríodoActivasNuevasLink sentCalls bookedBooked/LinkBooked/ActivasBooked/Nuevas
Semana actual (7d)106000.0%0.0%
Semana anterior (7d)2819000.0%0.0%
Ver desglose por día
DíaActivasNuevasLink sentCalls bookedBooked/LinkBooked/ActivasBooked/Nuevas
06-0242000.0%0.0%
06-010000
05-3132000.0%0.0%
05-3022000.0%0.0%
05-290000
05-2810000.0%
05-270000
05-2620000.0%
05-2543000.0%0.0%
05-2410000.0%
05-2311000.0%0.0%
05-2210000.0%
05-2175000.0%0.0%
05-201210000.0%0.0%
run 2026-06-02T17:28:49+00:00 · fuente: live DB state (daily_audit pipeline)
9/10
BP semánticos PASS
top-10 best practices
10/16
Determinísticos PASS
2 FAIL · 4 WARN
C0 · H0 · M1
Fails por severidad
critical / high / medium
Drift
DB vs repo local

BP semánticos (top-10 best practices)

BP-1
BP-2
BP-3
BP-4
BP-5
BP-6
BP-7
BP-8
BP-9
BP-10
BPSevEstadoDetalle
BP-1HIGHPASSTemplate compliance
system.md contains all 7 required sections for principles template: Identity, Voice, Keywords, Flujos, Criterio de calificación, NO_RESPONSE triggers, Principios, Fallback, and Herramientas. examples.md provides 21 worked examples covering the canonical scenarios.
BP-2MEDIUMFAILExample coverage and cap (7 base scenarios + conditional, ≤20 total)
Agent has 21 examples, exceeding the cap of 20. While coverage is strong (happy path, objections, disqualification, emotional/sensitive, re-engagement, off-topic, keyword triggers, price objection all present), the count violates the rule.
evidence (2)
  • {'file': 'examples.md', 'quote': '### Example 1 through ### Example 21 — 21 total examples listed'}
  • {'file': 'templates/principles.md', 'quote': 'Cap at 15 examples. If you need to add example #16, retire the oldest example'}
BP-3HIGHPASSExamples align with the flow
All 21 examples follow the declared flows (GUIA, BZ, DOC, FAKE, generic) in order and reach terminal states (booking confirmed, NO_RESPONSE, or derivation to WhatsApp joyería). No examples end mid-flow.
BP-4CRITICALPASSNo internal contradictions in system.md
system.md is internally consistent. The descarte rule (only when <$200 capital confirmed) is explicitly stated and Example 6 demonstrates it correctly. No conflicting parameter values or flow steps detected.
BP-5CRITICALPASSNo cross-file contradictions
All SDK files align. keywords.json declares keyword conditions (resource_with_flow, contextual); examples.md shows both patterns working correctly (e.g., Example 1 GUIA flow, Example 9 precio contextual handling). resources.json URLs match those cited in system.md and examples.md. program.json pricing rule ('no_price_in_chat') is honored in all examples.
BP-6MEDIUMPASSVoice consistency across examples
All 21 examples use consistent voice: Venezuelan Spanish, direct, warm, short DM-style messages (2–4 lines), tuteo (tú, tienes, vas), no emojis except 👀 in follow-ups, no em-dashes, no regional slang (papi, chamo, coño, dale, brother). Example 14 explicitly documents the anti-pattern to avoid.
BP-7CRITICALPASSUnguarded actions (PAT-004)
All risky actions in system.md and examples have inline guards. Descarte is guarded ('only if <$200 confirmed'). Resource sends are guarded by flow stage and lead response. NO_RESPONSE is guarded by explicit triggers (booking confirmed, emoji puro, off-topic). Examples demonstrate guards firing correctly.
BP-8HIGHPASSNo stale version language in examples
All examples use current flow language and CTAs matching system.md. Closing language ('Buenísimo!!', 3 burbujas + PDF) is consistent across Examples 13, 18. No deprecated phrases detected.
BP-9MEDIUMPASSNo duplicated instructions
Each behavioral instruction has a single canonical home. Descarte rule stated once in 'Criterio de calificación' section; NO_RESPONSE triggers stated once in dedicated section. Example 14 is a worked anti-pattern, not a duplicate rule. No instruction appears in two places.
BP-10MEDIUMPASSRule-vs-principle balance
Behavioral guidance (tone, flow, conversational style) is expressed via Voice section + 21 examples. Hard rules are limited to factual constraints (price range $1,000–$1,300, age 18+, descarte <$200 capital). The 7 Principios are actionable and pass the common sense test.

Checks determinísticos

6a
6c
6d
6e
6g
6h
6i
6j
6k
6l
6m
6n
6q
6r
6s
6t
CheckSecEstadoNotas
6a1.8PASSNO_RESPONSE present (limits not checked, --no-db)
6c3.xPASS101 lines
6d1.2PASS21 examples
6e1.3PASS7 principles
6gPAT-006WARNnon-STEP-0 keyword handling
6hAnti-patWARN2 'burbuja' mentions
6iAnti-patPASSno HTML comments
6jAnti-patFAIL24 em-dashes across 1 file(s); first: knowledge_base.md:1
6kPAT-006FAILtool-call syntax appears as raw text in examples.md (3 line(s))
6lResourcesPASSno placeholder URLs
6mHygienePASSno audit metadata in prompt files
6nPAT-008PASSURL forms consistent across files
6qPAT-001PASSno instruction duplication into examples.md, keywords.json, program.json, resources.json
6rKeyword-driftWARN4 keywords.json entr(ies) not named in system.md (no recent operator ask): ['clase', 'ganar', 'curso', 'flipping'] — likely legacy, review or remove
6sHygienePASSno expired dates in live SDK
6tCoverageWARN4/7 principle(s) without example: #1 Una pregunta a la, #4 Look it up before, #5 Redirigir a la llamada, #7 Examples antes que reglas
canal ninjo-operator-impact-bryan (C0AN4CMUUVD) · sync 2026-06-02
19
Digests
5 en últimos 14d
2
Cambios pedidos / pendientes
del checklist
20
Threads
en el canal
2026-06-02
Última sync
del digest

Cosas nuevas (digests recientes)

FechaTemaTags
2026-06-01weekly report low volume content cta strategyreporting, traffic, content-strategy, conversion
2026-06-01weekly funnel report low volume content reactivationfunnel, reporting, content-strategy, cta, volume
2026-05-25weekly funnel report may18 24 critical declinefunnel-metrics, keyword-performance, conversion-crisis
2026-05-25weekly funnel report zero conversions may18 24analytics, funnel, keyword-performance, critical
2026-05-25monthly performance review 296 convos zero salesanalytics, sales-tracking, marketing-strategy, critical
2026-05-18weekly funnel report may 11 17metrics, funnel-analysis, keyword-performance, action-items
2026-05-11weekly funnel report may 4 10metrics, funnel, keyword-performance, content-strategy
2026-05-11coordination meeting scheduledalignment, meeting
2026-05-07crm app access authentication linktechnical, access, crm, authentication
2026-05-07crm access authentication linkinfrastructure, crm-access, authentication
2026-04-07miguel testing v2 doc flowtesting, feedback, voice, follow-ups, DOC-flow, cleanup
2026-04-07bz academy training docs ingestedtraining-data, product-knowledge, watch-trading
2026-04-07monolithic prompt override deployment failuretechnical-issue, deployment, prompt-architecture
2026-04-07rapport vsl flow redesign bro banagent-behavior, prompt-redesign, vocabulary-guardrails, vsl-flow
2026-03-31rapport feedback lead magnetsrapport, feedback, lead-magnets, tone
2026-03-30calendly relinkcalendly, resources
2026-03-30prompt maestro bz keywordprompt-maestro, keyword-bz, activation, flow
2026-03-29live testing feedbacktesting, feedback, tone, vocabulary, ig-connection, trigger-mode, v5config, bug
2026-03-27agent creation deployonboarding, agent-creation, deploy, links

Cambios pedidos por el creador / pendientes

IDEstadoCambio pedido
E10pendienteFollow-up 1 (2h after silence): "Ey papi, llegaste a ver la info? Quedo pendiente si tienes alguna pregunta" style
I5pendiente~~resources.json whatsapp_joyeria URL pendiente~~
sentiment del cliente → Ninjo · caché (2026-06-02 19:39:29) · modelo claude-sonnet-4-6 · ventana 7d
+0
Sentiment score
neutral_con_señales_de_tension_operativa
Medio
Churn risk
del lado del cliente
2
Cambios pedidos
pendientes en checklist
2
Volumen cliente
agente: 6 convs

Matriz de volumen

re chequear
Cliente callado y agente con poco tráfico: ambiguo (puede ser período tranquilo). Re-chequear próxima ventana.

Sentiment del cliente

📋 El cliente está enganchado operativamente (sesiones de testing, 19-point feedback, restricciones precisas de vocabulario, solicitudes de datos de conversión) pero sin evidencia textual de satisfacción expresada; los KPIs de negocio son críticos (0 ventas en 296 convos en mayo) y hay un backlog largo de bugs/pendientes sin resolver. Riesgo medio de churn si en las próximas 2–3 semanas no se ve conversión real. Acción CS: agendar revisión de resultados con Miguel y Bryan, priorizar cierre del loop keyword→pago con edwar.paez.16/gabriel.specter, y resolver los pendientes técnicos de mayor impacto (guía zero-conversion audit, Calendly reminder) antes de que la frustración latente se vuelva explícita.
SeñalValorEvidencia (cita del cliente)
Enojado con la plataformano
Es queja
Queja constructiva (accionable)

Evidencia citada

SeñalCita textualFecha
El cliente (Miguel) impuso restricciones de vocabulario duras y permanentes al agente, señal de fricción con el output por defecto de la plataforma“None”2026-04-07
Miguel realizó una sesión de testing de 19 puntos y solicitó reescritura completa del agente (v2), indicando insatisfacción profunda con la versión anterior“None”2026-04-07
Bryan participó en sesión de testing en vivo con feedback extenso sobre tono, vocabulario, comportamiento y problemas de conexión IG — señal de alto esfuerzo del cliente para que el agente funcione“None”2026-03-29
Miguel confirma que la nueva versión funciona mejor pero pide más rapport — señal de conformidad parcial pero con expectativas no cubiertas aún“None”2026-03-31
296 conversaciones y cero ventas en mayo: resultado de negocio nulo acumulado, riesgo latente de desencanto si no hay conversión pronto“None”2026-05-25
Múltiples incidentes técnicos acumulados: IG no conectado, modo trigger incorrecto, dos agentes corriendo simultáneamente, desync SDK/monolítico, Calendly roto — patrón de inestabilidad operativa“None”

Cambios pedidos por el creador (Métrica 1)

Un creador que pide cambios concretos está enganchado (mejor señal que el silencio).

IDEstadoCambio pedido
E10pendienteFollow-up 1 (2h after silence): "Ey papi, llegaste a ver la info? Quedo pendiente si tienes alguna pregunta" style
I5pendiente~~resources.json whatsapp_joyeria URL pendiente~~