Invite-only beta

One click to tell you how it went.

Redback Feedback puts a row of rate-this-interaction buttons in your email, or a short survey behind a link, and turns the answers into CSAT and NPS you can act on. Australian owned and run. Your data stays in Sydney.

Request an invite Read the API docs

Two ways to ask

Build either kind of form in the dashboard, over the API or from an MCP client. Share it through the tools you already use. We never email your customers for you.

Survey

A page of questions behind a link. Send the one link to everyone, or mint a single-use invite link for each person so you know who answered and nobody answers twice.

How satisfied were you with your visit?

redbackfeedback.com/f/form_7k2m?ref=ORDER-1042

Good for CSAT questionnaires after a job, a visit or a delivery. Works for suppliers and staff as well as customers.

Footer

A row of rate-this-interaction buttons pasted into an email signature or template. Each button is a link. One click records the score, then a thank-you page offers follow-up questions and a comment box.

Sam from the support team
How did we go today?

😠
🙁
😐
🙂
😄

redbackfeedback.com/r/form_7k2m?s=5&ref={{ticket.id}}&a={{agent.email}}

Buttons are emoji or plain text, so they work in any email client with no images. Merge fields like {{ticket.id}} pass through untouched, so your helpdesk or mail tool fills them in at send time.

What you can measure

Six question types. Mix them in one form. Every answer carries the reference, agent and tags you put on the link, so the numbers line up with your tickets, orders and teams.

CSAT1 to 5. CSAT% is the share of answers that are 4 or 5.
Star rating1 to 5 or 1 to 10 stars.
NPS0 to 10. Promoters (9 and 10) minus detractors (0 to 6).
Yes or noOne tap. Good for "Was it fixed first time?"
Multiple choicePick one, or allow several.
Free textShort or long, with a length you set.

Stats, ready to use

CSAT%
NPS
Averages
Histograms
CSV export

See the numbers in the dashboard, pull them over the API, or ask for them from an MCP client in plain language.

Built for automation

Everything the dashboard does, the API does. Each organisation gets its own API keys (rb_live_...), and we store only a hash of each one. The MCP (Model Context Protocol) server exposes the same operations to Claude Code, Cursor, VS Code, n8n and any other client that speaks Streamable HTTP.

Add it to Claude Code

Terminal

claude mcp add --transport http redback https://api.redbackfeedback.com/mcp --header "Authorization: Bearer rb_live_..."

The MCP endpoint is https://api.redbackfeedback.com/mcp: Streamable HTTP with your API key as a bearer token. Tools include:

list_forms and create_form
get_form_stats and list_responses
create_invite_links and get_embed
record_response

Or call the REST API

Terminal

curl https://api.redbackfeedback.com/v1/forms -H "Authorization: Bearer rb_live_..."

The base URL is https://api.redbackfeedback.com/v1. JSON in, JSON out, with the same rules as the dashboard: an API key can do nothing a signed-in user cannot.

Read the API docs

Australian owned and run

Built and operated in Australia, for teams that answer to Australian privacy law.

Stored and processed in Sydney. All data lives in AWS ap-southeast-2.
Respondents never need an account. They click a link, answer, and they are done.
We never send email on your behalf. You share links through your own helpdesk, CRM or mail tool, so your customers only ever hear from you.
API keys are stored hashed. We keep a hash of each key, not the key itself.
Delete any response. Handle a privacy request in one call or one click.
Your data is yours. We do not sell it, share it or use it for advertising. Read the privacy policy.

Request an invite

Redback Feedback is in an invite-only beta. Tell us a little about your organisation and we will reply by email. There is no public sign-up yet.