PertoDaqui AI & Messaging • Technical Demo

Omnichannel Infrastructure

WhatsApp Business bridge with bookings, admin commands and human handoff

› Screenshots

3 planned
Mock conversation demonstrating human operator handoff and automated response flows.

Mock conversation demonstrating human operator handoff and automated response flows.

PREVIEW
#01

Mock WhatsApp command conversation.

· coming soon ·
#02

Inbox/handoff state with fake data.

· coming soon ·

› Technical Stack

REST API Webhooks Admin Commands Human Handoff

› Architecture Pipeline

WhatsApp Webhook →Booking / Router →AI Processing →Human Handoff →Inbox API

› The Problem

For many local businesses WhatsApp is the real operating channel. Automation must coexist with bookings, admin updates, media, inbox visibility and human takeover.

› What I Built

I built a WhatsApp Business bridge for PertoDaqui using webhooks, Hono/TypeScript APIs, booking-first routing, admin commands, inbox endpoints and human handoff state.

› Core Capabilities

  • Webhook handling for messages, buttons and list replies.
  • Booking router before general assistant logic.
  • Verified admin commands for daily business updates.
  • Human handoff that silences automation when staff takes over.
  • Inbox API for dashboard visibility and manual replies.

› Technical Decisions

01

Treat commands as operational updates, not casual chat.

02

Verify admin identity before accepting content changes.

03

Persist handoff state so the bot does not fight the human operator.

04

Design media workflows for menus, services and accommodation-style updates.

› What This Demonstrates

Webhook integration, messaging automation, admin command design, handoff logic and real operational constraints around WhatsApp.

› Limitations & Next Steps

  • Harden webhook retries under peak traffic.
  • Add voice-note transcription into the messaging flow.