Finding the pattern
The ecommerce manager at Acme asks what this week's low-star reviews have in common. Memtro reads company and product reviews rated two or below, and reports that five of seven mention late delivery, quoting two with their dates.
Ask what your latest low-star REVIEWS.io reviews complain about, and what your rating is.
Connect REVIEWS.io with your store key and API key and Memtro reads company, product and third-party reviews and product questions, with rating, title, text, reviewer name, date, product SKU, tags and replies. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can tag reviews for sorting, which nobody sees, and send review invitations to customers by email or text, or pause and change queued ones. An invitation reaches the customer and cannot be recalled once sent, and each text uses SMS credits from the plan.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right REVIEWS.io tool, reads what it needs, and answers with the source cited.
These tools change something in REVIEWS.io. 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 REVIEWS.io 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.
What do our latest one- and two-star reviews complain about?
What is our REVIEWS.io rating for company and product reviews?
Which product questions are still unanswered?
What did customers say about SKU NW-204 this month?
Send Dan Fletcher a review invitation for order 5521 next Tuesday
The ecommerce manager at Acme asks what this week's low-star reviews have in common. Memtro reads company and product reviews rated two or below, and reports that five of seven mention late delivery, quoting two with their dates.
Priya Nair in support sorted out a damaged parcel for Dan Fletcher and asks Memtro to invite him to review the replacement. Memtro queues a REVIEWS.io invitation email for the product, to go out on Tuesday, and Priya can pause it until then if anything changes.
The teams that lean on REVIEWS.io most, a question each of them asks, and what they connect beside it.
A record in REVIEWS.io 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.
API access needs the REVIEWS.io Plus plan
In the REVIEWS.io dashboard open Integrations → API and copy the public store key and the private API key on that page. The API key reads every review and lets Memtro tag reviews and send review invitations when asked
In Memtro open Connections → REVIEWS.io, paste the Store key and API key and connect
Ask what the latest low-star reviews complain about
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The REVIEWS.io tools are the same everywhere.
Only when you ask, and only what it has been granted: add a tag to a company review; add a tag to a product review; email a customer a company and product review invitation; text a customer a product review invitation (spends SMS credits); text a customer a company review invitation (spends SMS credits); edit or pause a queued product review invitation; edit or pause a queued company review invitation. 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.
Store key and API key. API access needs the REVIEWS.io Plus plan.
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