Review — andrefit_one

← overview

ventana últimos 7d vs 7d previos · tz America/Argentina/Buenos_Aires · último cambio Ninjo: 2026-07-02 19:03 (deploy config, hace 29d) · 393 untracked
139
Nuevas (7d)
prior 114
0
Calls booked
— de link
0
Link sent
0.0% de activas
$0
Revenue variable
393 msgs

Resumen — período vs período

Métricathis 7dprior 7dΔ
Activas289233+24.0%
Nuevas139114+21.9%
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.00$0.00

Funnel — semana actual vs anterior

PeríodoActivasNuevasLink sentCalls bookedBooked/LinkBooked/ActivasBooked/Nuevas
Semana actual (7d)289139000.0%0.0%
Semana anterior (7d)233114000.0%0.0%
Ver desglose por día
DíaActivasNuevasLink sentCalls bookedBooked/LinkBooked/ActivasBooked/Nuevas
07-303515000.0%0.0%
07-294717000.0%0.0%
07-285933000.0%0.0%
07-274324000.0%0.0%
07-262216000.0%0.0%
07-254114000.0%0.0%
07-244220000.0%0.0%
07-235425000.0%0.0%
07-225624000.0%0.0%
07-21189000.0%0.0%
07-203317000.0%0.0%
07-191411000.0%0.0%
07-182311000.0%0.0%
07-173517000.0%0.0%
run 2026-07-24T14:58:26+00:00 · fuente: live DB state (daily_audit pipeline)
9/10
BP semánticos PASS
top-10 best practices
12/16
Determinísticos PASS
1 FAIL · 3 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
All 7 required sections for the principles template are present in system.md: Identity (Identidad y Misión), Voice (Voz), Flow (Flujo de Conversación with 4 stages), Calibration (embedded in Flow via energy-state routing), Principles (5 principles listed), Tools (3 tools with explicit triggers), and NO_RESPONSE (mandatory section present). Content fits template intent.
BP-2MEDIUMPASSExample coverage and cap (7 base scenarios + conditional, ≤20 total)
examples.md contains 18 examples covering all 7 base scenarios (happy path Ex1/5/6, resource/link delivery Ex3/8, objection handling Ex4/7, disqualification Ex9/10, emotional/sensitive Ex7, re-engagement N/A, off-topic N/A) plus conditional keyword-trigger examples (Ex1/14/15 show keyword 'info' + audio path). Total count is 18, within the ≤20 cap.
evidence (2)
  • {'file': 'examples.md', 'quote': '### Ejemplo 1: Path A — Lead viene por keyword INFO, audio ya disparó (welcome sin saludo)'}
  • {'file': 'examples.md', 'quote': '### Ejemplo 9: Menor de edad\n**User:** hola, tengo 15 años y quiero hacer el plan\n**Agent:** Hola amor! Qué lindo que te interesés en cuidarte.\nEl Plan Mentalidad está pensado para adultas mayores de 18 años'}
BP-3HIGHPASSExamples align with the flow
Every example in examples.md follows the 4-stage flow from system.md (Stage 1 Apertura → Stage 2 Welcome → Stage 3 Branching → Stage 4 Post-link/NO_RESPONSE). All examples reach a terminal state (link sent, soft close, NO_RESPONSE, or derivation to Tami/Daiana). No example ends mid-flow.
evidence (1)
  • {'file': 'examples.md', 'quote': '**Agent:** Te paso todo el detalle del Plan Mentalidad\n🔥 Plan online MENTALIDAD 🔥 (mensual)\n...\n¿Te gustaría arrancar?\n**User:** dale, me anoto\n**Agent:** Buenísimo amor 🙌 La transferencia va al alias ladyfit1'}
