aaron

Smart call on the 0-Inbox and seven-folder cap — that’s the right constraint. Let’s level this up with a repeatable, three-pass pipeline that cleans titles and URLs, classifies with rules, and produces an import-ready bookmarks file. Fewer decisions, faster retrieval, clear metrics.

Why this works: messy titles and tracking-heavy URLs are what make AI misclassify. Normalize first, then classify. Finally, generate a clean import so you don’t drag-and-drop forever.

What you’ll need

• Your exported bookmarks HTML (backup).
• An AI assistant.
• Optional: a simple spreadsheet for quick scanning.

The three-pass pipeline (outcome-focused)

1. Sanitize titles and URLs (reduces errors by 30–50%)
   1. Feed AI your list as Title,URL pairs.
   2. Have it standardize titles to “Site — Page,” strip emojis and fluff, and remove tracking parameters (utm_*, gclid, fbclid, ref, source, share).
   3. Output CSV with clean titles and URLs, plus a simple duplicate hint based on domain + path.
2. Classify with a rule deck (push 75–90% auto-file)
   1. Provide your fixed folders and a short Rule Deck. Add your own company/client domains so Work is unambiguous.
   2. Return Category, Confidence, Reason. Anything Low goes to Review.
3. Build an import-ready bookmarks HTML
   1. Ask AI to output a Netscape-format bookmarks file with your folders in numeric order. Test-import 20 items, then run the full set.

Copy-paste prompts (use as-is)

Pass 1 — Sanitizer

“You are my bookmark sanitizer. I will paste CSV rows with columns Title,URL. For each row: 1) Normalize Title to the format ‘Site — Page’ (remove emojis and extra separators, keep under 80 chars). 2) Clean URL by removing tracking parameters (utm_*, gclid, fbclid, ref, source, share, s, pronoun, igshid, t). Preserve the canonical path and query needed for the page to work. 3) Emit CSV with columns: TitleClean,URLClean,Domain,Slug,Fingerprint,DuplicateHint. Set Domain from the host, Slug from the path (no query), Fingerprint = lower(Domain + Slug). DuplicateHint = Yes if Fingerprint repeats within the batch; otherwise No. Output CSV only, no commentary.”

Pass 2 — Classifier

“You are my bookmark classifier. Input columns: TitleClean,URLClean. Use ONLY these folders: Work, Personal, Read Later, Finance, Tools, Learning, Travel, Review. Apply rules: Work if URL host matches any in WorkDomains OR the title contains project/client terms; Personal for shopping, personal email, hobbies; Read Later for articles/opinion/essays; Finance for banking/investing/tax; Tools for apps/utilities/dashboards/docs/AI tools; Learning for tutorials/courses/how-tos; Travel for flights/hotels/itineraries. If unsure, set Category = Review. Emit CSV with columns: TitleClean,URLClean,Category,Confidence(High/Med/Low),Reason. Use these lists to guide decisions (edit before running): WorkDomains=yourcompany.com;client1.com;client2.com — PersonalDomains=gmail.com;outlook.com;amazon.com — FinanceKeywords=bank,invoice,tax,401k,brokerage,statements — ToolHosts=notion.so,trello.com,slack.com,openai.com,docs.google.com — LearningKeywords=tutorial,course,how to,guide — TravelKeywords=flight,hotel,itinerary,booking. Output CSV only.”

Pass 3 — Import file builder

“You are my bookmarks HTML builder. Input CSV columns: TitleClean,URLClean,Category. Generate a valid Netscape bookmarks HTML with top-level folders in this order: 0-Inbox, 1-Work, 2-Read Later, 3-Finance, 4-Tools, 5-Learning, 6-Personal, 7-Travel, 9-Archive, Review. Place each bookmark under its Category (Review goes in the Review folder). Use the classic structure with DOCTYPE and DL/DT/H3 tags. Use ADD_DATE and LAST_MODIFIED with the current UNIX epoch (use the same value for simplicity). Output the complete HTML only, no explanations. Keep titles from TitleClean and href from URLClean.”

Folder structure and naming

• Top-level: 0-Inbox, 1-Work, 2-Read Later, 3-Finance, 4-Tools, 5-Learning, 6-Personal, 7-Travel, 9-Archive, Review.
• Optional one sub-level: inside Work, create Project folders only if you have 20+ items for a project.
• Read Later shelf-life: anything older than 45 days moves to 9-Archive.

