| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 64 | 117 | -45.3% |
| Nuevas | 0 | 0 | — |
| Link sent | 7 | 1 | +600.0% |
| Calls booked | 0 | 10 | -100.0% |
| Booked/Link % | 0.0% | 1000.0% | -1000.0pp |
| Booked/Activas % | 0.0% | 8.5% | -8.5pp |
| Booked/Nuevas % | — | — | — |
| Revenue variable | $0.00 | $0.00 | — |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 64 | 0 | 7 | 0 | 0.0% | 0.0% | — |
| Semana anterior (7d) | 117 | 0 | 1 | 10 | 1000.0% | 8.5% | — |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 07-30 | 9 | 0 | 1 | 0 | 0.0% | 0.0% | — |
| 07-29 | 7 | 0 | 1 | 0 | 0.0% | 0.0% | — |
| 07-28 | 13 | 0 | 4 | 0 | 0.0% | 0.0% | — |
| 07-27 | 12 | 0 | 0 | 0 | — | 0.0% | — |
| 07-26 | 8 | 0 | 1 | 0 | 0.0% | 0.0% | — |
| 07-25 | 5 | 0 | 0 | 0 | — | 0.0% | — |
| 07-24 | 10 | 0 | 0 | 0 | — | 0.0% | — |
| 07-23 | 7 | 0 | 0 | 0 | — | 0.0% | — |
| 07-22 | 98 | 0 | 1 | 0 | 0.0% | 0.0% | — |
| 07-21 | 5 | 0 | 0 | 0 | — | 0.0% | — |
| 07-20 | 1 | 0 | 0 | 4 | — | 400.0% | — |
| 07-19 | 0 | 0 | 0 | 0 | — | — | — |
| 07-18 | 5 | 0 | 0 | 3 | — | 60.0% | — |
| 07-17 | 1 | 0 | 0 | 3 | — | 300.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 for principles template are present in system.md: Identity, Voice, Flow, Calibration, Principles, Tools, and NO_RESPONSE. Content matches template intent. |
| BP-2 | MEDIUM | FAIL | Example coverage and cap (7 base scenarios + conditional, ≤20 total) Agent has 22 examples, exceeding the 20-example cap. While coverage of base scenarios is strong, the count violates the rule. Examples 15–22 include redundant scenarios (multiple keyword CLASE examples, multiple price-objection examples, multiple ofrecer-llamada variants). evidence (2)
|
| BP-3 | HIGH | PASS | Examples align with the flow All examples follow the documented flow (Discovery → Fit → Contexto → Nutrir → Ofrecer llamada → Cerrar → NO_RESPONSE). Each example reaches a terminal state (link sent, NO_RESPONSE, or confirmed booking). |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md The PROMPT keyword exception is explicitly documented in the Flow section ('Excepcion: Si el lead escribe "prompt"...'), creating a stated carve-out from the general discovery-first rule. This is a single rule with an explicit exception, not a contradiction. No shared precondition produces conflicting outputs. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files are consistent. Keywords.json declares PROMPT as a special case with immediate delivery; system.md documents this exception explicitly. Examples.md demonstrates the CLASE keyword flow (discovery first, then delivery) and the PROMPT exception (immediate delivery without discovery) in separate examples, showing both rules coexist correctly under different preconditions. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples use consistent voice: short messages (max 3 lines), minimal emojis, rioplatense voseo, strategic/consultive tone, no filler greetings or excessive thanks. Tone is uniform across all 22 examples. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions (sending links, closing, NO_RESPONSE) have inline guards. Discovery step guards against premature Elite MED mention ('NO mencionar Elite MED hasta tener contexto'). Nutrir step guards link delivery ('Solo si el lead confirma... Solo avanzar a Ofrecer llamada cuando el lead dice algo afirmativo'). Cerrar step guards booking link ('Preguntar si puede agendar y mandar el link'). NO_RESPONSE triggers are enumerated in Principles section. Examples demonstrate guards firing correctly. |
| BP-8 | HIGH | PASS | No stale version language in examples All examples use current flow language and CTAs matching system.md. Closing language ('me confirmas cuando la agendaste?', 'ahi te van a estar esperando') aligns with current Cerrar step. No outdated phrasing detected. |
| BP-9 | MEDIUM | FAIL | No duplicated instructions The instruction 'No listar pilares, modulos ni detalles del programa en el chat' appears in three places: Flow section (Nutrir step), Principles section (item 1), and Knowledge Base (IMPORTANTE note). This is a single behavioral rule restated in multiple locations, creating maintenance risk. evidence (3)
|
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, discovery-first, no pillar listing) is expressed via principles and examples. Hard rules are reserved for factual constraints (pricing approach, NO_RESPONSE triggers, tool usage). The balance is appropriate for the principles template. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 120 lines |
| 6d | 1.2 | PASS | 22 examples |
| 6e | 1.3 | PASS | 6 principles |
| 6g | PAT-006 | WARN | non-STEP-0 keyword handling |
| 6h | Anti-pat | WARN | 1 'burbuja' mentions |
| 6i | Anti-pat | PASS | no HTML comments |
| 6j | Anti-pat | FAIL | 7 em-dashes across 1 file(s); first: objections.md:1 |
| 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 | WARN | 1 URL(s) appear with different tracking params or formats across SDK files |
| 6q | PAT-001 | PASS | no instruction duplication into examples.md, keywords.json, program.json, resources.json |
| 6r | Keyword-drift | WARN | 3 keywords.json entr(ies) not named in system.md (no recent operator ask): ['REFERENTE', '10X', 'PROTOCOLO'] — likely legacy, review or remove |
| 6s | Hygiene | PASS | no expired dates in live SDK |
| 6t | Coverage | WARN | 3/6 principle(s) without example: #2 No dar precios completos, #4 Si el lead llega, #5 Si no tienes la; 6/9 flow step(s) without example: #2 Fit, #3 Contexto, #5 Cerrar, #1 Saludar y preguntar su, #2 Si confirma ser profesional |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-06-29 | funnel stage analysis jun28 | analytics, funnel, conversion-tracking |
| 2026-06-29 | daily lead reporting pipeline jun28 | automation, lead-tracking, reporting |
| 2026-06-28 | daily lead reporting pipeline jun27 | automation, lead-tracking, reporting, conversion |
| 2026-06-27 | daily lead reporting pipeline jun26 | automation, lead-tracking, reporting |
| 2026-06-26 | daily lead report jun 25 | lead-generation, automation, reporting, data-pipeline |
| 2026-06-26 | daily lead reporting pipeline jun25 | automation, lead-tracking, reporting |
| 2026-06-25 | bot query performance timeout investigation | technical-debug, database, query-optimization |
| 2026-06-25 | cs update renovacion cliente elite med | client-success, renewal, performance, expansion |
| 2026-06-25 | daily lead report jun 24 7 leads | lead-generation, automation, daily-report |
| 2026-06-25 | daily lead report jun 24 | lead-generation, automation, reporting |
| 2026-06-24 | lead qualification batch jun24 | leads, qualification, data-processing, instagram |
| 2026-06-24 | daily lead report jun 23 19 leads | lead-generation, automation, daily-report |
| 2026-06-24 | cs update lolo tato renovation 3mo | cs-update, client-renewal, performance |
| 2026-06-23 | qualifying leads batch jun 22 10 processed | leads, daily-report, urgent-action |
| 2026-06-23 | lead qualification batch jun23 | leads, qualification, data-processing, instagram |
| 2026-06-23 | lead qualification batch 10 qualified leads | leads, qualification, action-items, data-processing |
| 2026-06-22 | daily leads batch jun 21 4 processed | leads, daily-report, follow-up |
| 2026-06-22 | daily lead conversion jun 21 | reporting, conversion, lead-tracking |
| 2026-06-22 | weekly funnel report jun 15 21 | analytics, funnel, leads, followup |
| 2026-06-22 | client renovation performance ongoing | client, renovation, performance, expansion |
Sin pendientes en el checklist ✅
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | sí | — |
| Queja constructiva (accionable) | sí | — |
| Señal | Cita textual | Fecha |
|---|---|---|
| Cliente reporta bug de doble pregunta y confirma que ocurre solo en producción, aportando diagnóstico técnico preciso | “Jaime confirma que el bug solo ocurre en producción, no en el chat de prueba — soporta la hipótesis de v5Config desync” | 2026-04-01 |
| Cliente solicita canal de comunicación alternativo a Slack para producción — señal de dependencia activa, no de abandono | “Cliente pide canal de comunicación alternativo a Slack para cuando esté en producción” | — |
| Cliente pide mejora funcional específica en el primer mensaje del agente | “Jaime pide que el primer mensaje pregunte por especialidad, no solo 'a qué te dedicás?'” | 2026-04-02 |
| Cliente pide feature de follow-up automático con especificación clara | “Jaime pide secuencia de follow-up (5 min sin respuesta)” | 2026-04-02 |
| Cliente reporta regresión de filtro profesional con criterio de corrección claro | “Jaime clarifica key criterion: health professional who wants to practice independently or already does” | 2026-04-12 |
| Cliente pide separación de canal de alertas — gestión activa de la operación | “Jaime asked for NO_RESPONSE alerts in a separate channel” | 2026-04-07 |
| Cliente define y valida reglas operativas del bot de forma precisa (pausa manual, exclusión de alumnos, descarte de residentes) | “Jaime requested: (a) deliver resources before continuing setteo, (b) NO_RESPONSE for alumni/students, (c) discard residents” | 2026-04-08 |
| Cliente reafirma patrón de trabajo colaborativo: exige confirmación explícita antes de cada cambio | “Bot must explain proposed changes and wait for explicit confirmation BEFORE applying any modification (Tato reaffirmed pattern)” | 2026-05-13 |
| Renovación en curso a los 3 meses — cliente no ha expresado intención de salida | “Lolo pidió a Tato coordinar renovación” | 2026-06-18 |
| Cliente mantiene engagement operativo activo hasta la última semana registrada (leads, estrategia de contenido, CRM) | “Sustain 'clase' keyword content strategy—highest conversation volume (123) and funnel activation (14 links, 1 confirmed)” | 2026-06-22 |
Sin cambios pendientes en el checklist ✅