Can I vibe code Casengo?

Build a production-ready omnichannel customer support desk app using Next.js App Router, Tailwind CSS, Supabase, and Server Actions.

1. DATA MODEL & ARCHITECTURE
Set up Supabase tables with Row Level Security:
- `customers`: id (uuid), email (string, unique), phone (string), name (string), metadata (jsonb).
- `conversations`: id (uuid), customer_id (fk), channel (enum: 'email', 'live_chat', 'whatsapp'), status (enum: 'open', 'pending', 'closed'), assigned_agent_id (uuid), priority (enum: 'low', 'medium', 'high'), created_at, updated_at.
- `messages`: id (uuid), conversation_id (fk), sender_type (enum: 'customer', 'agent', 'system'), sender_id (string), content (text), content_type (enum: 'text', 'html', 'media'), external_message_id (string), created_at.
- `canned_responses`: id (uuid), shortcut (string), content (text).

2. CORE UI & DASHBOARD
Construct a 3-column split view interface:
- Left Column: Filterable ticket queue (All, Unassigned, Mine, Closed) with live search and channel badge icons.
- Center Column: Threaded conversation view with real-time updates via Supabase Realtime (`postgres_changes` on `messages`). Include rich text editor, canned response dropdown insertion triggered by typing `/`, customer-visible vs. internal staff notes, and assignment dropdown.
- Right Column: Customer context drawer displaying lifetime value, past orders (via Shopify GraphQL mock integration), and direct metadata editor.

3. WEBHOOKS & CHANNEL HANDLERS
- Implement `/api/webhooks/whatsapp` to ingest Meta WhatsApp Cloud API webhooks. Parse incoming text and media payload into `messages` table. Add send endpoint handling Meta's 24-hour conversation window rule.
- Implement `/api/webhooks/email` to ingest incoming email JSON payloads from Postmark/SendGrid. Thread emails using `In-Reply-To` and `References` headers.
- Build a lightweight, embeddable JavaScript chat widget script (`public/widget.js`) that establishes a socket connection to `/api/chat/socket` for website visitors.

4. EDGE CASES & FAILURE HANDLING
- Implement agent collision detection: broadcast active agent viewing state via Supabase Presence so two agents don't type responses simultaneously.
- Sanitize raw HTML email contents using DOMPurify before rendering to protect against XSS.
- Gracefully handle API failures on outgoing WhatsApp/Email webhooks by retrying up to 3 times with exponential backoff and recording failure state in the message record.

$ each button prefixes agent-specific run instructions · build your own product, never copy proprietary code, trademarks or designs