What to expect

• First full run: 45–120 minutes depending on volume.
• Auto-file rate: 70–90% on pass 2; climbs with two or three small rule tweaks.
• After setup: monthly maintenance in 10 minutes or less.

Metrics to track (weekly for a month)

• Auto-file rate = High/Med ÷ total (target 80%+ by week 2).
• Time-to-find a known bookmark (target under 10 seconds).
• Review queue size (target under 5% of total).
• Duplicates removed per batch (drive to near zero after Pass 1).
• Read Later clearance rate (target 90% processed within 45 days).

Common mistakes and fast fixes

• Leaving tracking in URLs: always run Pass 1; it prevents duplicate clutter later.
• Over-granular folders: merge by purpose; keep top-level ≤7 plus Inbox/Archive/Review.
• Trusting Low-confidence items: anything Low goes to Review, always.
• Skipping a test import: test 20 items before importing the full file.
• No archiving rule: enforce the 45-day sweep for Read Later.

One-week action plan (crystal clear)

1. Day 1: Export bookmarks. Create folders exactly as listed. Move 20 items into 0-Inbox.
2. Day 2: Run Pass 1 (Sanitizer) on those 20. Fix any obvious duplicates. Confirm you like the title format.
3. Day 3: Run Pass 2 (Classifier) on the same 20. File High/Med; leave Low in Review.
4. Day 4: Ask the AI to build the small import HTML (Pass 3). Test-import the 20. Validate structure.
5. Day 5: Process 150–300 more items in batches: Pass 1 → Pass 2 → file High/Med.
6. Day 6: Build the full import HTML and import; archive anything older than 45 days in Read Later.
7. Day 7: Record metrics. Calendar a 10-minute monthly tidy: run Pass 1 + Pass 2 on 0-Inbox, sweep Read Later >45 days to Archive.

Insider tip: keep a tiny Rule Deck note and add one rule per week (e.g., “docs.google.com with ‘Q4 Plan’ in the title = Work”). Marginal gains here compound into fewer reviews and faster filing.

Your move.

Nice quick-win — that 5-minute “I wish / how do I” scavenger tip is exactly the kind of tiny habit that yields immediate, usable signals. Here’s a short, outcome-focused extension so you move from quotes to validated ideas and measurable results.

The problem

Forums are noisy. You can collect pages of complaints and still have nothing you can productize.

Why it matters

Turn chatter into paying customers by focusing on repeated, specific pains and validating with one-question tests fast.

Do / Do not checklist

• Do capture short verbatim quotes + thread link so you can prove context later.
• Do tag each quote by pain type (cost, time, complexity, missing feature).
• Do translate each quote into a one-line micro-idea (one sentence).
• Do not chase volume over signal — 10 high-quality quotes beat 100 vague ones.
• Do not validate with surveys that ask for opinions instead of commitments (use yes/no or micro-commitments).

Step-by-step (what you’ll need, how to do it, what to expect)

1. What you’ll need: browser, community account, spreadsheet (quote | link | date | tag | micro-idea | validation).
2. Set a 15-minute timer. Open one topic or saved search and scan 5–10 newest posts.
3. Capture 3 concise quotes that show pain/desire. Add tag + one-line micro-idea for each.
4. Use this AI prompt (copy-paste) to cluster and prioritize: “Here are 10 short user quotes about problems in [niche]. Group them into 3 themes, give a one-sentence product idea for each theme, and recommend the simplest validation test to run in the forum (one sentence each).”
5. Pick the simplest idea. Validate with one low-friction ask: a one-question poll, a reply asking “Would you pay $X for this? Yes/No”, or DM 3 active members.
6. Expected outcome: 4–6 sprints = 1–2 validated micro-ideas worth a landing page or pre-sell.

Metrics to track (KPIs)

• Quotes captured per session (target 3–5).
• Number of distinct themes after clustering (target 2–4).
• Validation response rate (target 20–30% for DMs, 5–10% for open replies).
• Commitments (yes to pay / join waitlist) — your green light: 5+ independent yeses.

Common mistakes & fixes

