| Métrica | this 7d | prior 7d | Δ |
|---|---|---|---|
| Activas | 34 | 49 | -30.6% |
| Nuevas | 21 | 22 | -4.5% |
| Link sent | 2 | 1 | +100.0% |
| Calls booked | 0 | 0 | — |
| 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% |
| Período | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| Semana actual (7d) | 34 | 21 | 2 | 0 | 0.0% | 0.0% | 0.0% |
| Semana anterior (7d) | 49 | 22 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| Día | Activas | Nuevas | Link sent | Calls booked | Booked/Link | Booked/Activas | Booked/Nuevas |
|---|---|---|---|---|---|---|---|
| 06-02 | 3 | 0 | 0 | 0 | — | 0.0% | — |
| 06-01 | 9 | 6 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| 05-31 | 5 | 3 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| 05-30 | 7 | 5 | 0 | 0 | — | 0.0% | 0.0% |
| 05-29 | 2 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 05-28 | 6 | 5 | 0 | 0 | — | 0.0% | 0.0% |
| 05-27 | 2 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 05-26 | 4 | 2 | 1 | 0 | 0.0% | 0.0% | 0.0% |
| 05-25 | 9 | 5 | 0 | 0 | — | 0.0% | 0.0% |
| 05-24 | 3 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 05-23 | 9 | 1 | 0 | 0 | — | 0.0% | 0.0% |
| 05-22 | 7 | 4 | 0 | 0 | — | 0.0% | 0.0% |
| 05-21 | 10 | 6 | 0 | 0 | — | 0.0% | 0.0% |
| 05-20 | 7 | 3 | 0 | 0 | — | 0.0% | 0.0% |
| BP | Sev | Estado | Detalle |
|---|---|---|---|
| BP-1 | HIGH | PASS | Template 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-2 | MEDIUM | PASS | Example 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-3 | HIGH | PASS | Examples 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-4 | CRITICAL | PASS | No 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-5 | CRITICAL | PASS | No 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-6 | MEDIUM | PASS | Voice 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-7 | CRITICAL | PASS | Unguarded 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-8 | HIGH | PASS | No 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-9 | MEDIUM | PASS | No 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-10 | MEDIUM | PASS | Rule-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. |
| Check | Sec | Estado | Notas |
|---|---|---|---|
| 6a | 1.8 | PASS | NO_RESPONSE present (limits not checked, --no-db) |
| 6c | 3.x | PASS | 148 lines |
| 6d | 1.2 | PASS | 13 examples |
| 6e | 1.3 | N/A | no Principles section |
| 6g | PAT-006 | N/A | no keywords |
| 6h | Anti-pat | PASS | no 'burbuja' |
| 6i | Anti-pat | PASS | no HTML comments |
| 6j | Anti-pat | FAIL | 15 em-dashes across 1 file(s); first: system.md:68 |
| 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 | N/A | no DB connection and no local keywords |
| 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-03-25 | facturacion question wording | wording, facturacion, prompt, question |
| 2026-03-24 | always respond spanish | language, spanish, meta-ads, english |
| 2026-03-24 | message delay 30 60s | message-delay, timing, platform |
| 2026-03-24 | ig comments response | instagram, comments, trigger, ads |
| 2026-03-24 | follow ups configuration | follow-ups, workflows, nurture, configuration |
| 2026-03-23 | currency conversion logic | qualification, currency, conversion |
| 2026-03-23 | qualification criteria update | qualification, ticket, facturacion, criteria |
Sin pendientes en el checklist ✅
| Señal | Valor | Evidencia (cita del cliente) |
|---|---|---|
| Enojado con la plataforma | no | — |
| Es queja | no | — |
| Queja constructiva (accionable) | no | — |
| Señal | Cita textual | Fecha |
|---|---|---|
| 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 |
Sin cambios pendientes en el checklist ✅