| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 81 | 37 | +118.9% |
| Nuevas | 47 | 19 | +147.4% |
| Link sent | 0 | 0 | — |
| Calls booked | 2 | 1 | +100.0% |
| Booked/Link % | — | — | — |
| Booked/Activas % | 2.5% | 2.7% | -0.2pp |
| Booked/Nuevas % | 4.3% | 5.3% | -1.0pp |
| Revenue variable | $0.00 | $0.00 | — |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 81 | 47 | 0 | 2 | — | 2.5% | 4.3% |
| Semana anterior (7d) | 37 | 19 | 0 | 1 | — | 2.7% | 5.3% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 09-27 | 10 | 6 | 0 | 0 | — | 0.0% | 0.0% |
| 09-26 | 12 | 8 | 0 | 0 | — | 0.0% | 0.0% |
| 09-25 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 09-24 | 10 | 9 | 0 | 0 | — | 0.0% | 0.0% |
| 09-23 | 10 | 4 | 0 | 1 | — | 10.0% | 25.0% |
| 09-22 | 17 | 10 | 0 | 1 | — | 5.9% | 10.0% |
| 09-21 | 19 | 10 | 0 | 0 | — | 0.0% | 0.0% |
| 09-20 | 0 | 0 | 0 | 1 | — | — | — |
| 09-19 | 7 | 4 | 0 | 0 | — | 0.0% | 0.0% |
| 09-18 | 9 | 4 | 0 | 0 | — | 0.0% | 0.0% |
| 09-17 | 7 | 5 | 0 | 0 | — | 0.0% | 0.0% |
| 09-16 | 4 | 3 | 0 | 0 | — | 0.0% | 0.0% |
| 09-15 | 6 | 2 | 0 | 0 | — | 0.0% | 0.0% |
| 09-14 | 4 | 1 | 0 | 0 | — | 0.0% | 0.0% |
⏳ Sin re-auditar hoy (sin cambios de prompt) — mostrando la última auditoría disponible. Estado vigente hasta nueva corrida.
| BP | Sev | Estado | Detalle |
|---|---|---|---|
| BP-1 | HIGH | PASS | Template compliance All 7 required sections present in system.md: Identity, Voice, Flow, Calibration, Principles, Tools, NO_RESPONSE. Content matches principles template specification. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base scenarios + conditional, ≤20 total) 15 examples provided. All 7 base scenarios covered: happy path (Ex 1), resource delivery (Ex 4, 6), objection handling (Ex 5), disqualification (Ex 7), emotional lead (Ex 13), re-engagement (Ex 8), off-topic (Ex 10). Both conditionals met: keyword trigger (Ex 4, 6) and price objection (Ex 5). Count is within cap. |
| BP-3 | HIGH | PASS | Examples align with the flow Every example follows the 6-step flow (Calificar → Dolor → Contexto → Posicionar → Cerrar → Post-booking) in order. All examples reach terminal states (link sent, NO_RESPONSE, or booking confirmed). |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md System.md is internally consistent. The 25-word limit on Voice is stated once and applies uniformly. Flow steps are ordered and non-contradictory. The post-booking rule ('Solo si la respuesta es genuinamente ambigua... preguntá UNA vez') is an explicit exception to the NO_RESPONSE rule, not a contradiction. Example 1 demonstrates this carve-out correctly. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files align. Keywords.json declares send_without_permission flags that govern delivery timing; system.md's Flow step 1 ('Si el lead pregunta por un keyword... entregá el recurso primero') is consistent with keyword conditions. Examples.md demonstrates both rules coexisting (Ex 4, 6 show keyword delivery then qualification). Program.json pricing rules match system.md's Principles (no Elite/Group prices in chat; AI Brain and Hiring Course allowed). No factual contradictions on revenue bands, URLs, or program details. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples use consistent voice: sharp, direct, no BS, rioplatense voseo, max 25 words per message (except intro), no emojis, no em dashes. Tone is uniform across scenarios (happy path, objections, disqualification, emotional). A reader would recognize the same agent throughout. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions are guarded. Sending links is guarded by revenue band (Step 4 posicioning) and explicit lead acceptance ('dale', 'sí', 'me interesa'). NO_RESPONSE is guarded by 7 explicit conditions in Principles §7. Keyword delivery is guarded by send_without_permission flags in keywords.json. Example 1 demonstrates the guard on post-booking ambiguity ('pudiste agendar?'). No unguarded actions exist. |
| BP-8 | HIGH | PASS | No stale version language in examples All examples use current flow language and CTAs. Closing language ('va + URL + cuando reserves avisame', 'bárbaro, te llega ahí el material', 'NO_RESPONSE') matches system.md's Flow and Principles. No outdated phrasing detected. |
| BP-9 | MEDIUM | PASS | No duplicated instructions Each behavioral instruction has a single canonical home. Revenue routing lives in knowledge_base.md (not repeated in system.md). NO_RESPONSE triggers are stated once in Principles §7. Post-booking sequence is in knowledge_base.md. Keywords.json notes cross-reference the flow ('resume normal qualification flow') rather than duplicating. No instruction appears in two places. |
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, flow, conversational style) is expressed via Voice examples and Principles. Hard rules are reserved for facts (revenue bands, pricing, URLs, eligibility). The 25-word limit is stated as a rule but is taught by Voice examples. Examples demonstrate all key behaviors (objection handling, disqualification, emotional leads) rather than prescribing them as rules. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 113 lines |
| 6d | 1.2 | PASS | 20 examples |
| 6e | 1.3 | FAIL | 14 principles, cognitive overload |
| 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 | 2 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 | FAIL | 5 in keywords.json + recent digest, never named in system.md: ['ceo', 'ops', 'fire', 'foco', 'testing']; (1 stale drift entr(ies) ignored — no recent digest mention) |
| 6s | Hygiene | PASS | no expired dates in live SDK |
| 6t | Coverage | WARN | 10/14 principle(s) without example: #2 No des el precio, #3 Si alguien parece menor, #6 No des coaching, estrategia, #7 Respondé con la palabra, #8 Si el mensaje solo; 4/6 flow step(s) without example: #2 Dolor, #3 Contexto, #4 Posicionar, #6 Post-booking |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-09-28 | weekly funnel report sep 21 28 42 percent link conversion | metrics, funnel, conversion, leads, keywords |
| 2026-09-23 | gender detection error system prompt review | agent-behavior, system-prompt, bug-fix |
| 2026-09-23 | external message pause config investigation | agent-configuration, external-messages, troubleshooting |
| 2026-09-23 | agent activation bug external pause | bug, agent-behavior, critical |
| 2026-09-22 | reports distribution setup | operations, reporting, agent-monitoring |
| 2026-09-21 | weekly funnel report sep 14 20 emprendedor keyword | metrics, keywords, conversion, content-strategy |
| 2026-09-21 | weekly funnel metrics sep 14 20 zero conversions | metrics, funnel, keywords, performance, conversion-optimization |
| 2026-09-18 | dual permission instagram messaging verified | instagram, messaging, manychat, ninjo, permissions, verified |
| 2026-09-17 | instagram manychat ninjo routing conflict resolution | instagram, manychat, ninjo, integration, bug-fix |
| 2026-09-16 | manychat instagram messaging conflict fix | bug, integration, instagram, manychat, ninjo, urgent |
| 2026-09-14 | funnel analysis sep 07 13 volume spike keyword wins | analytics, funnel, keywords, conversion, agendas |
| 2026-09-10 | say hi to new followers feature request | feature-request, ninjo, manychat, automation |
| 2026-09-07 | funnel analysis sep 01 07 keyword performance | analytics, funnel, keywords, conversion, leads |
| 2026-08-31 | weekly funnel report aug 25 31 | reporting, funnel-metrics, lead-qualification, performance |
| 2026-08-31 | weekly funnel report aug 25 31 volume growth | funnel-metrics, lead-quality, agent-performance, icp-validation |
| 2026-08-24 | weekly funnel report aug 18 24 | funnel, metrics, weekly-report, leads, conversion |
| 2026-08-17 | weekly funnel report aug 11 17 low volume | weekly-report, funnel-metrics, content-strategy, lead-follow-up |
| 2026-08-17 | weekly report low volume keyword signal | weekly-report, funnel-analytics, content-strategy, keyword-emprendedor |
| 2026-08-14 | instagram account restriction resolved | instagram, account-restriction, agent-pause, resolved |
| 2026-08-14 | mcp working notes claude project setup | mcp, claude-project, agent-setup, documentation |
| ID | Estado | Cambio pedido |
|---|---|---|
| M2 | pendiente | Clarity Call (team) |
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | sí | — |
| Queja constructiva (accionable) | sí | — |
| Señal | Cita textual | Fecha |
|---|---|---|
| bug reportado: agente se activa pese a estar deshabilitado (múltiples veces en la semana) | “None” | 2026-09-23 |
| bug reportado: error de detección de género en respuestas del agente | “None” | 2026-09-23 |
| engagement operativo activo: Benji monitorea y actualiza el agente diariamente, solicitó ser incluido en reportes | “None” | 2026-09-22 |
| historial extenso de iteraciones y mejoras al prompt (tono, reglas, ejemplos reales) — indica inversión sostenida en la plataforma | “None” | — |
| adopción de métricas y funnel tracking — cliente usa activamente los reportes para decisiones de contenido y conversión | “None” | 2026-09-28 |
Un creador que pide cambios concretos está enganchado (mejor señal que el silencio).
| ID | Estado | Cambio pedido |
|---|---|---|
| M2 | pendiente | Clarity Call (team) |