• Collecting vague complaints — fix: only save quotes that include consequence (time lost, money, frustration).
• Overbuilding before validation — fix: pre-sell or build a landing page MVP first.
• Asking the wrong validation question — fix: ask for choice/commitment (Would you pay $X?) not opinion.

Worked example (15-minute sprint)

• Scan a small accounting forum: capture 3 quotes about invoicing headaches, tag as “time” and “confusing”, write micro-ideas: “auto-fill tax codes”; “one-click invoice templates”; “reminder automation”.
• Run the AI prompt above to cluster; pick “one-click invoice templates” as simplest. Post a two-option poll in the thread: “Would a one-click invoice template save you 10–15 minutes per client? Yes / No.”
• If 5+ yeses and 20% reply rate -> build a simple landing page and collect emails for early access.

1-week action plan

1. Day 1: Set up spreadsheet and saved searches (30–45 minutes).
2. Days 2–6: Do one 15-minute micro-sprint each day, capture quotes and one-line ideas.
3. Day 7: Run AI clustering, pick one idea, validate with one poll or 3 DMs. Record results.

Your move.

Quick win (under 5 minutes): Ask an AI for a 3-step, 5-minute mini-routine you can do tomorrow morning — hydrate, 2 minutes of movement, one minute of breath — and schedule it as a single calendar reminder.

Good point from your message: personalization is the lever — clear wake time, exact minutes available, and one concrete goal (energy, calm, focus) give AI the context it needs to deliver usable steps.

The problem

People create routines that are too long or vague. Result: low adherence and no measurable improvement.

Why it matters

Morning routines are leverage — 10–30 minutes consistently executed changes focus and productivity for the entire day. Small wins compound into reliable behavior.

What I’ve learned

Keep it short, measurable, and repeatable. Start with a baseline week, track two KPIs, then refine with AI based on actual data.

What you’ll need

• A device (phone/tablet) with calendar/reminders.
• An AI chat tool (any simple chatbot).
• 5–30 minutes morning availability.

Step-by-step (do this now)

1. Pick one goal: energy, calm, or focus.
2. Decide available time (e.g., 10, 20, or 30 minutes) and your wake time.
3. Use the AI prompt below to generate a 20–25 minute routine, a 10-minute condensed version, and 7-day variations.
4. Copy your chosen routine into 3 calendar reminders (Hydrate / Move / Focus) with the 1–2 sentence scripts as notification text.
5. Execute for 7 days, record two KPIs each morning (adherence, perceived energy 1–10).
6. After day 7, ask the AI to refine the routine using your KPI results and one note about what felt hard.

Copy-paste AI prompt (use as-is)

“You are my personal morning routine coach. I wake at 6:30 AM, have 20 minutes, and my goal is to increase energy and reduce stress. Create a clear step-by-step 20-minute routine with exact times, 1-sentence scripts I can read aloud, a 10-minute condensed option, and a 7-day variation to keep it fresh. Include one simple daily metric to track (adherence or energy score). Keep tone practical and encouraging.”

Metrics to track

• Adherence rate (% days completed per week).
• Perceived energy (1–10 each morning).
• Secondary: time to first focused task (minutes).

Mistakes & fixes

• Too long — fix: cut to 2 prioritized activities and a 5–10 minute mini routine.
• Vague prompts — fix: give exact wake time and minutes available.
• All-or-nothing thinking — fix: set a minimum mini routine for busy days and log it as a success.

1-week action plan

1. Day 1: Run the prompt, pick a routine, add 3 reminders with scripts.
2. Days 2–7: Follow the routine, log adherence and energy each morning.
3. Day 8: Feed results back to the AI and get a refined routine (shorter where needed).

Expect a measurable change in perceived energy within 7 days if adherence >70% and energy scores trend up by at least 1 point. Your move.

Cut the waste fast: a 60-minute AI-assisted sweep typically exposes 3–7 subscriptions you don’t use and 1–2 outliers worth real money. Do this once, then set it on a quarterly cadence.

The real issue: small repeat fees and quiet annual renewals hide in plain sight under messy merchant names. You’re not missing intelligence — you’re missing structure.

Why it’s worth your hour: eliminating a handful of $8–$25 monthlies and one $99–$249 annual saves hundreds per year, improves cash flow, and reduces mental load. This is compounding: once you build the system, maintenance is minutes.

