# Nori

> Nori is Flare's customer agent — not AWS Kiro. FAQ from what Flare knows. Real bugs become tickets in the same Project.

## You shipped. Nobody's on support.

Drop the widget on the product. FAQ from what Flare knows. A real bug becomes a ticket in the same Project. Cursor fetches it. The loop does not reset.

## The customer never tours your backlog

- **Answers from what Flare knows** — “How do I invite?” → Settings → Team → Invite. No new hire.
- **A dead button becomes work** — Screenshot attached. Same ONB Cursor has open.
- **A request is staged, not promised** — Scheduled export. Three customers asked. Not a commitment in the widget.
- **MCP closes it** — Claude Code fetches the ticket, fixes, updates status. The graph keeps the why.

## Example: a support thread on acme.app/settings/team

**Customer** — How do I invite my teammates?

**Nori** — Settings → Team → Invite. If it lands in spam, resend from the same row.

**Customer** — The Invite button doesn't do anything.

**Nori** — Dead after click. I grabbed the screen. Opening this on ONB.

Result: a ticket — “Invite button does nothing” (Safari 18) — for the team. The customer never sees this card.

---
Site map: https://flares.in/sitemap.xml · Machine-readable summary: https://flares.in/llms.txt · Phase 2: https://flares.in/miro · The pipe: https://flares.in/mcp