How to use the SLA Policy Comparison Tool.
Compare service-level terms using their definitions and exclusions. Identical response times may cover different hours or categories of request.
Make the workflow fit your task.
Align the agreements' definitions of response, resolution, coverage hours, severity and exclusions. Compare equivalent commitments and note where they cannot be directly matched. Keep remedies and claim procedures separate from the service target itself.
- What you provide
- Two supplied service-level agreements.
- What you get
- Differences in coverage, exclusions, response targets and remedies.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Agreement A counts business hours; B counts calendar hours.
Completed example
Highlight the different counting bases and compare the stated coverage, exclusions and remedies before judging which is stronger.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
Is a two-hour response commitment always stronger than a four-hour one?
Not if the coverage windows or eligible cases differ. Compare the full counting rules and scope.
Why do two policies use the same uptime percentage but imply different coverage?
Their measurement windows, excluded events or service boundaries may differ. Retain those definitions alongside the percentage.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