1. Identification and purpose
Zyntello, S.R.L., a company incorporated in the Dominican Republic, provides the support service described in this document to every Subscriber with an active subscription to the app.zyntello.com platform.
Support contact: soporte@zyntello.com · WhatsApp +1 829 639 9877 · Administration: info@zyntello.com.
2. Definitions
- Incident: any support request the Subscriber reports.
- First response: the moment a person at Zyntello replies to the incident with a diagnosis, a specific question or a solution. It is not the automatic acknowledgement of receipt.
- Business hour: an hour elapsed within the service hours in section 4. An incident reported on a Friday at 17:00 with a 4 business hour commitment is answered by Monday at 11:00 at the latest.
- Resolution time: how long it takes to close the incident. It depends on its nature and is not committed in this SLA; what is committed is the first response.
3. Support channels
Support is requested through any of these channels:
| Channel | How | What it is best for |
|---|---|---|
| soporte@zyntello.com | Main channel. It leaves a written record of the whole case and allows screenshots and files to be attached. Your email goes straight into the case: if you reply to a message of ours, your reply is added to the same case, and if you write for the first time a new one is opened. | |
| +1 829 639 9877 | Short queries and urgent notices. Any case needing follow-up is moved to email. | |
| Web form | zyntello.com | When you do not yet have access to the platform or to the registered email address. |
4. Service hours
Monday to Friday, 8:00 to 18:00, Dominican Republic time (GMT-4), except Dominican national public holidays.
Outside those hours incidents can still be reported through any channel: they are logged and their response time starts counting at the beginning of the next business day.
5. Priority classification
The priority is assigned by Zyntello according to the actual impact on the Subscriber's operation, not according to how urgently it is reported. If the Subscriber disagrees with the classification, they may ask for it to be reviewed, stating the specific impact.
| Priority | What it means | Examples |
|---|---|---|
| Critical | The platform is unavailable, or a contracted module is unusable for the whole company and there is no alternative. | Cannot sign in · Cannot invoice · A whole module returns an error |
| High | An important function fails or produces incorrect data, but there is a way to keep operating. | A report shows figures that do not add up · A document cannot be voided |
| Normal | A secondary function fails, or there is a question about use or configuration. | How to set up a numbering sequence · A filter does not apply as expected |
| Low | Suggestions, improvements and queries that do not affect the operation. | A request for a new column in a list · A query about a future feature |
6. First response times
| Priority | First response |
|---|---|
| Critical | 4 business hours |
| High | 8 business hours |
| Normal | 1 business day |
| Low | 3 business days |
The clock starts when the incident arrives through one of the channels in section 3, within the hours in section 4.
7. What support includes
At no additional cost, within the active subscription:
- Correcting platform defects. If something does not work as documented, fixing it is our obligation and is never billed.
- Usage questions about the contracted modules.
- Configuration of the contracted modules: numbering sequences, chart of accounts, taxes, permissions and parameters.
- Access incidents: password recovery, two-step verification and locked users.
- Guidance on how to get the most out of an existing feature.
7.1. The artificial intelligence help assistant
Inside the platform there is an assistant that answers usage questions based on Zyntello's documentation. It is meant to settle the most frequent questions on the spot, without waiting for an agent to reply.
- It answers only on the basis of our documentation. When the documentation does not cover the question, it says so and offers to open a case rather than improvising an answer. We prefer not answering to answering badly: an invented instruction about an administrative system can make you lose data.
- It performs no actions. It explains how to do things; it does not do them for you nor change your information.
- It has a usage quota included in the subscription, with a per-user, per-day limit so that one person cannot exhaust everyone else's.
8. Support access to the account
Some incidents cannot be diagnosed from outside: a journal entry that does not balance, a document that will not issue, a permission that has no effect. To resolve them, a support agent may need to enter the Subscriber's workspace and see their data. This section states the limits under which that happens and —above all— how the Subscriber checks it for themselves.
8.1. How the agent signs in
- Never with the credentials of a person at the Subscriber. We neither ask for nor use the username or password of anyone on your team. The agent signs in with a Zyntello technical account, separate from yours.
- Every action is signed with the name of the actual agent, not that of the technical account nor that of a Subscriber's user. The log shows who did what.
- The technical account uses none of the licences included in your plan (see section 9) and does not appear in your user list or in the system's dropdowns.
- The agent must have verified their identity in two steps in order to open the access.
8.2. Read-only by default
The access starts read-only: the agent can see, but the system prevents them saving any change. To change anything they must elevate the session by stating a reason, and that elevation expires on its own — it does not stay open indefinitely even if the agent forgets to close it.
8.3. What is recorded
For each access we store the agent, the date and time of entry and exit, the stated reason, the IP address and whether the access was authorised or was an emergency. If the session was elevated to write, the detail of every piece of data changed is recorded as well.
8.4. Emergency access
When the incident makes waiting for prior authorisation impossible —a lockout that leaves the Subscriber unable to operate, for instance— the agent may sign in by stating the reason. That access is flagged as unauthorised and the account owner receives a notice. It is not a silent permission: it is an access that is declared and that shows.
8.5. How you audit it
8.6. What we do not do
- We do not access your data for commercial, statistical or artificial intelligence model training purposes.
- We do not extract copies of your information beyond what is needed to resolve the incident.
- We do not use support access for business operations on the Subscriber's behalf: if data needs to be captured or corrected in bulk, that is billable work and is quoted separately (see section 10).
8.7. The case portal
Any user of the Subscriber can open a case from Support in their own system, without special permissions: whoever runs into the problem is best placed to describe it. Each case receives a number (SOP-000123) by which it is tracked through any of the three channels.
- The Subscriber sees the whole thread of their case and can reply and attach files at any time.
- While we are waiting for a reply from you, the case is marked as such and that time does not count against the periods in section 6: it would mean charging Zyntello with a delay that is not its own.
- A case is only marked as billable if the Subscriber authorises it before the work begins (section 10). Reporting a platform defect never costs anything.
9. What is not included and what is billed
The following work is quoted and billed separately, and none of it is carried out without the Subscriber's prior written approval:
- Importing or bulk loading data from another system.
- Training the Subscriber's staff.
- Custom reports other than those the platform already offers.
- Development or adaptations specific to the Subscriber.
- Restoring backups for reasons unrelated to the platform.
- Correcting data where the error was not caused by the platform.
10. Included user licences
Each subscription includes two classes of access, described in detail in section 5.3 of the Terms:
| Class | Included | Scope |
|---|---|---|
| Subscriber users | 3 per account (including the owner) |
They reach every company in the account, with the permissions of their role: Administrator, Transactions, Read-only or Reports. |
| Internal users | 5 per account | Each one is assigned to a single company; their permissions, configurable module by module, reach that company alone. |
Both allowances can be increased by writing to info@zyntello.com; the increase is billed at the current rate. A deactivated user still occupies their licence until they are removed from the account. The technical accounts Zyntello uses to provide support do not consume the Subscriber's licences.
11. Service availability
Zyntello seeks the highest possible availability of the platform and performs periodic backups with integrity verification, in accordance with section 18 of the Terms.
Scheduled maintenance windows are announced at least 24 hours in advance by email, and are arranged outside service hours where possible.
12. Exclusions and limits
This SLA does not cover:
- Failures of the Subscriber's internet connection, equipment or network.
- Interruptions caused by third-party services outside Zyntello: payment gateways, email providers, tax authorities or messaging services.
- Use of the platform contrary to the Terms.
- The consequences of data uploaded incorrectly by the Subscriber or their users.
- Modules that have not been contracted.
- The demonstration account, whose data is deleted daily.
- The force majeure events provided for in the Terms.
13. Change log
A complete, cumulative record of every version of this document since it was first published. Earlier versions are available on request by writing to info@zyntello.com.
| Version | Date | Changes |
|---|---|---|
| 1.4 In force | 9 September 2026 | The artificial intelligence help assistant. Section 7.1 is added, declaring a new feature included in the subscription: an assistant that answers usage questions from Zyntello's documentation and that, when the documentation does not cover the question, says so and offers to open a case rather than improvising — we prefer not answering to answering badly, because an invented instruction about an administrative system can cause data loss. It states that it performs no actions, that it has a usage quota with a per-user, per-day limit, and above all that exhausting it does NOT leave the Subscriber without support: email and cases remain included just the same, because reporting a problem with the system cannot depend on a quota. It also states that no tier is marketed as “unlimited” —the top tier states its cap in writing— and that an answer that did not help does not consume quota. The channels, hours, priorities, committed first response times, included licences and availability target are unchanged. |
| 1.3 | 9 September 2026 | Email goes straight into the case. Section 3 declares that a message sent to soporte@zyntello.com is added automatically to the case —a reply to an email of ours is added to the same case; a new email opens one—, and section 6 declares that this process runs every fifteen minutes, so up to 15 minutes may pass between the Subscriber sending and it being logged. It also declares, and this is what matters, that that time is not deducted from the first response periods: the clock runs from when the Subscriber sends, not from when our system processes it —that would charge the Subscriber with a delay of ours—. The channels, hours, priority classification, committed first response times, included licences and availability target are unchanged. |
| 1.2 | 7 September 2026 | The case portal. Section 8.7 is added: any user of the Subscriber opens a case from their own system, without special permissions; each case receives a number by which it is tracked across the three channels; the Subscriber sees the whole thread and can reply and attach files. It also declares that the time a case spends waiting for the Subscriber's reply does not count against the first response periods in section 6 —it would charge Zyntello with a delay that is not its own— and refers to section 10 for the prior authorisation of billable work. The channels, hours, priorities, committed times and included licences are unchanged. |
| 1.1 | 6 September 2026 | Support access to the account. Section 8 is added, declaring an operation the previous version did not cover: to diagnose certain incidents, a support agent may need to enter the Subscriber's workspace and see their data. The limits are declared —the agent never uses the credentials of a person at the Subscriber but a technical account that consumes no licences and does not appear in their lists; the access starts read-only and elevating it requires stating a reason and expires on its own; the agent, the date, the reason, the IP and the detail of what was changed are recorded; an access without prior authorisation is flagged as such and notifies the owner— and, above all, that the Subscriber audits it themselves from Settings → Support access, without asking. It also declares what we do NOT do: no commercial, statistical or model-training purposes, and no business operations on the Subscriber's behalf —that is billable work under section 10—. The previous sections 8 to 12 are renumbered 9 to 13; their content is unchanged. The channels, hours, priority classification, committed first response times, included licences and availability target are unchanged. |
| 1.0 | 5 September 2026 | First publication. Initial document with 12 sections: identification and purpose, definitions, support channels, service hours, priority classification in four levels, committed first response times, scope of included support, billable work with mandatory prior approval, included user licences (3 Subscriber users and 5 internal users), service availability —whose 99.5 % target is set by the Terms, not by this document—, exclusions and the change log. |