Home / Services / Managed services / Support agreements
Support agreements
Know who picks up, and what happens after
A support agreement puts in writing how issues are reported, how they are prioritised, who handles them and how the work is reported back to you.
- Signed agreement with service levels and priority definitions
- Onboarding review and documentation of covered systems
- Helpdesk access for your team
- Named contact and escalation path
- Incident summaries for serious issues
- Monthly service report and periodic review meetings
Proof you can check
Our own products, numbers and community record, linked wherever you can check them.
(opens in a new tab)
(opens in a new tab)
(opens in a new tab)- 300,000+sites run Divi Extended (opens in a new tab)
- Platinumsponsor, WordCamp Rajasthan 2026 (opens in a new tab)
- 6 + 1free plugins and a theme on WordPress.org (opens in a new tab)
- 4.7 / 5on Trustpilot, 116 reviews of Divi Extended (opens in a new tab)
What is included
The work, piece by piece.
Written service levels
Priority levels defined in plain terms, with agreed response and resolution targets for each, set to the importance of the system.
One ticketing channel
Issues reported through a shared helpdesk or email address, so every request has a number, an owner and a history.
Named contact
A person on our team who knows your systems, attends reviews and is the first point of escalation.
Incident handling
For serious issues, a clear process: acknowledge, contain, fix, then a written summary of the cause and what changed.
Coverage of the whole stack
Websites, customer portals, booking systems, integrations with Odoo, SAP, Zoho or Salesforce, and the hosting they run on.
Service reviews
Monthly or quarterly reviews of tickets, incidents and open risks, with recommendations for the next period.
Signs you need this
When teams usually call us.
01
The system makes money or serves customers every day
A booking portal, a store or a customer account area cannot wait for a freelancer to become available.
02
Procurement or IT has asked for an SLA
Larger organisations and government entities often require written service levels before they sign or renew.
03
Issues get fixed, but nobody knows why they happened
Incident summaries and service reviews turn repeated problems into planned fixes.
How we work
No surprises, start to finish.
Talk to the developers doing the work, by email or call, whenever you need.
01
Talk
Tell us what you need. We ask questions until the scope is clear.
02
Plan and quote
A clear scope with an hourly, fixed or monthly-hours price.
03
Build on staging
Every change is built on a staging site first, never on your live site.
04
Sign off and launch
You review and approve. Then we go live with zero downtime.
05
Care
We stay on for updates, fixes and new features, if you want us to.
Related
Often part of the same project.
- Care plansUpdates on staging, monitoring and hours
- Care plansUpdates on staging, monitoring and hours
- Website securityAudits and hardening before trouble starts
- HealthcarePatient booking, reminders and clinic operations
- Hospitality and tourismDirect bookings, guest messaging and tour sales
- Facilities managementWork orders, technicians and SLA reporting
For agencies
Your development team for WordPress, under your name.
Agencies around the world send us their builds on WordPress. We do the work, you keep the client, and our name appears nowhere.
White-label
Your brand on everything. No Elicus credit, ever.
NDA-friendly
Happy to sign yours before we see a brief.
Scale on demand
We grow the team to fit the project.
Your terms
Something specific in mind? We'll talk it through.
Questions
Before you ask.
What response times do you offer?
They depend on the systems covered and the level you choose. We agree specific targets for each priority level during scoping and write them into the agreement.
Does the agreement include development work?
It can include a monthly allowance of hours for changes and improvements. Extra hours can be bought as a pack on our care plans page or quoted as a project.
Can you support systems another company built?
Yes, after an onboarding review. We document what we find and fix urgent issues before the service levels start.
How long is the agreement?
There is an initial term agreed with you, after which the agreement can continue month to month. If you leave, we hand over access and documentation.
Start a project
Tell us what you’re building.
A few lines is enough. The developers who will do the work read every message.
