Canonical page: https://usethem.ai/ > Them AI brings people and AI teammates into one shared workspace. Build and train AI teammates, organize work in rooms, and keep approved company memory and reusable skills. Mac-only, invite-only beta. # People and AI teammates. One multiplayer platform. Build an AI team around the way your company works. Give teammates a job, bring them into shared rooms, and turn reviewed work into memory and skills. And get work done. [Join the waitlist](https://usethem.ai/#beta) [See a team at work](https://usethem.ai/#team-example) Mac-only for now. Free during the beta (invite-only). Image: The Them view of the app, with a shared room and a prepared reply awaiting human approval Your people and AI teammates, working together in shared rooms. Prepared work stays open for human review. Multiplayer by design. Keep what your team learns. Who is Them? ## You already know Them. Them is who... sees problems differently from everyone else has years of judgment your company depends on knows how things work beyond the process documents remembers why important decisions were made has expertise that would take years to replace knows what to do when there is no playbook They are the person everyone turns to when the obvious answer is not good enough. People like Them help build companies. Them AI helps their expertise keep building, and pass on to the next employees and the next AI teammates. The problem ## Transferring memory to AI is not enough. Expertise should also follow. Your company saves the work, but not the thinking behind it. The presentation survives, but not the reasoning behind it. The process document explains what usually happens, but not what actually happens. When a customer asks for an exception or when a complex problem shows up, a decision has to be made without enough information. That is when experience matters. But experience lives in people. In corrections. In conversations. In hundreds of decisions nobody thought to document. When those people leave, change roles, or simply forget, the company keeps the files but loses judgment. Image: A prepared reply and a workflow waiting for human approval in Them AI **Support desk** Reply review The customer cannot find their receipt. The team prepares a reply, keeps the payment settlement check open, and asks Maya to confirm the next step with billing before anyone sends it. Riley · support teammate Maya Chen · billing check Reply review · awaiting approval Files can tell an AI what happened, but Them AI helps it learn how your best people handled it. The multiplayer workspace ## Humans and AI in the same room. One workspace. Many minds. Create a room for a project and bring in the people who understand it along with AI teammates that can help. Then let them work together with the same context. Rooms hold conversations and data. AI teammates carry their own training. Shared company memory gives them a common starting point. [Explore rooms and access boundaries](https://usethem.ai/rooms/) or [find your use case](https://usethem.ai/use-cases/) . Image: People and AI teammates working around one table in a shared studio, with the Them AI heart logo on the wall 01 ### AI teammates Give Riley the support job and Jamie the handoff. Choose their models, add instructions, and teach each teammate through reviewed corrections. [Explore AI teammates →](https://usethem.ai/product/ai-teammates/) Image: The AI teammates directory in Them AI, with search, status filters and named teammates 02 ### Workflows Prepare the handoff, review the draft, then share it in the room. Turn those steps into a workflow with a person at the decision. [Explore workflows →](https://usethem.ai/product/workflows/) Image: The Workflows screen in Them AI, with saved workflows and their review steps 03 ### Company memory Keep the verified billing decision with its source and owner. The next teammate can use the approved record instead of asking the team to explain it again. [Explore company memory →](https://usethem.ai/product/company-memory/) Image: Company memory in Them AI, showing source records, owners and review status 04 ### Skills Teach the check behind the answer: confirm payment status before promising a refund. Review the method before reusing it. [Explore skills →](https://usethem.ai/product/skills/) Image: Skills and teammate training rules in Them AI with their scope and approval status 05 ### Rooms Keep the ticket, policy, conversation and draft in Support desk. Give people and assigned AI teammates a common place to work from. [Explore rooms and data access →](https://usethem.ai/rooms/) Image: A Them AI room showing a prepared draft waiting for human review 06 ### External agents Let a configured Claude or Cursor client use Them AI knowledge through MCP. Give each connection its own key and retrieval scope. [Explore integrations →](https://usethem.ai/product/integrations/) Image: External agent connections in Them AI with their key permissions and retrieval scope 07 ### Call assist An AI teammate designed to suggest what to ask, check or explain while you are on the call. Company knowledge, right beside the conversation. [Explore Call assist →](https://usethem.ai/call-assist/) The desktop overlay #### Keep the call in view. We are building live suggestions that appear in the overlay as the conversation unfolds. Relevant past cases, policy guidance and the next useful question, without typing every prompt. Image: Them AI Call assist collapsed to a compact bar with controls to expand or return to the workspace Image: Riley in the Them AI Call assist overlay, with Support desk selected and notes about a customer's missing payment receipt 08 ### Room bridges Planned One room, several destinations. Planned bridges will connect the same room to multiple Slack or Microsoft Teams conversations. [Explore room bridges →](https://usethem.ai/rooms/#room-bridges) Them AI room #### Support desk Riley Jamie Your team - Slack **Support team** - Slack **Account team** - Microsoft Teams **Customer success** One Them AI room. Multiple conversations in the tools your team uses. A teammate for research. Another for the draft. Your people make the final call. Your people guide the thinking. Correct the mistakes. Make the final call. When one person improves the way a problem is solved, the whole team can benefit from it. How Them AI learns ## The learning loop. Let one project teach the next. Review what worked, keep the evidence, and write down the method. Learning here means reusable knowledge and instructions, not retraining the underlying AI model. 01 Work together Ask in the room where the work belongs. Start from its data and approved shared company memory. 02 Teach a teammate Teach Riley to confirm payment settlement before promising a receipt or refund. Explain the check behind the reply. 03 Review the rule Review Riley's proposed training rule. It stays with that teammate and needs approval before it can guide future runs. 04 Apply it again Use reviewed instructions in later work. Keep approval steps where the decision needs a person. 05 Keep it current Review the sources and improve the guidance as things change. Knowledge and instructions stay separate from model training. Image: A prepared reply and a workflow waiting for human approval in Them AI Every correction should fix more than one answer. Review the lesson, then use it in the next piece of work. Different jobs. Shared company knowledge. ## Your AI team Riley prepares the support reply. Jamie handles the handoff. Each teammate has its own job, room and training, with shared company knowledge to work from. Image: Five illustrated Them AI teammates working together: Riley checks notes, Jamie shares a folder, Parker writes, Morgan plans a story and Sage reads with a bird perched on its head Explore a team ### Different jobs. One piece of work. Your people direct the teammates and make the final call. Support desk Room #### A billing question needs more than a quick reply. Start with Ticket notes + billing records + approved policy 1. [**Riley** Customer support](https://usethem.ai/use-cases/customer-support/) Prepare the reply. Flag the payment check. Gemini 2. [**Sage** Team knowledge](https://usethem.ai/use-cases/knowledge/) Find the policy and the reason behind it. Claude 3. [**Jamie** Customer handoffs](https://usethem.ai/use-cases/customer-success/) Prepare a handoff for the billing team. OpenAI **Shared company memory** Approved knowledge in common. A model and reviewed training for each teammate. Support lead decides Check the current payment record, review the draft, and send the answer from your support tool. [See the support workflow](https://usethem.ai/use-cases/customer-support/) ### What would you teach a teammate? “Confirm payment settlement before promising a receipt or refund.” Explain the correction to a teammate. Review its proposed training rule before reuse. [See how teaching works →](https://usethem.ai/product/skills/) Proposal desk Room #### Turn the discovery call into a proposal you can stand behind. Start with Discovery notes + approved offer + relevant past decisions 1. [**Parker** Proposals](https://usethem.ai/use-cases/sales/) Draft the scope around the buyer’s needs. Claude 2. [**Sage** Team knowledge](https://usethem.ai/use-cases/knowledge/) Find the approved terms and earlier decisions. Gemini 3. [**Jamie** Customer handoffs](https://usethem.ai/use-cases/customer-success/) Give the account team a clear next step. OpenAI **Shared company memory** Approved knowledge in common. A model and reviewed training for each teammate. Account lead decides Confirm scope, pricing and commitments. Share the reviewed proposal and update the CRM. [See the sales workflow](https://usethem.ai/use-cases/sales/) ### What would you teach a teammate? “Separate an approved offer from a customer request that still needs agreement.” Explain the correction to a teammate. Review its proposed training rule before reuse. [See how teaching works →](https://usethem.ai/product/skills/) Client engagement Room #### Use the firm’s experience without losing the client’s context. Start with Client brief + assigned room records + shared company methods 1. [**Sage** Team knowledge](https://usethem.ai/use-cases/knowledge/) Find earlier reasoning and check its relevance. Gemini 2. [**Parker** Proposals](https://usethem.ai/use-cases/sales/) Turn the brief into a proposed work plan. Claude 3. [**Morgan** Marketing](https://usethem.ai/use-cases/marketing/) Build the client narrative around evidence. OpenAI **Shared company memory** Approved knowledge in common. A model and reviewed training for each teammate. Engagement lead decides Check what applies to this client. Review the evidence, recommendation and final deliverable. [See the consulting workflow](https://usethem.ai/use-cases/consulting/) ### What would you teach a teammate? “Explain where a past approach fits this client, and where it does not.” Explain the correction to a teammate. Review its proposed training rule before reuse. [See how teaching works →](https://usethem.ai/product/skills/) Customer care Room #### Resolve the order question. Keep the promise realistic. Start with Order notes + return policy + product information 1. [**Riley** Customer support](https://usethem.ai/use-cases/customer-support/) Prepare a reply grounded in the return policy. Gemini 2. [**Jamie** Customer handoffs](https://usethem.ai/use-cases/customer-success/) List what fulfilment needs to confirm. OpenAI 3. [**Morgan** Marketing](https://usethem.ai/use-cases/marketing/) Draft a clearer explanation for shoppers. Claude **Shared company memory** Approved knowledge in common. A model and reviewed training for each teammate. Customer care lead decides Verify the current order and stock details. Decide on the remedy and make the update in your store tools. [See the ecommerce workflow](https://usethem.ai/use-cases/retail-ecommerce/) ### What would you teach a teammate? “Check order eligibility and stock before offering a replacement.” Explain the correction to a teammate. Review its proposed training rule before reuse. [See how teaching works →](https://usethem.ai/product/skills/) One customer question. A team behind the answer. ### Know what happened. Decide what happens next. A customer changed plans. The workspace updated, but the invoice did not. Your support rep brings the question into a room and puts the right teammates to work. The question > “My plan changed, but the invoice still shows the old one. Was I charged twice?” Zendesk Stripe Bring the ticket and billing records as notes or an export. Add the reviewed billing policy to the room. [Explore the support workflow →](https://usethem.ai/use-cases/customer-support/) 1. 01 · Ask Riley #### Separate facts from open checks. Riley uses the policy to prepare a reply. A plan change is not proof of a second charge, so payment status stays an open check. 2. 02 · Ask Jamie #### Give billing a useful handoff. The rep asks Jamie to turn those checked facts into a handoff: the issue, the evidence, and what billing needs to confirm. 3. 03 · Maya makes the call #### Check the record. Send the answer. Maya verifies the current invoice and payment record, reviews the draft, and sends the reply from the support tool. Human control ## You decide what it learns. ### Review the lesson A draft is not company guidance. A reviewer decides what becomes approved memory or a reusable skill. [How skills are reviewed →](https://usethem.ai/product/skills/) ### Know what is shared People in a workspace can read its rooms. AI teammates use shared approved company memory plus their assigned room context. [Understand room access →](https://usethem.ai/rooms/#boundaries) ### Scope outside agents MCP connections have their own keys and permissions. External tools control their own actions and approval steps. [Connect an external agent →](https://usethem.ai/product/integrations/) ## Start with one team. One real piece of work. Bring a support question, a sales handoff, or a client brief. Start with the sources and the person who knows what a good answer looks like. Mac-only for now. Free during the beta (invite-only). Want to shape a workflow with us? [Plan a pilot](https://usethem.ai/contact/#design-partner) . People move on. Expertise should stay and evolve.