BP-4CRITICALPASSNo internal contradictions in system.md
system.md contains no self-contradictions. The Flow section explicitly documents exception paths (Path A for audio history, gym presencial derivation, keyword intent) as named carve-outs, not contradictions. All behavioral parameters (welcome content, pricing, NO_RESPONSE triggers) are stated once and consistently applied across all stages.
BP-5CRITICALPASSNo cross-file contradictions
All SDK files agree on behavior and data. keywords.json literal_responses (e.g., 'info' → landing link) are pre-agent auto-replies (different precondition than agent's conversational flow per dismissed false positive BP-5). system.md's Stage 1 Apertura and Stage 2 Welcome are the agent's own dialogue turns. program.json pricing ($50k ARS transfer / $60k tarjeta / $40 USD) matches examples.md and system.md. resources.json URLs match inline links in system.md and examples.md. No file contradicts another under the same precondition.
BP-6MEDIUMPASSVoice consistency across examples
All 18 examples use consistent voice: warm, direct, voseo rioplatense, minimal punctuation (commas/periods, no em-dashes), emoji usage (🔥✨🌿🙌), and message length (short, conversational). No jarring tonal shifts. A reader would believe all examples are the same agent (Tami's voice) talking to different leads.
evidence (2)
  • {'file': 'examples.md', 'quote': 'Hola amor, qué bueno que escribís'}
  • {'file': 'examples.md', 'quote': 'Te entiendo amor, es el clásico rebote de planes que restringen demasiado, no es tu cabeza.'}
BP-7CRITICALPASSUnguarded actions (PAT-004)
All risky actions in system.md's flow are guarded. Stage 2 Welcome is sent after Stage 1 Apertura (universal, not risky). Stage 3 branching is explicitly guarded: 'SÍ' → payment link, 'NO / lo pienso' → soft close, 'pregunta nueva' → derivation. Stage 4 post-link is guarded: 'cualquier respuesta' → NO_RESPONSE. Gym presencial derivation is guarded by keyword detection ('gym', 'gimnasio', 'ballester', 'presencial'). Examples demonstrate all guards firing correctly (Ex1 SÍ → link, Ex2 duda → soft close, Ex9 minor → NO_RESPONSE after one response).
evidence (2)
  • {'file': 'system.md', 'quote': '**SÍ** ("dale", "quiero", "sí", "arranquemos", "me sumo", "cómo pago") → cerrar con el link de pago'}
  • {'file': 'system.md', 'quote': '**NO / "lo pienso" / dudas / "ahora no" / "está caro"** → soft close'}
BP-8HIGHPASSNo stale version language in examples
All examples use current flow language from system.md. Welcome block in examples matches system.md verbatim (🔥 Plan online MENTALIDAD 🔥, ✅ bullets, pricing, ¿Te gustaría arrancar?). Closing CTAs match current system.md (link + alias + Tami WhatsApp). No stale phrases from prior flow versions detected.
evidence (2)
  • {'file': 'system.md', 'quote': '🔥 Plan online MENTALIDAD 🔥 (mensual)\n\nEsto incluye:\n✅ Plan de alimentación personalizado según tu objetivo'}
  • {'file': 'examples.md', 'quote': '🔥 Plan online MENTALIDAD 🔥 (mensual)\n\nEsto incluye:\n✅ Plan de alimentación personalizado según tu objetivo'}
BP-9MEDIUMFAILNo duplicated instructions
Principle 1 ('Welcome en un solo mensaje. Apertura + welcome + pregunta cierre van JUNTOS en el mismo turno. No partes.') is restated in system.md's Stage 2 section ('El welcome se manda en el mismo turno que la apertura (un solo mensaje, no dos). Nunca lo dividas.'). This is a duplicated instruction — the same rule appears in two canonical locations (Principles and Flow). One copy should be removed; the other should cross-reference.
evidence (2)
  • {'file': 'system.md', 'quote': '1. **Welcome en un solo mensaje.** Apertura + welcome + pregunta cierre van JUNTOS en el mismo turno. No partes.'}
  • {'file': 'system.md', 'quote': 'El welcome se manda en el mismo turno que la apertura (un solo mensaje, no dos). Nunca lo dividas.'}
BP-10MEDIUMPASSRule-vs-principle balance
Behavioral guidance (tone, flow, conversational style) is expressed via Voice section (5-6 real message samples) and Principles (5 principles + examples demonstrating them). Hard rules remain for factual constraints (pricing, eligibility age 18+, gym presencial contact). Principles 2, 7, 8, 9 are behavioral and are reinforced by worked examples (Ex6 objective, Ex7 pain reframe, Ex1/14/15 audio path, Ex16/17/18 gym derivation). No behavioral rule is stated without example support.

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.xPASS106 lines
6d1.2PASS18 examples
6e1.3WARN9 principles (target ≤7)
6gPAT-006WARNnon-STEP-0 keyword handling
6hAnti-patPASSno 'burbuja'
6iAnti-patPASSno HTML comments
6jAnti-patFAIL49 em-dashes across 1 file(s); first: system.md:1
6kPAT-006PASSno tool syntax leak
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-driftPASSall 9 keyword(s) consistent across keywords.json + system.md (no DB)
6sHygienePASSno expired dates in live SDK
6tCoverageWARN6/9 principle(s) without example: #2 Nunca preguntes "bajar o masa" como pregunta inicial., #3 No inventés información., #4 No prometás resultados específicos., #6 El plan arranca cuando se abona., #7 Reframe pain antes del welcome.
canal ninjo-operator-andrea · sync 2026-07-21
35
Digests
2 en últimos 14d
0
Cambios pedidos / pendientes
del checklist
36
Threads
en el canal
2026-07-21
Última sync
del digest

Cosas nuevas (digests recientes)

FechaTemaTags
2026-07-20weekly funnel report jul13 19 volume dropmetrics, funnel, keywords, content-strategy
2026-07-20weekly funnel report jul13 jul19 volume declinemetrics, funnel, keyword-analysis, automation
2026-07-13weekly funnel report jul 06 12 keyword performanceanalytics, keyword-performance, content-strategy
2026-07-06weekly funnel report jun29 jul05 volume declinemetrics, reporting, keyword-analysis, content-strategy
2026-07-02gym presencial ballester derivacion daianakeyword, routing, gym-presencial, daiana, deploy
2026-07-02gym presencial ballester routing daianarouting, gym-presencial, product-differentiation, keyword-triggers
2026-06-29weekly funnel report jun 22 28automation, metrics, weekly-report
2026-06-29weekly funnel report jun22 jun28reporting, metrics, funnel
2026-06-22weekly funnel report jun15 21 269 convosreporting, metrics, funnel-analysis, keywords, actionable
2026-06-22weekly funnel report jun15 21 keywords conversionsmetrics, keywords, conversion-optimization, actionable
2026-06-19price thread echo diagnosis
2026-06-16weekly plan enrollments 40 signups jun 08 14enrollment, sales-result, weekly-metric
2026-06-16weekly signups 40 enrollments june 8 14metrics, sales, data-request
2026-06-15weekly funnel report jun 08 14 keyword performancereporting, metrics, keyword-performance, conversion-funnel
2026-06-15weekly funnel report jun 08 14 conversion metricsreporting, funnel-metrics, keyword-analysis, conversion
2026-06-09agent conversation capture fix redeliveryagent-behavior, bug-fix, handoff-workflow
2026-06-08weekly funnel report jun 01 07 510 convosreporting, metrics, keywords, content-strategy
2026-06-05instagram comments audio handling fixinstagram, audio, technical-fix, bot-behavior
2026-06-04payment flow confirmation dual pricing livepayment, pricing, agent-config, confirmed
2026-06-04comment responses not opening dm bug investigationbug, ad-comments, dm-routing, in-progress

Cambios pedidos por el creador / pendientes

Sin pendientes en el checklist ✅

sentiment del cliente → Ninjo · caché (2026-07-28 15:42:39) · modelo claude-sonnet-4-6 · ventana 7d
+1
Sentiment score
conforme
Bajo
Churn risk
del lado del cliente
0
Cambios pedidos
pendientes en checklist
0
Volumen cliente
agente: 139 convs

Matriz de volumen 🚨

alarma real
Cliente callado mientras el agente tiene tráfico: desenganche / churn silencioso. Abrir loop proactivo.

Sentiment del cliente

📋 Sin citas directas del cliente en el digest, pero la evidencia operativa muestra a Tami co-diseñando flujos, pidiendo mejoras de atribución y reportes semanales — perfil de cliente activo y enganchado, sin señales de frustración ni churn. Acción CS: aprovechar el pedido recurrente de atribución (170 derivaciones → 40 ventas) para entregar ese cierre de loop esta semana; reforzaría el valor percibido de Ninjo y convertiría a Tami en promotora.
SeñalValorEvidencia (cita del cliente)
Enojado con la plataformano
Es quejano
Queja constructiva (accionable)no

Evidencia citada

SeñalCita textualFecha
Tami define activamente el flujo de pago y links, señal de apropiación del agente como herramienta propia“None”2026-05-23
Tami provee imagen con flujo nuevo para implementar en el agente, participación activa en la configuración“None”2026-05-26
Tami gestiona el handoff y define routing (Daiana para gym presencial, ella para online), co-diseñando la operación con Ninjo“None”2026-07-02
Pedido recurrente de atribución (lista de compradoras para cruzar con utm_term), señal de que el cliente quiere optimizar y escalar, no abandonar“None”

Cambios pedidos por el creador (Métrica 1)

Sin cambios pendientes en el checklist ✅