Reading the week's reviews
Maya Okafor, e-commerce manager at Acme Ltd, asked what customers said about the new range this week. Memtro read the published reviews with their ratings and sentiment, and named the products with the most negative ones.
What are customers saying in this week's reviews, and which ones need a reply?
Okendo collects your Shopify store's reviews, surveys and loyalty, and Memtro reads them for you. It reads product reviews by status with rating, text, reply and sentiment. It reads survey and quiz results as counts, averages and NPS per question, and a loyalty member's status, tier and active coupons. When asked and granted, it can reply to a review, approve, hold or reject one, and adjust a member's points or redeem a reward. Okendo can tell Memtro when a review is submitted, and a job can start on it. Free-text survey answers and points balances are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Okendo tool, reads what it needs, and answers with the source cited.
These tools change something in Okendo. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Okendo for you. Each event can start a job, with the event as its input. Okendo signs every delivery, and one whose signature does not check out is refused before it is read.
Events and webhooksOnce Okendo 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.
Which reviews of one star or two came in this week?
What is the average rating for the linen shirt?
What was the NPS on last month's post-purchase survey?
What VIP tier is this loyalty member on, and how many coupons do they hold?
Reply publicly to the latest review of the travel mug to thank them.
Maya Okafor, e-commerce manager at Acme Ltd, asked what customers said about the new range this week. Memtro read the published reviews with their ratings and sentiment, and named the products with the most negative ones.
When Okendo told Memtro a review had been submitted at Northwind, a job started. It read the review and its rating, and posted it to Tom Reilly, the customer care lead, to decide on a reply.
The teams that lean on Okendo most, a question each of them asks, and what they connect beside it.
A record in Okendo 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.
In the Okendo app, go to Settings, then Integrations, then API. Copy the store's User ID and the 32-character key beside it.
In Memtro, open Connections → Okendo and paste the User ID and the API key.
The key has full access to reviews, surveys and loyalty. An administrator grants the review and loyalty actions by name only to the teams that need them. Events are turned on from the connection's Events tab.
Ask which low-rated reviews came in this week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Okendo tools are the same everywhere.
Only when you ask, and only what it has been granted: reply to a review publicly or privately, emailing the customer only when asked; approve, hold for moderation or reject a review; add or remove a loyalty member's points; redeem a points reward for a loyalty member (issues a coupon or store credit); trigger a custom earning rule for a loyalty member; set or clear a loyalty member's minimum VIP tier; record progress towards a custom loyalty achievement. 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.
User ID and API key. In the Okendo app, go to Settings, then Integrations, then API. Copy the store's User ID and the 32-character key beside it.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Okendo for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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