How it all connects

One CRM workflow from first enquiry to won deal

DigiPix Flow runs your whole CRM workflow on one set of records, not five tools sharing a login. Capture, conversations, the pipeline, handover and reports all read and write the same records, so every team picks up exactly where the last one left off — and nobody types the same customer in twice.

  • Capture feeds the pipeline
  • Every message lands on the record
  • Won deals hand over cleanly
An example customer record at the centre of DigiPix Flow, connected to capture, leads, the inbox, follow-ups, deals, proposals, clients and reports. The enquiry is captured and assigned, a WhatsApp reply lands on the record and it is converted to a deal, the customer accepts the proposal and the rep marks the deal won, and the handover is accepted and a client is created.
The journey

Follow one enquiry from lead to deal, and beyond

Five stages, one set of records. At each step you can see what arrives, what your team and the CRM do with it, and what moves on to the next stage.

01/Capture

Every enquiry becomes one lead

Whichever channel a buyer uses, the enquiry goes through the same steps: it becomes a lead, possible duplicates are flagged for review, the lead is scored, and your assignment rules give it an owner. The rep hears about it in the app and on their phone, with a first task ready if you've switched that on.

See the lead inbox
CaptureStage 1 of 5
ARRIVES
Meta Lead Ads
Google Ads lead forms
IndiaMART enquiries
Website forms and the Lead API
CSV imports
WHAT HAPPENS
One lead record per enquiry
Possible duplicates flagged for review
Scored against your rules
Assigned by round robin, weight or workload
MOVES ON
Owner notified on web and phone
First task for the owner
02/Work

Every conversation lands on the record

Each email thread gets its own reply address, so answers find their way back to the right lead or contact, and WhatsApp and SMS messages match by phone number. Follow-ups and sequences keep the next touch on the calendar. When the buyer is ready, one conversion creates or links the contact, the company and the deal.

See follow-ups
WorkStage 2 of 5
ARRIVES
An assigned lead with an owner
Its source and consent
WHAT HAPPENS
Email replies matched to the record
WhatsApp and SMS matched by phone
Follow-ups with reminders
Sequences that can stop on a reply
MOVES ON
A contact and company, created or linked
A deal carrying the owner and source
The lead stays linked to all three
03/Close

Deals close by the rules you agreed

The deal moves across the board with the stage rules your team set, and big wins or deep discounts wait for approval. Send a proposal with a link the customer can accept or decline — their signature and the version are recorded, and the rep is notified to close the deal. Once it's closed, its open follow-ups and reminders are cancelled.

See the pipeline
CloseStage 3 of 5
ARRIVES
A deal with its owner and source
The contact and company behind it
WHAT HAPPENS
Stage rules checked on every move
Approvals for discounts and large wins
Proposal accept link for the customer
MOVES ON
Rep notified when the customer accepts
Deal marked won, with the reason
Open follow-ups on the deal cancelled
04/Hand over

Won deals hand over without losing context

A rep converts the won deal into a client. The handover is prepared and submitted by one person and accepted by another, who can send it back with requested changes. The client keeps its link to the deal, so the delivery team starts from what sales already knows.

Explore clients & handover
Hand overStage 4 of 5
ARRIVES
A won deal
Its contact, company and proposal
WHAT HAPPENS
Deal converted to a client by the rep
Handover prepared and submitted
Accepted by a separate reviewer
MOVES ON
A client record linked to the deal
Handover accepted, ready for workflows
05/Measure

The same records become the report

Reports don't need an export and a clean-up first. Leads by source and pipeline by stage are calculated from the records your team has been working all along, and each person sees the totals their role allows. Save the reports you use, put them on a schedule, or export a CSV.

See reports
MeasureStage 5 of 5
ARRIVES
Leads with their sources
Deals with their stages and values
WHAT HAPPENS
Leads by source
Pipeline by stage
Scoped to each person's role
MOVES ON
Saved and scheduled reports
CSV exports for finance
Automation

The rules that tie it together

Workflows listen for the moments that matter across the CRM — a new lead, a lead turning hot, a deal changing stage, a deal won or lost, a new client, an accepted handover — and act on them: assign an owner, create a task, send an email or SMS, notify the team, tag the record or wait before the next step.

