Support and SLAs

Setting customer expectations of support and SLAs

In the previous lesson, we looked at how large volumes of customer feedback are handled using tools to operate a support model. It is also vital that we communicate our support offering to customers so that they have a clear understanding of what level of support they can expect. This is where our concepts of API maturity are instrumental. For experimental APIs, we can control the exposure to a limited set of customers because it is natural that the product and documentation are not thorough at this point and there is more support needed for customers to use such APIs.

It is standard practice for API product documentation to have a page dedicated to maturity. This maps each maturity level to the level of support provided. This allows customers to have an understanding of what to expect when they reach out to support for help. This mapping also involves expectations of how frequently APIs may change or whether any APIs are on the path to deprecation. Customers look at these pages to plan development and manage dependencies on their end to make sure their integration is stable and their customers are not impacted by changes to the underlying APIs.

For large customers, there are complex contracts in place that ensure a high ...