Ask what your Feefo rating is and what customers said about you this month.
Connect Feefo with your merchant identifier and Memtro reads your overall service and product ratings with counts per star, and recent reviews: the service rating and review, any product reviews with product, SKU and rating, the customer's display name and the date. No key is needed to read, since Feefo's reviews API is public. It reads on demand and there is no hourly sync. With an App Key added, when you ask and once an administrator has granted the action by name, it can publish a public reply to a review, which cannot be edited or removed from Memtro.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Feefo tool, reads what it needs, and answers with the source cited.
These tools change something in Feefo. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Feefo is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Feefo + MemtroWhat is our Feefo rating right now?
How many 1-star reviews did we get this month?
What did customers say about delivery in the last month?
Which products got low ratings in recent Feefo reviews?
Reply to yesterday's 2-star review apologising for the late delivery
The customer service lead at Northwind asks how last week's Feefo reviews look. Memtro reads the rating summary and recent reviews, gives the service score with the count per star, and quotes the two lowest reviews, both about late delivery.
Priya Sharma in customer service asks Memtro to reply to a 2-star review about a cracked kettle lid. Memtro publishes her approved apology under the Northwind Care Team name, where anyone can see it, and asks Feefo to email the customer as she requested.
The teams that lean on Feefo most, a question each of them asks, and what they connect beside it.
A record in Feefo is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
Find your merchant identifier in the Feefo Hub. It is usually also the last part of your public Feefo reviews page address
To let Memtro reply to reviews, open Feefo Hub → Settings → Connectivity → App Keys, create an App Key granting the reviews services only, and copy its Client ID and Client Secret from Details. Leave this out to keep Memtro to reading
In Memtro open Connections → Feefo, enter the Merchant identifier, add the App Key client id and secret if replying, and connect
Ask what customers said about you this month
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Feefo tools are the same everywhere.
Only when you ask, and only what it has been granted: publish a public reply to a Feefo review, under a named author. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Merchant identifier, plus an App Key for replies. Find your merchant identifier in the Feefo Hub. It is usually also the last part of your public Feefo reviews page address.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time
