Can I vibe code Trengo?

Build a multi-tenant unified shared customer support inbox in Next.js, Supabase, and Tailwind CSS.

1. DATA MODEL:
- Organizations, Users (agents with roles: admin, agent), Contacts (name, email, phone, avatar).
- Conversations: id, organization_id, contact_id, channel ('email', 'whatsapp', 'widget'), status ('open', 'assigned', 'closed'), assigned_user_id, created_at.
- Messages: id, conversation_id, sender_type ('contact', 'agent', 'bot'), content, attachments (jsonb), metadata (jsonb for channel-specific IDs), created_at.
- Shopify Context Cache: Store customer order history linked by contact email/phone.

2. INGESTION ENGINE:
- Build HTTP POST Webhook handlers for incoming messages:
  - /api/webhooks/postmark: Parse incoming email JSON (subject, body HTML/text, attachments) and normalize into a Message record.
  - /api/webhooks/whatsapp: Parse Meta Cloud API payload, extract sender phone, message text/media, match or create Contact, insert Message.
  - Real-time updates: Use Supabase Realtime (WebSockets) to broadcast new messages instantly to connected agents.

3. AGENT INTERFACE:
- Three-column layout: Left (Filterable conversation list by status and channel), Center (Thread history, rich text composer, canned responses, internal notes toggle), Right (Contact details + Shopify integration panel showing recent orders fetched via GraphQL).
- Actions: Assign ticket, change status, send response (triggers outbound API call to Postmark or WhatsApp Cloud API depending on channel).

4. FAILURE HANDLING:
- Deduplicate incoming webhooks using provider message ID idempotency keys.
- Store failed outgoing messages in a retry queue with exponential backoff.

OUT OF SCOPE:
- VoIP calling capabilities.
- Complex automated flowbot builder (stick to static canned responses and simple assignment rules).

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