Conversational proposal flow on chat-ui + Telegram

Bringing the proven 5-workflow proposal playbook (Sales team uses with Claude) into Agentee chat-ui & Telegram, running inside the existing agent-runtime. Mid-flight state in our Postgres, finalized revisions pushed to Twendee ERP via deals.addProposalDraft.

01 · ARCHITECTURE

Agent ↔ Twendee ERP topology

mermaid · storage boundary · lifecycle sequence

System topology showing channels (chat-ui, Telegram), API (sales-agent, proposal-builder, ConfirmationLedger, renderers), our Postgres state, blob storage, and Twendee ERP. Storage boundary table — what lives where. Sequence diagram across a week.

Open diagram 02 · UI MOCKUP

User flow on chat-ui & Telegram

6 chat-ui frames · 2 telegram mobile frames

Pixel-honest mockups bám design Agentee hiện tại: empty state → W1 requirements → W2 module catalog → W4 cost + finance gate → W6 finalize/downloads → v2 revision. Plus Telegram parity: cross-channel resume + file upload.

Open mockup

Key design decisions

State decoupled from chat session — proposal_drafts sống độc lập; one draft, many sessions, many channels, many owners. chat_sessions.active_proposal_draft_id là pointer.
6 workflows — W1 Requirements · W2 Scope · W3 Technical · W4 Cost · W5 Plan/Team/Training · W6 Finalize. Mỗi workflow có confirm gate.
Per-deal config (rates, currency, T&C, payment terms) — sống trong proposal_revisions.config_json, không phải tenant-level. Varies per deal.
Module catalog per tenant — seeded from real proposal sample (M1..M12). Rep clone vào draft, edit per deal.
Revisions first-class — v1 → v2 → v3, mỗi revision = full snapshot + LLM-generated "What Changed" callout. Match ERP version auto-inc.
Finance approval gate at W4 end qua existing ConfirmationLedger nếu total/discount vượt threshold.
Output: Markdown + DOCX + PDF — DOCX renderer mới (~400 LOC, docx npm pkg), PDF reuse md-to-pdf. EN + VI MVP, RTL/Arabic v2.
Replace legacy proposal-generator skill — kill 11-step CRM-deal-driven orchestrator.

Cohabit UX — chat-ui vẫn chạy task khác giữa proposal

Entry tự động qua natural language — "Tạo proposal cho ACME" → LLM tool-call startNewProposal → header switch sang phase tabs. Không cần slash command.
Exit explicit — /unbind, click "↩ pause & switch topic", hoặc nói "thoát proposal". Tránh auto-unbind sai.
Off-topic giữa proposal OK — rep tạo lead/customer trong khi đang W4 proposal: agent xử lý bình thường, phase tabs vẫn hiện, footnote nhỏ nhắc.
Cross-channel resume — chat-ui Mon → Telegram Tue → fresh chat-ui Wed cùng pd_a4f2. State load từ DB, không từ chat history.