A reseller I work with — let’s call him the Pune guy, because he asked me not to name his agency — lost a 14-seat deal last year over a single sentence. The mid-size logistics prospect liked his rebranded WhatsApp CRM; the demo went well, the pricing was fine. Then procurement sent one email: what’s your SLA? He didn’t have one. He typed back something vague about “we usually reply same day,” and the deal went cold within a week.
Here’s the part that stings. A few months later he over-corrected — wrote an SLA, copied most of it from a generic SaaS template, and left in a line promising 99.9% uptime. He doesn’t host any servers. Six weeks later a client’s WhatsApp Web session broke for an afternoon (just a browser update), and the client waved that 99.9% line back at him and asked for a credit. He had promised a number he never controlled.
I’m Rakshit Soni, co-founder of Lion CRM, a WhatsApp CRM Chrome extension built by LotsOfCode Private Limited. I’ve spent about four years building WhatsApp automation tooling, and a big chunk of that now goes into helping whitelabel resellers turn a rebranded Lion CRM into a real subscription business. The SLA question comes up with almost every one of them, right after they win their first client with a procurement team. This guide is the document I wish the Pune guy had read before either mistake. (If you’d rather watch than read, the LotsOfCode YouTube channel covers reseller operations in video form.)
We’ll cover why an SLA is a sales asset, what you can and cannot promise when your product is a Chrome extension with 100% local data storage, the five components every whitelabel WhatsApp CRM SLA needs, a 3-tier ladder you can copy, the rupee math on staffing each tier, how to price a Priority tier, and a 7-step playbook to publish it. It’s built for the Vikram-style reseller — a 35-year-old running a 5-to-50-person agency in India, reselling a rebranded CRM to SMB clients on a monthly subscription.
TL;DR — the SLA you can keep beats the SLA that sounds impressive
| Basic | Standard | Priority | |
|---|---|---|---|
| First-response target | Next business day | 4 business hours | 1 business hour |
| Resolution target (best-effort) | 5 business days | 2 business days | Same business day where possible |
| Support hours | Mon–Fri, 10am–6pm IST | Mon–Sat, 9am–7pm IST | Mon–Sat, 9am–9pm IST + emergency line |
| Channels | Email / ticket form | Email + WhatsApp | Email + WhatsApp + scheduled call |
| Escalation | Tier-1 only | Tier-1, tier-2 | Tier-1, tier-2, named account contact |
| Who it’s for | Price-sensitive micro-clients | Most SMB clients | Clients with a procurement checklist |
A Lion CRM reseller hosts no infrastructure, so your SLA is a support SLA — a promise about how fast your team answers and fixes things — not an uptime SLA. Build three tiers, put in real numbers you can hit on your worst week, and never copy a hosted-SaaS 99.9% uptime clause you don’t control. An SLA you can keep wins more deals than an impressive one you’ll breach.
Why a whitelabel WhatsApp CRM SLA wins deals
Most new resellers treat an SLA as a defensive document — something a lawyer makes you write so clients can’t sue you. Flip it. A whitelabel WhatsApp CRM SLA is a sales asset. Who actually asks for one? Almost never the one-person dukandar paying ₹499 (~US$6) a month — it’s the prospect with twelve seats and a procurement checklist, comparing you against two or three vendors on can I trust this small vendor to still be answering my emails in eight months. An SLA answers that in writing. It signals operational maturity, removes a procurement objection, and lets you charge more — a Priority tier with a one-hour response promise is a line item the client can see and value.
The deeper point: the worst outcome isn’t having no SLA. It’s having a bad one. A copied SLA that promises things you can’t deliver wins the deal, then loses the client — plus a refund and a bad reference. An honest SLA you can keep is worth more than an aggressive one you’ll breach in month two.
What an SLA promises — and what a Chrome-extension reseller can’t
A traditional hosted-SaaS SLA has two halves. One is availability — the vendor’s servers are up, the dashboard loads; the famous 99.9% uptime line lives here. The other is support — how fast a human answers your ticket. Generic templates online are written for hosted SaaS, so they lead with availability.
Here’s what Lion CRM actually is, and you have to internalise this before writing a single clause. Lion CRM is a Chrome extension that runs on top of your client’s own WhatsApp Web session, inside their own browser. The client’s own number sends and receives every message. Contacts, tags, notes, templates — all stored locally on the client’s device with 100% local data storage. It is not a hosted dashboard, there’s no Meta partnership, and there’s no WhatsApp Business API in the loop.
So you, the reseller, host nothing. You cannot promise server uptime, because there is no server of yours to be up. If the client’s laptop is off, the CRM is off, and that isn’t a breach, it’s just how a Chrome extension works. What’s left is support. A Lion CRM reseller’s SLA is overwhelmingly a support SLA — a strong position, because you’re promising the one thing you genuinely control. There’s exactly one thin availability line you can honestly include — a best-effort pass-through of LotsOfCode’s admin-panel and license-activation availability — covered later. Everything else under a template’s availability heading should be deleted, not edited.
The local-storage architecture also helps your data clause. Because contact data lives on the client’s device and not on a server you operate, you aren’t a data processor the way a hosted SaaS is — you’re not holding a copy of their customer database in your cloud. Your SLA’s data clause can say so plainly, and that’s far more reassuring than a vague we take security seriously line. (For the architecture detail, the Lion CRM WhatsApp CRM Chrome extension guide is the canonical reference.)
The single most common reseller SLA mistake — I’ve seen it a dozen times — is copying a hosted-SaaS template and leaving the 99.9% uptime clause in. The moment a client’s browser hiccups, they point at that number and ask why you breached it. Promise what’s yours.
The five components of a whitelabel WhatsApp CRM SLA
Strip away the boilerplate and a working whitelabel WhatsApp CRM SLA has exactly five moving parts:
- First-response time — how fast a human acknowledges a request and starts looking. A promise to respond, not to fix.
- Resolution time — how long until the issue is solved. A best-effort target, never a hard guarantee.
- Support hours and channels — when your team is available, in a stated timezone, and through which channels.
- Escalation ladder — a clear path from tier-1 to tier-2 to a platform escalation with LotsOfCode.
- Platform-availability pass-through — the one honest, carefully-worded availability line covering the LotsOfCode-hosted admin panel and license activation, best-effort, no invented number.
Notice what’s not on the list: server uptime guarantees, network SLAs, data-centre redundancy. None of it applies, because you host none of it — a whitelabel WhatsApp CRM SLA is leaner than a hosted-SaaS SLA, and that’s a feature.
Thinking about reselling but haven’t started? Pick a plan, brand the extension, and generate licenses at admin.lioncrm.com. The SLA comes after you have something to support.
First-response time: the number that actually closes deals
First-response time is the most important number in your SLA, and the one new resellers most often get wrong — by promising too much.
Define it cleanly: it’s the gap between a client submitting a request and a real human acknowledging it and starting to investigate. An automated we got your email bounce-back doesn’t count — the clock stops when a human has read the issue and replied specifically.
What’s reasonable? Across B2B SaaS support teams in 2026, common benchmark targets land roughly here: critical issues get a response inside 15 to 30 minutes; high-priority inside 1 to 2 hours; medium-priority inside 4 to 8 business hours; low-priority within one business day — the same P1-to-P4 shape most help-desk SLA frameworks use. But you’re not a 200-person SaaS company with a 24/7 rota. The rule I give every reseller: promise the response time you can hit when one team member is on leave and another is in a meeting — your normal-bad case, not your best.
A practical tiered shape, the one in the ladder later:
- Basic tier — first response by next business day. Sounds slow? It’s honest, and still better than the no-SLA competitor. A micro-client paying ₹499 a month doesn’t need an hour-long response.
- Standard tier — first response within 4 business hours. Fits most SMB clients: quick enough to feel cared for, slow enough that a two-person team can hold the line.
- Priority tier — first response within 1 business hour. The number procurement teams want, and the one you charge real money for, because hitting it reliably means someone watches the queue all day.
One thing resellers skip: define your business hours in the SLA, in a named timezone, and define when the clock pauses. If your hours are Mon–Sat 9am–7pm IST and a ticket arrives at 8pm, the one-hour Priority clock starts at 9am the next morning. The biggest source of SLA arguments isn’t missing a target — it’s two parties measuring the same clock differently.
Honestly? Getting this right took the Pune guy three rewrites. His first draft promised two-hour response on every tier; he breached it within a month. His third draft is the shape above, and he hasn’t breached since.
Resolution time and why you never promise a hard fix deadline
Resolution time is how long it takes to actually solve the problem — not acknowledge it, solve it. The rule: never promise a hard resolution deadline. Always make resolution a best-effort target, clearly labelled.
Why? You don’t control every variable. Some issues you’ll solve in ten minutes; others depend on things outside your hands — the client takes two days to send a screenshot, or the issue is a Chrome update and the real fix comes from LotsOfCode’s next extension build. You can’t put a guaranteed clock on a problem whose solution sits partly with the client and partly with the platform vendor.
The mistake is everywhere: resellers conflate response time with resolution time. They write 4-hour SLA and the client reads fixed in 4 hours, while the reseller meant we reply in 4 hours. Fast response is not the same as fast fix, and your SLA must say so in plain words, in bold.
Three moves to write the clause honestly. Label it best-effort: We aim to resolve Standard-tier issues within 2 business days. This is a target, not a guarantee. Define a stop clock — the resolution clock pauses whenever you’re waiting on the client. And separate resolved from workaround provided: a good SLA promises a workaround inside the target even when the full fix takes longer.
The honest resolution targets: Basic, 5 business days best-effort; Standard, 2 business days best-effort; Priority, same business day where possible with a workaround inside the day. Every one has best-effort attached — that’s the truth, and the truth keeps the client when something runs long.
Want the reseller economics, not just the SLA? The margin side of a whitelabel WhatsApp CRM business deserves its own read — Whitelabel WhatsApp CRM margins: what resellers actually make breaks down the rupee numbers in full.
Support hours and channels: match the SLA to your team size
Support hours and channels is where ambition does the most damage. It’s tempting to write 24/7 support because it sounds world-class. Don’t — your SLA’s support hours must describe your actual team on its worst week. A realistic hours ladder for an Indian reseller:
- Basic tier — Monday to Friday, 10am to 6pm IST. Standard business hours, no weekend cover. Honest for a small team, fine for a low-paying client.
- Standard tier — Monday to Saturday, 9am to 7pm IST. Saturday matters in India — many SMB clients work six days.
- Priority tier — Monday to Saturday, 9am to 9pm IST, plus an emergency contact for genuine business-stopping issues. Note emergency — that channel is for “nothing is sending and I have a campaign,” not “how do I change a template.” Define what qualifies in writing, or the emergency line becomes a 24/7 line by accident.
Each channel you list is a promise you’ll watch it, so list only the ones you will. Email or a ticket form is the floor — every tier gets it, because it’s asynchronous and creates a written record, gold in any dispute. WhatsApp is natural for this product, but an open WhatsApp channel feels like it should be instant — so put it only on tiers where your response promise survives that expectation: Standard and Priority, yes; Basic, keep to email. Scheduled calls belong on Priority, because they cost real time.
A whitelabel note: every channel should carry your brand — support email, ticket form, WhatsApp number, help docs. The client should never see Lion CRM or LotsOfCode anywhere. Set this up once in the Branding section of the reseller admin panel, and the support number a client taps inside their CRM is yours.
The escalation ladder: tier-1, tier-2, LotsOfCode
An escalation ladder answers a client’s quiet worst fear: what happens when the first person can’t fix my problem? For a whitelabel WhatsApp CRM reseller, three rungs.
Rung one — tier-1, front-line support. Whoever picks up the ticket first, handling the bread-and-butter: how-to questions, configuration help, license activation, basic troubleshooting. Realistically, 70 to 80 percent of tickets never leave this rung.
Rung two — tier-2, your senior person. When tier-1 can’t solve it — a stranger bug, a webhook misfiring — it goes to your most experienced person, who can read logs and tell a misconfiguration from a genuine break.
Rung three — platform escalation to LotsOfCode. For the small set of issues genuinely Lion CRM-side: a confirmed extension bug, an admin-panel problem, a license-activation failure. As a whitelabel partner you have a direct line to LotsOfCode — your tier-2 person packages the issue and hands it up.
The honesty rule for rung three: in your SLA you commit to escalating platform issues promptly and to keeping the client informed — not to a fix deadline, because that fix isn’t yours to schedule. Word it: Issues confirmed to originate with the platform are escalated to the platform vendor within one business day, and we will keep you updated until resolution. Your two rungs are your team, branded as you; LotsOfCode is behind the curtain. The client experiences one support brand, yours.
The operational side of running 25+ client licenses — provisioning, renewals, trial-to-paid conversion — is its own discipline. Multi-tenant license management for WhatsApp CRM resellers is the deep-dive.
Platform availability: the one honest pass-through line
This is the shortest section on purpose, because this part of your SLA should be short, careful, and honest.
As a Lion CRM reseller you host no infrastructure, so you cannot and must not promise application uptime. But there is a sliver LotsOfCode hosts that genuinely needs to be available: the admin panel and the license-activation service. So your SLA can include one carefully-worded line — a best-effort pass-through.
Don’t write: We guarantee 99.9% platform uptime. You don’t host the platform and can’t measure that number. It’s the exact landmine the Pune guy stepped on.
Do write something like: The Lion CRM platform — including license activation and the management back-end operated by the platform vendor, LotsOfCode Private Limited — is provided on a commercially reasonable, best-effort availability basis. We monitor platform status and will inform affected clients promptly of any extended disruption. Day-to-day use of the CRM runs locally in your browser and does not depend on continuous platform connectivity.
That paragraph is honest — it uses best-effort, not a percentage — and it makes a promise you can keep: you’ll monitor and inform. A procurement person who knows what they’re reading trusts you more for an honest best-effort line than for a confident percentage you can’t back.
The 3-tier whitelabel WhatsApp CRM SLA ladder
Here’s a complete 3-tier whitelabel WhatsApp CRM SLA ladder you can adapt and publish. Three is the right number — two doesn’t differentiate enough, four or more confuses clients and overloads a small team.
| Component | Basic | Standard | Priority |
|---|---|---|---|
| First-response target | Next business day | 4 business hours | 1 business hour |
| Resolution target | 5 business days, best-effort | 2 business days, best-effort | Same business day where possible; workaround within the day |
| Support hours | Mon–Fri, 10am–6pm IST | Mon–Sat, 9am–7pm IST | Mon–Sat, 9am–9pm IST + emergency line |
| Channels | Email / ticket form | Email + WhatsApp | Email + WhatsApp + scheduled call |
| Escalation | Tier-1 | Tier-1, tier-2 | Tier-1, tier-2, named account contact |
| Platform availability | Best-effort pass-through | Best-effort pass-through | Best-effort pass-through + proactive status alerts |
| Onboarding | Self-serve help docs | Guided setup call | White-glove setup + template configuration |
| Who it’s for | Micro-clients, 1–3 seats | The default SMB client, 4–15 seats | Larger clients, procurement checklist, 12+ seats |
The platform-availability row is identical across all three tiers — best-effort pass-through — because that part isn’t yours to differentiate. Everything that does scale is a support behaviour you control: response speed, hours reachable, channels watched, escalation depth, onboarding hand-holding. Keep each tier to one page, and write it so a tier upgrade is an obvious sale — when a Basic client outgrows next-business-day response, the Standard and Priority rows show what more money buys.
What each whitelabel WhatsApp CRM SLA tier costs you to deliver
Every promise in your whitelabel WhatsApp CRM SLA costs you something to keep. Skip this math and you’ll lose money on your Priority clients. Let’s model a Vikram-style agency of 25 SMB clients. Assume a competent support person costs roughly ₹30,000 per month fully loaded (~US$360).
Basic tier — next business day, Mon–Fri. The queue gets checked twice a day, tickets can wait. Roughly ₹40–₹70 per client per month (~US$0.50–US$0.85) — almost nothing, which is why the tier exists.
Standard tier — 4-hour response, Mon–Sat extended hours. Someone watches the queue through the day. Roughly ₹150–₹300 per client per month (~US$1.80–US$3.60).
Priority tier — 1-hour response, Mon–Sat 9am–9pm, emergency line. The expensive one, and resellers consistently underprice it. A one-hour promise across a 12-hour day keeps someone on the queue all day. Roughly ₹600–₹1,200 per client per month (~US$7–US$14).
Total it for the 25-client agency, with a typical split of 8 Basic, 13 Standard, 4 Priority:
| Tier | Clients | Loaded cost each / month | Tier subtotal / month |
|---|---|---|---|
| Basic | 8 | ~₹55 (~US$0.65) | ~₹440 (~US$5) |
| Standard | 13 | ~₹220 (~US$2.65) | ~₹2,860 (~US$34) |
| Priority | 4 | ~₹900 (~US$11) | ~₹3,600 (~US$43) |
| Total | 25 | ~₹6,900/month (~US$83) |
Supporting all 25 clients costs this agency roughly ₹6,900 a month — about a third of one support person. Notice the shape: 4 Priority clients cost more to support than 13 Standard clients. Priority is the most expensive thing you deliver, and it has to be priced like it. Documentation quality swings the numbers most — good branded help docs can cut Standard and Priority time by a third.
Test the product before you build a support operation around it. Install Lion CRM yourself — the 7-day free trial is automatic — and you’ll see which features generate tickets before a client asks. Steps are a few sections down.
Pricing your SLA tiers: what to charge for priority support
You know what each tier costs. What do you charge? An SLA tier is a product, and you price it on value, not a markup over cost. The cost math is your floor — never sell below what it costs to deliver — but the price is set by what the tier is worth to the client.
Two ways resellers package SLA pricing. Bundled into the plan: Basic with your entry plan, Standard with the mid plan, Priority with the top plan — simplest to sell, where most should start; the risk is under-charging the top plan because you didn’t isolate the cost of Priority support. Paid add-on: the client buys a plan, then optionally adds a support tier — this makes the value of support visible and lets a price-sensitive client stay on Basic without you losing the deal.
Here’s the mild hot take. Most resellers leave real money on the table by bundling Priority into the top plan and pricing it as just more features. It isn’t — Priority support is a person partly dedicated to a client. If your top plan is only ₹800 (~US$10) a month more than your mid plan, and Priority support alone costs ₹900 a month per client, you are paying clients to be on your best tier. Whatever model you pick, the Priority increment should clear your delivery cost with margin — ideally ₹1,500–₹2,500/month (~US$18–US$30). The client buying Priority is buying certainty, and certainty is worth a premium.
How does this sit on the Lion CRM whitelabel cost base? Your platform cost is the reseller tier fee plus a per-user-per-month license fee — Starter is US$150 one-time plus US$2.50/user/month, Growth is US$200 one-time plus US$2.00/user/month (the popular pick), Enterprise is US$250 one-time plus US$1.00/user/month. At Growth, roughly US$2/user/month is about ₹166/user/month. Your client price covers three stacked costs: platform license, support delivery, and margin. A Standard client paying ₹999/month — ₹166 to platform, ~₹220 to support, the rest gross margin. A Priority client at ₹2,999/month carries the same ₹166 platform cost, ~₹900 of support, and still leaves healthy margin. Sanity-check current numbers on the Lion CRM pricing section; the whitelabel WhatsApp CRM pricing models guide walks all five models with rupee math.
Ready to set your own tier prices? Buy a whitelabel plan, brand the extension, and you control every price your clients see. Start at admin.lioncrm.com — PayPal checkout runs through paypal.com, and Kuldeep handles partnership questions on WhatsApp at +91 74260 34448.
How to write and publish your SLA document
You’ve got the components, the tiers, the cost math, the pricing logic. Here’s the 7-step playbook to turn it into a published SLA your sales team can hand a prospect.
Step 1 — Pick your tiers and lock the numbers. Use the 3-tier ladder above as your frame. For each tier, write down the exact first-response target, resolution target, support hours, channels, and escalation depth. The hard rule: every number must be one you can hit on a bad week. If you can’t, soften it now — free to fix on paper, expensive to breach in production.
Step 2 — Write the scope and definitions section. Define your terms in plain language: what counts as a support request, what first response means (a human, not an auto-reply), what business hours mean in IST, and when the clock pauses. Most SLA disputes are definition disputes, so this dull section prevents the most fights.
Step 3 — Write the five components, in order. First-response time, resolution time (best-effort, with the response-is-not-resolution sentence in bold), support hours and channels, the escalation ladder, the platform-availability pass-through line — using the wording from the sections above.
Step 4 — Write the honest exclusions. State plainly what the SLA does not cover: issues caused by the client’s own hardware, internet, or browser; WhatsApp account problems from messaging cold contacts against safe-send guidance; third-party tools connected via webhooks. Clear exclusions protect you and, counter-intuitively, make the client trust the rest more.
Step 5 — Decide on remedies, and keep them modest. You can offer a small goodwill credit if you miss a response target badly, but tie remedies only to things you control. Never tie a remedy to uptime or to a resolution deadline — an aggressive remedy clause is a liability you wrote yourself.
Step 6 — Brand it and put it where prospects can find it. It carries your agency’s name, logo, and colours — Lion CRM and LotsOfCode appear nowhere. Publish it as a clean PDF for your sales deck and a page on your website.
Step 7 — Review it quarterly. An SLA isn’t write-once. Each quarter, check: did you breach any tier, did your team grow, did client mix shift? Adjust the numbers to reality.
A focused afternoon gets you the first draft if you use the ladder above. Don’t rush step 1 and don’t skip step 4 — those are the two that bite.
Try Lion CRM free for 7 days
Before you design a support operation around a product, know it cold — which features generate the most how-to tickets. The fastest way is to run Lion CRM yourself. Every first-time Chrome Web Store install gets an automatic 7-day trial.
Steps:
- Click the install link → Get Lion CRM on Chrome Web Store
- Click “Add to Chrome” — the extension installs in seconds.
- Open WhatsApp Web in your browser — Lion CRM activates automatically on top of your own session.
- Your 7-day trial starts the moment you log in. No credit card needed.
- Walk through the 16 features — Bulk Messaging, Kanban Board, Message Templates, Quick Reply, Smart Calendar, Webhooks, the rest — and note which ones a client would need help with. That note becomes your tier-1 support playbook.
- After 7 days, pick a paid plan (₹99 first-month special, then ₹299/month, or ₹2,360/year ≈ ₹197/month) or move straight to the whitelabel reseller plan below.
The features that confuse you in the first hour are the ones that will generate tickets.
Start your whitelabel WhatsApp CRM SaaS
Once you’ve tested the extension and you’re ready to resell it under your own brand and SLA tiers, here’s the reseller flow:
Steps:
- Go to the admin panel → admin.lioncrm.com
- Register your agency account, then log in.
- Choose a plan — Starter (US$150 one-time + US$2.50/user/month), Growth (US$200 one-time + US$2.00/user/month, the popular pick), or Enterprise (US$250 one-time + US$1.00/user/month) — and complete payment. PayPal checkout runs through paypal.com. You’ll be redirected to the reseller dashboard.
- Open the Branding section → fill in your white-label details (brand name, logo, colours, support number, your website URL) → click Save. The support number you enter here is the one your SLA promises.
- Click Download Extension to get your own white-label branded build of the Chrome extension.
- Open the Licenses section to generate licenses:
– Paid licenses (each consumes one active-user slot at your tier’s per-user/month fee)
– 7-day free trial licenses (give to prospects so they can test your branded extension first) - The Overview section gives you 1 month of free license for your own personal use.
- Add balance once in the Wallet section — it removes per-license payment friction, since each new license draws from the wallet balance.
- Distribute your branded extension, activate client licenses, and hand each client the SLA tier they bought. You’re now running your own whitelabel WhatsApp CRM SaaS — with a support SLA you can actually keep.
One compliance note: whitelabel partners need a minimum of 30 active user licenses after a 3-month grace period. The same reseller flow is walked through on the LotsOfCode YouTube channel if you’d rather watch it, and Kuldeep handles partnership and onboarding questions on WhatsApp at +91 74260 34448.
The honest verdict: which SLA tier model fits which reseller
If you skipped to the bottom, here’s the decision-tree version.
- Brand new, first few clients, no procurement-grade prospects yet. Publish a simple two-tier SLA, Basic and Standard, with honest, generous numbers. Don’t build a Priority tier you can’t staff; add it the day a deal needs it.
- Established reseller, 15–40 clients, a support person or two. Run the full 3-tier ladder. Bundle Basic into your entry plan, Standard into the mid plan, and price Priority as a clearly-costed top tier or paid add-on. This is the sweet spot the guide is built for.
- You keep losing bigger deals and don’t know why. It’s probably the missing SLA. A vendor with no SLA fails a procurement checklist silently — the prospect just goes quiet, the way the Pune guy’s did. Publish even a basic tiered SLA this month.
- Tempted to copy a generic SaaS SLA? Don’t. It hands you a 99.9% uptime clause you can’t honour, because you host no servers. Build a support SLA from the five components instead.
The thread through every case is the same: your whitelabel WhatsApp CRM SLA should promise exactly what you control — response speed, support hours, escalation depth — and nothing you don’t. Resellers who write the honest tiered version close bigger deals and keep their clients. The ones who copy the impressive generic version spend the next quarter explaining breaches. Write the one you can keep.
Frequently asked questions
Q: What should a whitelabel WhatsApp CRM reseller’s SLA include?
Five components: first-response time, resolution time (labelled best-effort), support hours and channels, an escalation ladder, and a carefully-worded platform-availability pass-through line. Plus supporting clauses — scope and definitions, honest exclusions, a modest remedies clause, and a data line noting CRM data is stored locally on the client’s device. What it should *not* include is a server-uptime guarantee, because a Lion CRM reseller hosts no infrastructure — the product is a Chrome extension running in the client’s own browser.
Q: What first-response time should I promise in my SLA?
Promise the response time you can hit on a bad week — someone on leave, someone in a meeting — not your best case. A sensible reseller ladder is next-business-day for Basic, 4 business hours for Standard, and 1 business hour for Priority. B2B SaaS benchmarks are tighter, but those are for large teams with a 24/7 rota. An honest next-business-day promise you always keep beats a 2-hour promise you breach.
Q: Should my whitelabel WhatsApp CRM SLA promise uptime?
No — not as a number. Lion CRM is a Chrome extension that runs on the client’s own WhatsApp Web session in their own browser, with 100% local data storage. You host no servers, so you can’t measure or guarantee application uptime. Copying a generic *99.9% uptime* clause is the single most common reseller SLA mistake. The only honest availability line is a best-effort pass-through covering the LotsOfCode-hosted admin panel and license activation — with no invented percentage.
Q: How do I price a Priority support tier?
Start with what it costs to deliver — realistically ₹600–₹1,200 per Priority client per month (~US$7–US$14) in loaded staff time, since a 1-hour promise across a 12-hour day keeps someone on the queue all day. That’s your floor. Then price on value: the increment between your Standard and Priority prices should comfortably clear that delivery cost with margin, typically around ₹1,500–₹2,500/month. Clients buy Priority for certainty, and certainty is worth a premium.
Q: What’s the difference between response time and resolution time?
Response time is how fast a human acknowledges the ticket and starts looking. Resolution time is how long until the problem is actually solved. Response time is always shorter and is the one you can firmly commit to. Resolution should always be a best-effort target, never a hard guarantee, because some fixes depend on the client or on the platform vendor. Resellers conflate the two — they write *4-hour SLA* and the client reads *fixed in 4 hours*. Put a sentence in bold stating fast response is not the same as fast fix.
Q: How many SLA tiers should I offer?
Three is the sweet spot — Basic, Standard, Priority. Two tiers don’t differentiate enough between a ₹499 micro-client and a 15-seat client with a procurement team. Four or more confuses clients and overloads a small support team. If you’re brand new, even start with two (Basic and Standard) and add Priority only when a real deal needs it.
Q: Should my SLA offer service credits if I miss a target?
You can offer a small goodwill credit — a few days of free service — if you badly miss a response target, since response time is something you fully control. Never tie a credit to uptime (you don’t host infrastructure) or to a hard resolution deadline (resolution is best-effort and partly depends on the client and platform vendor). An aggressive credit clause copied from a hosted-SaaS template is a self-inflicted liability.
Related guides
These Lion CRM articles go deeper into the reseller-operations and economics side:
- Whitelabel WhatsApp CRM onboarding checklist for resellers — the Day-1 to Day-30 reseller onboarding playbook that pairs with your SLA.
- Multi-tenant license management for WhatsApp CRM resellers — the operational deep-dive on running 25+ client licenses without losing track.
- Whitelabel WhatsApp CRM pricing models: agency playbook 2026 — five pricing models compared with full rupee math.
- Whitelabel WhatsApp CRM margins: what resellers actually make — the reseller margin economics, tier by tier.
- Whitelabel WhatsApp CRM comparison India 2026: honest guide — the pillar guide every reseller article links back to.
- Launch your own WhatsApp CRM SaaS in 7 days — the end-to-end stand-up playbook from zero to first client.
- Whitelabel WhatsApp CRM software: founder’s 2026 guide — start here if you’re new to whitelabel reseller economics.
Written by Rakshit Soni, co-founder at LotsOfCode Private Limited and creator of Lion CRM, with about four years building WhatsApp automation tooling and working directly with whitelabel resellers. If you have a question this guide didn’t answer — about SLA tiers, pricing, or the reseller flow — the fastest channel is WhatsApp to Kuldeep, co-founder, at +91 74260 34448.