Warranty and Service Plan Tracker for Retailers

AI Prompts to Build This

Copy these build prompts into Claude, Cursor, or your AI coding tool. Create a free account to unlock the full research behind them.

1. 1. Project Setup

   Create a Next.js 14 (App Router, TypeScript, Tailwind) project called "CoverageDesk" for retailers to track warranty and service-plan coverage. Provision Supabase with these tables:
   - stores (id, name, plan TEXT default 'starter', location_count INT default 1, stripe_customer_id)
   - staff_users (id, store_id, email, role TEXT CHECK role IN ('owner','manager','staff'))
   - customers (id, store_id, name, phone, email)
   - coverage_records (id, store_id, customer_id, product_name, provider TEXT, plan_term_months INT, purchase_price_cents INT, plan_price_cents INT, starts_at DATE, expires_at DATE, receipt_number TEXT UNIQUE, status TEXT default 'active')
   - reminder_log (id, coverage_record_id, channel TEXT CHECK channel IN ('sms','email'), sent_at, template TEXT, converted BOOLEAN default false)
   
   Enable row-level security scoped to store_id on every table. Add trigram indexes on customers.phone, customers.email, and coverage_records.receipt_number for fast partial-match search. Wire Stripe with three subscription products (Starter $29, Growth $79, Multi-Location $199). Add env vars for TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, TWILIO_PHONE_NUMBER, and RESEND_API_KEY.

2. 2. Instant Coverage Lookup

   Build a /lookup page and matching API route for staff to find a customer's coverage during a live support call.
   
   Requirements:
   - Single search input accepts a phone number, email, or receipt number in any format (strip formatting before querying)
   - Query coverage_records joined to customers, matching on normalized phone, email ILIKE, or receipt_number, scoped to the logged-in staff member's store_id
   - Return results in under 300ms for stores with up to 50,000 coverage records — use the trigram indexes, avoid full table scans
   - Result card shows: product name, provider, plan term, purchase date, expiration date, status badge (Active / Expiring Soon if under 30 days / Expired), and the original receipt number
   - If no match, show a clear "no active coverage found" state with a button to log a new sale for this customer
   - Log every search to an audit table (staff_user_id, query, matched_record_id, searched_at) for accountability

3. 3. Renewal Reminder Engine

   Build the automated renewal reminder system as a Vercel Cron job that runs once daily.
   
   Logic:
   1. Query coverage_records where status = 'active' and expires_at falls in exactly 60, 30, 14, or 3 days from today
   2. For each match, check reminder_log to avoid sending the same window twice to the same record
   3. Send an SMS via Twilio using a template keyed to the window (e.g., the 30-day template offers a renewal link; the 3-day template adds urgency language) and a parallel branded email via Resend
   4. Personalize with store name, product name, and a renewal link containing a signed token tied to the coverage_record id
   5. Log every send to reminder_log with channel, template, and sent_at
   6. Build a /renewals dashboard for the store owner showing upcoming expirations grouped by window, reminders sent, and conversion rate (renewed vs. lapsed) per window, so they can see which reminder cadence is actually working
   7. Handle Twilio and Resend failures with retry-with-backoff; never let a failed send silently drop a customer from the reminder sequence