How is the Q4 NPS survey doing, and what did people say in it?
Qualtrics holds your surveys and what people said in them. Memtro lists the surveys your token's user can see, with their questions, reads distributions with their counts, and reads recent responses without IP address, location or recipient details. When asked and once an administrator has granted the action by name, it can email or text survey invitations, reminders and thank-yous to your contacts, which cannot be recalled once sent, create and change surveys and mailing lists, and record a response. Sending uses your licence's distribution quota or SMS credits. Deleting a survey, response or distribution is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Qualtrics tool, reads what it needs, and answers with the source cited.
These tools change something in Qualtrics. 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 Qualtrics 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.
How is the Q4 NPS survey doing?
What did people say in last week's responses to the onboarding survey?
How many people opened the reminder for the customer survey?
Which surveys are active right now?
Send a reminder for the Q4 NPS invite tomorrow at 9am.
Maya Okafor, Head of Customer Experience at Acme Ltd, asked how the Q4 NPS survey was landing. Memtro read the survey's distributions and set the invite beside the reminder, with sent, opened, started and finished counts for each.
Tom Reilly, Product Manager at Northwind, asked Memtro to remind customers who had not finished the onboarding survey. Memtro scheduled a reminder on the original email distribution for 9am the next day, and Qualtrics emailed it to the recipients who had not finished.
The teams that lean on Qualtrics most, a question each of them asks, and what they connect beside it.
A record in Qualtrics 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.
CallRail
Fullstory
WhatConverts
Lightdash
Microsoft Clarity
Eppo
Holistics
MouseflowIn Qualtrics, open Account Settings → Qualtrics IDs → API and generate a token. It acts as your user with no scopes, and generating a new one invalidates the old one at once.
Use a dedicated Qualtrics user for Memtro with access only to the surveys it should work with. Note the Datacenter ID in the User box, such as iad1 or fra1.
In Memtro, open Connections → Qualtrics and paste the API token and the Data centre.
Ask: How is the Q4 NPS survey doing?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Qualtrics tools are the same everywhere.
Only when you ask, and only what it has been granted: email a survey invitation to a contact, a mailing list or a transaction batch, or text it by SMS; email a reminder or a thank-you for an earlier distribution; generate personal survey links for a mailing list without emailing anyone; create an empty survey, or activate, deactivate, rename, set the open dates of or hand over a survey; create a mailing list, and add, change, opt out or remove a contact in one; record one survey response collected elsewhere; delete a distribution (cancelling it if not yet sent), a survey, or one response, permanently. 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.
API token and Data centre. In Qualtrics, open Account Settings → Qualtrics IDs → API and generate a token. It acts as your user with no scopes, and generating a new one invalidates the old one at once.
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
