1. Compliance posture
Если ты обслуживаешь regulated industries (Med, Legal, Edu, EU customers), compliance — gating concern, не nice-to-have.
-
HIPAA-compliant? Sign а BAA?
Почему важно: Без BAA, твоя firm assumes liability за any PHI processed by vendor.
SLAtech ответ: Yes — SLAtech Medical ships BAA-eligible single-tenant option. BAA executed перед any PHI ingest.
Как verify: Ask vendor к send sample BAA. Если он говорит "contact sales" вместо share — signal.
-
Где data хранятся? Могу я require EU residency?
Почему важно: GDPR + 2025 Schrems-III decision tightened EU-to-US transfer requirements. Non-EU vendors carry transfer-risk.
SLAtech ответ: EU residency available by default для European tenants (Франкфурт + Амстердам). US residency available для US tenants.
Как verify: Look для explicit data-center geography на /trust/ или /security/. Если page says "global cloud" без specifics — escalate.
-
Есть SOC 2 Type II или ISO 27001?
Почему важно: Annual independent audit сигналит real security investment vs marketing claims.
SLAtech ответ: SOC 2 Type II audit в процессе (closure Q3 2026). ISO 27001 timeline TBD based на EU enterprise traction.
Как verify: Ask для audit report (под NDA). "We're working on it" forever = red flag.
-
Будете удалять мои data по окончании contract? В течение скольких дней?
Почему важно: Data-retention без explicit deletion clause оставляет forever-copy твоих customer PII у vendor.
SLAtech ответ: 30-day grace period после termination, затем full deletion. Audit log of deletion provided.
Как verify: Get this в writing в MSA. "As required by applicable law" alone недостаточно.
2. Eval / quality measurement
Любой vendor может claim "powered by GPT-4" или "94% accuracy". Real signal — опубликованная, reproducible eval methodology.
-
Какую eval methodology используешь? Опубликована?
Почему важно: Vendors, не способные describe свой eval process, likely не run его regularly.
SLAtech ответ: 200-question per-vertical sealed eval harness, LLM-as-Judge scoring на factuality/hallucination/confidence axes. Methodology open-sourced.
Как verify: Ask vendor share sample eval report. Если он refuses "trade secret" — что-то скрывает.
-
Каков твой bot containment rate (% conversations resolved без human handoff)?
Почему важно: Containment rate drives ROI — 50% containment vs 80% containment = 30-percentage-point cost-of-support difference.
SLAtech ответ: 65-80% baseline в зависимости от vertical. Med 78%, Legal 73%, General-Business 72%. Tracked per-tenant в dashboard.
Как verify: Run 100-conversation trial против своего traffic. Compare vendor's claim vs reality.
-
Как часто re-run evals после model updates?
Почему важно: Vendors, не re-eval после model swaps, risk silent quality drift.
SLAtech ответ: Every model swap триггерит full eval rerun. Eval-score history published в changelog (/ru/changelog/).
Как verify: Check vendor's changelog / release notes для eval-rerun mentions. Absence = signal.
3. Multilingual + locale depth
Если ты operate в Israel, EU или anywhere outside US-English, locale depth — hidden differentiator.
-
Поддерживаешь Hebrew RTL с proper bidi rendering?
Почему важно: Hebrew RTL done badly produces garbled forms, broken date pickers, mis-aligned buttons. Most vendors auto-translate, не localise.
SLAtech ответ: Hebrew RTL first-class, bidi-aware UI primitives, date/time/currency format locale-aware. Tested на every release.
Как verify: Spin up vendor's demo в Hebrew. Send message; check renders correctly, date format dd/mm/yyyy не mm/dd.
-
Поддерживаешь Russian с native-locale phone/date/currency formatting?
Почему важно: Russian-speaking diaspora significant в Израиле, Германии, Кипре, Эстонии. English-only chatbots leak этот traffic.
SLAtech ответ: Russian first-class language, phone format +7 / +972 / EU formats auto-detected, rouble currency available.
Как verify: Set vendor's demo language на Russian, test phone-number entry. Auto-formatting? Translation от English к Russian buttons?
4. Data portability + vendor lock-in
Lock-in — common vendor strategy. Look для explicit data-portability commitments.
-
Могу я export все conversation logs в standard format?
Почему важно: Без export, switching vendors = losing all conversation history + training-signal investment.
SLAtech ответ: JSON Lines export of every conversation, 24-hour SLA на export request. No "per-export fee".
Как verify: Ask vendor демо export 100 sample conversations. Если они require "data services SOW" — lock-in red flag.
-
Могу я export свою knowledge-base / FAQ / training data?
Почему важно: Если knowledge-base locked к vendor schema, ты платишь за schema-conversion при every switch.
SLAtech ответ: Markdown export of knowledge-base, source-of-truth stored в Git repo on customer side если customer prefers.
Как verify: Ask vendor демо knowledge-base export в standard format (Markdown, JSON, CSV).
-
Будете charge me за switching off (egress fees, exit fees)?
Почему важно: Некоторые vendors hide vendor lock-in через prohibitive egress / exit fees.
SLAtech ответ: Zero egress fee. Zero exit fee. Documented в pricing page (/ru/pricing/) и в MSA.
Как verify: Get "no egress fee" в writing в MSA. "Contact sales для pricing" = signal.
5. Pricing transparency
Per-conversation pricing с hidden overage — dominant lock-in vector.
-
Pricing published on website?
Почему важно: "Contact sales для pricing" alone signals enterprise-lock-in motion. Buyers должны budget без sales call.
SLAtech ответ: Full pricing matrix на /ru/pricing/ с live API-driven numbers. No "contact sales" gate для Starter/Pro tiers.
Как verify: Check vendor's pricing page. Если не можешь get number без email-gate — это где procurement stuck.
-
Какова cost за conversation в overage?
Почему важно: Overage rate — где surprise bills hide. Некоторые vendors charge 10× base rate.
SLAtech ответ: Overage rate published per plan tier. Hard cap option available — bot stops vs unlimited overage.
Как verify: Run TCO calculator (/ru/tco-calculator/) с vendor's overage rate. Compare к base subscription.
6. Implementation timeline + ongoing support
Most enterprise chatbot deployments take 6-12 weeks с forced implementation-consultant SOW.
-
Сколько typical implementation? Consultant SOW обязателен?
Почему важно: Forced consultant SOW often costs более чем first year subscription.
SLAtech ответ: Self-serve setup за 30-45 минут для Starter/Pro. Custom Solutions tier offers white-glove (optional, не required).
Как verify: Sign up для vendor's free trial. Если setup wizard exists end-to-end, это signal of no-consultant motion.
-
Кому email для support? SLA response?
Почему важно: Tier-1 support routing к ticket queue с 72-hour first-response — common SaaS pattern. Mid-market expects faster.
Как verify: Email vendor pre-sales question. Сколько до response? Human reply или canned template?
7. Roadmap + company stability
AI vendor space — volatile. Покупка chatbot у pre-funded startup, который falls under через 18 months — risk.
-
Company profitable? Last funding round когда?
Почему важно: Pre-revenue startups burning $20M / quarter risk shutdown / acquihire vs delivering roadmap.
SLAtech ответ: Bootstrapped (без VC) — sustainable от subscription revenue с 2025. Founder Emil Slavin (see /ru/founder/).
Как verify: Check Crunchbase / PitchBook для funding history. Bootstrapped или profitable = different risk profile vs $200M Series C.
-
Какой твой public roadmap?
Почему важно: Vendors, не publish roadmap, оставляют тебя guessing будет ли feature next quarter или next year.
SLAtech ответ: Public roadmap на /ru/roadmap/ — current quarter shipping, next quarter committed, future quarter directional.
Как verify: Look для public roadmap page. "Contact sales" или "we don't publish roadmap" = signal.
