Why most chat ROI math gets laughed out of the room
The usual pitch multiplies every chat by an invented conversion lift and calls it revenue. A CFO dismantles that in one question: "would those customers have bought anyway?" A framework survives scrutiny when it states its costs fully, claims its benefits conservatively, and names its own caveats before the CFO does.
The cost side (count everything)
Cost per resolved conversation = (agent time on chat x loaded hourly cost + software cost) / conversations resolved. Two honest inclusions people skip: the time agents spend BETWEEN chats staying available, and the software line. The second is where flat-priced tooling quietly changes the math — a per-agent, per-feature stack grows the denominator's cost with every hire; a flat plan does not.
Benefit 1: chat-assisted revenue (with honest attribution)
Count orders or signups where a chat happened BEFORE the purchase, in the same visit or within a defined window — your transcripts plus order timestamps give you this. Then say the honest sentence out loud: "some of these would have converted anyway." Claim the assisted number as an upper bound and let the trend line, not the absolute, carry the argument: if assisted conversions grow when you staff chat better, the channel is working.
Benefit 2: deflection value (the sturdiest number)
Every question your knowledge base and AI absorb is a conversation that did not consume agent minutes. Deflected volume x your measured cost-per-ticket is real, defensible saving — it survives scrutiny because both factors come from your own books. Track it monthly; it is usually the number that grows fastest as your deflection layers mature.
Benefit 3: the concurrency dividend
Compare cost per resolved conversation across your channels. Chat's advantage is structural — one agent, several conversations — so the same demand handled in chat instead of phone shows up directly as cost avoided per conversation, using entirely internal numbers.
What NOT to claim
- Industry-average conversion lifts applied to your traffic — borrowed numbers, instantly challenged.
- Every chat-touched sale as chat-caused — state assisted, not caused.
- Satisfaction-score deltas as dollars — keep CSAT as a health signal, not a revenue line.
The one-page version
Costs: agent chat hours x loaded rate + software. Benefits: assisted revenue (upper bound, trend), deflection savings (volume x own cost-per-ticket), channel cost advantage (chat vs phone per resolution). Caveats stated in the same document. Your operating metrics feed the model; transcripts and the resolution dashboard are the audit trail. On MyLiveChat's flat pricing, the software line stays constant as the team grows — which, in this framework, is simply a denominator that stops moving.