Remote, without an office
We have no office in Almaty, so this page gives no address; to reach us, use WhatsApp or e-mail (the Contacts page).
More detail
We work on Kazakhstan time (Asia/Almaty), write and meet in Russian and Kazakh, and deploy and train remotely; a meeting at your site can be agreed as a separate clause of the contract. There is no public sign-up: access is by invitation.
The site and the website chat work in Russian, Kazakh and English. The panel is in Russian today: Kazakh and English are prepared for the next release, some sections such as the request queue are still Russian-only, and a native speaker is still checking the Kazakh translation.
Who it suits in Almaty
Every case runs on the shared modules; what is industry-specific is on each scenario page.
- Clinics and dental practices: patient requests, consents, a journal of record reads.
- Agencies and studios: projects, deadlines, invoices, approvals.
- Retail and service companies: requests, a queue, time to first reply.
- Training centres and schools: parents’ questions from the confirmed knowledge base.
- Sales teams with several channels: leads, deals by stage, tasks with deadlines.
Questions
Where will our data be stored?
Data residency is a declared decision, not a default: region, jurisdiction, who confirmed it and when are four separate values, none of them preset. Until it is declared, both routes out — an external copy of the database and the mail transport — are blocked at start-up; a deployment that sends nothing out works without it.
Does the product confirm that our setup is lawful?
No. Its “legally reviewed” field is always false: that is a decision for the owner and their lawyer, not a conclusion of a program.
Basis: the data processing rules; the list of product limitations; the site content map. This page describes what exists in this build, not what is planned.