Deploy Field Agents
Interloom is the surface where a domain expert designs a workflow, lines up the agents that will run it, plugs in the tools the work needs, watches each case as it moves, and steers cost as the volume grows. Every part of the system is steerable in plain language, from one conversation with an assistant that sees what you see.
Describe to Automate
Everything in Interloom is constructed from natural language. A procedure is written the way you would explain it to a new colleague. An agent is briefed the way you would brief a contractor. The system reads what you wrote, builds what you described, and runs it.
Automation Primitives
An Interloom operation is built from a small set of named things. Learn three and you can read any workflow that runs through the system. Each one is the unit of a familiar idea, given a precise meaning the agents share with you.
A ticket. An order. A request. A question. A transaction. A claim. Each piece of work flowing through Interloom is a Case: a discrete unit with a status, a history, attached files, and a thread where humans and agents speak. The Case is the noun the rest of the system is in service of.
Field agents are the workers carrying out the operation. Given their own credentials and a narrow scope, they run autonomously, pulling from the memory of previous work, completing what was asked, producing the artifacts. When the work falls outside their scope, an agent raises its hand and pulls in the domain expert who briefed it. Autonomy and accountability, in one move.
A Procedure is a sequence of stages, each with its instructions, that defines how a class of Case is handled. Written in plain language, with deterministic scripts and tools dropped in where the work needs them. Agents and people pass the Case down the line. A Procedure is an assembly line that anyone in the operation can read.
Procedures, Up Close
A Procedure does not force you to pick a side. Any stage can be done by a person, an autonomous agent, or a deterministic script, and the system does not care which. You compose the line the way the work actually wants to be done.
Procedure · Insurance Policy Review
You describe each stage in the words you would use to brief a person. Interloom turns that description into a stage that runs.
For the parts that must not drift (a tax calculation, a schema validation, a webhook to a system of record), drop in a script or a tool as a stage.
An expert review is just another stage. The Case sits on your desk, you weigh in, and it moves on. The audit trail records the moment.
The Interloom Assistant
There is one assistant inside Interloom, and it can do anything Interloom can do. It sees what you see (the Space, the Case, the Procedure, last week's costs), so the same conversation runs the platform, designs it, and explains it. You do not learn an interface. You talk, and the interface obeys.
Integrations
Interloom connects to the systems your operation already runs on. The bundled set covers the common back-office surfaces (identity, mail, CRM, ERP, ticketing, document storage, messaging) with one-click setup, scoped credentials, and an audit trail of every agent call. Everything else is a sentence away: describe an internal API or a partner's webhook to the assistant, and the integration is built as a tool any stage can call.
Salesforce
Microsoft 365
Google Workspace
SAP
Jira
ServiceNow
Slack
Outlook
Bespoke
· · ·
Oversight
Out of the box, Interloom shows you everything that is happening, everything that has happened, and what each piece of the operation is costing you. The same surface you build the operation on is the one you watch it from. No separate analytics product to wire up, no warehouse to feed.
Production Grade
Three capabilities separate software that runs alongside a business from software the business runs on. The freedom to pick any frontier model and switch as the cost-quality tradeoff moves. Compute that runs in the cloud, without anyone's laptop open. And a schedule that keeps the operation moving in the hours nobody is at the desk.
Pick any of the top models from any of the frontier labs, and switch when the cost-quality tradeoff moves. A high-stakes adjudication stage might call the most capable model; a triage stage at scale might call the cheapest one that gets the answer right. The choice is set per Procedure, per stage, or per agent, and changes are live the moment you make them.
The economics of the operation are not bound to a single vendor. As the frontier moves, your unit costs move with it.
Send work off, walk away. An Interloom agent does not need your laptop open, your browser tab focused, or you logged in to keep working. Hand it a Case, a Procedure, or a question, close the laptop, and go to sleep. The agent runs in the cloud, on Interloom's compute, with its own credentials and its own session. By the time you are back at your desk, the work is done or waiting on your decision.
Always-on is the default. Field agents do not clock in. Nights, weekends, time zones, none of it matters. The operation runs at the cadence of the work, not the office.
Some work does not wait for a person to start it. A morning digest of yesterday's email. A weekly pass over the policy library to flag stale entries. A nightly sweep for regulatory updates in your jurisdictions. A reconciliation that runs on the first of the month. Schedule any of it in natural language and let the operation run itself in the hours nobody is at the desk.
Scheduled tasks are first-class citizens: same Procedures, same agents, same audit trail. The cadence is the only thing that changes.
A Standing Invitation
The fastest way to understand Interloom is to put one of your own workflows through it. Bring a process you wish someone else were running, and we will build the first version with you, in real time.