mirror of
https://github.com/x1xhlol/system-prompts-and-models-of-ai-tools.git
synced 2026-06-18 23:39:34 +00:00
Phase 1-6 implementation for Dealix AI Revenue OS: - AI Arabic Engine: NLP (arabic_nlp.py), lead scoring (lead_scoring.py) - PDPL Compliance: consent manager, data rights handler, consent model - Sequence Engine: multi-channel sequences with WhatsApp/Email/SMS - CPQ System: quote engine, AI proposal generator - Security Gate: pre-release checks, PDPL message validation - Tool Verification: agent action audit trail - Project Operating Files: AGENTS.md, CLAUDE.md - Project Memory: architecture, ADRs, provider routing, PDPL checklist - Design System: IBM Plex Sans Arabic tokens, RTL-safe components - Sequence/Consent models for database https://claude.ai/code/session_01LsnvBa7HwF5hs99VZbgLGj
1.1 KiB
1.1 KiB
ADR-002: WhatsApp as Primary Communication Channel
Status: accepted Date: 2026-03-28 Decision: Build WhatsApp as a first-class CRM channel, not a third-party add-on
Context
WhatsApp has 85%+ penetration in Saudi Arabia (30M+ users). It is THE primary business communication channel. Competitors (Salesforce, HubSpot) treat WhatsApp as a third-party integration.
Decision
WhatsApp Business API is integrated directly into the core platform:
- Inbound webhooks create/update leads automatically
- AI chatbot handles initial qualification in Arabic
- Unified inbox merges WhatsApp with Email and SMS
- Sequences support WhatsApp as a step type
- Proposals can be sent and tracked via WhatsApp
Rationale
- 85%+ of Saudi business communication happens on WhatsApp
- No global CRM treats WhatsApp as the primary channel
- This is Dealix's strongest competitive moat in KSA
- Close.com proved that building communication natively wins vs third-party
Consequences
- Must maintain Meta Business API compliance
- Template messages need pre-approval from Meta
- 24-hour messaging window rules apply
- PDPL consent must be checked before every message