Getting Started | Interloom

This guide walks you through the core process of working with Interloom: creating a space, building a workflow, configuring agents, and collaborating on cases.

Navigating the UI

The left sidebar has two tabs: Spaces and Assistant.

The Spaces tab is your command center:

• Home — your personal inbox showing assigned work, @mentions, and active cases
• Spaces — browse and open your organization’s spaces
• Team — find and manage people and AI agents in your organization
• Secrets — manage credentials for external integrations (SharePoint, custom APIs, and other configured tools)

The Assistant tab shows your Assistant Chat conversations with Odin.

Spaces

Spaces separate teams, departments, and use cases. A space is the top-level boundary and defines the environment, the available agents, and the data isolation.

Space Types

My Tasks: Your personal space. Only you (and your agents) can read and write here. It is created automatically and cannot be deleted. Any case not associated with another space lives here by default.

General: A shared system space available to everyone in the organization. Use it for cross-team collaboration or work that does not belong to a specific department.

Custom Spaces: The most common way to organize a business — create spaces for departments, projects, or client engagements with specific procedures, specialized agents, and membership-based access control.

Create a Space

1. Navigate to your organization in the sidebar
2. Click New Space. If you do not see this option, your organization may have disabled space creation for regular members; ask an owner or admin for access.
3. Give it a descriptive name and optional description
4. Invite team members by adding them as members

Note: Organization members can create custom spaces only when member space creation is enabled for the organization. If you cannot create a space, ask an organization manager or owner to enable it or create the space for you.

Workflows

The Workflows section is the “Architect’s Studio” for a space. It is where you define the automated logic, procedures, and rules that govern how work is executed. Triggers can be toggled on, allowing you to configure automated workflows for every new case in the space.

Follow Procedure: The library where you create, edit, and store procedures — standardized sets of stages used to automate recurring work. When enabled, every new case in the space automatically gets the procedure’s stages applied.

Auto-Assign: Assign a default agent to new cases in the space, so the right specialist is automatically tasked when a new case is created.

Create a Procedure

1. Open the Workflows section in your space

2. Click New Procedure and give it a descriptive name (e.g., “Customer Onboarding”)

3. Add stages in order — each stage defines one step in the workflow:

   • Title — a clear, action-oriented name (e.g., “Review incoming documents”)
   • Instructions — what needs to happen and what “done” looks like. Be specific about expected inputs and outputs
   • Assignee — the human or agent responsible for this step (optional)

4. Reorder stages by dragging them into the right sequence

5. Toggle Follow Procedure on to auto-apply the procedure to every new case in the space

When a procedure is applied to a case, each procedure stage creates a runtime stage on the case that tracks its own status and progress. You can also ask Odin in Assistant Chat to help you design a procedure — describe the workflow and it will draft stages and instructions for you.

For detailed guidance on writing effective procedures, see Best Practices.

Example: Customer Onboarding Procedure

Agents

Interloom agents are AI users assigned to cases or stages within a workspace. They execute instructions, use tools to interact with the platform, and collaborate with humans and other agents in a shared thread.

Native Agents

A built-in assistant is available out of the box:

• Odin — the primary assistant, specializing in procedure design, agent configuration, task planning, and general platform guidance. Odin is also the agent behind Assistant Chat, and can search the web for up-to-date information on behalf of your workflows

Custom Agents

You can create your own agents via New Agent in Team, if agent creation is enabled for organization members; otherwise, ask an organization manager or owner to enable it or create the agent for you. Each agent is configured with:

• Job description — what the agent should do, how it should respond, its expertise and boundaries
• Organization fields — optional job title, manager, and department details that describe where the agent fits in the organization
• Profile details — job title, department, and manager. If no manager is specified, the person creating the agent is set as the manager.
• Tool access — which platform capabilities it can use (e.g., create notes, search documents, manage tasks)
• Model and reasoning effort — which AI model powers the agent, plus an optional reasoning_effort for models that support reasoning. Use the model selector/model discovery to choose a supported model and available reasoning effort; unsupported reasoning efforts are rejected.

Every new agent starts with a read-only baseline — it can read notes and files, view a task and its thread, and use skills. You grant additional tools (writing, integrations, code execution, and so on) on top, per agent.

You can write the agent’s job description yourself or ask a native agent to help draft them based on the role you need.

What Agents Can Do

Beyond basic task management, agents have access to powerful capabilities depending on their tool grants:

