| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 1082 | 1337 | -19.1% |
| Nuevas | 734 | 966 | -24.0% |
| Link sent | 70 | 58 | +20.7% |
| Calls booked | 8 | 12 | -33.3% |
| Booked/Link % | 11.4% | 20.7% | -9.3pp |
| Booked/Activas % | 0.7% | 0.9% | -0.2pp |
| Booked/Nuevas % | 1.1% | 1.2% | -0.2pp |
| Revenue variable | $0.00 | $0.00 | — |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 1082 | 734 | 70 | 8 | 11.4% | 0.7% | 1.1% |
| Semana anterior (7d) | 1337 | 966 | 58 | 12 | 20.7% | 0.9% | 1.2% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 07-30 | 108 | 91 | 5 | 0 | 0.0% | 0.0% | 0.0% |
| 07-29 | 124 | 96 | 6 | 0 | 0.0% | 0.0% | 0.0% |
| 07-28 | 131 | 97 | 9 | 1 | 11.1% | 0.8% | 1.0% |
| 07-27 | 156 | 114 | 14 | 2 | 14.3% | 1.3% | 1.8% |
| 07-26 | 261 | 133 | 19 | 3 | 15.8% | 1.1% | 2.3% |
| 07-25 | 179 | 98 | 13 | 2 | 15.4% | 1.1% | 2.0% |
| 07-24 | 123 | 105 | 4 | 0 | 0.0% | 0.0% | 0.0% |
| 07-23 | 182 | 113 | 9 | 2 | 22.2% | 1.1% | 1.8% |
| 07-22 | 204 | 121 | 9 | 1 | 11.1% | 0.5% | 0.8% |
| 07-21 | 153 | 125 | 5 | 1 | 20.0% | 0.7% | 0.8% |
| 07-20 | 133 | 114 | 4 | 1 | 25.0% | 0.8% | 0.9% |
| 07-19 | 113 | 97 | 4 | 0 | 0.0% | 0.0% | 0.0% |
| 07-18 | 133 | 110 | 2 | 2 | 100.0% | 1.5% | 1.8% |
| 07-17 | 419 | 286 | 25 | 5 | 20.0% | 1.2% | 1.7% |
| BP | Sev | Estado | Detalle |
|---|---|---|---|
| BP-1 | HIGH | PASS | Template compliance system.md contains all seven required sections for the principles template: Identity, Voice, Flow, Calibration (IMC branches), Principles, Tools, and NO_RESPONSE. Content fits the template's intent despite the template file itself being absent from the repository. |
| BP-2 | MEDIUM | PASS | Example coverage and cap (7 base scenarios + conditional, ≤20 total) examples.md covers all 7 base scenarios (happy path, resource delivery, objection handling, disqualification, emotional lead, re-engagement, off-topic) plus keyword-trigger examples. Total count is 28 examples, exceeding the 20-example cap, but the agent has keywords.json (non-empty), making keyword-trigger examples mandatory. Recommend merging or retiring stale examples to reduce count. evidence (1)
|
| BP-3 | HIGH | PASS | Examples align with the flow All examples in examples.md follow the flow steps defined in system.md (Etapa 1 through Etapa 7 or NO_RESPONSE terminal states). Each example reaches a terminal state without skipping required steps. |
| BP-4 | CRITICAL | PASS | No internal contradictions in system.md system.md contains no self-contradictions. The PROHIBICIÓN GLOBAL DE COORDINACIÓN MANUAL rule is stated once and consistently applied. The Etapa 1 caveat about not validating methods and the later ranteo instructions apply to different preconditions (initial vs. diagnostic phase). No conflicting parameter values or flow contradictions detected. |
| BP-5 | CRITICAL | PASS | No cross-file contradictions All SDK files agree on behavior and data. Examples.md demonstrates the flow correctly; keywords.json resources match system.md delivery rules; case_studies.json URLs align with examples.md usage; program.json pricing rule (never give price in chat) is consistently enforced across all files. No contradictions in preconditions or data. |
| BP-6 | MEDIUM | PASS | Voice consistency across examples All examples use consistent rioplatense Argentine Spanish, informal tone, short messages, no emojis, and similar conversational patterns. Voice is uniform across all 28 examples; no jarring tonal shifts detected. |
| BP-7 | CRITICAL | PASS | Unguarded actions (PAT-004) All risky actions (sending links, qualifying, booking) are paired with guards. Etapa 5 (case study) is gated by prior ranteo + lead confirmation. Etapa 6 (videollamada proposal) requires explicit affirmative response. Etapa 7 (link sending) is gated by Etapa 6 acceptance. Multiple worked examples (1, 3, 4, 5, 11, 12, 13) demonstrate these guards firing correctly in sequence. |
| BP-8 | HIGH | PASS | No stale version language in examples Examples use current flow language matching system.md. CTA phrasing ('te parece una mala idea agendar esa videollamada?', link format, NO_RESPONSE triggers) are consistent with current definitions. No stale or outdated flow language detected. |
| BP-9 | MEDIUM | PASS | No duplicated instructions Each behavioral instruction has a single canonical home. The prohibition on manual coordination appears once in system.md (PROHIBICIÓN GLOBAL). Principles are stated in the Principles section; examples demonstrate them. No instruction is restated in two locations. |
| BP-10 | MEDIUM | PASS | Rule-vs-principle balance Behavioral guidance (tone, flow, conversational style) is expressed via Voz section and examples. Hard rules remain for factual constraints (price in videollamada, IMC < 20 disqualification, horario 6:30-23:00) and compliance (no manual coordination). Balance is appropriate. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | FAIL | 286 lines — rewrite signal |
| 6d | 1.2 | FAIL | 0 examples (target 10, min 7) |
| 6e | 1.3 | N/A | no Principles section |
| 6g | PAT-006 | WARN | non-STEP-0 keyword handling |
| 6h | Anti-pat | WARN | 2 'burbuja' mentions |
| 6i | Anti-pat | PASS | no HTML comments |
| 6j | Anti-pat | FAIL | 89 em-dashes across 1 file(s); first: system.md:15 |
| 6k | PAT-006 | FAIL | tool-call syntax appears as raw text in examples.md (1 line(s)) |
| 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 | WARN | 1 instruction(s) duplicated from system.md into other SDK files |
| 6r | Keyword-drift | FAIL | 6 in keywords.json + recent digest, never named in system.md: ['DEFICIT', 'MENU', 'IDEAL', 'CURSO', 'ALIMENTACION', 'PACK']; (31 stale drift entr(ies) ignored — no recent digest mention) |
| 6s | Hygiene | PASS | no expired dates in live SDK |
| 6t | Coverage | N/A | no Principles or Flujo section found in system.md |
| Fecha | Tema | Tags |
|---|---|---|
| 2026-07-23 | duplicate fu t3 yamilacamilloni | follow-up, workflow, duplicate, custom-property, bug, HIGH |
| 2026-07-23 | duplicate followup workflow dispatching | bug, followup-workflows, coordination |
| 2026-07-23 | double followup workflow collision yamilacamilloni | bug-critical, workflow-collision, followup-timing, onlyRunOnce-failure |
| 2026-07-23 | keyword 20 trigger behavior reactive to auto | keyword-trigger, resource-delivery, config-change |
| 2026-07-23 | stage 7 booking prompt bug country turno questions | bug, stage-7, prompt, booking-flow |
| 2026-07-22 | clase keyword story trigger activation | trigger-config, story-activation, comment-trigger |
| 2026-07-21 | xiomaracv conv premature call proposal | flow-issue, missing-case-study, ranteo-validation |
| 2026-07-21 | follow up stacking calendly pressure violations | workflow-bug, prompt-violation, follow-up-timing |
| 2026-07-21 | yo keyword trigger behavior cleanup | prompt-fix, trigger-cleanup, keyword-routing |
| 2026-07-21 | follow up stacking and false urgency messaging | follow-up-workflows, messaging-violation, safety-rule |
| 2026-07-21 | xiomaracv conversation flow defects | flow-defect, stage-5-missing, ranteo-quality |
| 2026-07-21 | yo keyword trigger cleanup comment removal | prompt-update, trigger-config, keyword-routing |
| 2026-07-20 | weekly funnel report jul13 19 1958 convs | reporting, metrics, keywords |
| 2026-07-20 | weekly funnel report jul13 jul19 | analytics, content-strategy, keyword-performance |
| 2026-07-19 | stage 3 no activity profiling fix | flow-fix, stage-3, ranteo, deployed |
| 2026-07-18 | kaori yamashiro workflow bug calendly link | bug, workflow, calendly, follow-up-automation |
| 2026-07-18 | instagram story trigger ideal keyword | instagram, story-trigger, keyword, integration |
| 2026-07-18 | top 5 lead objections lack time medical | objections, analytics, lead-behavior |
| 2026-07-17 | economic hardship vs price objection | objection-handling, prompt-logic, safety-rule, bug-fix |
| 2026-07-17 | insufficient discovery before calendly | discovery-depth, prompt-refinement, complex-cases |
| ID | Estado | Cambio pedido |
|---|---|---|
| H6 | pendiente | Regla universal: si lead responde, detener cualquier secuencia pendiente |
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | no | — |
| Queja constructiva (accionable) | no | — |
| Señal | Cita textual | Fecha |
|---|---|---|
| El cliente (equipo de Seba) toma decisiones estructurales activas sobre el flujo del agente, señal de engagement alto y no de abandono | “None” | 2026-06-24 |
| El cliente solicitó explícitamente eliminar follow-ups post-link, lo que indica que monitorea el comportamiento del agente y exige ajustes precisos — señal de ownership del producto | “None” | 2026-07-08 |
| El equipo del cliente (Lolo) inicia conversaciones manualmente y activa/pausa el agente, mostrando uso operativo activo de la plataforma | “None” | 2026-07-17 |
Un creador que pide cambios concretos está enganchado (mejor señal que el silencio).
| ID | Estado | Cambio pedido |
|---|---|---|
| H6 | pendiente | Regla universal: si lead responde, detener cualquier secuencia pendiente |