A house is sold over many calls. After each one, a salesperson at Viya had to retype the summary, the promises and the lead details into ProjectSignal by hand. Now the recording becomes a word-timed transcript and a drafted summary, and each item is filed to the right lead only when the salesperson clicks it. Transcription has been live since 23 October 2026, filing since 27 October.
[01]What changedViya Constructions
Figures from the workflow's own rules.
What the client was told during the sale is what the site is later held to. Each note names its recording, each promise carries a date, and each entry carries the name of the person who filed it.
[02]Why this is hardViya Constructions
While a deal is open, the salesperson tracks land, home loan, design progress, estimate and proposal. Expected closure runs from under one month to three months or more. What was said on an early call must be findable on the last one.
"I will send the plan by Wednesday" is said mid-conversation. Unless it is written down with a date, nobody else can keep it or check that it was kept.
Viya's call recordings mix Malayalam, Hindi and English. So nobody picks a language: it is detected per recording, and English words inside Malayalam or Hindi speech are kept in English letters.
Finishes, brands and dates promised during the sale tend to reach the project manager by phone. They return later as disputes or unplanned cost.
[03]How it worksViya Constructions
The transcript opens in a panel beside the chat, with two tabs: Transcript and Summary.
The salesperson types "/" in Bleno, picks Transcribe and attaches the recordings. Audio or video, several at once.
Each recording is cut into 10-minute pieces, and up to four are transcribed at a time. The language is detected per file. Every word keeps its start and end time.
Opening the Summary tab runs one reading and keeps it. It drafts three to five sentences in English: who the client is, what they want, budget, objections and what was agreed. Then up to 10 dated promises, a stage and up to 14 fields. It is told to leave out any detail that was not said.
Any stage outside ProjectSignal's seven is dropped. So is any field outside the 14, and any promise without a real calendar date.
The salesperson picks the sales book. Mobile numbers in the file name, and any number said on the call, are compared with it. A lead with the same number is suggested or, failing that, leads with the client's name. Each suggestion states its reason, and nothing is chosen until the salesperson picks one. If there is no lead, one can be created after a duplicate check.
Notes, status update, promises, stage and each field have their own buttons. The text can be edited first. The salesperson is asked to check promise dates, because they become reminders.
A note or a lead field can be undone only if it still holds what was written. If someone has changed it since, the workflow says so and leaves it alone.
The reading returns each promise with its due date, the exact words used and the time they were said. On the Transcript tab, clicking a word jumps the recording to that point.
[04]Connected to ProjectSignalViya Constructions
Each write uses the salesperson's own ProjectSignal connection.
Opening the Summary tab writes nothing: it shows back what it read, and every save is the salesperson's own click. The lead book is shared, and ProjectSignal stamps every entry with the person whose sign-in wrote it. So there is one button per write, and the chat assistant is never given these write actions.
Each write goes through ProjectSignal's own sales rules, so an update filed from a call is held to the same date lock, access and audit rules as one typed by hand. A promise from a call becomes the same kind of commitment as a typed one, on the same daily board of promises due. That board has no "mark done" button: a promise is closed only by a later status update that names it.
Filing stops at the lead and its deal. The quotation and agreement workflows that follow start from their own documents. A handover pack for the project manager is planned, not built.
[05]Who decides whatViya Constructions
Nothing is filed automatically.
Every Bleno workflow at Viya follows one pattern: the AI reads, fixed logic calculates, a person confirms. Here there is no money to calculate, so fixed logic matches and limits. One exception: a promise's due date comes from the reading, so the salesperson is asked to check it before saving.
[06]More detailViya Constructions
What a client was promised is on the lead with a date and the name of who filed it, not only in one person's memory.
A promise from a call shows on the same daily board as a typed one. Only a filed status update counts as contact. Opening a lead does not.
Each salesperson connects their own sign-in. The chat assistant cannot write to the sales book.
To start we need a few real recordings, the stages and fields on your lead record, one owner in sales, and thirty minutes a week.
Two planned workflows build on it. One records minutes for every client interaction and compiles them into a requirement timeline: asked, changed, final. The other assembles a handover pack when a deal is won, listing call notes and dated promises as obligations the project manager accepts. Each obligation must point to a document clause or a call date.
[07]Where this fitsViya Constructions
Send us a few real call recordings. We will show you what a first version would read from them and file. Start with one workflow. You only pay if it works.