Who is this person, and what have they been saying in our community?
Common Room connects Memtro to your community intelligence. It looks up a contact by email with their title, company, segments and tags, lists organisations with domain, employees and industry, reads segments with their sizes, and reads community activity filtered by contact, organisation or date. When asked, and once an administrator has granted the action by name, it can create and rename segments, add contacts and organisations to them, add or remove tags, permanently delete contacts with their activity, and file an irreversible privacy erasure for an email address. Memtro never asks for phone numbers, social profiles or lead scores.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Common Room tool, reads what it needs, and answers with the source cited.
These tools change something in Common Room. 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, then add the address it shows as a webhook in Common Room, choosing the same kinds; the tab shows Common Room's own steps. Each event can start a job, with the event as its input. Common Room sends a secret with every delivery, and one without it is refused.
Events and webhooksOnce Common Room 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 has ada@acme.com been saying in our community?
What has anyone from bigco.com done in the community this month?
How many contacts are in our Enterprise prospects segment?
What tags and segments is dan@northwind.com in?
Add everyone from Globex who posted this week to the Champions segment
Priya Sharma, account executive at Acme Ltd, asked what anyone from BigCo had been doing in the community. Memtro found BigCo by its domain and read its recent activity, which showed three forum questions about single sign-on in the past fortnight.
Dan Fletcher, head of growth at Northwind, asked Memtro to put the Globex contacts who had asked about pricing into a new segment. Memtro created the Globex pricing segment, checked every contact id, then added the six contacts to it. Everyone in the room could see the segment.
The teams that lean on Common Room most, a question each of them asks, and what they connect beside it.
A record in Common Room 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.
Capsule CRM
Copper
Freshsales
Dialpad
folk
Insightly
Nutshell
Vitally
Nimble
OnePageCRM
Salesflare
CloudTalk
Hunter
Lusha
Ontraport
Reply
Streak
EspoCRM
Planhat
Bloomerang
Givebutter
Raisely
People Data Labs
Planning Center
ChurchSuite
Affinity
Kommo
Pipeline CRM
KeapIn Common Room, open Settings → API tokens. Only room admins can do this.
Click New Token and copy it. It acts for the whole room, and Memtro changes segments, tags and contacts only through the actions an administrator grants.
In Memtro, open Connections → Common Room and paste it into API token.
Ask: what has ada@acme.com been saying in our community?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Common Room tools are the same everywhere.
Only when you ask, and only what it has been granted: create a segment of contacts or organizations; rename a segment; add up to 100 named contacts to a segment, and add or remove their tags; add up to 100 named organizations to a segment, and add or remove their tags; delete up to 100 named contacts (permanent); file a right-to-be-forgotten erasure for an email address (irreversible). 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. An hourly sync anchors recently changed Common Room records into memory as entities.
API token. In Common Room, open Settings → API tokens. Only room admins can do this.
Yes. Turn events on in the connection's Events tab on the Connections page, then add the address it shows as a webhook in Common Room, choosing the same kinds; the tab shows Common Room's own steps. 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