Skip to main content

Multi-Channel Orchestration

Skeep is built on the philosophy that channels (WhatsApp, Dashboard, Mobile Apps) should only act as thin veneers over a unified API core.

Principle: Channel Disruption​

Channels do NOT get custom logic.

Whether a request comes through the WhatsApp bot or the Skeep Express API, they are processed by the same Core Logistics engine using the same validation, pricing, and dispatch rules.

1. WhatsApp Integration​

The Skeep WhatsApp bot serves as a conversational interface for many of our users. It orchestrates complex flows by calling several APIs in sequence:

  • Quote API: To provide instant price feedback.
  • Create Delivery API: To commit orders.
  • Status & Tracking APIs: To send automated push updates to the user.

2. Skeep Dashboard​

The Vendor and Admin dashboards are comprehensive visual tools for managing large-scale operations. They consume:

  • Vendor Analytics APIs: For reporting.
  • Order Orchestration APIs: For manual dispatch and oversight.
  • Settlement APIs: For financial management.

3. Internal Products (Food & Commerce)​

Skeep's own food delivery and e-commerce platforms are "Customer Zero" for our API surface. They leverage:

  • Vendor APIs: For deep operational integration.
  • Core Logistics: For seamless fulfillment.

Technical Implications​

  1. Single Source of Truth: Data remains consistent across all interfaces.
  2. Permission Guarding: While the APIs are shared, permissions are scoped via the Authentication layer.
  3. API-First Development: Every new feature is built as an API endpoint before it is added to any channel.