• Show their reasoning — a thinking step reveals how the agent breaks a task down and picks its tools, so you can follow along and course-correct
• Search your document library — find information across all indexed files and notes
• Create and manage notes — capture analysis, working documents, and structured outputs
• Create subtasks — break work down and delegate to other agents or humans
• Move objects — move tasks between spaces or under parent tasks, move notes between spaces or task threads, move files between spaces or tasks, and move procedures between spaces; moving a procedure out of its auto-applied source space clears that source space’s auto-apply setting
• Manage private space membership — add or remove humans or agents from private spaces when access is needed for a workflow, while preserving at least one space member
• Manage tags — categorize cases, notes, and files for filtering and discovery
• Design procedures — create and edit procedures and their stages programmatically
• Run Python code — analyze data, transform documents, generate structured outputs in a sandboxed environment
• Connect to external systems — query Salesforce, search SharePoint, call GraphQL APIs, or define custom tools for other services
• Schedule messages — post a message to a thread later — once or on a recurring schedule — optionally @mentioning a person or agent, for reminders, follow-ups, or deferred work
• Draft and send emails — compose correspondence as part of a workflow
• Create and manage other agents — the assistant can help you build specialized agents

Tools are granted individually per agent — each agent only has access to the capabilities it needs for its role. Credentials for external integrations are stored as Secrets in the sidebar.

Cases

Cases are the primary unit of work in Interloom.

1. Inside your space, click New Case
2. Add a title — something specific like “Onboard Northwind Group” rather than “New customer”
3. If the space has a procedure configured, stages are created automatically
4. Assign the case to a user or agent, or leave it unassigned for the team to pick up. Assigning an eligible agent when the case is created, or reassigning an unconcluded case/subtask to an eligible agent later, invokes that agent to begin work.
5. Optionally set a due date for deadline tracking

Working on a Case

The case starts as open. When the first message is posted in the thread, the case moves to started, the first stage activates, and the assigned agent (if any) begins working.

If the case has stages, work progresses sequentially:

• The stage assignee works on the stage’s instructions
• When a stage completes, the next pending stage activates automatically
• If an agent gets stuck, it signals blocked and waits for human help

You can also manually control stages at any time — begin, complete, skip, or block a stage from the UI. This gives you full override capability over the automated flow.

For parallel work, create subtasks — each subtask has its own thread and lifecycle while the parent case’s stages continue sequentially.

Collaborate in the Thread

Every case has a Thread — a chronological timeline of everything that happens:

• Messages from human users and AI agents
• Status changes as the case progresses
• Assignee changes when a case is assigned, reassigned, or unassigned
• Stage transitions as stages start, complete, or are skipped
• Files attached — documents, images, data
• Notes created during the work
• Subtask updates as child tasks progress

The thread is the single source of truth for what happened, when, and by whom.

Completing a Case

Cases move through these statuses: open → started → completed. At any point a case can be blocked (needs intervention) or cancelled (no longer needed).

When all stages are done (or the work is otherwise finished):

• Complete the case — status moves to completed
• Cancel the case — status moves to cancelled if the work is no longer needed
• Block the case if it needs external intervention before it can continue

Document Library

Files uploaded to any space are automatically indexed and searchable. Agents can search the document library to find relevant information across all files they have access to — PDFs, spreadsheets, images, notes, and emails.

This means agents working on a case can draw on your organization’s full knowledge base, not just the files attached to that specific case.

Tags

Use tags to categorize and filter cases, notes, and files. Tags are short labels (e.g., “urgent”, “compliance”, “Q2”) that help you organize work across a space. You can add and remove tags manually or let agents manage them as part of a workflow.

Tags are searchable across the platform, making it easy to find all cases related to a specific topic or category.

Assistant Chat

You don’t always need a case to interact with an agent. Assistant Chat — your Private Assistant — gives you a direct conversation with Odin, the primary Interloom assistant. Open it from the sidebar, or in a sidecar panel alongside whatever you’re viewing. These chats keep their own history, separate from your case data.

Use it to:

• Design procedures — describe the workflow you need and Odin will draft stages, instructions, and agent assignments
• Create agents — explain the role you need filled and Odin will configure the job description and tool access
• Plan work — discuss a new case before creating it, or ask Odin to find similar past cases for reference
• Manage sidebar pins — ask Odin to inspect or update your pinned spaces and tasks in the sidebar for the current organization
• Learn the platform — ask questions about features, capabilities, or how to set things up

Assistant Chat is a good starting point when you are new to Interloom. Rather than configuring everything manually, describe what you want to achieve and Odin will help you build it.

Mentions

Use @mentions in thread messages to bring people and agents into a conversation:

• @mentioning an agent invokes it only if the agent is eligible for that case’s space. For private/custom spaces, the agent must be a space member; agents are not eligible for broad invocation in public spaces.
• @mentioning a human sends them a notification in their inbox when they are eligible for that space. In public spaces, all humans in the organization can be mentioned broadly.
• If you mention someone who is not a member of the case’s space, the thread will indicate that they need to be added to the space before they can participate or be notified

Next Steps

• Read Core Concepts to understand the full domain model — the environment tree, status lifecycle, stages, and how entities relate
• Explore Best Practices for tips on designing effective procedures and workflows
• Check the API Reference for programmatic access

Need Help?

Contact us at hello@interloom.com to get started with your first workflow.