01
Reduce no-show rate by 30-50%
Applicable to: Med, Beauty, Hospitality, Fitness, Event
Configure tiered reminder cadence: T-1 week (calendar add), T-24 hours (confirm question), T-2 hours (final reminder with rebook link). Channel matters - WhatsApp reminders outperform email by 3-5×. SLAtech ships a pre-configured reminder template; tune cadence to your industry. Beauty tenants see best results adding a 4-hour reminder with stylist's name personalised. Event venues see best results adding a T-week-of run-sheet reminder.
02
Multilingual launch playbook
Applicable to: All verticals with customers in more than one language
Decide which language each answer should be in: automatic - the language of the question - suits a mixed audience, a fixed language suits a single-language one. Make sure every page declares its language with <html lang>, because both the widget and the choice of sources read it. Write the welcome message once; it is translated into Hebrew and Russian automatically. There is no need to translate the site first: answers are written from your content in the language of the question. English, Hebrew and Russian are built in; additional languages are available on request.
03
Compliance-first launch playbook
Applicable to: Med, Legal, regulated industries
Execute compliance posture BEFORE first conversation: (1) sign DPA / BAA per industry. (2) enable PII protection on sensitive document uploads. (3) configure UPL safeguard rules in Legal. (4) document data-retention policy. (5) train staff on the human-handoff escalation pattern. (6) test compliance-relevant queries against sealed test set. (7) document audit-trail access procedure. Launch only after all 7 are confirmed.
04
Vertical-graduation path
Applicable to: Generic Business → Med / Edu / Hospitality / Sales / Legal / Beauty / Fitness / Event
SLAtech AI Business surfaces a "graduate to [vertical]" recommendation when admin Inbox detects >60% of conversations match a single vertical's intent profile. Decision rule: graduate if your traffic mix is >80% a single vertical AND volume justifies the vertical's monthly fee. Stay on Business if mixed coworking / training-centre profile or if compliance is light. Migration is single-click - knowledge corpus and conversation history carry across.
05
Lead-scoring optimisation
Applicable to: Sales, Business, Hospitality
Configure a 4-axis lead score: (a) ICP fit (company size, industry match) → 25 points. (b) BANT depth (captured budget, authority, need, timeline) → 30 points. (c) Engagement intensity (page visits, conversation length) → 25 points. (d) Channel quality (organic-search > paid > social) → 20 points. Total 100. Route 80+ to senior reps, 50-79 to nurture, <50 to auto-FAQ. Tune thresholds quarterly based on close-rate analytics.
06
Direct-booking conversion lift
Applicable to: Hospitality
Bot's job is to make direct booking obviously better than OTA booking. Surface 3 specific perks to direct bookers consistently: (a) free breakfast (or upgrade-class equivalent). (b) flexible cancellation (24-hour vs OTA's 7-day). (c) early-check-in / late-check-out priority. Mention all 3 in the first booking interaction. Median direct-booking lift: 20-35% within 90 days.
07
Multi-channel handoff
Applicable to: Beauty, Sales, Hospitality, Event
A customer may start in one channel (WhatsApp, say) and come back on the website later. Each channel keeps its own conversation history - SLAtech does not merge one person across channels. On the website, a returning visitor is recognised from their own earlier widget conversations, so the assistant does not start from nothing. Configure handoff thresholds: complex queries (>5 turns without resolution) escalate to human inbox automatically; simple queries (price, hours) stay bot-resolved.
08
First-week activation
Applicable to: All verticals - for new SLAtech tenants
Day 1: install widget on production. Day 2: upload 20+ source documents (FAQ, pricing, hours, contact). Day 3: run 10 internal test conversations covering top traffic patterns. Day 4: connect Telegram and WhatsApp Business if you use them. Day 5: configure the lead webhook (to your own endpoint, or through Zapier / Make into HubSpot, Salesforce or Pipedrive). Day 6: configure calendar sync if booking workflow. Day 7: enable bot live on production.
09
Cross-CRM integration
Applicable to: Sales, Business - any tenant with CRM
On the Pro tier and above, point SLAtech's lead webhook (the new_lead event) at your own endpoint, or at a Zapier or Make hook that creates the record in HubSpot, Salesforce or Pipedrive. There are no native CRM connectors: SLAtech sends the lead and does not read from or update your CRM. The payload is JSON - event, timestamp, site_id, site_domain and lead (name, email, phone, question, page, language) - with an optional HMAC-SHA256 signature to verify. Test with a sample lead before enabling live. Failed deliveries are retried automatically, up to 3 attempts with backoff.
10
Disaster-recovery runbook (per RPO 1h / RTO 4h targets)
Applicable to: All verticals - production-critical deployments
Quarterly DR test cadence: (1) trigger simulated region failure in staging. (2) verify failover to secondary region within 4 hours. (3) validate data integrity (compare last-hour conversations). (4) test admin recovery (login, audit log, knowledge re-upload if needed). (5) document any deviation from target. Real-incident triggers: contact emergency@slatech.ai with tenant ID, expected impact, time window. SLA-backed Enterprise tenants get hands-on assistance.
