Customers
Service, sales, onboarding, collections and alerts — across WhatsApp, voice, email and SMS. Every interaction attaches to a 360° customer record with identity, history, documents and open items.
Customer deskflow · The business operating system
The operating system for the whole business.
flow runs the business's processes — customers, suppliers, employees, procurement, HR, finance operations, documents, scheduling, field work — with WhatsApp, voice, email and SMS built in as the front door. AI agents do the work and hand over to a person only when it matters. And whatever the business needs that isn't there yet, it builds inside flow. One system for every technological need of the business.
09:42:07 · identityIdentity verifiedOTP + device match · 1.8 s
09:43:15 · core bankingCard transactions fetchedRead scope · last 5 · masked
09:47:02 · transaction agentTransfer executed$1,200 · within limit · ref 88213
policyAbove limit? Handover.Draft + context go to a banker
MB
Meridian BankOfficial business account
Message
BUILT FOR
Retail & commercial banks
Card issuers & fintech
Insurers
Telecom operators
Utilities
Healthcare providers
Retail & e-commerce
Accounting & law firms
Logistics
Public sector
SMBs, via channel partners
Retail & commercial banks
Card issuers & fintech
Insurers
Telecom operators
Utilities
Healthcare providers
Retail & e-commerce
Accounting & law firms
Logistics
Public sector
SMBs, via channel partners
01 — The platform
Every relationship and every process the business runs. One system of record.
Most companies run their business across a dozen tools: a CRM, a ticketing system, a procurement workflow in email, HR in spreadsheets, documents in a shared drive, and the real conversations on employees' personal phones. flow is one system where the relationships, the processes and the communication live together — and where the work actually gets done.
Suppliers
Purchase orders, quotes, invoices, delivery notes and compliance documents — with a supplier communication center that keeps procurement, finance and the warehouse on the same thread.
Supplier deskEmployees
HR self-service, shifts, approvals, forms and onboarding. Each employee gets a personal, verified link — no app to install, no shadow WhatsApp groups where important messages get lost.
Employee deskProcesses
Not a communication tool with a CRM attached. The place the business runs its processes.
Every process has a record, a workflow, the conversations around it and the agents that move it forward. The communication center is the front door; the processes are the building.
Operations & approvalsTasks, workflows, checklists, SLAs, recurring processes
ProcurementSuppliers, quotes, tenders, POs, invoices, committees
HR & workforceOnboarding, shifts, time off, forms, payslips, policies
Finance operationsBilling, collections, payment links, reconciliation, expense flows
Documents & complianceCollection, classification, e-signature, retention, audit
Scheduling & fieldAppointments, technicians, deliveries, rooms and resources
Sales & serviceLeads, quotes, cases, disputes, renewals, win-back
Anything missingDescribed in plain language, built inside flow — see below
02 — AI, two ways
AI isn't a feature we bolted on. It's how the platform works — and how it grows.
Two things make flow different from a suite of apps with a chatbot in front. First, the same engineering tooling our team uses to build flow is available to every customer — so any technological need the business has can be met inside the platform, not bought as another tool. Second, agents don't just chat — they verify, decide, act and hand over, inside the same system where the processes run.
Way one
Every customer is a developer.
Describe what's missing — a screen, a report, a whole process, an automation, an integration with a system you already run — in plain language. flow builds it inside your tenant, with the same code base, tests and review gates our engineers use, and puts it into service. This is how one platform can cover every technological need of a business: what isn't there yet gets built, not bought.
- No development queue and no change-request backlog with your vendor
- Built with the platform's own components, permissions and audit trail
- Every change is versioned, reviewed and reversible
- Partners can package what they build and ship it to their own customers
You ask flow
Plain language. Any role with build permission. Runs inside your tenant.
flow builds it
- Understand the request and the data it touches
- Generate screen, query and permissions
customers.missing_docs - Wire the WhatsApp reminder action
- Run tests and policy checks
- Review gate · deploy to tenant
Customers missing documents · September new screen
| Customer | Missing | Owner | |
|---|---|---|---|
| Bar Levi Holdings | 2 of 5 | Maya | Remind |
| Gold Dental Clinic | 1 of 4 | Tal | Remind |
| Nir Transport | 3 of 3 | Maya | Remind |
Way two
Agents embedded in the work — not a chatbot in front of it.
flow runs focused agents. Each one has a single job, a defined set of tools, and a policy that says what it may do on its own and what needs a person. Agents read from and write to the same records, systems and audit log as your staff.
- Identity agent — verifies the person on the other end using the components you choose: OTP, document + selfie, voice, device signals
- Service agents — answer from your policies and data, open cases, book, change, cancel, explain
- Transaction agents — execute in core systems within limits: transfers, refunds, claims, orders
- Risk agents — score requests, challenge anomalies, freeze and escalate
- Co-pilot agents — prepare the summary, the draft and the next action for the human who takes over
Explainable
Every answer carries the policy or record it came from. Every action carries who allowed it.
Bounded
Limits per agent, per customer segment and per channel. Above the limit, a person approves.
Reversible
Actions are logged as transactions with compensations where the core system allows it.
Model-agnostic
Claude via our cloud by default; your own model contract or on-premise inference where policy requires.
03 — How a conversation runs
Automated end to end. A person when it matters — and even then, most of the work is already done.
The customer doesn't see a bot and then a queue. They see one conversation that gets resolved. Behind it, flow moves through five stages and decides at each one whether a human needs to be involved.
1
Channel
The message arrives on WhatsApp, a call, an email or a web chat and is matched to a customer, supplier or employee record.
2
Identity
The identity agent picks the verification level the request needs — from none, to OTP, to document and liveness.
3
Resolution
A service or transaction agent answers from policy and executes in your systems, within its limits.
4
Handover
When a rule, a risk score or the customer asks for it, a person takes over — with the full context and a drafted reply.
5
Close & learn
Summary on the record, tasks created, SLA measured. Corrections by staff feed the next version of the policy.
The human side
When a person steps in, they inherit everything.
The banker, the adjuster, the support lead — they open a conversation that has already been verified, summarized and drafted. Their job is judgment: approve, adjust, or say no. Typically that's a read and a click.
- Verified identity and risk score, already on screen
- Summary of the conversation and what the agent already did
- A drafted reply and the proposed action, waiting for approval
- One inbox for WhatsApp, calls, email and SMS — nothing on personal phones
- Response-time and resolution metrics per team member
CONVERSATIONS · 14
DL
Dana LeviCredit limit increase…
yoursOS
Omer SassonClaim #CL-77120 · booked
agentNB
Noa BarRouter replaced · closed
agentRA
Ronit AdlerPO-2231 revision
supplierTK
Tomer KatzTime off · approved
agentAM
Amit MorInstallment rescheduled
agentDana Levi✓ Verified · OTP + deviceWhatsApp
DANAI need to raise my credit limit before Thursday — $12,000
FLOW · AGENTIncreases above $10,000 need a banker's approval. I've opened the case with everything ready — a banker will confirm right here.
FLOW · SUMMARY FOR MICHAELCustomer since 2019 · 24 months, no late payments · income on file $9,400/mo · current limit $5,000 · utilization 31% · risk score 12/100. Request within policy band B (auto-approvable up to $15,000 with banker sign-off).
DRAFT REPLY · WAITING FOR YOUR APPROVAL
Hi Dana, Michael here. I've reviewed the request — approved for $12,000, effective now. Anything else?
Approve & sendEditDecline with reason
Identity
MethodOTP + deviceScore98 / 100Last seenApp · 2 days ago
Done by agent
- Verified identity
- Pulled 24-month history
- Checked policy band
- Opened case #CR-5521
- Awaiting banker approval
Prepared for you
≈ 90% of the work
04 — Where this goes
The only software the business needs. Reached one process at a time.
We're not building another tool for the stack. The aim is that flow runs every process in the business — and that the systems it connects to today are replaced by flow tomorrow, where the business wants that. Partners sell and deliver that roadmap; the build tooling is what makes it realistic.
Today
Unify and replace the edges
- Communication on every channel, off personal phones
- Customers, suppliers and employees as records with processes
- Tasks, documents, approvals, scheduling, collections
- Agents doing the routine; people approving the rest
Connected
Core systems as components
- Core banking, ERP, HRIS, policy admin, OSS/BSS plugged in
- Two-way sync, no double entry
- Agents execute in the core within policy
- Departments build what they need on top
Target
flow runs the business
- Every process, screen and workflow in one system
- Connected tools replaced one by one, where wanted
- Automation end to end, with people where judgment lives
- Fewer systems. One system of record. One audit trail.
05 — Components, not projects
Channels on one side, your systems and specialist components on the other. flow in the middle.
Until flow replaces them, the systems a business already runs plug in as components: core banking, ERP, HRIS, policy administration, OSS/BSS — alongside specialist capabilities like identity verification, fraud prevention, telephony, payments and e-signature. A component has a contract and becomes a tool that agents, workflows and staff can use. A partner's component installed once is available to every tenant that switches it on.
WhatsApp Business Platform
Voice · managed telephony, recording & transcription
SMS & RCS
Email
Web & in-app chat
flowrecords · agents · workflows
Identity verification · OTP, document, liveness, voice
Fraud & risk scoring
Core banking · ERP · CRM
Payments & collections
E-signature · calendars · document storage
Building a verification, risk, telephony or payments product? Package it as a flow component and it becomes a tool every agent can call — across every tenant on the platform.
See the component catalog06 — Who runs on flow
The same platform, from a bank with millions of customers to a clinic with two receptionists.
What changes between them is which processes are switched on, the components connected, the agent policies, and how far flow has replaced the systems around it — not the product.
Banking & fintech
Verified self-service on WhatsApp: card transactions, transfers, disputes, limits, loans — with bankers approving what policy reserves for them.
Strong identity · fraud · auditInsurance
First notice of loss, claim status, policy changes and renewals handled in the conversation. Adjusters step in only when the estimate says so.
Claims · underwriting handoverTelecom & utilities
Outages, remote diagnostics, plan changes, billing questions and technician scheduling at the volume operators deal with.
Diagnostics · field schedulingHealthcare
Appointments, reminders, pre-visit forms, results delivery and referrals — with the consent and privacy controls the sector requires.
Scheduling · consentLarge organizations
Multi-department, multi-brand deployments with SSO, dedicated environments, phased rollout and department-level capability building.
Multi-tenant · dedicatedSMB, through partners
Banks, telcos and software vendors offer flow to their business customers under their own brand — a WhatsApp desk with an agent, ready on day one.
White-label · channel07 — Partners
We grow through partners. That's a design decision, not a sales channel.
flow is the platform; the deployment is yours. Integrators bring the domain and the relationship, component vendors bring specialist capability, and platform partners put flow in front of thousands of businesses under their own brand. What partners sell isn't a channel or a module — it's the system the business will run on, and the roadmap to get there. The product was built to be extended by people who are not us.
Technology partners
Identity, fraud, telephony, payments, e-signature. Package your product as a component; agents call it as a tool.
Solution partners
Integrators and consultancies that design, deploy and extend flow for banks, insurers and enterprises.
Channel & resellers
Distributors and vertical software vendors that sell and support flow in their market, with margin and enablement.
Platform & white-label
Banks, telcos and BSPs that offer flow to their SMB base as their own product, on a multi-tenant deployment.
08 — Built for regulated environments
Designed to pass the review of a bank's security team — then deployed everywhere else.
100%of agent actions logged with actor, policy, inputs and outcome
0customer messages stored on employees' personal phones
3deployment models: shared cloud, private cloud, dedicated on your infrastructure
1audit trail across channels, agents, staff and customer-built capabilities
Identity by level
Each request type declares the verification it needs. Low-risk questions need none; a transfer needs OTP and device; a limit change may need document and liveness. The identity agent enforces it, not the conversation designer.
Human-in-the-loop by policy
Approval thresholds are written per agent, segment and channel. Anything above them lands on a person's desk with the draft ready — and the log shows who approved what.
Data where it must be
Tenant isolation, encryption at rest and in transit, residency options and model inference that can run inside your boundary when regulation asks for it.
Questions partners ask first
Straight answers.
Is flow a chatbot or a messaging platform?
No. flow is the system a business runs its processes on — customers, suppliers, employees, procurement, HR, finance operations, documents, scheduling — with the communication center as the front door and agents working inside it. A chatbot answers; a flow agent verifies the person, executes the transaction, moves the process forward, writes it to the record and hands over with a draft when policy says so. The conversation is the interface, not the product.
Is it a CRM? An ERP? A ticketing system?
It replaces the jobs those tools do, process by process, and connects to the ones it hasn't replaced yet as components. The aim is that a business needs one system, not a stack — and that whatever that system is missing can be built inside it by the business or its partner, rather than bought as another tool.
Which AI models does it run on?
By default, Claude models served from our cloud, with usage billed transparently. Enterprise deployments can bring their own model contract, route by data class, or run inference inside their own boundary. Agents are model-agnostic by design; policies, tools and audit are flow's.
What does "every customer is a developer" actually mean?
Every tenant has access to the same build tooling our engineers use — a natural-language interface on top of the platform's code base, components and tests. A customer or partner describes a capability; flow generates it, runs it through automated tests and a review gate, and deploys it to that tenant. It is real software in the platform, not a no-code layer beside it.
Can we white-label it?
Yes. Platform partners run flow under their own brand on a multi-tenant deployment, with their own component bundle, pricing and support tier. See the partner programs page for the models.
How long does a deployment take?
A WhatsApp desk with service agents on top of an existing CRM: weeks. A bank with identity, fraud and core-banking transactions: a phased program, typically starting with read-only self-service and adding transaction agents as controls are signed off. Partners run most deployments; we support the first ones together.
Where is the company?
flow is developed and operated by Flow Advanced Systems Ltd., Israel. The platform is in production with customers in accounting, professional services and SMB segments, and is being deployed with partners in financial services and enterprise.
Let's design the next deployment together.
Tell us about your market, your customers and the components you bring. We'll show you flow running, and what a partnership looks like in practice.