Triggers7
Lead created
Lead became hotIn use
Deal stage changed
Deal won or lost
Client created
Handover accepted
Added to a segment
Hot lead hand-off
Workflow · 1 trigger, 3 actions
Active
When
A lead becomes hot
Trigger
Then · step 1
Assign it to a senior rep
Senior reps · round robin
Then · step 2
Create a call task for today
Call · due today
Then · step 3
Notify the team lead
Team lead · in app and push
Actions8
Assign an owner
Create a task
Send an email
Send an SMS
Notify the team
Add a tag
Log an activity
Wait, then branch
An example DigiPix Flow deal record for an office revamp at Rao Interiors, linked to the lead, contact and company it came from, with a timeline showing an email reply, a WhatsApp message, a completed follow-up, a stage change and the conversion from lead.
The record

Everything about a customer, on their record

Open a lead, contact, company, deal or client and its timeline shows what happened: messages sent and received, follow-ups, tasks, stage changes and conversions, in order. Linked records sit at the top, one click apart.

Linked, not copied

The lead stays linked to the contact, company and deal it became.

One search box

Find leads, contacts, companies and deals from anywhere in the app.

Same rules everywhere

Role scopes apply to lists, the inbox, search and reports alike.

Everywhere

Wherever your team works

The mobile app

Leads, deals, proposals, clients, follow-ups, the inbox and reports — the same records in your pocket.

Notifications

Assignments, overdue work, approvals, proposal views and customer replies, in the app and as push.

Global search

Leads, contacts, companies and deals in one search.

Roles & audit

Data scopes by role, and an audit log of who changed what.

Audit & compliance

Outbound webhooks

Signed lead, contact, company and deal events sent to your systems, with retries.

Webhooks

Lead API

Create leads from any system you already run.

Lead API
FAQ

How the pieces fit, answered

Something we haven't covered? Talk to an expert

What is a CRM workflow?

A CRM workflow is the path an enquiry takes from the moment it arrives to a won deal and a handed-over client. In DigiPix Flow that path runs through five stages — capture, work, close, hand over and measure — and every stage reads and writes the same records, so nothing is retyped between teams.

What happens to a lead when it's converted?

Conversion creates or links a contact and a company, and can create a deal at the same time. The owner, the lead source and the consent record carry across, and the lead stays linked to all three, so you can always see where a customer came from.

Does an accepted proposal close the deal?

No — a person stays in charge of that. When the customer accepts a proposal through its link, the acceptance and signature are recorded, a note is added to the deal and the rep is notified. The rep then marks the deal won, with any approvals your rules require.

How do emails and messages find the right record?

Every email thread sent from DigiPix Flow has its own reply address, so a reply returns to the conversation it belongs to. Other incoming email is matched to a lead or contact by the sender's address, and WhatsApp and SMS messages are matched by phone number.

Does a won deal become a client on its own?

A rep converts the won deal into a client, which starts the handover. One person prepares and submits the handover and another accepts it or asks for changes, so what sales promised is checked before delivery begins.

What can workflows react to?

Workflows can start when a lead is created or updated, when a lead becomes hot, when a deal changes stage or is won, lost or reopened, when a client is created, when a handover is accepted and when a record joins a segment. They can assign, create tasks, send email or SMS, notify people, tag records, log activity, update scores, wait and branch.

What happens to open follow-ups when a deal closes?

Closing a deal as won or lost cancels its pending follow-ups, tasks and queued reminders. They stay on the record for history, so nobody keeps getting nudged about a finished conversation.

Can other systems hear about changes in DigiPix Flow?

Yes. Outbound webhooks send signed events when leads, contacts and companies are created or updated, and when deals are created, change stage, or are won or lost — with retries if your endpoint is down. The Lead API lets other systems create leads.

Do permissions follow people across the CRM?

Yes. A person's data scope applies to lists, records, the inbox, tasks, search and reports, so a rep who can only see their own leads sees only those everywhere. Changes are recorded in the audit log.

See one lead travel the whole way

Talk to an expert — bring a real enquiry from last week and watch it move from capture to handover in one workspace.

  • A real person, not a bot
  • Bring a real lead from last week
  • See every step in one workspace
Talk to an expert