Put a Price on Support Hours Saved

Why this matters

A bot that "helps with customer service" is a vague nicety nobody pays for. A bot that "saves you about 9 hours and roughly 2,700 rupees of staff time every month" is a business case. The difference is one arithmetic calculation, and it's the calculation you'll repeat for every client for the rest of your career. Getting comfortable turning "a lot of questions" into a defensible monthly number now means that later, when you're pricing a bot at a setup fee plus retainer, you're anchoring your price to money the client already agrees they're losing. Owners argue with opinions but nod at their own numbers. This task teaches you to build the number honestly, so it survives scrutiny.

Demo

Let's price Meera's yoga studio from the last task. Add up her weekly question volume: 25 + 15 + 12 + 10 + 6 = 68 questions per week. Now estimate handling time. These are short questions, but each one includes the interruption, reading, replying, and getting back to what she was doing — call it 3 minutes each on average (be honest; a DM you answer between clients realistically eats more than the 30 seconds of typing). So 68 questions × 3 minutes = 204 minutes/week, which is 3.4 hours/week. Over a month (~4.3 weeks) that's about 14.6 hours/month.

Now put a price on an hour. Meera's time — or a part-timer she'd pay to cover the desk — is worth, say, 300 rupees/hour (use your own realistic local number; for a US shop it might be $18/hour). So 14.6 hours × 300 = roughly 4,380 rupees/month spent answering questions a bot could handle. That's your value anchor. Write it as one honest sentence: "Flow Room spends about 14.6 hours and 4,380 rupees a month answering five repeated questions by hand." Two rules keep this credible: round down when unsure (say 3 minutes, not 5, if you're guessing), and never claim the bot saves 100% — a good bot deflects maybe 70-80% of these, so the real saving is closer to 10-11 hours and ~3,200 rupees. Under-promise the saving and the number stays yours in an argument.

Try it yourself

1. Sum the weekly frequencies of your five FAQs into one questions-per-week number.
2. Assign an honest average handling time in minutes per question (include the interruption cost, not just typing time) and multiply to get minutes per week.
3. Convert to hours per month by dividing by 60 and multiplying by 4.3.
4. Pick a realistic hourly cost for whoever answers these questions in your business, and multiply to get monthly money spent.
5. Apply a 70-80% deflection rate to get the honest monthly saving, and write it as one plain sentence naming the business, the hours, and the money.

References

• Zendesk — Customer support metrics and KPIs
• Intercom — Support ROI and deflection