CRM Pipeline
Leads, sticky-routing, missed-call dedup, tags, sources.
Tartib closes the pilgrim journey from the first call to return from Makkah: pipeline, departure series, hotels, Nusuk visa, rituals, documents, finance — in one window. Replaces amoCRM + Excel + WhatsApp + telephony with one platform.
amoCRM has no idea what mandub or nusuk_visa is. Excel breaks at pilgrim #500. WhatsApp loses voice notes. Telephony doesn't record conversations. Conversion leaks between them.
mandub, ritual_type, nusuk_visa, accommodation_makkah / madinah, package_with_flight — first-class DB schema, not custom fields. amoCRM takes six months of customization just to get here.
BPMN-style YAML per merchant. Change your pipeline without a code release. Ajva's 9-stage pipeline is config, not development.
Asterisk → Whisper transcription → GPT sentiment / topics / action items. Daily Telegram digest to the director. Russian, Uzbek, Arabic.
Electron agent on the operator's machine: screenshots, webcam, active window, system info every 30 seconds. Neither amoCRM nor Bitrix24 reach in there.
Each module is production-ready, ships solo or bundled. Tartib is designed so an operator starts with CRM and adds the rest as it grows.
Leads, sticky-routing, missed-call dedup, tags, sources.
Mandub, Nusuk visa, accommodation, departure series, Makkah and Madinah hotels.
Call recording, AMI events, AI quality score, multi-tenant contexts.
Passports, visas, vouchers, contracts. PDF generation in any language.
Payments, agent fees, multi-currency (UZS, USD, SAR, RUB).
BPMN YAML per merchant. Change processes without a deploy.
Electron operator monitoring: screenshots, webcam, active window.
Instagram / WhatsApp leads via HMAC webhook. Auto-routing into CRM.
“One lead used to be handled in 5 places. Now — one window. We save 300 operator hours a month.”
Every plan includes Asterisk PBX, AI call analysis, and Desktop Agent. They differ by operator count, merchant slots, and SLA.
Up to 5 operators. Core CRM + PBX. Self-service onboarding.
5–20 operators. Workflow Engine + AI Call Intelligence.
20–50 operators. Desktop Agent + Daily Reports + priority support.
Multi-branch, 1h SLA, on-prem optional. COGS ~$105, margin ~96.5%.
Tartib is domain-native for Umrah: mandub, ritual_type, nusuk_visa, accommodation in Makkah / Madinah — first-class in the DB schema, not custom fields. amoCRM needs six months of customization and still doesn't cover the pilgrimage specifics (multi-tenant PBX, AI call analysis, Workflow Engine).
Base migration (contacts + deals + call history) is included in onboarding for the Business and Enterprise plans. For Lite / Pro — a separate service starting at $500 depending on data volume and source system.
Yes. Tartib integrates with any Asterisk via AMI. FreePBX, Issabel, and cloud providers (Beeline Cloud PBX, MOBI, UnicellPBX) are supported too. If you don't have a PBX — we'll stand up a multi-tenant Asterisk on our infra.
Yes. Whisper transcription works in Russian, Uzbek (Latin and Cyrillic), Arabic, English. The AI analysis (sentiment, topics, action items) and Telegram reports are available in all four languages.
Tartib is compliant with the UZ Personal Data Law No. 547-IV. A DPA for EU merchants is available on request. Hosting — isolated tenants in KSA and UZ data centers, no cross-border replication.
Base onboarding — 1 week (merchant setup, pilgrim import, pipeline config). Full adaptation to the operator's workflow — 2–4 weeks with a Customer Success manager. Operator training — 2 hours.
The Desktop Monitoring Agent works offline with a local buffer and syncs on reconnect. The pilgrim mobile app is offline-first for documents. The Asterisk PBX is independent of the Tartib server: calls keep flowing and recording.