Skip to main content

Branch Bot Response — Customer/Contact Field — Status 2026-07-27

Delivery / Program Management — periodic status report.

This is a retroactive first report, not a live reporting cycle. The initiative was built and GA'd in 2026-Q2 without ever being recorded in this repo; it was reconstructed on 2026-07-27 from the Confluence PRD and Epic BOT-3864. It exists to give the README's progress_pct provenance. There is no prior report to trend against.

Summary​

Health: completed. 11 of 11 Stories Done (100%). The PRD targeted GA 2026-04-01; the actual production rollout behind the enable_branch_customer_field flag was requested and confirmed on 2026-07-09. The five Stories that had been sitting To Do under the already-closed Epic (BOT-4044, BOT-4045, BOT-4047, BOT-4048, BOT-4052) were closed on 2026-07-27 on the DRI's confirmation that the work had already deployed, so the Epic and its Stories now agree. One defect remains open — BOT-4308.

Highlights​

  • GA'd to all Qontak One customers 2026-04-01 (UI configuration following after), delivering the Customer Field branch condition type: schema-driven field selector, type-aware operators, and real-time CDP evaluation with BSUID identification.
  • Six Stories Done: BOT-3928 (field discovery), BOT-4043 (single text input UX), BOT-4046 (max 3 conditions), BOT-4049 (single-line text evaluation), BOT-4050 (multi-line text evaluation), BOT-4051 (dropdown evaluation).
  • Backend CUSTOMER_FIELD support landed on both the create and update branch paths (BOT-3930, BOT-3931, BOT-3932) with the runtime evaluation engine (BOT-3934).
  • QA execution ran across five board tasks (BOT-4118, BOT-4132, BOT-4182, BOT-4282, BOT-4365).

Lowlights & blockers​

  • Five Stories still To Do under a Done Epic — resolved 2026-07-27. BOT-4044, BOT-4045, BOT-4047, BOT-4048, BOT-4052 were transitioned to Done on the DRI's confirmation that the work had already deployed. Recorded here because the closure was retroactive bookkeeping, not fresh delivery — none of these Stories has an individual code-evidence trail in this repo.
  • An open production defect remains — BOT-4308 (intermittent 500 saving a branch with a second condition, To Do, assigned to Agus Suparman). It was a child of no Epic — the finding that triggered this whole record — and was parented to BOT-3864 on 2026-07-27. Note it now sits, unfixed, under a Done Epic.
  • No effort was ever captured, so there is no man-day burnup, no forecast, and no way to state progress in the repo's canonical unit.
  • No E2E specs exist in tests/, so none of the PRD's composite ACs are traceable to automation (PRD OQ-6).

Risk & dependency changes​

  • The feature depends 100% on real-time Mekari CDP availability with no caching layer, under a 2–3s timeout. That is a standing runtime risk carried from the PRD's constraints, not a new one — the PRD flags proactive caching as a future consideration if latency proves problematic post-launch.
  • No decision records were written during delivery; delivery/decisions/ is empty for this initiative.

Metrics​

  • Progress: 11 / 11 Jira Stories done (100%). Man-days: TBD — never sized, so the percentage is story-count-based, the same convention the roadmap uses for unsized buckets. Caveat: five of those eleven were closed retroactively on 2026-07-27 as bookkeeping, so 100% reflects board state on a DRI attestation, not eleven independently evidenced completions.
  • Evidence — partial, and this is a known gap. The Jira half is confirmed (the Story keys above, read from the board on 2026-07-27). The merged-code half was not collected: this initiative's ~35 delivery Tasks predate its record here, and no commit/PR refs from chatbot / chatbot-fe were gathered. Per the two-source progress rule this reading is therefore Jira-only and should be treated as unverified against code. One incidental data point: BOT-4303's description cites the branch fix/BOT-0000-customer-field-value-validation — a BOT-0000 placeholder, which would not join to a Jira key in any code-evidence check.
  • Throughput this period: not applicable — no prior report.
  • Forecast: none. GA is in the past (2026-04-01) and the remaining tail is unsized.

Next period​

Board wiring and the Story tail were settled on 2026-07-27 (see retroactive record). What remains:

  • Fix BOT-4308 — the only open work. Decide whether it is tracked here (currently parented to the Done Epic BOT-3864) or moved to a bucket story under Chatbot 26Q3 Engineering Initiatives (BOT-4620) — still an open decision.
  • Answer the PRD's OQ-1 … OQ-5; OQ-2 (numeric fields specified but absent from the field catalogue) is the one that changes buildable scope.
  • Consider a QA intake check so branch-response Bugs get an Epic at file time (BOT-4274 was the second unparented one; both are now parented).