What experience shows: after dozens of clean-ups, 80% of savings come from 6–10 merchants. The win is prioritization — normalize names, rank by frequency and spend, then act on the top items only.

Execution plan (clear steps)

1. Pull data (5 min): Export 3–6 months of transactions (Date, Merchant, Amount). If you have a Memo/Category column, include it. Remove account numbers and personal IDs.
2. Normalize names (5–10 min): In Sheets/Excel, quickly group obvious variants (e.g., “STREAMFLIX”, “STREAM FLIX”, “STRMFLX”). Keep a simple “Alias → Canonical Name” list. This single step cuts false flags dramatically.
3. Create a quick baseline (10 min): Make a pivot by Merchant to see total spend and count. Add a helper column Month = first day of month (use YEAR and MONTH). Pivot by Merchant x Month to spot cadence (monthly, quarterly, annual).
4. Run the AI triage (5–10 min): Paste 20–50 representative rows per merchant cluster. Use the prompt below to force structure, cadence detection, and a prioritized action list. Keep output capped so you can act.
5. Verify the top 5 (30–45 min): For each flagged item, check your email receipts or the service account page. Decide: keep, downgrade, cancel, or dispute if unauthorized. Note expected savings and next charge date.
6. Document once (5 min): Build a simple tracker with columns: Merchant, Plan, Amount, Cycle (monthly/annual), Next Charge, Owner, Status (Active/Cancelled), Notes.
7. Set a recurring check (2 min): Calendar reminder every quarter. Next run takes 15–20 minutes.

Insider tricks that move the needle

• Alias map first, analysis second: AI and pivots perform far better once you standardize names. Keep this list; it compounds accuracy over time.
• Three-threshold filter: 1) Small-repeat under $15 monthly, 2) Mid-tier $15–$50 monthly, 3) Annuals over $100. Prioritize cancellations by annualized savings.
• Duplicate guardrail: Only flag same-merchant/same-amount charges inside 72 hours unless the memo clearly differs (e.g., two restaurant visits in a day).

Copy-paste AI prompt (use as-is)

Act as my personal expense auditor. Input columns: Date (YYYY-MM-DD), Merchant, Amount (positive = charge, negative = refund). Tasks: 1) Normalize merchant aliases into a single canonical name. 2) Identify recurring subscriptions with cadence (monthly/annual), typical charge window (e.g., 1st–5th), and next expected date. 3) Flag outliers: amounts >3x the median for that merchant or >$100 if there’s no history. 4) Find likely duplicates: same merchant and amount within 72 hours (exclude obvious restaurants/groceries). 5) Highlight small recurring fees under $15 that appear monthly. 6) For each finding, provide: Canonical Merchant, Finding Type (Subscription/Outlier/Duplicate/Small-Recurring), Evidence (dates/amounts), Recommended Action (keep/downgrade/cancel/dispute), Estimated Monthly Savings, Confidence (0–100). 7) Output no more than 15 findings and a prioritized Top 5 Actions list by savings. Use concise bullet points.

What good output looks like: a short list of recurring services with dates and amounts, a few outliers with context, and a Top 5 Actions section you can execute today. Expect some false positives; verify before disputing.

Metrics to watch

• Potential monthly savings identified ($)
• Confirmed savings realized ($) and count of cancellations
• Outliers/duplicates found vs. verified (precision %)
• Time spent per review (minutes)
• Next expected charge coverage (% of active subs with a noted next date)

Common pitfalls and fast fixes

• Mixing refunds and charges: Filter negatives into a separate view so AI doesn’t misread them as anomalies.
• Over-flagging same-day spend: Apply the 72-hour duplicate rule; restaurants and travel often have multiple same-day charges.
• Ignoring annuals: Scan for single large charges around the same month each year; set the next expected date in your tracker.
• Sharing sensitive data: Mask account numbers, addresses, and full card PANs before pasting anywhere.
• Acting without proof: Always check receipts or account pages before canceling or disputing.

One-week plan to lock this in

