Stein-cv

πŸ›οΈ Enterprise Systems Architecture Dossier

Document ID: ARCH-MASTER-2026
Lead Systems Architect & Author: Steinley Goh
Scope: Full-Stack Operational Infrastructure, Multi-Dealer Messaging Flow, Database Integrity, Hardware Telemetry


πŸ“‘ Document Control & Overview

This technical manual outlines the rigorous logic, state machines, and API integration flows designed to transition regional marketing and customer relationship operations from highly manual legacy dependencies into autonomous, scalable infrastructures.


⚑ Module 1: Multi-Dealer WhatsApp Distribution Engine (TRD-101)

1.1 Gateway Topography

Interconnected the Official Yadea WhatsApp Business API (Meta Cloud) with the Mekari Qontak messaging core. Webhooks parse asynchronous user communication JSON payloads to extract conversation triggers automatically.

1.2 Geographic Intent & Chatbot Screening

Incoming traffic flows through an automated conversational pre-screening node to capture location coordinates and operational variables.

1.3 Competition Mode State Machine (β€œFirst-to-Respond”)

To enforce rapid response SLAs and prevent sales personnel from cherry-picking leads, a thread-safe Competition Mode distribution protocol executes via atomic DB checks:

[ Incoming Lead Message Payload ]
               β”‚
               β–Ό
   [ DB State Set: UNCLAIMED ] ───► [ Broadcast Interactive Push to Reps A, B, C ]
               β”‚
               β–Ό
[ Intercept Rep Button Tap Callback ]
               β”‚
               β”œβ”€β–Ί If State == UNCLAIMED:
               β”‚        β”‚
               β”‚        β”œβ”€β–Ί Execute DB Update: State = CLAIMED (Lock Acquired)
               β”‚        β”œβ”€β–Ί Route Full Customer Context to Winning Rep
               β”‚        └─► Append Handoff Timestamp to CRM Ledger
               β”‚
               └─► If State == CLAIMED:
                        β”‚
                        └─► Fire Async Webhook: Send "❌ Too Slow" Interface Notice

πŸ›‘οΈ Module 2: CRM Integrity, Fraud Prevention & Alert Tiering (BRD-201)

2.1 Asynchronous Data Validation

Operating concurrently across 110+ individual dealer portals, internal triggers actively enforce compliance to protect unit margin economics:

2.2 Alert Tiering Framework

To prevent notification blindness among executive staff, message bus traffic is categorized into three strict tiers:

  1. P0 (Critical): Dispatched natively via WhatsApp push alerts directly to regional management for immediate SLA bottlenecks.
  2. P1 (Warning): Surfaced dynamically within the custom administrative web interface to track recurring serial anomalies.
  3. P2 (Info): Aggregated asynchronously into daily formatted Markdown/HTML email recaps outlining regional conversion health.

πŸ“Š Module 3: Unit Economics Analytics Engine (ROI-301)

3.1 Visual Analytics Core

Configured customized visual interface matrices inside Feishu Base and Google Looker Studio built upon an absolute mathematical proof linking operational burn directly to unit-level customer acquisition momentum.

3.2 The 10-Variable Dynamic Ledger

The analytical model ingests, computes, and charts 10 core operational vectors alongside multi-channel performance comparisons (benchmarking TikTok performance, Google Search volume, and unassigned physical walk-ins):

  1. Total Event Spend: Overall capital outlay deployed per localized marketing initiative.
  2. Dealer Support Cost: Internal subsidies allocated from headquarters to sustain regional operations.
  3. Baseline Dealer Cost: Fixed infrastructural maintenance mapping to specific partner nodes.
  4. Out-of-Pocket Dealer Spend: Unsubsidized capital deployed independently by regional dealers.
  5. Average Cost per Activity: Efficiency metric comparing overall spend against isolated event footprints.
  6. Average Cost per Day: Dynamic burn rate calculated across ongoing active operational pushes.
  7. Cost-Per-Lead (CPL) Trends: Granular tracking mapping absolute monthly CPL metrics alongside interactive daily trendline distributions.
  8. Total Activity Volume: Cumulative count of strategic events launched.
  9. Active Duration Days: Combined temporal operational footprint measured in campaign lifecycles.
  10. Verified Sell-Through Outcomes: Absolute monthly lead generation outputs cross-audited against finalized vehicle purchase registrations.

πŸ”— Module 4: Hardware Telemetry Integration Architecture (IoT-401)

4.1 Native Figma Layout Blueprint

Designed the comprehensive 12-24 Month System Architecture Roadmap natively inside Figma (including highly specialized vendor alignment interface views crafted For mekari To view) to standardize communication flows between software CRM entities and smart hardware units.

[ Finalized Hardware Point-of-Sale ]
                β”‚
                β–Ό
  [ Trigger Embedded IoT Telemetry ]
                β”‚
                β–Ό
   [ Dispatch Async API Handshake ]
                β”‚
                β–Ό
  [ Update Central Hub Ledger State ]

4.2 Execution Protocols


πŸ“ Module 5: Standalone System Components

For immediate production deployment, refer directly to companion operational repositories: