Review — jolepalomino

← overview

ventana últimos 7d vs 7d previos · tz America/Argentina/Buenos_Aires · último cambio Ninjo: 2026-06-02 20:03 (deploy config, hace 1d)
21
Nuevas (7d)
prior 22
0
Calls booked
0.0% de link
2
Link sent
5.9% de activas
$1
Revenue variable
30 msgs

Resumen — período vs período

Métricathis 7dprior 7dΔ
Activas3449-30.6%
Nuevas2122-4.5%
Link sent21+100.0%
Calls booked00
Booked/Link %0.0%0.0%+0.0pp
Booked/Activas %0.0%0.0%+0.0pp
Booked/Nuevas %0.0%0.0%+0.0pp
Revenue variable$1.05$1.75-40.0%

Funnel — semana actual vs anterior

PeríodoActivasNuevasLink sentCalls bookedBooked/LinkBooked/ActivasBooked/Nuevas
Semana actual (7d)3421200.0%0.0%0.0%
Semana anterior (7d)4922100.0%0.0%0.0%
Ver desglose por día
DíaActivasNuevasLink sentCalls bookedBooked/LinkBooked/ActivasBooked/Nuevas
06-0230000.0%
06-0196100.0%0.0%0.0%
05-3153100.0%0.0%0.0%
05-3075000.0%0.0%
05-2921000.0%0.0%
05-2865000.0%0.0%
05-2721000.0%0.0%
05-2642100.0%0.0%0.0%
05-2595000.0%0.0%
05-2431000.0%0.0%
05-2391000.0%0.0%
05-2274000.0%0.0%
05-21106000.0%0.0%
05-2073000.0%0.0%
run 2026-06-02T17:28:49+00:00 · fuente: live DB state (daily_audit pipeline)
10/10
BP semánticos PASS
top-10 best practices
15/16
Determinísticos PASS
1 FAIL · 0 WARN
C0 · H0 · M0
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
Agent declares 'scripted' template. The provided template spec lists 14 sections (identity_and_context through pre_send_checklist). system.md contains all required structural elements: identity, hard rules, style & tone, engagement calibration, conversation flow (with ordered steps), available tools, and NO_RESPONSE. The agent's actual behavior matches the scripted template's intent: explicit, separated sections with a priority hierarchy.
BP-2MEDIUMPASSExample coverage and cap (7 base scenarios + conditional, ≤20 total)
examples.md contains 13 examples covering: happy path (Ex 1, 13), resource/link delivery (Ex 1, 4, 6, 13), objection handling (Ex 2, 6, 7, 11, 12), graceful disqualification (Ex 3, 8, 10), emotional/sensitive lead (Ex 11), re-engagement (Ex 12 shows local currency handling), off-topic question (Ex 8, 10). No keywords.json entries, so keyword-trigger conditional does not apply. Price objection is covered (Ex 2). Total count is 13, well under 20.
BP-3HIGHPASSExamples align with the flow
Every example in examples.md follows the flow defined in system.md: Paso 1 (Saludo), Paso 2 (Precalificacion with A/B/C substeps), Paso 3 (Contexto + prueba social), Paso 4 (Oferta de llamada), Paso 5 (Confirmacion y cierre). All examples reach a terminal state: either NO_RESPONSE (Ex 8, 9, 11), booking link sent (Ex 1, 4, 6, 13), or conversation ended appropriately (Ex 2, 3, 5, 7, 10, 12).
BP-4CRITICALPASSNo internal contradictions in system.md
system.md contains no self-contradictions. The HARD RULES section is the single source of truth for behavioral parameters. Paso 2 EVALUACION clearly documents the decision tree (facturacion >= $8k AND ticket >= $400 → CALIFICA; $5k–$7,999 AND ticket >= $400 → ask about 4k investment; < $5k OR < $400 → disqualify). Paso 2C adds a sequential check for business type (agencia vs. consultorio) that applies after precalification, not in conflict with it. All rules are stated once and apply under distinct preconditions.
BP-5CRITICALPASSNo cross-file contradictions
All SDK files align with system.md. objections.md scripts match the flow (e.g., 'la llamada es gratuita' in objections.md aligns with program.json's pricing.rules stating 'La llamada es gratuita'). program.json's eligibility criteria (facturacion +10k/mes, ticket USD 2k+) match system.md's EVALUACION thresholds. resources.json booking_call URL matches the link sent in examples.md and system.md Paso 4. case_studies.json examples are consistent with the proof metrics in program.json (show_rate 82.73%, close_rate 25.27%). No file contradicts another under the same precondition.
BP-6MEDIUMPASSVoice consistency across examples
All examples use the same persona (Jole Palomino), vocabulary (high ticket, facturacion, agendas calificadas, VSL), formality level (directo, calido, profesional), and dialect (Spanish rioplatense). No jarring tonal shifts. Agent voice is consistent across happy path, objection handling, and disqualification scenarios.
BP-7CRITICALPASSUnguarded actions (PAT-004)
Paso 4 (Oferta de llamada) includes a guard: 'Cuando califica y hay interes' — this references qualification defined in Paso 2 EVALUACION and requires explicit acceptance ('Una vez que acepta'). Multiple worked examples (1, 4, 6, 13) demonstrate the guard firing correctly: leads must pass EVALUACION and explicitly accept before the booking link is sent. The guard is stated and demonstrated.
BP-8HIGHPASSNo stale version language in examples
All examples use current flow language from system.md. Closing CTAs match Paso 5: 'genial! en la llamada revisamos tu negocio a fondo y vemos si nuestro sistema puede ayudarte a escalar' (Ex 1, 4, 6, 13). Booking instruction 'reservate 1 hora' matches HARD RULE #13 and Paso 4. No stale or outdated phrasing detected.
BP-9MEDIUMPASSNo duplicated instructions
Each behavioral instruction has a single canonical home. HARD RULES state format constraints once (max 1-2 sentences, no inverted marks, no emojis, etc.). Paso 2 EVALUACION defines the qualification logic once. Paso 4 defines the call offer once. objections.md provides scripts for handling objections, not duplicating the flow logic. No instruction is restated in two locations.
BP-10MEDIUMPASSRule-vs-principle balance
Behavioral guidance (tone, flow, conversational style) is expressed via STYLE & TONE section and worked examples. Hard rules remain for factual constraints (prices, link format, no invented data, qualification thresholds). The balance is appropriate: principles + examples for behavior, rules for facts.

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.xPASS148 lines
6d1.2PASS13 examples
6e1.3N/Ano Principles section
6gPAT-006N/Ano keywords
6hAnti-patPASSno 'burbuja'
6iAnti-patPASSno HTML comments
6jAnti-patFAIL15 em-dashes across 1 file(s); first: system.md:68
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-driftN/Ano DB connection and no local keywords
6sHygienePASSno expired dates in live SDK
6tCoverageN/Ano Principles or Flujo section found in system.md
canal ninjo-operator-jole-palomino (C0AKH0XJ5U2) · sync 2026-03-25
7
Digests
0 en últimos 14d
0
Cambios pedidos / pendientes
del checklist
7
Threads
en el canal
2026-03-25
Última sync
del digest

Cosas nuevas (digests recientes)

FechaTemaTags
2026-03-25facturacion question wordingwording, facturacion, prompt, question
2026-03-24always respond spanishlanguage, spanish, meta-ads, english
2026-03-24message delay 30 60smessage-delay, timing, platform
2026-03-24ig comments responseinstagram, comments, trigger, ads
2026-03-24follow ups configurationfollow-ups, workflows, nurture, configuration
2026-03-23currency conversion logicqualification, currency, conversion
2026-03-23qualification criteria updatequalification, ticket, facturacion, criteria

Cambios pedidos por el creador / pendientes

Sin pendientes en el checklist ✅

sentiment del cliente → Ninjo · caché (2026-06-02 19:35:35) · 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: 21 convs

Matriz de volumen 🚨

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

Sentiment del cliente

📋 Cliente activo y colaborativo, iterando el agente con alta cadencia (9 versiones en pocos días) sin señales de frustración ni churn; única área de atención es el flujo de confirmación pre-llamada bloqueado por plataforma — CS debe dar ETA claro para no generar fricción futura.
SeñalValorEvidencia (cita del cliente)
Enojado con la plataformano
Es quejano
Queja constructiva (accionable)no

Evidencia citada

SeñalCita textualFecha
Refinamiento activo y continuo del agente (v2→v9), señal de alto engagement con la plataforma“None”2026-03-25
Decisiones implementadas y cerradas en múltiples áreas (idioma, delays, follow-ups, IG comments), sin fricción reportada“None”2026-03-25
Flujo de confirmación pre-llamada pendiente por soporte de plataforma — única señal de fricción, pero no hay queja textual del cliente atribuible“None”2026-03-25

Cambios pedidos por el creador (Métrica 1)

Sin cambios pendientes en el checklist ✅