1. Day 1 (15–20 min): Export 3–6 months. Normalize obvious merchant aliases. Build a quick pivot by Merchant and by Merchant x Month.
2. Day 2 (15 min): Run the AI prompt on 20–50 representative rows. Capture the Top 5 Actions.
3. Day 3 (30–60 min): Verify and execute: cancel/downgrade at least the top 3; request refunds on any confirmed duplicates.
4. Day 5 (10 min): Update your tracker with Status and Next Charge. Record estimated monthly savings.
5. Day 7 (10 min): Review card statements or emails to confirm cancellations queued. Set a quarterly calendar reminder.

Result to aim for this week: $20–$100/month in confirmed savings, 3+ subscriptions documented or canceled, and a simple tracker that prevents future creep.

Your move.

Agreed: your three‑pass check (Neutralize, Balance, Stress‑Test) is the right core. Now bolt on a results layer so you can prove bias dropped before full launch and lock a repeatable process.

The business problem

Biased questions distort decisions, slow launches, and waste budget. You don’t need fancy stats — you need a simple loop that flags bias early, quantifies the fix, and freezes winning wording.

• Do design backward from decisions (name the 1–2 decisions this survey will drive).
• Do keep one idea per question, set clear timeframes, and include “Don’t know/Not applicable.”
• Do A/B test 2–3 high‑risk questions with 30–60 respondents to detect order/wording skew.
• Do label every scale point; anchor ranges (0, 1–3, 4–7…).
• Don’t mix behavior + opinion in one item; separate “Did you?” from “How did you feel?”
• Don’t remove domain terms the market understands; preserve critical wording.
• Don’t force answers; always offer a clean exit when the item doesn’t apply.
• Don’t randomize gating questions; keep screening first, then randomize blocks.

What you’ll need

• 6–12 draft questions tied to a one‑sentence objective.
• Your survey tool, plus an AI chat/editor.
• 30–60 people for a micro A/B pilot (warm audience is fine).
• A simple spreadsheet to track versions and KPIs.

Step‑by‑step: the Bias KPI loop

1. Prioritize risks: mark questions that judge quality, pricing, or satisfaction. These are prone to leading language.
2. Generate neutral variants: run your three‑pass check and produce 2 versions (A/B) for each high‑risk item.
3. Micro A/B pilot: split 30–60 respondents randomly. Keep everything identical except the test item or block order.
4. Score bias quickly: compute KPIs (below). If A and B differ materially, pick the lower‑bias option.
5. Freeze wording: version‑lock your final items; keep a change log for traceability.
6. Launch + monitor: watch first 100 responses; trigger fixes only if thresholds trip.

Copy‑paste prompts (use as‑is)

• Bias Risk Report: “Review this survey question and answer options. Identify loaded words, hidden assumptions, excluded groups, and scale mismatches. Propose two neutral rewrites (A and B), each under 15 words, with a fully labeled 5‑point scale plus ‘Don’t know’ and ‘Not applicable’. Preserve these domain terms: [LIST TERMS]. End with a one‑sentence rationale for the least biased version. Question: [PASTE QUESTION]”
• Order‑Effect Test Plan: “Design a simple A/B plan to detect order bias for this block of questions. Specify block order for A and B, expected risks, and the primary metrics to compare after 50 total respondents. Block: [PASTE BLOCK]”

KPIs that prove you reduced bias

• Completion rate: target ≥60% for short surveys.
• Item nonresponse: ≤5% per question (≤3% is excellent).
• Midpoint usage: 15–35% on opinion scales (too low can signal pushy wording).
• Top‑2 box spread (A vs. B): ≤10 percentage points difference; larger gaps suggest wording bias.
• “Not applicable/Don’t know” rate: usually 3–15%. Near 0% can indicate forced responses.

Worked example

• Biased draft: “How fair is our competitive pricing?”
• Issues: asserts “competitive”; begs for a positive answer; no prior usage screen.
• Fix the sequence (behavior before opinion): “In the past 30 days, did you purchase [Product]?” Options: Yes; No; Don’t know; Prefer not to say.
• Neutral satisfaction item (shown only if Yes): “Overall, how satisfied are you with the price you paid?” Scale: Strongly dissatisfied, Dissatisfied, Neither, Satisfied, Strongly satisfied, Don’t know, Not applicable.
• A/B wording check:
  • Version A: “How satisfied are you with the price you paid?”
  • Version B: “How reasonable was the price you paid?”
