Global. SLA backed. Always on.

Application support, project support, training and skilled resources. We don't go away after go-live, we stick around so the platform you bought keeps getting better, not older.

What Support covers

Four kinds of help, engaged separately or together

Application support, project support, training and skilled resources, scoped to what is actually needed.

Why choose SMYL for Support?

Support should make the platform better over time, not just keep it alive. That difference shows up in how it is structured.

SLA backed, not best effort.

Response and resolution times are defined and measured, so support is accountable rather than "we will get to it."

Global coverage.

Support for implementations across multiple locations and time zones, not a single office model that struggles once you scale.

Continuous optimisation, not just fixing faults.

The goal is a platform that keeps getting better after go-live, not one that just gets patched when something breaks.

Context retained from delivery.

Because Support connects back to the same Microsoft platform expertise behind Implement and Advisory, issues get resolved with real context, not from a cold start.

Flexible engagement.

Application Support, Project Support, Training and Resources can be engaged separately depending on what is actually needed, not as a bundled package.

FAQ

Common questions

Specific to the Support practice.

How is ongoing Support typically priced?

Most engagements run on a retainer basis sized to expected volume and SLA tier, with Resources (dedicated skilled people on your programme) typically priced separately by day rate or engagement length. We scope this based on your current support load and desired response times, not a flat package that treats every client the same.

What's the difference between Application Support and Project Support?

Application Support is ongoing, SLA driven help with the live platform: incidents, fixes, minor changes. Project Support is different. It is brought in for the duration of a specific implementation or rollout, particularly across programmes across multiple locations and time zones, to bridge gaps in the client's own project capacity.

What SLA response times can we expect?

Response and resolution targets are agreed upfront and vary by severity. A system outage gets a materially faster commitment than a minor cosmetic request. These are set during onboarding based on your business's actual risk tolerance, not a generic tier applied regardless of what is actually at stake.

Can Support take over a system SMYL didn't originally implement?

Yes. Application Support and Training in particular are commonly engaged on systems built by another partner. We would typically run a short assessment first to understand the existing configuration before SLAs are agreed, so commitments are realistic rather than guessed.

After go-live

Tell us what is breaking. We'll tell you what it takes to fix it.

Sixty minutes with the team who would own your SLAs. You'll hear how we would structure cover and what response times are realistic.