Named customer success manager and priority SLA.

Be careful with those two numbers, because they are the ones most likely to be misread. The 15-minute response target and the 99.9% uptime figure printed on this page are examples of the kind of terms a priority agreement can contain — they are illustrative, plan-dependent and contract-dependent, not a universal guarantee that applies to every customer the moment they see this page. What an SLA genuinely commits anyone to lives in a signed agreement, and that document is the only thing that binds. It is where the real definitions sit: what counts as a response versus a resolution, which severity levels get which targets, what hours those targets apply in, how uptime is measured and over what window, what is excluded (planned maintenance, third-party outages, things outside the provider's control), and what you actually receive if a target is missed — typically service credits calculated a particular way, with terms and caps, rather than an open-ended remedy. None of that can be read off a dashboard mock, and we would rather say so plainly than let a “15 min” label do work a contract has not agreed to. So the honest answer is: these figures show the sort of commitment a Priority SLA is built around, the precise targets and credit terms are set by your plan and your agreement, and you should get them from sales in writing and read the SLA schedule itself before relying on any specific number. Ask, in particular, for the severity definitions, the measurement method for uptime, the exclusions, and the exact remedy — those four points are where an SLA either means something or doesn't.

That is a commercial question, and the honest answer is that it depends on your plan and is best confirmed with sales or pricing rather than guessed from this page. A dedicated, named customer success manager is a resource-heavy offering — it is a real person's time — so it is typically positioned at the higher end: an enterprise or priority-tier benefit, sometimes bundled into such a plan and sometimes available as a paid add-on on top of a lower tier. We are deliberately not naming a specific plan, a price or a tier boundary here, because inventing one would be worse than useless: tier names, what each includes, and where the CSM sits can differ by region, by contract and over time, and the page does not state them. What you can reasonably do is ask sales three direct questions and get the answers in writing. First, on the plan you are considering, is a dedicated CSM included, an add-on, or not available at all? Second, if it is an add-on, what does it cost and how is it billed? Third, what exactly does the role include at that level — how many hours, how often you meet, whether the performance audit and structured training are part of it or separate. Those answers, tied to your specific plan, are the ones that actually matter, and they come from your account conversation rather than from this marketing page.

Take those three numbers as illustration, not as a promise. The 98 health score, the 84% adoption figure and the 42 resolution-time value on this page are sample data drawn to show what a success dashboard looks like when it is populated — they were not measured at your business, they are not a forecast of your results, and they are not a target anyone is committing you to hit. So no, a CSM does not come with a guaranteed uplift in ROI, adoption or performance, and we are not going to imply otherwise. What a good CSM actually provides is guidance and structure: a written account plan, a periodic performance audit that points out where you are underusing the product, training that helps your team adopt the features they are paying for, and a faster route to the right people when something goes wrong. Those are inputs, and they genuinely tend to help — but the outcome depends on your operations. Whether adoption rises depends on whether your managers roll out the training and your staff use what they learn. Whether resolution times fall depends on your own processes as much as ours. Whether any of it turns into return depends on decisions only you can make on your own floor. The honest framing is that a CSM improves the odds and the clarity, and gives you someone whose job is to keep pushing on your behalf; the results are earned in your operation, not delivered by the role. Measure against your own baseline over enough time to be real, and judge the value of the CSM against that — not against a figure that exists to make a demo screen look healthy.

The shape the page describes is a sensible one and worth walking through, as long as the timeline labels are read for what they are. It runs roughly: a kickoff, where your CSM and team agree what success looks like and build the account plan; onboarding, where the product is configured to how you actually work and your data is brought in; training, so the people who will use it every day know how; go-live, the switch to running for real, ideally with your CSM close at hand; a review shortly after, to catch what the plan missed and fix it while it is fresh; and then an ongoing optimization loop — the periodic performance audit — where you keep tuning as you grow. The “Week 1” and “Month 2” style labels on this page are there to show that this is a staged journey with early wins and later refinement, not a single flip of a switch. They are a typical shape, not a contract, and the real timeline varies a lot with your size and complexity. A single site with a simple menu and clean data can move quickly; a multi-site operation, or one migrating years of history, integrating other systems, or training large or shift-based teams, will take longer, and pushing that faster than the operation can absorb is usually a false economy. So the useful thing to do is not to fix on a number from the page but to ask your CSM to build a realistic plan for your situation, with the dependencies named — data you need to supply, hardware that has to be in place, people who need to be freed up to train — and to agree what “done” means at each stage. Onboarding goes well when it is paced to your operation; the labels here describe the arc, not a delivery date.

This is the honest limit of a named-person model, and it is better to be clear about it up front than to discover it during an outage. Your dedicated CSM is one human being: they have a timezone, working hours, holidays, and a life outside your account. That is exactly why they are the right person to own your plan and your relationship, and exactly why they are the wrong person to be your emergency line. So urgent problems — the terminal down mid-service, the thing that cannot wait until morning — do not route to the individual. They route through the standard support channel and the on-call and escalation path that sits behind it, which is staffed to cover the hours a single CSM cannot, and which is where the SLA response targets discussed above actually apply. Your CSM's job is to make sure that path is set up correctly for you before you need it: that the right people at your business know how to raise a priority issue, that the contacts and severity levels are configured, and that when something serious does happen they pick it up afterwards — checking it was handled, chasing anything still open, and feeding it into the account plan so it is less likely to recur. Think of it as a division of labour: the CSM owns the relationship and the follow-through during their hours, and the support and on-call function owns the clock. Two things are worth pinning down with sales in writing before you rely on any of it: what the support hours and escalation path actually are for your plan, and whether the priority response targets apply around the clock or only within stated hours. Those answers, not the reassurance of a named contact, are what tell you what happens at 2am.