Answering a customer fast
Priya Sharma, support agent at Acme Ltd, asked what the help centre said about changing a billing address. Memtro searched Helpjuice and quoted the matching public article with its link. She sent the link to the customer.
What does our help centre say about this?
Helpjuice connects Memtro to your knowledge base. It reads articles with audience, published or draft, views, dates, URL and text, runs full-text search, and reads categories with their article counts and users by name and role, never their email. The key acts as the account owner. When asked, and once an administrator has granted them by name, it can draft and edit articles, publish them, including to the public knowledge base, create, archive or change categories, and add, change, deactivate or reactivate users. Deleting an article or category is permanent, and edits to a published article reach readers at once.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Helpjuice tool, reads what it needs, and answers with the source cited.
These tools change something in Helpjuice. 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 Helpjuice 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 does our help centre say about resetting a password?
Which internal articles were updated since the start of the month?
How many draft articles are sitting in the Billing category?
Draft an article in Billing on changing your invoice address, using the steps I just gave you.
Publish the new returns article to the public knowledge base.
Priya Sharma, support agent at Acme Ltd, asked what the help centre said about changing a billing address. Memtro searched Helpjuice and quoted the matching public article with its link. She sent the link to the customer.
Dan Fletcher, documentation lead at BigCo, asked Memtro to turn the steps he had written for a customer into a help article. Memtro created a draft in the Billing category with the name and body he approved, then published it as public when he asked, putting it on the public knowledge base.
The teams that lean on Helpjuice most, a question each of them asks, and what they connect beside it.
A record in Helpjuice 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 Helpjuice, go to Settings → API Credentials and enable "Require token for API?".
Copy the API key. It acts as the account owner with no scopes, so it reads internal and private articles and every change Memtro is asked to make is made as the owner.
In Memtro, open Connections → Helpjuice. Enter Account, the name before .helpjuice.com such as acme, and paste the key into API key.
Ask a first question, such as "What does our help centre say about resetting a password?"
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Helpjuice tools are the same everywhere.
Only when you ask, and only what it has been granted: create a draft article in one or more categories; edit an article's name, description, slug, body or categories; publish or unpublish an article and set who can read it (public, internal, private, URL only); delete an article (permanent); create a category; rename, move, archive or change the audience of a category; delete a category (permanent); add a user to the knowledge base with a role; change a user's name, email, role or groups; deactivate a user so they lose access, or reactivate them. 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.
Account and API key. In Helpjuice, go to Settings → API Credentials and enable "Require token for API?".
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