Concepts
Surface
A place where work reaches the pod: Slack, Gmail, WhatsApp, Telegram, Teams, Outlook.
What a surface is
Without a surface, work only enters Lemma when someone types here. Connect Slack or Gmail and the pod’s agents can pick up messages, triage them, and reply — in the place your team already works. Each surface is wired to a specific agent, so you control exactly what handles inbound work.
For example
Connect the support Gmail inbox; the triage agent labels each email and files a row in the Tickets table.
Reach for it when
- Work arrives in Slack, email, WhatsApp, or Teams and someone copy-pastes it in.
- Customers or people on your team should reach the pod without learning a new tool.
- Approvals should be one click in the surface people already watch.
- You want the pod to reply where the conversation started.
Open the front door
- Open Surfaces and pick the surface where work already arrives.
- Connect the account and choose which agent handles inbound messages.
- Set the routing rules — which Slack channels, which mentions, which inbox labels.
- Send a test message from the surface and watch it appear in Conversations.
Where it lives
Surfaces in the left sidebar. Each card shows a surface, its status, and its routing.
Related concepts
| Concept | In short |
|---|---|
| Agent | An AI worker with a role, instructions, and scoped access to your tables, files, and apps. |
| Connector | An authenticated connection to a third-party app that agents and flows can act on. |
| Conversation | A thread between you (or a surface) and this pod’s agents, with every tool call visible. |