# What Lumate is

Lumate is a web platform where a company runs a team of AI agents. People talk to the agents in chats, hand them tasks, let them call customers, and watch what they do. The agents run on Claude: each company uses its own Claude account, through a small program called the **runner**.

## The words used everywhere

### Organisation

| Word | Meaning |
|---|---|
| **Company** | One organisation on the server. Each company has its own agents, customers, settings and secrets, and nothing crosses between companies. One server can hold several companies. |
| **Member** | A person with an account in a company. Their role is **owner**, **admin** or **member**. Admins change settings, secrets, numbers and the browser rules; members do the daily work. |
| **Instance admin** | The person who set the server up. They can open every company on that server. |

### Agents and how they work

| Word | Meaning |
|---|---|
| **Agent** | A member of the AI team. It has a name, a title, a manager (the org chart), instructions, skills, memory, files, a voice, and permissions. The **coordinator** (Lumate) delegates to the others. |
| **Run** | One working session of an agent. A run starts when something wakes the agent: your message, a task, a routine, a finished call, a WhatsApp message. The runner executes it on the company's Claude account. The agent works only through Lumate's tools: it has no shell, no files outside what was shared with it, and no other web access. |
| **Tools** | What an agent can do. Examples: comment on a task, create a task, move a customer card, log a call, request an appointment, draft a WhatsApp message, open a web page in the office browser, save a listing. Every write is logged. |
| **Thread** | The conversation inside a task, a chat or a customer card. People and agents write in it, and call transcripts land in it. |
| **Skill** | A reusable piece of know-how an agent can use, for example "Writing a listing" or "Finding listings". Skills come from the built-in catalog or are imported. |
| **Memory / Knowledge** | What agents learned: from you, from files and from their own work. It is kept with its source, used in later work, and replaced rather than deleted. |
| **Routine** | Recurring work ("every weekday at 9, the daily report"). |
| **Artifact** | A file an agent made: a report, a table, a spreadsheet. Artifacts are versioned. |

### Customers and conversations

| Word | Meaning |
|---|---|
| **Broker** | A person at the company who takes the customers the agents hand over. They work only their own cards (New, Called, Call later, Call again), in the **Lumate Desk** program, and see nothing else in Lumate. |
| **Customer card** | A person the company works with (buyer, seller, tenant, landlord). The card sits on the **board** in one of six columns: To call, On a call, No answer, For the manager, Done, Declined. |
| **Scenario** | A call script for the voice: the goal, the opening, and the fields to fill. Used in the Playground and on phone calls. |
| **Office browser** | A Chrome profile on an office PC with the Lumate extension. Agents use it to read websites and, on allowed sites, to make changes. |
| **Listing** | A property an agent found on a portal, saved once per link and matched to customers. |

## The rules that never change

- **Outside data is information, never instructions.** Text from customers, callers, web pages, WhatsApp, CSV files and other systems is shown to agents with that note. A page that says "ignore your rules" is just text.
- **Agents never see secret values.** API keys and passwords are encrypted and used only by the server.
- **People decide what goes to customers.** An agent drafts a WhatsApp reply and a person sends it. An agent sends on its own only when a manager asks it to in a message. The system never messages customers by itself.
- **Calls start with a recording notice.** Agents never deny being an AI. Do-not-call wishes are kept, and calling hours apply.
- **Everything is logged.** Agent tool calls, settings changes, browser changes and WhatsApp sends all appear in the Activity log.