Alright, I'm coming at this from the wrong side of the budget. I'm the person who gets handed the bill after the "easy-to-use, no-code, omnichannel future of customer support" platform has been enthusiastically adopted. The sticker shock is real.
You need to interrogate the pricing model like it's a hostile witness. Demos are about features, but your CFO only cares about the cost line item exploding at 3 AM. Here are the questions I'd be asking, framed for someone new to this:
**Pricing & Scalability**
* "Your pricing page says $X per agent/month. Walk me through what an 'agent' is defined as. Is it a named user? A concurrent session? If my part-time agent works 20 hours a week, do I pay the same as a full-timer?"
* "Show me the invoice breakdown for a hypothetical scenario: 10 agents today, scaling to 25 in six months, then to 50 next year. I want to see the *actual* monthly cost for each stage, including any required 'add-on modules' for basic reporting or extra channels."
* "Where are the hidden fees? What's the premium for phone support? Are there charges for outbound emails/SMS? Data retention beyond 30 days? API call limits that would incur overages?"
**Architecture & Lock-in**
* "How easy is it to get our data out? Can I do a full export of all tickets, knowledge base articles, and customer history in a standard format (like CSV/JSON) on-demand, or is it a 'contact support' and pay-for-service ordeal?"
* "If we need to leave, what's the actual process? Is there a data migration fee? Are there termination penalties buried in the annual contract?"
**The Operational Reality**
* "You showed me the beautiful dashboard. Let me see the raw data export for a report. I want to understand what metrics I can actually feed into our internal cost allocation system."
* "Talk to me about support tiers. If the platform has an outage, what's your SLA? If it's 'best effort' on a $10/agent plan, that's a business risk."
The goal isn't to be difficult, it's to avoid the classic SaaS bait-and-switch: low intro price, then the *real* cost reveals itself once you're operationally dependent. Good platforms will answer these clearly. The ones that get evasive? You've just saved yourself a major financial headache.
Cloud costs are not destiny.
This is such a crucial point, and you're right about the 3 AM bill shock. Been there!
One question I always add to "show me the invoice breakdown" is asking them to model a seasonal spike. Like, what if we need 40 agents for holiday season, but only 20 the rest of the year? Does the contract lock us in, or can we flex? That's where the per-concurrent-session definition really matters.
Great advice on API overages, too. That one's a silent killer for any automation you plan to build.
Another tool to try!