The same platform, from a bank with millions of customers to a clinic with two receptionists.

Verified self-service on WhatsApp, with bankers approving what policy reserves for them.

Card questions, transfers, disputes, limits, loans and alerts — handled by agents under policy cards written by risk, executed through the core-banking component, and handed to a banker with the draft ready when the amount, the risk score or the regulation says so.

• Identity levels mapped to request types — from OTP to document + liveness
• Transaction agents bounded by amount, payee type, segment and frequency
• Fraud alerts as outbound conversations with block, replace and case in one thread
• Full audit trail: inputs, tool calls, policy version, approver

Banking deep dive →

First notice of loss, claims, policy changes and renewals — in the conversation, with adjusters stepping in only when the estimate says so.

Claims are conversations with documents. flow opens the claim, collects photos and forms, runs the estimate through your component, books the garage or the assessor, and keeps the customer informed — with the adjuster handling the exceptions.

• FNOL in chat with photo intake, classification and extraction
• Estimate and fraud components as agent tools with thresholds
• Policy service: certificates, schedules, beneficiary changes with the right identity level
• Renewals and payments as outbound journeys with consent

Outages, diagnostics, billing and field scheduling at operator volume — with remote fixes before anyone is dispatched.

The service agent reads the network and billing systems, runs remote diagnostics, explains the bill, changes the plan within retention rules, and books the technician from the field-service system. Volume is what flow is built for; the person handles the 10% that need judgment.

• OSS/BSS connectors as agent tools: line status, remote reset, provisioning
• Billing explanations from the actual invoice, not a script
• Plan changes within retention policy; downgrades handed with an offer prepared
• Technician slots from field-service systems; ETA updates outbound

Large-organization deployments →

Appointments, reminders, pre-visit forms, results and referrals — with consent and privacy controls built in.

Clinics and providers run on schedules and forms. flow books and moves appointments, sends pre-visit questionnaires into the visit notes, delivers results with the right identity level, and handles referrals — while clinicians and front desks stay in one inbox.

• Scheduling components: clinic systems, calendars, room and resource booking
• Encrypted form fields; consent recorded per person and purpose
• Results delivery gated by identity level and clinician release
• No-show reduction with reminders and one-tap rescheduling

Order status, returns, replacements and store questions — resolved in the thread, with refunds under policy.

The service agent reads orders and shipments, executes returns and replacements within policy, answers product and store questions from your catalog, and hands over when a refund crosses the threshold or the customer is unhappy.

• Order, shipment and returns connectors as tools
• Refund and replacement limits per segment and order value
• Catalog and store data for questions — with sources
• Outbound: delivery updates, back-in-stock, abandoned checkout with consent

Accounting, legal and advisory firms: document collection, client communication and deadlines — where flow started.

flow runs in production in accounting firms today: document collection with reminders and classification, client communication on WhatsApp and email, task and deadline management, supplier and advisor directories, and integrations with accounting and audit software.

• Required-document tracks per client type, with completeness views
• Agent-driven reminders and intake with OCR and classification
• Telephony with transcription and automatic task creation
• Focused control agents for annual-report checks — one check per agent, explainable

Deliveries, suppliers and the shop floor — three desks, one platform.

Customers reschedule deliveries in chat. Suppliers ask about invoices and revise purchase orders on the supplier desk. Employees swap shifts and file requests on the employee desk. Operations sees all three in one communication center with the ERP behind it.

• Delivery scheduling and ETA updates from your TMS
• Supplier desk: POs, invoices, delivery notes, compliance documents
• Employee desk for shift and field workers without email
• Procurement workflows with tenders and approvals

Resident services on the channel residents already use — with the identity and record-keeping the sector requires.

Municipalities and agencies handle permits, fines, bills, appointments and reports. Agents resolve the routine from the records, with the identity level each service needs, and route the rest to the right department with the case prepared.

• Identity levels per service, from none to government ID verification
• Case management with departments, SLAs and public status
• Multi-language service from one knowledge base
• Accessibility and record-retention rules per jurisdiction