• What to expect: Version B often inflates positives. If Top‑2 box is A=58%, B=69% with similar samples, prefer A (less leading). Aim for midpoint usage 20–30% and item nonresponse ≤3%.

Common pitfalls & fast fixes

• Over‑sanitizing (AI strips vital terms) → Add “Preserve these terms: [X, Y]” to your prompt.
• Scale mismatch (agreement scale on a frequency question) → Match stem to scale type.
• Missing base logic (asking non‑users to rate) → Insert usage screen; route “No” to skip.
• Order bias (benefits before satisfaction) → Randomize blocks or separate with neutral items.
• Vague timeframes (“often”) → Replace with explicit ranges or days.

1‑week action plan

1. Day 1: Define survey decisions; write the one‑sentence objective; draft 6–12 items.
2. Day 2: Run the three‑pass AI check; produce A/B variants for 2–3 risky items.
3. Day 3: Build survey; add screens, labels, coverage options; set randomization rules.
4. Day 4: Micro A/B pilot (30–60 people).
5. Day 5: Compute KPIs; choose lower‑bias versions; finalize wording.
6. Day 6: Prepare full sample; write a short field plan with KPI thresholds.
7. Day 7: Launch; monitor first 100 responses; intervene only if thresholds trip.

Bottom line

Keep your three‑pass edits, but add the KPI loop and a tiny A/B. You’ll cut bias, lock cleaner questions, and protect decisions — in under an hour.

Your move.

5-minute win: Grab 5–10 recent support transcripts about the same feature. Paste them into AI with the prompt below and get a one-page mini-spec with user story, acceptance criteria, telemetry to add, and a help-center snippet you can ship today. You’ll walk away with a shippable ticket and a quick-help update in one pass.

The problem: Most teams stop at “themes.” Themes don’t move metrics. You need a repeatable way to turn transcripts into prioritized specs with clear success criteria.

Why it matters: Every unresolved root cause compounds support cost, churn risk, and engineering rework. Turning raw transcripts into a scoped fix and a deflection asset reduces tickets in weeks, not quarters.

What works in practice: Package evidence once, then execute on two tracks: fast deflection (docs/UI copy) and root-cause fix (small, testable change). Measure ticket reduction and time-to-resolution for that issue. Repeat weekly.

What you’ll need

• 50–200 redacted transcripts in a sheet (id, date, channel, raw_text).
• One AI assistant (chat or API).
• 15 minutes daily for triage; a product owner to approve top fixes.

Step-by-step — from transcript to shipped fix

1. Normalize the data: In your sheet, keep one transcript per row. Add columns: summary, category, severity, root_cause, product_fix, quick_help, confidence.
2. Cluster quickly (10–15 min): Paste 10 mixed transcripts into AI; ask for 3–5 themes with counts. Sanity check with your support lead.
3. Extract structured insights: Batch through the AI to fill the columns. Gate items with confidence < 0.7 for human review.
4. Merge duplicates: Roll similar summaries into a single “issue card.” Keep a frequency count.
5. Score for action: Rank issues by Frequency × Severity × Business Impact. Use a simple Effort modifier (High, Medium, Low). Prioritize high score, low effort.
6. Create an evidence pack for the top issue (template below). This is the handoff engineers will actually pick up.
7. Two-track execution: Ship one quick-help item immediately (FAQ, tooltip, UI copy). Scope one product change with clear acceptance criteria and instrumentation.
8. Instrument and measure: Add events or server logs that confirm the fix is used. Compare 2–4 weeks pre vs. post.

Copy-paste AI prompt — mini-spec from transcripts

“You are a pragmatic product manager. I will paste 5–10 support transcripts about one feature. Produce a one-page output with: 1) Problem summary (2 sentences). 2) Job story (When/If… I want… so I can…). 3) Root cause hypothesis (one line). 4) Acceptance criteria (5–7 testable bullets). 5) Proposed product change (max 2 sentences, smallest viable). 6) Telemetry to add (event names + properties). 7) Quick-help asset (FAQ or tooltip copy, 80–120 words). 8) Rollout and measurement plan (guardrail + success metric). 9) Risks/assumptions. Keep it concise and consistent.”

Evidence pack template (copy this into your ticket)

