# Smart Lead System

Instagram, WhatsApp, Facebook, SMS and calls in one workspace, with call transcripts and a clear view of how managers respond to customers.

- Role: Product architecture, workflow design and operating QA.
- Status: In operation
- Status code: in-operation
- Case page: https://oleksii.almalvs.online/work/smart-lead-system
- Reviewed: 2026-09-06

## Problem

Customer conversations are spread across social platforms, text messages and calls. Managers have to piece together the context, and owners struggle to see how customers are being answered.

## Constraints

- Human review of customer-facing actions
- No invented customer facts
- Clear ownership for the next action

## Architecture

- Instagram, WhatsApp, Facebook, SMS and calls
- Shared workspace and call transcripts
- AI intent and priority
- Manager response and owner oversight
- Next-step handoff

## Decisions

- Prepare suggestions, not autonomous outreach
- Keep facts separate from generated drafts
- Make the next responsible action visible

## Evidence

- Instagram, WhatsApp, Facebook, SMS and calls are brought together in one workspace
  - Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.
  - Sources: None published.
- Call transcription makes spoken conversations available as text
  - Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.
  - Sources: None published.
- The owner can see how managers respond to customers
  - Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.
  - Sources: None published.
- One operational view combines AI intent, priority, facts, summary, next step and reply draft
  - Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.
  - Sources: None published.

## Safety and boundaries

- Reply drafts remain under human review
- No customer or lead records are published
- No unsupervised customer communication

## Stack

- TypeScript
- Workflow automation
- CRM integrations
- Operational QA

## Media

![Smart Lead application showing the inbox, conversation and lead details in its built-in demo mode.](https://oleksii.almalvs.online/images/evidence/smart-lead-runtime.png)

Actual application screenshot, captured September 6, 2026. Built-in fictional demo data; contact fields concealed. Not a production conversation.

## Credits

- None published.

## Public sources

- None published.

## Related projects

- [field-operations](https://oleksii.almalvs.online/work/field-operations)
- [ecogen-controller](https://oleksii.almalvs.online/work/ecogen-controller)

## Business result

Canonical case section: [https://oleksii.almalvs.online/work/smart-lead-system#result](https://oleksii.almalvs.online/work/smart-lead-system#result)

Instagram, WhatsApp, Facebook, SMS and calls come together in one window. Managers can follow customer conversations without switching between separate apps. The owner can see how each manager responds to customers and stay involved without asking the team to relay every conversation.

Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.

Sources:
- None published.

## How it works

Canonical case section: [https://oleksii.almalvs.online/work/smart-lead-system#workflow](https://oleksii.almalvs.online/work/smart-lead-system#workflow)

Call transcription turns conversations into text that the owner can review alongside customer messages and manager replies. The same workspace brings together AI intent and priority, grounded facts, a concise summary, the next step and a reply draft. A person reviews each draft before it is sent to a customer.

Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.

Sources:
- None published.

## Control boundary

Canonical case section: [https://oleksii.almalvs.online/work/smart-lead-system#boundary](https://oleksii.almalvs.online/work/smart-lead-system#boundary)

The system supports decisions instead of impersonating a sales team. It does not invent facts, silently update records or send an unreviewed reply.

Provenance: First-hand account. Published from Oleksii Mazur's first-hand account.

Sources:
- None published.