TGH Tech
Case study · Workflow 01 of 20 · Win the work · Live

A sales call goes in as a recording. Its notes, promises and stage land on the lead, one click at a time.

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.

Client
Viya Constructions
Department
Sales
Starts from
A call recording, audio or video
Gives you
A transcript, a summary and entries on the lead
Connected to
The lead and its deal in ProjectSignal
Status
Live. Both parts live since late October 2026.

[01]What changedViya Constructions

The call itself is the record. Not a retyped line about it.

Before

Listen, remember, retype.

  • Summary, promises and lead details retyped into ProjectSignal after each call
  • A promise tracked only if the salesperson typed it into the remark
  • Recordings in Malayalam, Hindi and English that nobody could search or read
Now

Read it back, click what is right.

  • A summary drafted in English, whatever language the call was in
  • Each promise read with its date, the exact words and the minute it was said
  • A transcript that plays back word by word and can be asked about later
  • 14
    lead and deal fields one call can fill
  • 7
    lead stages it may suggest, and no others
  • 10
    dated promises read from one call, at most
  • 0
    items written to the lead without a click

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

A house is sold over weeks of calls. The promises made on them outlast the sale.

  1. 01

    A deal stays open for weeks or months

    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.

  2. 02

    Promises are made in passing

    "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.

  3. 03

    Calls change language mid-sentence

    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.

  4. 04

    What sales promised, the site must deliver

    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

From recording to lead in seven steps. The last three belong to the salesperson.

The transcript opens in a panel beside the chat, with two tabs: Transcript and Summary.

  1. 01Salesperson starts

    Attach the recordings

    The salesperson types "/" in Bleno, picks Transcribe and attaches the recordings. Audio or video, several at once.

  2. 02The workflow

    Transcribe

    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.

  3. 03The workflow

    Read the call once

    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.

  4. 04Fixed logic

    Keep only what fits

    Any stage outside ProjectSignal's seven is dropped. So is any field outside the 14, and any promise without a real calendar date.

  5. 05Salesperson confirms

    Match the lead

    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.

  6. 06Salesperson confirms

    File, one button at a time

    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.

  7. 07Salesperson decides

    Undo, if nothing has moved

    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.

Every promise comes with the words behind it.

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.

  • "By Friday" becomes the coming Friday. "Month end" becomes the last day of the month.
  • The instruction is to suggest no stage unless the call clearly moves the lead.
  • Words selected in the transcript can be saved to the lead too.
Summary · Site A inquiry call
LeadSite A inquiry. Same phone as the recording.Use this lead
SummaryOwns the plot. Wants two stories, three bedrooms. Home loan in process.Add to Notes
Promise · 12:40Send revised floor plan. Due Fri 13 Nov. "I will send it by Friday."Add promise
Promise · 18:05Client to share loan sanction letter. Due Mon 30 Nov. "By month end."Add promise
StageHot. Reason: asked when the agreement could be signed.Mark as Hot
Land statusOwnedSet field
Illustrative. A made-up call recorded on Tuesday 10 November 2026, laid out to show what the reading returns. Each label on the right is a separate button.

[04]Connected to ProjectSignalViya Constructions

It files to the lead as the salesperson. Same sign-in, same sales rules, their name on the entry.

  1. Reads

    From ProjectSignal

    • Leads in the sales book the salesperson picks
    • Phone, alternate phone, name and stage
    • Current notes and field values, before any change
  2. Does

    What happens in between

    • Transcribes the recording
    • Drafts summary, promises, stage and fields
    • Suggests the lead by phone, then by name
    • Waits for a click on each item
  3. Writes

    To ProjectSignal

    • A dated entry under the lead's notes
    • A status update
    • Promises, as dated commitments
    • The stage, and lead and deal fields
    • A new lead, if none exists

Each write uses the salesperson's own ProjectSignal connection.

ButtonWhat lands on the leadThe rule
Add to NotesThe date, "Call recording", the file name and the text, under the notes already thereRefused if the notes would pass 4,000 characters.
Post as status updateOne entry in the lead's historyProjectSignal sets the date, and the salesperson cannot backdate it. Only a status update counts as contact.
Add promisesOne history entry. Each promise becomes a commitment with a due date, marked as read by AI.Reminded on the due day and the working day before. If missed, carried forward, never dropped.
Mark as stageThe lead's stage, one of sevenA lead marked Hot becomes a pipeline deal without a second entry.
Set fieldOne of six lead fields or eight deal fieldsA deal field on a lead with no deal first moves the lead into the pipeline.

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.

  1. Lead assigned
  2. Sales call filed
  3. Estimate check and quotation
  4. Agreements
  5. Quotation summary

Where the connection ends today.

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

The AI reads. Fixed logic matches and limits. The salesperson files.

StepDone by
Speech into text, with a time on every wordA speech model. It only transcribes.
Summary, promises, suggested stage, field valuesThe AI, in one reading, from what was said
Turning "by Friday" into a dateThe AI reading, counting from today. The salesperson is asked to check each date.
Dropping stages, fields and undated promises that do not fitFixed logic
Phone matching, duplicate check, note limit, undo checkFixed logic
Which lead, and every saveThe salesperson
Dating entries, reminders, carrying missed promises forwardProjectSignal's own sales rules

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

The rules it follows

Every rule, written down.

RuleWhat it does
Seven stagesCold, Warm, Hot, Qualified, Engaged, Potential, Lost. Anything else is dropped.
14 fieldsOn the lead: budget range, location, project type, service, email, alternate phone. On the deal: house type, house size, land status, loan status, design phase, decision maker, expected closure, client mood.
A promise needs a dateSomething the salesperson or the client committed to do by a date. The call is taken as today's, Indian time, unless the file name says otherwise.
Phone matchingOnly 10-digit Indian mobile numbers starting 6 to 9, with +91 or a leading 0 removed. The lead book is searched on the last five digits, and a lead is suggested only if its phone or alternate phone matches all ten.
No second leadA lead created from a call is first checked for the same name and number, marked "Call recording" and assigned to the salesperson.
UndoOnly notes and lead fields, and only while ProjectSignal still holds what was written. History is added to, never edited.
LengthOne reading covers up to 24,000 characters of transcript. The summary is at most 3,000, a promise 300, a field value 500.
No speechThe Summary tab says so and drafts nothing.
TranscriptionA recording that already has a transcript is skipped on a second run. A network or server failure is retried, up to three attempts. A file with no audio track says so.
What goes in, what comes out

Recordings in. A transcript, a summary and entries on the lead out.

ItemFormat
In: recordingsAudio or video, several at once. Malayalam, Hindi, English or a mix.
Out: on the leadNotes entry, status update, dated commitments, stage, lead and deal fields, each under the salesperson's name
Out: transcriptRead-along panel with a time on every word. Copy, or download as a text file.
Out: PDFOne PDF with a section per recording, or one each, word for word
Out: video descriptionTwo to four sentences and three to eight timed scenes, for videos such as site walk-throughs
Out: in BlenoFiled passages highlighted on the transcript
What it means for you

Three readers, three answers.

  1. For owners

    Promises stay with the company

    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.

  2. For sales heads

    One set of rules for calls and typed updates

    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.

  3. For your technical person

    Writes go through the platform

    Each salesperson connects their own sign-in. The chat assistant cannot write to the sales book.

Is this your problem too?

  • Calls are recorded, or could be, and never opened again
  • Follow-ups are one line, with no date against what was promised
  • The project manager hears what was promised by phone

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.

Where it goes next

Call filing is live. Meetings and handover are planned, not built.

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.

What did your sales team promise on the phone last week?

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.