4 Commits

Author	SHA1	Message	Date
Yashas	e90e4204ec	console: redesign the UI — one card language, icons, filters, live trail ... Visual and information-architecture pass across every screen. No API call, payload, poll, permission rule or workflow mirror changes; forms still render from the live schema and the timeline's merge/grouping is unchanged (only the display order is reversible). Design language - Ground + white cards with one hairline and one radius; sentence-case headings; shared primitives in index.css (.card .pill .btn .avatar .live). - One inline icon set (components/Icon.jsx); no more filled navy/red tiles. - Read-side labels in api/display.js: roles and enum tokens humanized, customer initials/tones, money and date formatters. Nothing sent changes. Shell - 56px header with brand, global lead search (portfolio rows, "/" to focus) and identity chip with a human role label. - Sidebar rows carry icons and a clear active bar; AI roster at the foot, each opening its remit card. Login - Operator copy instead of retail copy; centred sign-in card with show/hide password; demo persona picker that fills the EMAIL only. Overview - "Who holds the work" as four quiet cards that warm only when owed. - Pipeline flow bar with every stage named beneath it; KPI strip in a card. - Action rows with chevron / view-only eye; expiry bands filter the table. Queues - Filter bar (search, product, channel, expiry band, stalled, hide closed) and sortable columns, all client-side on the fetched page. - Avatars, product/channel chips, stage chips for closed leads, tinted stalled rows, count inline with the title. Lead - Avatar + chips in the header; metrics card with the stage rail inside, and a branch node for Referred / Parked / Lost / Declined. - Timeline newest-first by default (toggle), the worker's face as the node, one footer row per entry, AI markdown rendered as bold. - "AI team on this lead" panel with per-agent step counts; PDF tags on docs. Forms & dialogs - Required marked with an asterisk + legend; "Select…" placeholder; dd Mon yyyy hint under date inputs; open activity form in a titled panel; one-line dialog footnotes. Fixes: horizontal overflow at 1024px, boxed "in N days" figure, raw tokens (sme_underwriter, verbal_call, Rsa), findings cut at "1.". Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>	2026-09-09 11:37:42 +05:30
Yashas	009153fc0c	console: a type scale, so size can carry meaning again ... The app had FIFTY-FOUR distinct font sizes and forty of them sat between 0.58rem and 0.95rem — a three-pixel band. The most-used size was 0.78rem, so body copy was 12.5px. That is not a hierarchy, it is a fog of small grey text, and it is the main reason the screen read as a decade old: nothing could be emphasised because everything was already the same size. Nine steps now, with real jumps. 12px is the floor and is reserved for uppercase eyebrows — every one of the 53 declarations sitting there that was not an eyebrow has been lifted off it. The surfaces people actually read — the trail's entries, WhatsApp bubbles, field values, table cells — are at body size rather than meta size. The hairline cages are gone with them. The lead metrics and the overview KPIs were seven equal cells in a 1px grid, every value the same size as its label, which left the reader to do the prioritising themselves on every lead. They are separated by whitespace now, values at 22px against 12px labels, with premium and commission larger again: size does the prioritising instead. Panels breathe at 32px rather than 24, radii went 10/14 -> 12/16/20, borders dropped to the softer line, and the stage rail, the queue table and the cards were rebuilt on the same spacing rhythm. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-08 23:36:21 +05:30
Yashas	4b590474e4	console: the call, in the customer's own words ... Recording is now on for Meera (93) and the transcript is kept on the lead (94), so the call stops being a thing only one AI ever saw. The wake that ends a call already carried far more than Engage used — a summary, a sentiment analysis, and the FULL TRANSCRIPT, turn by turn — and all of it was dropped once the three-sentence write-up was done. So a customer said "I think it's 12,000 rupees" and "lower premium", and the file held a paraphrase. That matters here more than it would elsewhere: consent_artefact = verbal_call is written from what the agent HEARD, and it is the artefact justifying every later contact. The evidence for it should be the customer's own words. "Hear the call" now sits on the Log Contact entry and opens the conversation, laid out like the WhatsApp thread — agent right, caller left — because it is the same kind of thing and should not need learning twice. It also files under Contact in the lead record. Turns are split on the speaker labels rather than on newlines: a single turn wraps, and splitting per line shattered one sentence into four bubbles. A transcript that will not parse is shown raw — it is still evidence, and "nothing to display" would be a lie. NOT INCLUDED: the audio. Recording is enabled and the WAV is uploaded, but recording_url is delivered to the agent's post-call WEBHOOK (voice_internal_handler.go:429), not in the wake payload, so nothing puts it on the lead. Wiring that webhook to an external-API activity is a separate change, worth doing when someone asks to listen rather than to read. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-08 17:19:53 +05:30
Yashas	171aa4c2fa	console: a live trail, faces for the agents, and the thread as a thread ... Five of the six asks. The sixth — the whole row as the click target — shipped in 704afe1 and is already live on both grids. THE AUDIT TRAIL WAS FROZEN. Timeline fetched the rows once on mount and never again, so a lead being worked by five agents in three minutes showed the trail as it was when the page opened — on the one screen whose job is watching work happen. The rows move to the lead page, which already polls every 12s, and Timeline becomes presentational. One fetch, one poll, and the conversation view reads the same rows so the two cannot disagree. THE ACCEPTANCE BUTTON OUTLIVED THE ACCEPTANCE. Recording an acceptance twice is not a loop, a recovery or an alternative — it is meaningless, and offering it invites someone to overwrite a customer's WhatsApp acceptance with a worse record of the same event. Gone once acceptance_ref is set, replaced by a line saying who accepted and when. THE AGENTS HAD NO FACE. Five of them carry this workflow and the console named them three different ways — "ai_engage" here, "Engage" there, "Engage AI" elsewhere — so nobody could see that the thing which called the customer and the thing which wrote the quote were one worker. One roster now (api/agents.js): a short name, a colour and two initials each, used wherever an agent is named. People get a disc too, in grey — a trail where the machines are decorated and the humans are plain text reads as though the machines are the important ones, which is backwards on a screen built for oversight. A "Worked by" strip above the trail shows the team at a glance. THE CONVERSATION WAS A LOG, NOT A THREAD. Each turn sat as its own entry among twenty others. Now one button opens it as a thread — theirs left, ours right, oldest first — and the footer says plainly which parts it holds: the quote, the read receipt and the acceptance confirmation are sent by trigger nodes and never written to a field, so they are not there. A thread that quietly omitted them would be worse than one that admits what it is. CONFIRMING A PREMIUM IS A SIGN-OFF, NOT A TASK. It is the only step locked to one role and the only one that touches money — an employee that could mark a premium received could put a customer on risk for a policy nobody paid for. It sat fourth in a list of six queues. It gets its own band now, shown only to the role that owns it, amber only when something is actually waiting: a permanent alert colour on an empty queue teaches people to stop seeing it. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-08 15:29:02 +05:30