1. Scope
2. Definitions
- Service — the hosted software, platform, or website covered by your active subscription or retainer.
- Downtime — a period during which the Service is fully unavailable to authenticated users, as measured by our monitoring, excluding the scenarios listed in Section 8.
- Incident — any unplanned event affecting the Service that requires our intervention.
- Response time — the elapsed time between receipt of a properly raised support request and our first substantive acknowledgement by a member of the team.
3. Service availability
4. Support channels
Support is available through:
- email at info@dynamiccommercegroup.com — the primary channel for all clients and the official record for SLA timing;
- any dedicated client channel we have agreed (for example, a shared workspace, ticketing portal, or on-call hotline for higher-tier engagements);
- scheduled review calls, where the engagement includes them.
Support is provided in English. Urgent incidents should be clearly flagged in the subject line; we operate on-call rotations and aim to acknowledge critical incidents around the clock.
5. Severity levels and response targets
We classify requests by severity. The targets below are response-time targets — first substantive acknowledgement — not resolution-time guarantees.
- P1 — Critical: the Service is fully unavailable or unusable for all users, or a security incident is suspected. Target response: within 1 hour, 24/7.
- P2 — High: the Service is significantly degraded, a major feature is unavailable, or a substantial group of users is affected. Target response: within 4 business hours.
- P3 — Medium: a feature is partially impaired or a workaround exists. Target response: within 1 business day.
- P4 — Low: a question, enhancement request, or minor cosmetic issue. Target response: within 3 business days.
Business hours are 09:00–18:00 Georgia time (GET, UTC+4), Monday to Friday, excluding Georgian public holidays.
6. Scheduled maintenance
7. Backups and data continuity
8. Exclusions
The following events do not count toward Downtime or breach this SLA:
- scheduled maintenance, as defined above;
- outages caused by third-party services or infrastructure outside our reasonable control (for example, upstream cloud providers, DNS, email relays, payment processors);
- outages caused by your own actions or configurations, by code or content you supplied, or by integrations you control;
- outages caused by misuse, by a denial-of-service attack directed at you, or by other unforeseeable third-party conduct;
- events of force majeure, including natural disasters, war, civil unrest, government action, or large-scale network failures;
- beta, preview, or experimental features clearly marked as such.
9. Remedies
10. Client responsibilities
To enable us to meet our targets, we ask that you:
- keep your billing current and your account in good standing;
- designate at least one technical and one business point of contact reachable during incidents;
- give us reasonable notice of unusual events that may affect demand (launches, campaigns, peak sales periods);
- use the Service in line with our Acceptable Use Policy;
- apply security and configuration recommendations we share with you.

