Can I vibe code Kayako?

Build a multi-channel support ticketing platform for an ecommerce store using Next.js App Router, Supabase Postgres, and Tailwind CSS.

1. DATA MODEL:
- Schema: customers (id, email, name, shopify_customer_id), tickets (id, ticket_number, customer_id, status: open/pending/closed, priority: low/medium/high, assigned_agent_id, subject, created_at, updated_at), ticket_messages (id, ticket_id, sender_type: customer/agent/system, body_text, body_html, message_id_header, created_at), macros (id, title, payload_text).
- Implement Row Level Security: agents can read/write all tickets; customers can only access their own via auth.

2. INBOUND & OUTBOUND EMAIL:
- Create an API route `/api/webhooks/inbound-email` accepting incoming JSON from Postmark/Resend inbound parsing.
- Extract `In-Reply-To` and `References` headers to match incoming messages to existing tickets. If no match exists, create a new ticket.
- Strip previous email quote tails from incoming body text using common delimiting regex.
- Route outbound agent messages through Resend API using standard custom `Message-ID` headers to preserve threading.

3. SHOPIFY INTEGRATION & CONTEXT SIDEBAR:
- Build a sidebar inside the agent ticket view that queries Shopify Admin GraphQL API using the customer's email.
- Fetch and display the last 5 orders, order statuses, tracking numbers, total spend, and refund buttons.

4. REALTIME & AGENT COLLISION:
- Use Supabase Realtime to push new messages to the active ticket view without page refresh.
- Track active agent presence on a ticket using Supabase Presence. Display an alert badge: 'Agent X is currently viewing this ticket' if another user is present.

5. FAILURE MODES & OUT OF SCOPE:
- Handle email parse failures by logging raw payloads to a dead-letter table with retry mechanisms.
- Out of scope: Voice/telephony integrations, complex mobile apps, native mobile SDKs.

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