Financi OPS
Financi OPS: insurance agency operations on the same database as the CRM
Financi OPS is the operations module (Ops) of Financi: managing work with operators, with processes, tasks and statistics. It sits on the same database as the CRM, so handing work from the agent to the back office is a data read, not an integration.
Last updated:
What it does
Work management with operators: processes, tasks and statistics, wired straight into the CRM.
Processes
An operator sees the processes the agent handed over, works on them and returns them. The visual demo shows process types such as a clearing-house order, a policy copy and a Har HaBituach query.
Tasks
Tasks with an owner and a due date on the card, and a clear next action for each process.
Load and statistics
You see how many processes are open and how the load is spread across operators.
The same database
No syncing, no duplicates, no “who updated whom”. The operator works directly on the process, not on a copy sent along.
A signature opens work
When the customer signs, a signed event reaches the CRM and the ops card, and the next task opens.
Role-based permissions
You define what an agent, an operator or a manager sees, so everyone sees what their role allows.
Rafi, the process assistant
Rafi reads notes and client data and proposes values for fields in a process. You approve each value, with undo.
In plain words: what an operator does in Ops
An operator is an operations person who works with the agency. This is what shared work between an agent and an operator looks like.
Agent in the CRM
Opens a process and hands it to operations
One database
Operator in Ops
Sees it instantly, works on it and returns it
- 1
The agent opens a process and hands it to operations
No files passed around and no WhatsApp message and hope: the process itself moves.
- 2
The operator sees it instantly
It is in the same database, so there is no sync to wait for.
- 3
The operator works on it
Tasks, calls and WhatsApp messages, all on the same card, with a clear next action.
- 4
It returns, and management sees
The process goes back to the agent, and whoever manages sees load and statistics by operator.
How it fits the rest of the suite
Ops is not a separate system: it is the half of the work that happens with operators, on the same client card and the same database as the CRM. A signing event from forms and e-signing opens work in operations, conversations from the shared inbox are recorded on the same card, and clearing-house and Har HaBituach requests are process types that move through it.
Overview of the whole system (all six modules on one client card). Support centre and FAQ
The other modules
- CRM & processesLeads, customers, policies, processes and tasks, with commissions, calendar and role-based permissions.
- WhatsAppA shared inbox for the team: campaigns, chat assignment, document requests and analytics.
- Forms & e-signingThe customer fills in and signs with a finger from a phone, no login, and a signed, sealed PDF comes back.
- Clearing house & Har HaBituachOrder and pull the customer's pension and insurance data, unified in one card.
A related free tool
- Sales pipeline health check for your agencyA free check of an agency's sales pipeline: enter how many leads reached each stage to see the sharpest drop and whether open leads are being left waiting.
- Agency admin hours-saved calculatorA free calculator that shows how many admin hours a year an insurance or pension agency could free up, from your clients, tasks and automation assumption.
Keep reading
- Automating the Admin: Where the Hours Go and What to Start Withwhere the administrative hours go and what to start with
- When an Insurance and Pension Agency Outgrows Spreadsheets and WhatsAppwhen handing work over by message stops being enough
- An AI Team for Your Agency: Delegate Without Abdicatinghow Rafi proposes and a person approves
Who it is for, and when it makes sense
- Agencies with a back office or operators, where handing work over today happens by message, file or call.
- Managers who want to see load by operator and which processes are open, without collecting it by hand.
- Teams where an agent and an operator need to work on the same process, on the same card, with no copy sent along.
What it does not do, and limits
- Ops is not a separate system with a copy of the data: it works on the same database as the CRM.
- It does not replace the agent's work with the customer. The CRM is the agent's work, and Ops is the management of work with operators.
- Values that Rafi proposes for fields are not written without a person's approval.
Frequently asked questions
What is the difference between the CRM and Ops?
The CRM is the agent's work: leads, customers, policies, processes and tasks. Ops is work management with operators: processes, tasks and statistics. Both sit on the same database, so handing work to a back office is a data read, not an integration.
Who is an operator?
Operators are the operations people who work with the agency. In Financi they work in Ops on the processes the agent hands over, in the same database.
Do we need an integration between the CRM and operations?
No. CRM and Ops are on the same database, so when an agency hands work to a back office it is a data read. No syncing, no duplicates, no “who updated whom”.
Who sees what in Ops?
Permissions are role-based: everyone on the team sees what the role you gave them allows. When you hand a process to an operations team, the operator works on it directly in the same database, not on a copy sent along.
What happens when a customer signs a form?
A signed event reaches the CRM and the ops card, and the next task opens.
How do we start?
Book a demo, walk through the system with your team, and match the plan to the agency's size.
Want to see it on your agency?
Book a demo, or write to us directly. We go through the system with your team, not a generic tour.
Financi is a CRM for insurance and pension agencies, by Shavve.
