Service level agreement (SLA)
Spell out uptime commitments, severity levels, response and resolution times, service credits and exclusions as a contract exhibit both sides can verify.
Prompt
Draft a service level agreement for a cloud contact center platform for businesses. Purpose: attach it to the service contract so customers know exactly what service level we commit to and both sides have a clear basis. Requirements: define scope and key terms, state the monthly uptime commitment and how it's calculated, define P1–P4 severity levels with examples, tabulate first response, update frequency and resolution targets per level, describe support channels, escalation and scheduled maintenance, set out service credits, the claim process and exclusions, and cover service reporting and reviews. Use the figures we provide and mark any we haven't given as "TBD".
- Source
- Ofox
How to use
- 1
Tap “Make one like this”
Ofox Chat opens with this document’s structure ready to go. Sign in first if you haven’t.
- 2
Make it yours
Edit the highlighted parts of the prompt to swap in your own details.
- 3
Send and create
Send it and Ofox Chat writes the full document for you to download. Keep chatting to revise it.
FAQ
What kind of file do I get?
A complete, downloadable document (Word or PDF) — not just a block of text in the chat.
Do I need to prepare anything?
No — you can send it right away and Ofox Chat writes a first version from the template. Add your background, data or existing documents (paste them in, or upload PDFs, Word files and more) and the result fits your situation much better.
Can I edit the prompt?
Yes. The prompt goes into the Ofox Chat input box — swap in your own topic, add requirements or drop what you don’t need before sending.
Can I copy and use the prompt directly?
Yes. Tap “Copy” on the prompt card to get the plain text — it works in other AI writing tools too.
More like this
More Support prompts- FAQGroup the questions customers ask most by topic and answer each directly with steps, so people can help themselves and repeat tickets drop.Support
- Customer support SOPStandardize the support team's workflow, response-time targets, scripts and escalation paths as the basis for onboarding, daily work and QA.Support
- Complaint reportReconstruct a complaint, verify the facts, find the root cause, document the resolution and compensation, and set trackable fixes to prevent repeats.Support
- Help center articleWalk users through one feature: prerequisites, numbered steps, how to confirm success and common errors, so they can finish the task on their own.Support
- Monthly support reportSum up the month's volume, response times, satisfaction and issue mix, explain big swings, and send recurring issues to the teams that can fix them.Support
- Support reply libraryReady-to-send replies by scenario, from pre-sale and shipping to refunds and complaints, with placeholders, next steps and phrases to avoid.Support
- Outage noticeUpdate customers during an outage on impact, progress and workarounds, then explain the cause, fixes and credits after recovery to keep their trust.Support
- Customer onboarding planPlan a new business customer's path from kickoff and setup to training and rollout, with owners on both sides, success criteria and milestones.Support
- Voice of the customer (VOC) reportPull together customer feedback from support, reviews, surveys and more, cluster it by theme and sentiment, surface the top issues and give prioritized recommendations.Support
- Customer apology letterApologize sincerely to a customer for a service failure or delivery problem: explain what happened and its impact, own it, and offer remedies and concrete fixes to rebuild trust.Support
Have an idea of your own? Start creating
Describe the image you want in one sentence, and Ofox Chat creates it from scratch.