FlareCRM
The call
Who, when, how long, and the recording. Filed before the handset is down.
The phone rings andthe customer isalready on screen.
Calls, WhatsApp, deals and notes for one customer, on one timeline, on a server you control.
The call lands
The handset at rest. Wanjiru Kamau is calling the main line.
A seam of light. Her number matched a contact before the first ring ended.
The record inside it, lit. Company, owner, two open deals, the last three things that happened.
The screen rises out of the handset. The agent answers knowing what the call is about.
The panel is the product. Her record, open, before anybody has said hello.
INSIDE THE PRODUCT FROM HERE
A counter with a phone on it, and forty years of customers nobody wrote down.
Six shops and one number. Whoever answers should know who is calling.
Somebody reconciling at nine at night, from three phones and a notebook.
What lands on the timeline
The message
One WhatsApp thread per customer, whoever on the team answers it.
The note
Two lines typed during the call, still there six weeks later with a name on them.
The deal
A stage, a value in shillings, a reason when it is won or lost.
The task
Call back Tuesday. Assigned, due, and on the timeline when it is done.
The report
Missed calls nobody rang back, as a list rather than a guess.
Per month, in shillings, agreed with you.
A plan is a set of switches and a set of limits. We agree them on a call, and the price follows from what you switch on and how many people use it.
PHONE TEAMS
Calls
KES/ mo
Telephony, screen pops, recordings, contacts, tasks, notes and each person’s own reports.
Talk to us
SALES AND SUPPORT
Calls and WhatsApp
KES/ mo
Everything in Calls, plus the inbox, templates, leads, web forms, deals, team reports and the live board.
Talk to us
LARGER OPERATIONS
Everything
KES/ mo
Plus the softphone in the browser, audit change details, backup downloads and the API.
Talk to us
Your data is on your server.
One company, one installation, one database, one address. Not a row in ours.
Every consequential action is written to a log nobody can edit, including what we do when you ask for help.
Nightly backups, fourteen kept, retention on the schedule you set.
What that means in practice
01
Your own server, your own address
Each company gets its own installation and its own database at yourcompany.flarehub.co.ke, or your own domain. Nobody else’s data is in the same table.
02
An audit log nobody can edit
Every consequential action, including refusals and our own support actions, is written to a log that no administrator can change or delete.
03
Backups and retention you set
Nightly backups, the last fourteen kept. Recordings and records are deleted on the schedule you choose, by a job that runs whether anyone remembers or not.