• Problem: [2-sentence summary]
• Job story: When [context], I want [action], so I can [outcome]
• Root cause: [one line]
• Acceptance criteria:
  • [AC1: specific, testable]
  • [AC2]
  • [AC3]
  • [AC4]
• Smallest product change: [one or two sentences]
• Telemetry: event_[name], properties: [x, y]; success = [definition]
• Quick-help: [FAQ/tooltip copy]
• Rollout: [% rollout or A/B]; Guardrails: error rate, support spikes
• Owner: [PO]; ETA: [date]

Bonus prompt — structured extraction at scale

“You are classifying support transcripts. Return CSV rows with: transcript_id, one-line summary, category (billing/onboarding/performance/UX/other), severity (low/medium/high), likely root cause (short phrase), recommended smallest product change (one sentence), recommended quick-help (one sentence), confidence 0–1. Keep formats consistent.”

Metrics to track (set targets before you ship)

• Ticket reduction for the issue: target 30–50% drop within 2–4 weeks.
• Time-to-resolution for that issue: target 20–30% faster.
• Support contact rate (tickets per 1,000 active users): down and to the right.
• Doc/tooltip deflection: views per issue ÷ tickets for that issue > 3:1.
• % tickets mapped to top 5 issues: aim for 70% to focus your roadmap.
• Engineering ROI: tickets avoided per engineering day > 10.

Common mistakes and fast fixes

• Theme-only work (no spec): Fix — always produce an evidence pack with acceptance criteria and telemetry.
• Small-sample bias: Fix — wait for 90–200 transcripts or validate across channels before big product changes.
• Inconsistent AI outputs: Fix — use structured prompts and a review gate for confidence < 0.7.
• Over-fitting to “how-to” tickets: Fix — split usage education (docs/UI) from defects or UX gaps (product fixes).
• No instrumentation: Fix — require telemetry in the spec; no event, no ship.
• No owner: Fix — assign a single PO to approve top 2 fixes each cycle.

1-week action plan

1. Day 1: Export and redact transcripts. Populate the sheet. Run the quick cluster; align on top 3 issues.
2. Day 2: Batch extract structured fields. Merge duplicates. Flag low-confidence items for review.
3. Day 3: Build one evidence pack using the mini-spec prompt. Get PO approval.
4. Day 4: Ship the quick-help asset (FAQ or tooltip). Add telemetry.
5. Day 5: Scope the smallest product change, finalize acceptance criteria, schedule into the sprint.
6. Days 6–7: Launch to a subset or A/B. Start measuring ticket reduction and TTR against baseline.

Do this weekly: one quick-help shipped, one root cause fixed or in-flight, metrics reviewed every Friday. Less noise. Fewer tickets. Faster roadmap.

Your move.

Hook: Route by fit and urgency, protect the customer experience, and prove the lift in two weeks. Here’s the exact setup, KPIs, and guardrails.

The problem

Most routing either overweights urgency or buries great leads in nurture. The result: slow handoffs, annoyed prospects, and reps chasing noise.

Why it matters

Done right, AI triage cuts response time, raises qualified meetings, and improves first-touch satisfaction. The metric signal shows up within 14 days — if you measure the right things and keep humans on the edge cases.

Lesson from the field

A two-score model (Fit + Urgency) with confidence-gated handoffs beat rigid rules. The unlock was tracking speed to first meaningful response (not just any reply) and giving reps a one-line opener they could send instantly.

What you’ll need

• Lead inputs: role, company_size, industry, budget_range, timeline, contact_channel, raw_message.
• An LLM that returns strict JSON via webhook.
• CRM automations to assign owner, set SLA, and create a human-review queue.
• Dashboards for response time, SQL rate, handover quality (rep-rated), CSAT, and misroute rate.

High-value refinements (insider tricks)

• Confidence gate: Only auto-route when confidence_score ≥ 75 and the score is ≥ 5 points clear of a threshold. Else, send to a 1-hour review queue.
• Channel-aware urgency: Weight “phone” and “direct referral” +10 urgency; deprioritize after-hours web form by -5 but keep SLA sane.
• VIP overrides: Maintain a target-account list that always escalates to your best rep regardless of score.
• Shadow routing: First week, route normally but “shadow” the AI decision in a field. Compare outcomes before flipping to live.
• Meaningful response SLA: Track first substantive reply (answers their ask or proposes times), not just an automated “got it.”

