zurich_kotak/src
Yashas eea044b9f9 config: the two scheduled activities
The workflow now schedules work for itself. Two activities exist that
nobody navigates to — the scheduler performs them — and both are offered
here as well, because a person needs to be able to do by hand what the
timer does on its own.

Retry Call, in Awaiting Contact. Booked automatically four hours after an
unanswered call, clamped into 09:00-21:00 IST, three attempts and then
the lead closes. It records the attempt; whether it also DIALS is gated
on the lead's `auto_retry` field, which ships unset, so nothing rings a
phone until somebody arms it deliberately.

Send Document Reminder, in Document Pending. Fires at 24h, 72h and 120h
from Engage's request. On the third unanswered one the lead leaves the
queue — Parked if the renewal is still weeks off, Lost if the cover is
about to lapse. That is the bound: a chase with no ceiling fills a book
with leads nobody will ever work, all of them looking active.

Both are labelled "Scheduled — or you" rather than given an AI or a role,
because neither is true. The performer on the timeline will read System.
2026-09-07 14:12:42 +05:30
..
api config: the two scheduled activities 2026-09-07 14:12:42 +05:30
assets Wire the console to the platform and make it deployable 2026-08-24 15:20:13 +05:30
components Updated to new frontend specifications 2026-09-04 13:26:20 +05:30
layout Updated to new frontend specifications 2026-09-04 13:26:20 +05:30
pages Wire the console to the platform and make it deployable 2026-08-24 15:20:13 +05:30
screens Updated to new frontend specifications 2026-09-04 13:26:20 +05:30
App.jsx Make the console operable: add a lead, work a lead 2026-08-24 16:11:28 +05:30
index.css UI Enhancements in recordsview and detailsview 2026-09-02 15:33:26 +05:30
main.jsx Wire the console to the platform and make it deployable 2026-08-24 15:20:13 +05:30
runtimeConfig.js UI Enhancements in recordsview and detailsview 2026-09-02 15:33:26 +05:30