Skip to content
Ask your quotes anything. It cites, or it refuses.See how
madfeed
Get started

Features

Everything between a customer's words and your reply

One place and one data model for what customers said, what it is worth, and telling them what you did about it.

  • Useful from the first pasted conversation
  • Nothing sent without your approval

Bring feedback in, from anywhere

Conversations arrive in many places, so there are many ways in. All of them end in the same place: an untouched, stored source, split into pieces, with sensitive numbers hidden, waiting to be read.

  • Paste a conversation, with the person, account and a link back if you have them.
  • Upload a call or interview recording (large files, resumable) and get a transcript with speakers and timing.
  • Import people and accounts from a CSV: columns are detected, you see a preview, and every bad row is named.
  • Add a feedback form or a chat window to your website, limited to the sites you allow, with files in chat both ways.
  • Forward or route customer email in from any mail provider.
  • Collect messages from a Slack channel you choose.
  • Let other tools post in: help desks, form tools, automation services and call-recording tools send notes and transcripts through one endpoint, and a retry never stores one twice.
  • Run surveys; free-text answers join the review queue.

Cited extraction and a review queue

The AI reads each source and proposes the requests inside it. Each suggestion shows the original text with the supporting sentence highlighted, a confidence, and whether it looks like a new request or more evidence for an existing one.

  • Every quote must appear word for word in the original at the stored position. Two code checks and a database rule enforce it, so an invented quote cannot be stored.
  • Nothing becomes a request until a person accepts it. Accept, edit the title, merge into an existing request, or dismiss; undo any of it.
  • Bulk-accept suggestions above a confidence you choose.
  • A suggestion that looks like an existing request says so, with the reason, and a person presses the button. Nothing merges by itself.

Requests, people and what they are worth

A request gathers evidence: who said it, which account they belong to, in which source, and exactly where. The numbers update as evidence is added.

  • Impact shows quotes, people, accounts and total value. Value is summed over distinct accounts, so two people from one account count that account once.
  • Customisable statuses, tags and areas; filters; sorting by value or newest; saved views you can share.
  • People and accounts with revenue, plan and renewal date, from a strict CSV import, by hand, or read-only from HubSpot or Salesforce.
  • Search quotes by meaning, so "I can't log in with my company account" finds "SSO is broken" too.

Questions and briefs you can verify

Ask in plain language and get an answer you can check, or an honest refusal.

  • Ask a question about what customers said. The answer is built only from stored quotes and cites them, or says there is no evidence. Questions with a false premise are refused.
  • A decision brief for any request summarises the evidence, with every claim linked to its quote.
  • A quality page shows how often accepted suggestions were edited or dismissed, and a weekly spot check samples answers and briefs for a person to grade.

Close the loop with the people who asked

Marking a request shipped prepares a personal draft for each person who asked, written from their own words. You review each message, edit it, and approve. Only approved messages are sent, and that rule lives in the sending code, not just the screen.

  • A send log, a signed unsubscribe link in every message, an honoured opt-out list, and bounce and complaint handling.
  • "Told about this" marks on each request, so you know who has heard.
  • Release notes written by you, linked to requests, published now or scheduled for an exact moment, with a public page.
  • A public roadmap where signed-in visitors vote; votes from known customers are marked verified.

Want to see the loop on your own data?

Paste one conversation and watch it become cited, weighted requests.

Calls, highlights and findings

Turn recordings into searchable moments, and share what you learned as quotes that cannot drift.

  • Timed transcripts with speakers and a player; every highlight maps to a moment.
  • A tag codebook with definitions and colours; merge two tags and undo it exactly.
  • Highlight by hand, or accept suggested highlights from the codebook.
  • A quotes screen as a table or a board, with tags over time and feeling labels (by a model or a person, with agreement measured).
  • Findings documents made of quote cards that always show the stored words, shared by a link you can revoke.

Surveys

Ask the right people the right question, and feed the answers into the same queue.

  • NPS, CSAT, choice and free-text questions.
  • An audience built from rules over your people and accounts, with a preview of who would get it.
  • Approved email invitations and reminders, a public link, or an embed in your own page.
  • Questions that appear depending on up to four earlier answers, combined with "all" or "any".
  • One final answer per person. If a person is deleted, their answers are removed or anonymised, as you choose.

A support desk that feeds the same loop

Answer customers in one shared inbox, and turn what they say into requests without copying anything.

  • Website chat and email in one shared inbox, with private notes and assignment to a named teammate.
  • Saved replies, a reply-time target, median and slow-end first-reply times, and who is waiting.
  • Two people cannot reply at once: a conversation that changed while you read it asks you to look again.
  • Send a customer's message to the review queue and watch what came of it.

Public pages

Show customers what you are doing, and let them weigh in.

  • A release-note page and a public roadmap on a short address you choose.
  • An embeddable feedback form, chat window and survey.
  • Only items you explicitly publish are public; nothing private is on a public route.

Integrations, an API and AI assistants

Fit into the tools you already use, or build your own with a few lines of code.

  • Open issues in GitHub (and, as each is switched on, Linear, Jira, ClickUp, Asana and Azure DevOps) and let the request follow the issue. Issues never contain customer quotes, names or emails.
  • Signed webhooks for your own code, or plain sentences in a Slack, Discord or Teams channel.
  • A public API with scoped, expiring, address-limited keys.
  • Ten tools for AI assistants (Claude, ChatGPT, Cursor and others) behind an approval page you control, with quotes that look like instructions withheld from them.
curl -X POST "$API/v1/ext/feedback" \  -H "Authorization: Bearer $KEY" \  -H "Content-Type: application/json" \  -d '{    "text": "We rebuild this every Monday.",    "source": "Help desk",    "title": "Ticket 4812: export",    "externalId": "4812",    "email": "priya@example.com"  }'

Trust

Trust, privacy and control

  • Isolated workspaces

    Separated at the database level, with roles enforced on every route.

  • Never trains models

    Customer text goes only to AI routes marked as allowed to receive it.

  • Every AI call logged

    Provider, model, prompt version, tokens and cost, plus a daily allowance.

  • Export and delete

    Export your whole workspace, or delete a person and everything about them.

  • Invite teammates by email, give each an admin, member or viewer role, and change or remove them any time.
  • A daily AI allowance per workspace stops runaway cost.
  • Built toward WCAG 2.2 AA, with keyboard use and phone layouts.

Read the security page

See it with your own conversations

Paste a customer conversation and get cited requests in minutes. No setup first.