Most companies discover how their 1C support really works at the worst possible moment: an exchange stops, a month won't close, "the programmer is on vacation". Here is how support looks when it works.

A 1C consultant answers questions and trains users; a business analyst handles processes and settings; a developer and an architect take code and complex technical cases. A team lead assigned to your company orchestrates it all.
Requests are accepted in a Telegram chat — first response within 15 minutes, working hours 1:00–23:30 CET. Every request becomes a task: confirmation, estimate, deadline, status.
You see the live status of all tasks and the hours spent, any time. Honest statuses: "postponed" never masquerades as "done". Estimates over 40 hours are agreed in advance.
We build an AI knowledge base of your IT system: documentation, settings, decisions, meeting notes. If a specialist changes, the next one enters context in hours, not months.
1C rarely lives alone: banks, e-invoicing, warehouses, online stores. We take responsibility for the system as a whole — when our recommendations are followed, it simply works.
All custom development is done through extensions, so your configuration keeps receiving vendor updates. Updates are tested on a copy before they touch the working base.
Accounting closes on time, exchanges run, users get answers instead of queueing behind one overloaded admin. Fewer fires every month — that is the main quality metric of support.
You stop being the dispatcher between the accountant and the programmer. Reports and dashboards arrive in Telegram; decisions are based on numbers, not on gut feeling.
Yes. Support scales from a few hours per month. You pay for actual time spent, with a transparent log of every task.
That is our usual starting point. We begin with an AI diagnostic: it maps all customizations and shows what can be simplified, standardized, or must stay custom.
Of course. We handle the 1C side — configuration, exchanges, fixes — and cooperate with your accountant on local compliance requirements.
English and Serbian for communication and documentation — whatever your team is comfortable with.
Tell us what hurts — we will honestly say whether we can help, and show how everything works on a live example.
© iTeal · 1C:Enterprise support and implementation in Europe · Belgrade, Serbia