CRM Pitfalls, Contracts and Official Sources
CRM uptime, SLAs and support: what the percentages mean and what to ask
How to read a CRM service level agreement: uptime percentages as downtime hours, exclusions, service credits, support tiers and Australian business hours, with illustrative examples.
A CRM service level agreement (SLA) usually promises a monthly uptime percentage, lists exclusions such as scheduled maintenance, and offers service credits (a small discount on future bills) if the target is missed. For a small business, the more practical questions are when maintenance happens in Australian time, how fast support responds during your business hours, and whether the SLA applies to your tier at all, because many vendors offer formal SLAs only on higher plans. Service credits rarely cover the cost of an outage, so treat the SLA as a signal of reliability, not as insurance.
This guide is part of why CRM rollouts fail. Figures are illustrative.
Uptime percentages as hours
An average month has about 730.5 hours.
| Monthly uptime commitment | Allowed downtime a month | Allowed downtime a year |
|---|---|---|
| 99.0% | about 7.3 hours | about 87.6 hours |
| 99.5% | about 3.7 hours | about 43.8 hours |
| 99.9% | about 44 minutes | about 8.8 hours |
| 99.95% | about 22 minutes | about 4.4 hours |
The calculation is: allowed downtime = hours in the period × (1 − uptime %). A 99.9% commitment allows 730.5 × 0.001 ≈ 0.73 hours, or about 44 minutes, a month.
Read the exclusions
Uptime commitments usually exclude:
- scheduled maintenance, often announced in advance; check whether windows fall in Australian business hours, since a weekend night in the US can be Monday morning in Sydney;
- emergency maintenance;
- problems caused by your internet connection, devices or third-party integrations;
- partial outages (for example email sync or reporting down while the core works), which may not count as downtime;
- beta features and add-ons.
Also check how uptime is measured (the vendor's own monitoring, usually) and whether you have to claim a credit within a time limit.
Service credits: an illustrative example
A 10-seat business pays an illustrative $700 a month. The SLA promises 99.9% and gives a 10% credit if monthly uptime falls below that. One month, the CRM is unavailable for 3 hours on a weekday.
- Uptime that month: 1 − 3 ÷ 730.5 ≈ 99.59%, below 99.9%, so a credit applies.
- Credit: 10% × $700 = $70, usually against a future bill, and only if claimed.
- Cost to the business: 8 salespeople unable to work normally for 3 hours at $55 an hour = 8 × 3 × $55 = $1,320, plus any lost sales.
The credit covers about 5% of the cost. That is typical: SLAs limit the vendor's exposure. Your protection is choosing a reliable vendor, having a fallback (for example, an offline copy of key contacts and today's tasks), and contract rights to exit if reliability is persistently poor.
Support levels
| What to check | Questions |
|---|---|
| Channels | Email, chat, phone? Which are in your tier? |
| Hours | Are support hours in Australian time zones? Is there weekend cover? |
| Response targets | First response times by severity, for your tier |
| Language and location | Who answers and from where (relevant to data access) |
| Onboarding | Is there included onboarding or training? |
| Premium support | Price and what it adds |
| Partner support | If a partner supports you, what are their hours and terms? |
Illustrative example. Basic support with email only and a 24-hour first-response target sounds acceptable until a Friday afternoon problem waits until Monday. A premium support plan at an illustrative 15–25% of subscription may be worth it for a business that cannot sell without the CRM; for others, it is not. Count it in the 3-year TCO.
Reliability and security signals
You cannot audit a vendor yourself, but you can ask:
- Is there a public status page with incident history?
- What independent security certifications or audit reports cover the service?
- Where are data and backups hosted, and is an Australian region available? See the Privacy Act guide.
- How quickly will the vendor notify you of a security incident affecting your data? See the data breach response plan.
- What are the recovery point and recovery time objectives (how much data could be lost, and how long restoration takes)?
Building a fallback
- A weekly export of key contacts and open deals, stored securely (see data export and exit).
- Phone numbers of top customers available offline to the people who need them.
- A simple procedure for taking enquiries during an outage and entering them later.
- Monitoring of integrations so an outage does not silently stop syncing to Xero or MYOB.
Contract points
- Is the SLA part of the contract, or a policy the vendor can change?
- Is there a right to terminate after repeated SLA failures?
- Does the liability cap leave any meaningful remedy?
The Australian Consumer Law's consumer guarantees may apply to services costing $100,000 or less, including a right to remedies for a major failure. See contract traps and auto-renewal.
Frequently asked questions
Is 99.9% uptime good?
It is a common commitment for business cloud services. The exclusions and the times outages happen matter as much as the number.
Do small plans get an SLA?
Often not a formal one. Ask, and check the terms that apply to your tier.
Should we pay for premium support?
If the CRM is critical to daily selling and your team is small, faster support can be worth it. Trial standard support first and see how responsive it is.
Who do we contact about a serious, unresolved service failure?
Start with the vendor's escalation process, then see complaints, disputes and official sources.
Sources
- Australian Competition and Consumer Commission — consumer guarantees for services bought by businesses
- Australian Cyber Security Centre — choosing secure cloud services and backups
- Office of the Australian Information Commissioner — security obligations and overseas data
- Australian Small Business and Family Enterprise Ombudsman — supplier disputes
