Questions, answered.

Them AI brings people and AI teammates into one shared workspace. They work together in shared rooms, with approved company knowledge and reusable skills.

Keep the facts and decisions worth reusing as memory, and write repeatable methods as skills for the next person or connected agent.

AI teammates are built and trained in Them AI. Give each a job, choose its model, and choose the person it runs with. For example, Riley can prepare a support reply while Jamie drafts the handoff.

External agents run in other tools and connect through MCP, a protocol for sharing tools and context. Each connection has its own key and access scope. Workflows put steps in order and can pause for a person's approval.

By default, a teammate reads approved shared company memory and its assigned room's data. Access to additional rooms needs an explicit grant. Shared company memory can be turned off for a teammate.

Client boundaries still apply. Human workspace access is organization-wide, so these AI retrieval settings do not make a room private to selected people.

Yes. A teammate can use the workspace default or a configured model connection. A workspace key uses your account with the selected provider. Without a workspace model key, the platform default uses Google (Gemini) under Them AI's account.

If an authorized member enables platform fallback for a connection, an unsuccessful request may be retried through that platform account. A configured connection without this permission does not use platform fallback. Changing the model does not change data permissions or human approval requirements. Read about model processing.

Give a teammate an example, explain the correction, and review the training rule it proposes. An approved rule guides that teammate's later work. It does not automatically become a rule for every teammate.

Your team can separately review useful facts as shared memory and repeatable methods as shared skills. This reuses knowledge and instructions; it does not retrain the underlying model after each conversation.

Memory keeps facts, decisions, sources, and context. Skills preserve repeatable ways of completing work and making decisions.

Memory can tell an agent what happened last time. A skill helps it decide what to do this time.

No. You teach an AI teammate a job and a method, not a person's identity. Your team chooses which professional examples, decisions, and corrections to keep.

A useful training example might explain why a support lead checked payment settlement before promising a refund. It does not recreate that person's personality.

A chatbot usually helps one person in one conversation. Them AI is built for an entire team.

People and several AI teammates share rooms, context, decisions, and reusable skills. What the team approves can improve how every authorized agent works.

Yes. Authorized people can review, approve, correct, and assign owners to memories and skills. Roles control who can contribute, govern, manage connectors, and manage the team.

In the current beta, human room and memory access is organization-wide. Roles do not make individual rooms or client records private to selected members.

Yes. Them AI works with Claude, Cursor, and compatible MCP agents through an authenticated MCP connection.

Knowledge-only keys retrieve approved memory and approved skills. They cannot read room conversations or post messages. Keys with workspace access can also read permitted room conversations, post messages, and invoke AI teammates where allowed. Those conversations can contain messages that have not been approved as company knowledge.

Review the key's access mode and scope. Setup and available MCP features depend on the AI tool you use.

No. Human room and memory access, including drafts, is organization-wide in the current beta. A room name or client label is not a separate privacy boundary.

For approved knowledge retrieval, client-scoped MCP feeds limit agents to that client's approved records plus approved shared company material. Keys with workspace access can additionally read permitted room conversations, including unapproved messages. Check human access, key mode, and feed scope separately before importing client work. Read the access boundaries.

People with the required governance permissions can delete memory records and skills. Removing a connected source requires permission to manage connectors. Deleting a source stops future syncs but does not delete memories already created from it.

A client record with linked workspace records cannot be deleted while those links remain; it can be archived instead. Archiving does not delete the linked content. Ask your workspace administrator for help with permissions, or contact hello@usethem.ai about a personal-information request or deleting a whole workspace. Read the privacy policy.

External agents run in their own tools and can use Them AI as a source of approved context. Them AI does not host autonomous computer use or enforce approval on every action an external agent takes.

Keep the necessary review and access controls in the agent's own environment.

Native memory version history is not available in the current beta. Memory records can have supporting sources, an owner, approval status, and verification information.

A version in a source title, such as Discount policy v3, identifies that source. It is not a history of changes to the memory record.

No. Citations help you inspect supporting sources, but they do not guarantee that an answer or recommendation is correct, complete, or current.

Review the evidence and apply human judgment before relying on an output, especially for consequential decisions.

Teams that repeatedly need the context behind an answer: support and customer success, sales and marketing, consulting and advisory, and ecommerce operations.

Start with one recurring task, such as a support escalation, account handoff, or client brief, using material your workspace members are authorized to see. Explore the use cases.

Source connectors support Notion, Confluence, GitHub, Jira, and Linear, alongside document uploads and public pages. Setup and import options vary by source.

For a CRM, helpdesk, or commerce tool without a native connector, bring permitted notes or an export. A platform logo in an example does not mean automatic sync or write-back. Room bridges to Slack and Microsoft Teams are planned. See connection options.

Yes, that is the Call assist direction: prepare with the customer history, get automatic suggestions as the conversation unfolds, and review a follow-up afterward. Live suggestions are in development and are designed to surface relevant past cases, policy guidance and questions in a desktop overlay, without typing every prompt.

The current flow uses notes you provide. It does not join a meeting, capture live audio, or automatically update your CRM. You review the output and choose what to share. Explore Call assist.

Mac-only for now. Free during the beta (invite-only). Join the waitlist with your business email. Joining the waitlist does not provide immediate product access.

For a design partnership or a specific access question, contact hello@usethem.ai.