Step-by-step

1. Baseline rules: Define Fit by role match, company_size bands, and budget bands. Define Urgency with modest boosts: keywords (+30), timeline ≤ 30 days (+20).
2. Scoring: Fit (0–100), Urgency (0–100). Start with Priority = 0.6*Fit + 0.4*Urgency.
3. Extraction prompt: Have the AI normalize free text, return scores, a confidence_score, a route, and a one-line opener the rep can send.
4. Routing map: 80+ Enterprise (15-min SLA), 60–79 SDR (15–30 min), 40–59 Channel Specialist (24 hrs), <40 Nurture/Request Info. Confidence <75 or within ±5 of a boundary = review queue.
5. CRM automation: On create: set owner by route, apply SLA timers, post a push alert, prefill the opener into the task so reps can send in one click.
6. Human loop: Weekly 30-minute review: sample 20 routed + 20 reviewed leads; record false positives/negatives and adjust weights.
7. Shadow → live: Run shadow for 7 days on 10% traffic. If KPIs improve, go live for 50% and re-check in week two.

Copy-paste AI prompt

“You are a lead triage assistant. Input fields: name, message, company_size, industry, role, budget, timeline, contact_channel. Return strict JSON only with: {fit_score:0-100, urgency_score:0-100, confidence_score:0-100, recommended_route: one of [‘Enterprise’,’SDR’,’Channel Specialist’,’Nurture’,’Request Info’], reason_short: string (max 18 words), follow_up_text: string (one-line opener proposing next step)}. Scoring: company_size bands (1-10:0, 11-49:+10, 50-199:+30, 200+:+50), budget bands (<10k:0, 10-24k:+10, 25-99k:+30, 100k+:+50), role match to buyer persona +10. Urgency: keywords [‘today’,’ASAP’,’this week’,’this month’] +30; explicit timeline ≤30 days +20; contact_channel=’phone’ or ‘referral’ +10. If timeline or budget missing, set recommended_route=’Request Info’ and write a polite follow_up_text asking for both. Keep outputs consistent and deterministic.”

What to expect from the prompt

• Consistent JSON the CRM can parse without manual cleanup.
• Short rationale so reps understand the decision at a glance.
• Send-ready opener to increase first meaningful response rate.

Metrics that prove it’s working

• Speed to first meaningful response: target ≤ 30 minutes for top tiers.
• SQL rate from routed leads: monitor lift vs. baseline (aim for +10–25% within 30–60 days).
• Handover quality (rep-rated 1–5): aim for ≥ 4.0 on top tiers.
• CSAT on first touch: lightweight survey or reply sentiment; aim for ≥ 4/5.
• Misroute rate: percentage of leads rerouted within 24 hours; keep < 8% and trending down.
• SLA breach rate: especially for Enterprise and SDR queues; keep < 5%.

Common mistakes and fixes

• Overweighting urgency: Cap urgency boosts and use the confidence gate. Review weekly.
• Ignoring channel and timing: Add channel-aware modifiers and office-hours rules; maintain fair SLAs.
• Dirty inputs: Normalize currency and company_size; enrich missing fields automatically.
• No shadow period: Always run shadow routing for a week to capture baseline deltas.
• One-way automation: Add a “wrong route” button for reps; capture the correct route and reason to retrain.

One-week action plan

1. Day 1: Define Fit/Urgency rules, thresholds, and VIP override list. Create review queue in CRM.
2. Day 2: Implement the prompt and webhook. Add fields for scores, route, confidence, reason, opener.
3. Day 3: Run on 1,000 historical leads. Compare to past outcomes; tune weights and boundaries.
4. Day 4: Set SLAs, push alerts, and prefilled opener tasks. Build the shadow-routing workflow (10% traffic).
5. Day 5: Launch shadow. Start dashboard for response time, SQL rate, handover quality, CSAT, misroute rate.
6. Day 6: Rep feedback session; adjust opener tone and boundary rules. Confirm VIP overrides work.
7. Day 7: Go/no-go: if speed-to-meaningful-response improves ≥ 20% and misroutes ≤ 10%, expand to 50% traffic.

Closing: Build the two-score model, gate with confidence, measure meaningful response, and shadow before scaling. Your move.