# Understanding Your Usage
Source: https://docs.lindy.ai/account-billing/usage

How your team shares one pool of credits, why Lindy pauses on a heavy task, and what to do when you need more

<Frame>
  <img alt="Lindy pausing a heavy task in Slack and asking whether to continue" />
</Frame>

Your whole team draws from **one shared pool of credits**. Every seat adds to it, and every Lindy your team works with spends from it: the shared Lindy out in your channels, and the private Lindy in each person's DMs.

This page covers what actually uses credits, why Lindy sometimes pauses to check in, and what to do if your team needs more. For seats, pricing, and trials, see [Lindy Teammate Billing](/coming-soon/lindy-teammate-billing).

## Usage Warning: Why Am I Seeing This?

Lindy paused a task because it's using significantly more resources than usual. This is a **protection for your team**, not an error.

When a task starts drawing more from the pool than expected, Lindy stops and checks in before continuing. It asks right where you delegated the work: in the Slack thread if you @mentioned it in a channel, or in your DM if you asked there.

You can **continue** (the task finishes normally) or **stop** (no additional credits are used). If you stop, the thread stays open and you can pick it back up later.

<Tip>
  You're not doing anything wrong. The warning just makes sure your team stays in control of a pool everyone shares.
</Tip>

## Credit Usage by Feature

Every plan covers every feature. Nothing here is gated. What follows is a general sense of what each kind of work draws from your pool.

### Your team's Lindy, in your channels

Shared with the whole team, drawing on your approved team sources. This is where most of a team's credits go, because everyone @mentions the same Lindy.

| What Lindy does                                    | Credit impact |
| -------------------------------------------------- | ------------- |
| Answering a question from approved team sources    | Low           |
| Pulling a report or a lookup from a connected tool | Low           |
| Drafting a client update, summary, or document     | Moderate      |
| Team routines, priced by how often they run        | Moderate      |
| Deep research across channels and Drive folders    | **Varies**    |

### Your personal Lindy, in your DMs

Private to each person, and much lighter. These run on their own to keep you ahead of your day.

| What Lindy does                                             | Credit impact |
| ----------------------------------------------------------- | ------------- |
| Daily brief                                                 | Very low      |
| Email alerts on time-sensitive mail                         | Very low      |
| Open-loop nudges when an ask goes unanswered                | Very low      |
| Meeting prep briefings                                      | Very low      |
| Catch-up summaries when you're @mentioned in a busy channel | Low           |
| Meeting recaps and notes                                    | Low           |
| Ad hoc research you delegate in a DM                        | **Varies**    |

<Note>
  Both Lindys spend from the same pool. A busy channel where the whole team @mentions Lindy will move the number faster than any one person's DMs.
</Note>

**Most teams never come close to their limit.** Your pool resets every billing cycle, and unused credits do not roll over.

## Checking your usage

To see your workspace's total, go to **Settings → Billing** and scroll to the usage section.

To see it person by person, open **Settings → Members**. The **Credits** column shows what each teammate has drawn this cycle, and sorting by it is the fastest way to find out where your pool is going.

## Spend caps per teammate

Admins can cap how much any one person draws from the shared pool. It's the main tool for keeping one heavy user from spending the team's month.

<Frame>
  <img alt="Setting a per-teammate credit limit from the Members table" />
</Frame>

In **Settings → Members**, click the **⋯** menu on a row and choose **Edit credit limit**. When someone hits their cap, Lindy pauses that person's credit-using actions with a clear message and keeps working for everyone else. Leave a cap unset for unlimited draw.

## What Happens When Your Team Hits the Limit?

1. **Lindy pauses** until your next billing cycle.
2. **Your data and settings are safe.** Lindy won't automatically restart paused tasks, but nothing is deleted. Anyone can manually restart their own work once the pool resets.
3. **Your pool resets monthly** from your workspace's signup date.

<Accordion title="What if we need more before the pool resets?">
  Admins have three options:

  1. **Buy a top-up**: extra workspace credits at **\$10 per 1,000 credits**, in 1,000-credit blocks. Top-ups are a one-time buy and never touch your base plan's credits.
  2. **Upgrade the plan**: go to **Settings → Billing → Upgrade** to move to a higher tier on a month-to-month basis. Every seat on the new tier adds more credits to the pool.
  3. **Enable Overages**: in **Settings → Billing**, toggle on Overages to let Lindy keep working past the limit. Overage usage is charged at **2x the cost of regular Lindy credits**.
</Accordion>

<Accordion title="Does adding a teammate add credits?">
  Yes. Credits belong to the workspace, not to each person, and every seat adds its tier's allotment to the pool. A Plus seat adds 3,000, a Pro seat 15,000, and so on. Someone who joins by @mentioning Lindy in Slack gets a free first week before their seat converts to paid. See [Lindy Teammate Billing](/coming-soon/lindy-teammate-billing).
</Accordion>

<Accordion title="Will paused tasks pick up automatically?">
  No. When the pool resets, each person needs to manually restart anything that was paused. Nothing is lost: conversations, settings, and history are all preserved.
</Accordion>

If your team is regularly hitting the limit, [reach out](mailto:support@lindy.ai) and we'll find the right fit.

## Credit Optimization

Most teams never come close to their limit. If you want to stretch the pool further, these are the levers that make the biggest difference, in rough order of impact.

<AccordionGroup>
  <Accordion title="Scope your team sources tightly">
    The shared Lindy searches everything you've approved. Point it at the channels and Drive folders that actually hold your team's answers, not at the whole workspace.

    Open **Settings → Lindy Teammate → Team sources** and prune anything stale. A narrower set of sources is cheaper to search and gives better answers, so this is the rare lever that improves quality and cost at once.
  </Accordion>

  <Accordion title="Review team routines monthly">
    Team routines run on their own schedule whether or not anyone reads the result, and a workspace-wide routine spends for the whole team every time it fires. They're the easiest thing to set up and forget.

    Open the **Routines** page from the left sidebar and review both the **Team** and **Personal** tabs once a month. Flipping a routine off stops it without removing it, so you can turn it back on whenever you want. See [Routines](/coming-soon/routines).
  </Accordion>

  <Accordion title="Start a new thread for a new topic">
    Every message in a thread re-reads everything above it, so a long-running thread gets more expensive with each turn. This matters more in a busy channel than in a DM, because the whole team keeps adding to it.

    Starting a fresh thread for an unrelated topic keeps every conversation lean. You lose nothing: what Lindy knows from your team's sources carries across every thread.
  </Accordion>

  <Accordion title="Batch related asks into one thread">
    The flip side of the same rule. One thread per topic is the goal, not the fewest threads possible.

    If your team has five questions about the same account, ask them in one thread instead of opening five. If the next question has nothing to do with the last one, start fresh.
  </Accordion>

  <Accordion title="Be specific about what you delegate">
    Deep research is the row in the tables above whose cost genuinely varies, and vagueness is usually the reason. A precise brief tells Lindy when it's done; an open-ended one doesn't.

    * **Costs more**: "@Lindy research Acme."
    * **Costs less**: "@Lindy give me five bullets on Acme's funding history and their last two product launches."

    The same goes for length. If you want a short answer, say so.
  </Accordion>

  <Accordion title="Pick the right model">
    Advanced models earn their cost on hard reasoning and analysis. Routine work like summarizing, drafting, and lookups runs well on a cheaper one.

    Every plan gets every model, trial seats included, so this is purely a cost choice. Switch the model from the dropdown below the taskbar, then select **Set as default** to apply it to new conversations.
  </Accordion>

  <Accordion title="Remove seats you aren't using">
    A seat stays billed until an admin removes it, and you keep it through the end of the current cycle with no mid-cycle proration. When someone leaves the team, remove them in **Settings → Members**.

    If a removed person @mentions Lindy again, it tells them it can't help and pings an admin. It won't quietly re-add them.
  </Accordion>

  <Accordion title="Check usage weekly">
    A quick look at **Settings → Billing** once a week turns an end-of-month surprise into a small adjustment you make on a Tuesday. Sorting **Settings → Members** by the **Credits** column is how you notice one person or one routine burning more than you expected.

    Worth knowing: if your team goes over and has Overages enabled, that usage is charged at **2x** your plan's standard rate.
  </Accordion>
</AccordionGroup>

<Tip>
  You don't have to catch all of this yourself. If a single task starts running unusually heavy, Lindy pauses and checks in before continuing. See [Usage Warning](#usage-warning-why-am-i-seeing-this) above.
</Tip>

## Overages

If your team exceeds the pool's limit, overage usage is charged at **2x your plan's standard rate**.

## Relevant Docs

<CardGroup>
  <Card title="Lindy Teammate Billing" icon="credit-card" href="/coming-soon/lindy-teammate-billing">
    Seats, trials, top-ups, and your shared credit pool
  </Card>

  <Card title="Set up Lindy" icon="slack" href="/teammate/setup">
    Get Lindy into your team's Slack and connect your tools
  </Card>
</CardGroup>


# Export Docs for LLM
Source: https://docs.lindy.ai/export-full-docs





# Ad Hoc Tasks
Source: https://docs.lindy.ai/features/ad-hoc-tasks

Delegate research, knowledge lookups, and on-demand tasks to Lindy

## Your On-Demand Assistant

<div>
  <div>
    <video />
  </div>
</div>

Beyond running your inbox and meetings, Lindy handles one-off tasks whenever you need something done. Just ask.

<Note>
  **Works on both surfaces** — ask your own Lindy in a DM and the answer is yours alone. Ask in a [Slack channel](/teammate/slack-commands) and the whole channel sees the work, which is how the rest of the team picks it up.
</Note>

## Research

Lindy combines your **work context** (emails, meetings, calendar) with **deep web research** to give you thorough, relevant answers.

* **Prep for a meeting**: "Research \[company] before my meeting tomorrow." Lindy pulls company info, recent news, and cross-references with your past interactions
* **Industry research**: "What's the latest on \[industry topic]?" Web research grounded in what's relevant to your work
* **Summarize content**: Send any URL or YouTube link and get the key points back
* **Competitive intel**: "What is \[company] announcing this quarter?" Lindy finds public info and connects it to your deals and conversations
* **People research**: "What do I know about \[name]?" Lindy pulls from your emails, meetings, and the web

## Knowledge Bank

Lindy remembers everything from your past emails and meetings. Ask questions anytime:

* **Recall conversations**: "What did \[name] say about pricing in our last call?"
* **Find emails**: "Find the email where \[name] sent the contract"
* **Check history**: "When was my last meeting with \[company]?"
* **Surface action items**: "What were the action items from last week's team sync?"
* **Track commitments**: "What did I promise \[name] I'd send them?"

## Ask Lindy To...

<AccordionGroup>
  <Accordion title="Calendar and scheduling">
    * "Block 2 hours for deep work this week"
    * "Move my 3pm to Thursday"
    * "What does my week look like?"
    * "Schedule a 30-min call with \[name] next week"
    * "Cancel my meeting with \[name] tomorrow"
  </Accordion>

  <Accordion title="Email">
    * "Draft a reply to that last email from \[name]"
    * "Follow up with \[name] if they don't reply by Wednesday"
    * "What emails need my attention right now?"
    * "Draft a cold intro to \[name] at \[company]"
  </Accordion>

  <Accordion title="Meetings">
    * "Prep me for my next call"
    * "Research \[person/company] before my 2pm"
    * "Send \[name] a recap with next steps"
    * "What action items came out of today's meetings?"
  </Accordion>

  <Accordion title="Reminders">
    * "Remind me to follow up with \[name] on Thursday"
    * "Remind me every Monday to review my pipeline"
    * "Check in with me at 5pm about whether I finished the proposal"
  </Accordion>

  <Accordion title="Research">
    * "Summarize this" + paste a link
    * "What's \[company] been up to lately?"
    * "Find a restaurant near \[location] for a client dinner"
  </Accordion>

  <Accordion title="Daily habits">
    * "Send me my wins at 8pm every day"
    * "Text me my top 3 priorities every morning at 7am"
    * "Recap my day at 9pm as a voice note"
  </Accordion>

  <Accordion title="Tasks">
    * "Add \[task] to my to-do list"
    * "What's still on my list from this week?"
    * "What did I commit to after yesterday's meetings?"
  </Accordion>

  <Accordion title="Personal">
    * "Find a gift under \$100 for \[name]"
    * "Book a reservation for 2 at \[restaurant] Saturday night"
    * "What's coming up this week I might forget?"
  </Accordion>
</AccordionGroup>

<div>
  <img alt="Send reminders — Lindy: 'Don't forget to close the loop with Marketing!'" />

  <img alt="Organize & prioritize — Lindy: 'You're meeting with John from ACME, here's everything you need to know'" />
</div>

## Next Steps

<CardGroup>
  <Card title="iMessage & SMS" icon="message" href="/features/imessage-sms">
    Delegate to Lindy from your phone
  </Card>

  <Card title="Inbox Management" icon="inbox" href="/features/inbox-management/email-triage">
    How Lindy runs your inbox autonomously
  </Card>

  <Card title="Meeting Assistant" icon="video" href="/features/meeting-assistant/meeting-prep">
    Meeting prep, notes, and follow-ups
  </Card>
</CardGroup>


# Chrome Extension
Source: https://docs.lindy.ai/features/chrome-extension

Lindy runs inside Gmail. Triaged inbox, a morning brief, drafted replies, and a sidebar chat, all without leaving your tab.

## Lindy, Inside Gmail

Open Gmail and Lindy is already working. Your inbox is triaged with color-coded labels, a morning brief tells you what happened overnight, and every email that needs a response has a draft waiting. Everything's written in your voice and ready to send in one click.

<Note>
  **Your personal Lindy** — the extension works your own inbox, in your own voice. Nothing here is shared with your team. The Lindy your team shares lives in [Slack channels](/teammate/slack-commands).
</Note>

<Frame>
  <img alt="Lindy's new tab dashboard: a greeting, a chat bar, quick-action cards, upcoming meetings, and a daily activity summary" />
</Frame>

<Note>
  The Chrome extension is currently **Gmail only**. Outlook is coming soon.
</Note>

## Installing the Extension

<Steps>
  <Step title="Add Lindy to Chrome">
    Install the Lindy extension from the Chrome Web Store and pin it to your toolbar.
  </Step>

  <Step title="Open Gmail">
    Head to your Gmail tab. Lindy loads automatically inside the inbox.
  </Step>

  <Step title="Connect your account">
    Sign in with the Lindy account you use at [chat.lindy.ai](https://chat.lindy.ai). Your settings, labels, and drafting instructions carry over.
  </Step>
</Steps>

## What You Get

<CardGroup>
  <Card title="Triage labels" icon="tags">
    Every email is sorted and tagged with color-coded label pills before you open your inbox.
  </Card>

  <Card title="Morning brief" icon="sun">
    A daily card at the top of Gmail recaps what Lindy handled overnight.
  </Card>

  <Card title="Draft replies" icon="pen">
    Pre-written responses in your voice, with quick-action buttons to send in one click.
  </Card>

  <Card title="Compose bar" icon="wand-magic-sparkles">
    Rewrite, schedule, or ask Lindy anything right from the reply window.
  </Card>

  <Card title="Label learning" icon="graduation-cap">
    Lindy learns from how you re-label emails and gets better over time.
  </Card>

  <Card title="Sidebar chat" icon="comments">
    A floating or docked panel to chat with Lindy without leaving Gmail.
  </Card>
</CardGroup>

## Triage Labels

Lindy reads every incoming email and assigns it to the right category, shown as color-coded label pills right in your inbox list. Important messages stay front and center. Everything else gets filed away.

<Frame>
  <img alt="A Gmail inbox list with color-coded Lindy label pills: Calendar, FYI, To Respond, Comments, and Promotions" />
</Frame>

Your labels and categories are shared with your main Lindy settings, so anything you set up at [chat.lindy.ai](https://chat.lindy.ai) shows up in the extension too.

<Tip>
  Want to fine-tune your categories? See [Email Triage](/features/inbox-management/email-triage) for how labeling works and how to add your own.
</Tip>

## Draft Replies

Lindy drafts replies automatically, even if you don't have the Chrome extension installed. Open an email that needs a response, and your draft is already there, written in your voice.

The Chrome extension lets you refine that draft without leaving Gmail.

Use **Quick actions** like **Let's meet**, **Need time**, or **Not interested**, or simply ask Lindy to make changes. The draft updates instantly, right where you're working.

Review, edit, or send - nothing is ever sent without your approval.

<Note>
  Drafting works with or without the Chrome extension. The extension simply makes editing faster by letting you adjust tone, choose a quick action, or request changes directly inside the draft.
</Note>

<Frame>
  <img alt="A drafted reply in Gmail with quick-action buttons (Let's meet, Need time, Not interested) and the Lindy compose bar" />
</Frame>

<Tip>
  Drafts use the same drafting instructions as the rest of Lindy. See [Email Drafting](/features/inbox-management/email-drafting) to tune your tone, length, and sign-offs.
</Tip>

## Compose Bar

Lindy replaces Gmail's "Help me write" compose tool with an input that actually knows your context. From the reply window you can:

* **Rewrite**: reshape a draft to be shorter, warmer, or more direct
* **Schedule**: turn an email thread into a meeting
* **Ask anything**: type a request and Lindy handles it inline

Just type into the compose bar (*"Schedule, rewrite, or ask Lindy anything..."*) and Lindy takes it from there.

<Frame>
  <img alt="The Lindy compose bar with a typed request: 'Make it shorter and offer Thursday at 2.'" />
</Frame>

## Label Learning

When you re-label an email, Lindy notices. A toast confirms it learned from the change (*"Lindy learnt from your label"*), and future emails get sorted accordingly. Teach Lindy once, and it remembers.

<Frame>
  <img alt="An inbox row with a 'To Respond' label and a tooltip: 'Teach Lindy by changing this label'" />
</Frame>

## Sidebar Chat

A Lindy chat panel lives inside Gmail, floating or docked to the side. Ask Lindy anything without switching tabs. The sidebar supports:

* **Voice input**: speak instead of type
* **File attachments**: bring in documents for Lindy to work with
* **Model selector**: choose the model behind your chat

<Frame>
  <img alt="The Lindy sidebar chat panel inside Gmail, with a conversation and a task input bar with voice, attachments, and a model selector" />
</Frame>

## Security

Lindy is **SOC 2**, **GDPR**, and **HIPAA** compliant. See [Security](/resources/security) for details on how your data is handled.

## Next Steps

<CardGroup>
  <Card title="Email Triage" icon="inbox" href="/features/inbox-management/email-triage">
    How Lindy organizes and labels your inbox
  </Card>

  <Card title="Email Drafting" icon="pen" href="/features/inbox-management/email-drafting">
    How Lindy drafts replies in your voice
  </Card>
</CardGroup>


# iMessage & SMS
Source: https://docs.lindy.ai/features/imessage-sms

Text Lindy like a friend. Delegate work from your phone.

## Text Lindy, Anywhere

<Frame>
  <img alt="iMessage conversation with Lindy showing delegation over text" />
</Frame>

<Note>
  **Your personal Lindy** — texting reaches the Lindy that knows your email, calendar, and meetings. The Lindy your team shares lives in [Slack channels](/teammate/slack-commands).
</Note>

Lindy works over both **iMessage** and **SMS**, so you can delegate to your AI assistant right from your phone. No app to install. No dashboard to check. Just text it and it's done.

## Getting Set Up

Add your phone number during [signup](/start-here/quickstart) and verify with a confirmation code. That's it. Lindy sends you your first message, already personalized with context from your email and calendar. Just text back.

<Tip>
  If you skipped the phone number step during signup, you can add it anytime: click your workspace image at the top left, select **Settings** from the dropdown, and find it on the **General** settings page.
</Tip>

## What You Can Delegate

### Calendar & Meetings

* **Schedule a meeting**: "Set up a 30-min call with Sarah next Tuesday"
* **Ask about past meetings**: "What did we decide in last week's standup?"
* **Prep for your next meeting**: "Brief me on my 2pm meeting"

### Email

* **Let someone know you're running late**: "Tell my next meeting I'll be 5 minutes late"
* **Set up email alerts**: "Text me when I get an email from \[name]"
* **Search your inbox**: "Find the last email from \[name] about the proposal"

### Quick Tasks

* **Summarize a link**: Send a YouTube video or any URL and Lindy gives you the key points
* **Find contact information**: "What's \[name]'s email?"
* **Voice notes**: Send a voice note and Lindy transcribes and acts on it. You can also turn voice notes into Notion pages (requires Notion to be connected via text)

### Time & Priorities

* **Audit your time**: "How did I spend my time this week?"
* **Prioritize your day**: "What should I focus on today?"
* **React to changes**: "My 3pm cancelled, what should I do with that time?"

### Recurring Tasks

* **Daily briefings**: "Send me a briefing every morning at 7am" (includes your calendar, important emails, weather, and news)
* **Reminders**: "Remind me to follow up with \[name] on Friday"
* **Standing instructions**: "Every time I finish a meeting, send the notes to Slack"

<div>
  <img alt="Schedule an ad hoc meeting — 'add this to my cal'" />

  <img alt="Ask questions about past meetings" />
</div>

## Good to Know

<AccordionGroup>
  <Accordion title="Lindy gets better over time">
    The more you use Lindy, the better it understands your preferences, priorities, and communication style. Give feedback directly: "That draft was too formal" or "Always CC Becky on those."
  </Accordion>

  <Accordion title="Works on any phone">
    iMessage works on iPhone. SMS works on any phone. Lindy adapts to whichever you're using.
  </Accordion>
</AccordionGroup>

## Troubleshooting

### Lindy stopped responding

If Lindy stops replying to your texts, try these two steps in order:

1. **Re-verify your phone number.** Go to [chat.lindy.ai](https://chat.lindy.ai), click your username in the top-left, select **Settings → General**, and delete the phone number shown there. Then re-enter your number and verify with the code Lindy sends you.
2. **Wake the assistant from your phone.** Open [chat.lindy.ai](https://chat.lindy.ai) in your mobile browser, find your Lindy Assistant's contact card, and tap **"Start a conversation"** to send a quick hello. That refreshes the contact and wakes the assistant back up.

### Not receiving texts

If you're not receiving text messages, ensure your **Text message service** is aligned with your device settings. To update this, in Lindy's web UI, go to **Settings → General → Text message service**.

<Frame>
  <img alt="General settings showing Phone number and Text message service set to Auto (no preference)" />
</Frame>

The setting defaults to **auto**, but you can override it to match your mobile device. If you're on Android and want to use RCS, open the **Google Messages** app, tap your profile picture, go to **Settings → RCS chats**, and turn on **"Turn on RCS chats"**.

## Next Steps

<CardGroup>
  <Card title="Ad Hoc Tasks" icon="wand-magic-sparkles" href="/features/ad-hoc-tasks">
    Research, knowledge bank, and on-demand tasks
  </Card>

  <Card title="Inbox Management" icon="inbox" href="/features/inbox-management/email-triage">
    How Lindy runs your inbox autonomously
  </Card>

  <Card title="Meeting Assistant" icon="video" href="/features/meeting-assistant/meeting-prep">
    Meeting prep, notes, and follow-ups
  </Card>
</CardGroup>


# Email Alerting
Source: https://docs.lindy.ai/features/inbox-management/email-alerting

Lindy texts you when something time-sensitive hits your inbox, so you never miss what matters

<div>
  <div>
    <video />
  </div>
</div>

<Note>
  **Personal routine** — runs for you alone, in your own Lindy. Alerts go to you, on the rules you set. Routines that run for the whole team are [Workspace routines](/teammate/routines).
</Note>

## Never Miss the Urgent Stuff

Email alerting is a built-in **routine** that watches your inbox and pings you when something time-sensitive arrives, so you can stay out of your inbox without missing what matters.

## Before you start

* A connected **Gmail or Outlook** inbox.
* A plan with Assistant features.
* Not turned off by your workspace admin. If it is, the card shows **Disabled by admin**.

## Turn it on

<Steps>
  <Step title="Open the routine">
    Go to the **Routines** page. On the **Personal** tab, find the **Email alerting** card ("Alerts you to time-sensitive emails") and click it to open its drawer.
  </Step>

  <Step title="Flip it on">
    Use the enable switch. While the routine is off, its fields are greyed out, so turn it on first, then tune it.
  </Step>
</Steps>

## Tune your alerts

* **Alert instructions** — describe what counts as urgent. This drives what gets through:
  * **Time-sensitive meetings**: *"Only alert me about meetings within 30 minutes, or emails that seem extremely urgent."*
  * **VIP senders**: *"Alert me when I get an email from \[VIP client]."*
  * **Specific threads**: *"Alert me if someone replies to the proposal thread."*
* **Delivery channel** — where alerts go: a text message, a Slack DM, Lindy chat, or your default proactive channel.

## Connect another inbox

At the top of the drawer, each connected inbox shows as a chip, with a **+ Add account** button beside them. Click **+ Add account**, choose **Google** or **Outlook**, and follow the prompts to link another inbox. Settings are per-account, so pick the chip first, then edit.

<Tip>
  This pairs well with [iMessage & SMS](/features/imessage-sms). You get pinged on your phone and can reply to Lindy right there.
</Tip>

## Next Steps

<CardGroup>
  <Card title="Email Triage" icon="inbox" href="/features/inbox-management/email-triage">
    How Lindy labels and organizes your inbox
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/teammate/routines">
    Manage alerting and your other routines
  </Card>
</CardGroup>


# Email Drafting
Source: https://docs.lindy.ai/features/inbox-management/email-drafting

AI-drafted replies that land in your drafts folder, ready to review and send

<Frame>
  <img alt="A morning card from Lindy that reads Morning, Jane! Labeled 48 emails and drafted 5 replies, with important things to catch up on: a meeting request, payments due, and follow up needed" />
</Frame>

<Note>
  **Personal routine** — runs for you alone, in your own Lindy. Drafts land in your drafts folder in your voice, and nobody else sees them. Routines that run for the whole team are [Workspace routines](/teammate/routines).
</Note>

## Replies That Sound Like You

After [Email Triage](/features/inbox-management/email-triage) sorts your inbox, Lindy drafts replies for emails that need a response. Every draft lands in your drafts folder for you to review, edit, and send. Nothing goes out without your approval.

## Find it in Routines

On the **Routines** page, email drafting shows up as two built-in routine cards:

* **Email drafting** — "Allow Lindy to draft email responses with your tone and voice."
* **Follow-up bumps** — "Draft a bump when sent emails get no reply."

If you're coming from the old settings page, you'll hit a *"These settings moved to Routines"* card that links you straight here.

## Turn it on

Flip the **Email drafting** toggle to enable auto-drafting. While a routine is off, its detail fields are greyed out, so turn it on first, then tune it. Each card also has a **Learn more** link.

Once it's on, Lindy reads incoming emails that need a response, drafts a reply in your style, and saves it to your drafts. From there you review, tweak, and send.

## Tune your drafts

Click the **Email drafting** card to open it. You'll see:

* **Drafting instructions** — the main box. Describe how you want replies written: tone, formality, length, and when to draft versus skip. Saves automatically when you click out of the field.
* **Your signature** — your sign-off, shown above the Lindy line. Markdown is supported, so you can paste your Gmail signature or write a new one. Autosaves on blur.
* **Learned instructions** — the style Lindy has picked up from how you actually write. This one is different: it doesn't autosave. Edit it, then click **Save learned instructions** (the button stays disabled until you make a change).
* **Include "Sent with Lindy"** — keep or drop the Lindy footer on this inbox. This may not appear, depending on your rollout.

<div>
  <div>
    <video />
  </div>
</div>

The more specific your drafting instructions, the better the drafts. Worth spelling out:

* **Tone**: formal, casual, friendly, direct.
* **Length**: short and punchy, or thorough.
* **Sign-offs**: "Best," "Thanks," or your custom signature.
* **Rules**: who never to reply to, what to escalate instead.

Lindy also learns from your edits. Fix a draft before sending and it picks up on the change over time.

## Follow-up bumps

A separate routine drafts a bump when a sent email gets no reply. See [Follow-up Bumps](/features/inbox-management/follow-up-bumps).

## Connect another inbox

At the top of the drawer, your connected inbox shows as a chip (like `you@company.com`) with a **+ Add account** button beside it. Click **+ Add account**, choose **Google** or **Outlook**, and follow the prompts to grant access. You can connect as many inboxes as you like, across both providers.

Settings are per-inbox, so when you have more than one connected, select the account chip first, then edit. Drafting only works once a Gmail or Outlook account is connected.

## Next Steps

<CardGroup>
  <Card title="Email Triage" icon="inbox" href="/features/inbox-management/email-triage">
    How Lindy organizes your inbox
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/teammate/routines">
    Manage drafting, follow-ups, and your other routines
  </Card>
</CardGroup>


# Email Labeling
Source: https://docs.lindy.ai/features/inbox-management/email-triage

Lindy automatically labels and sorts your inbox so you start every day in control

<div>
  <div>
    <video />
  </div>
</div>

<Note>
  **Personal routine** — runs for you alone, in your own Lindy. Your labels and priorities apply to your inbox only. Routines that run for the whole team are [Workspace routines](/teammate/routines).
</Note>

## Your Inbox, Handled

Lindy reads every incoming email and labels it, archiving what you don't need to see and keeping what matters visible. No rules to write, no filters to manage. Email labeling is a built-in **routine**, so it runs automatically on incoming email.

## Before you start

* A connected **Gmail or Outlook** inbox.
* A plan with Assistant features.
* Not turned off by your workspace admin. If it is, the card shows **Disabled by admin**.

If no inbox is connected yet, you'll see a **Connect account** prompt first.

## Turn on email labeling

<Steps>
  <Step title="Open the routine">
    Go to the **Routines** page. On the **Personal** tab, find the **Email labeling** card ("Keeps your inbox organized"). Its badge shows the current state: **Off**, **On**, or **On for N of M accounts**. Click the card to open its drawer.
  </Step>

  <Step title="Flip it on">
    Use the enable switch in the drawer header, or the toggle on the card. Toggling from the card turns it on across all your connected inboxes at once.
  </Step>
</Steps>

<Warning>
  Turning it on does nothing until you've created at least one label.
</Warning>

## Connect and pick your account

At the top of the drawer, each connected inbox shows as a chip, with a **+ Add account** button beside them. Click **+ Add account**, choose **Google** or **Outlook**, and follow the prompts to link another inbox. Everything you edit applies to the selected account only, so pick the chip first, then edit. **Remove account** turns off every email routine for that inbox.

## Add and edit labels

<div>
  <video />
</div>

Two drag-and-drop sections, each with a **+** to add a label:

* **Move these out of my inbox** — Lindy applies the label and archives the email.
* **Keep these in my inbox** — applies the label but leaves the email in your inbox.

Drag a label between the two sections anytime to switch that behavior.

In the **New label** / **Edit label** dialog:

* **Name** — the label text. Reserved Gmail names like Inbox, Sent, or Spam are rejected.
* **Color** — pick a swatch.
* **Instructions** — the important one: describe when Lindy should apply it, like *"Any email from an investor."* This drives the classification.
* **Remove on reply** — optionally clear the label once you reply.

**Create label** / **Update label** saves immediately (Cmd/Ctrl+Enter works too).

### Default labels

Lindy starts with a set of labels you can keep, edit, or remove:

| Label             | What it catches                                  |
| ----------------- | ------------------------------------------------ |
| **To Respond**    | Emails that need a reply from you                |
| **FYI**           | Informational, no action needed                  |
| **Newsletters**   | Subscriptions and recurring content              |
| **Comments**      | Mentions, comments, and notifications from tools |
| **Notifications** | System alerts and automated messages             |
| **Invoices**      | Bills, receipts, and payment-related emails      |

<Note>
  Email labeling is a **built-in routine**, so it doesn't expose the custom-routine extras (trigger, schedule, delivery channel, smart filter, or run history). It just runs on every incoming email. Its siblings on the Personal tab are **Email drafting**, **Email alerting**, and **Follow-up bumps**.
</Note>

## Next Steps

<CardGroup>
  <Card title="Email Drafting" icon="pen" href="/features/inbox-management/email-drafting">
    How Lindy drafts replies in your voice
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/teammate/routines">
    Manage email labeling and your other routines
  </Card>
</CardGroup>


# Follow-up Bumps
Source: https://docs.lindy.ai/features/inbox-management/follow-up-bumps

Lindy drafts a follow-up when a sent email gets no reply, so nothing slips through the cracks

<Frame>
  <img alt="Routines page with an arrow pointing to the Follow-up bumps card, and the Draft follow-ups after setting highlighted with its options open" />
</Frame>

<Note>
  **Personal routine** — runs for you alone, in your own Lindy. It tracks the mail you sent, not your team's. Routines that run for the whole team are [Workspace routines](/teammate/routines).
</Note>

## Chase the Replies You're Owed

Follow-up bumps is a built-in **routine** that tracks the emails you've sent and, if one gets no reply, drafts a bump for you to review. You keep the final say before anything sends.

## Before you start

* A connected **Gmail or Outlook** inbox.
* A plan with Assistant features.
* Not turned off by your workspace admin. If it is, the card shows **Disabled by admin**.

## Turn it on

<Steps>
  <Step title="Open the routine">
    Go to the **Routines** page. On the **Personal** tab, find the **Follow-up bumps** card ("Drafts a bump when sent emails get no reply") and click it to open its drawer.
  </Step>

  <Step title="Flip it on">
    Use the enable switch. While the routine is off, its settings are greyed out.
  </Step>
</Steps>

## Set the timing

Set **Draft follow-ups after** to **Never**, **1**, **2**, **3**, **5**, or **7 days**. If a sent email gets no reply in that window, Lindy drafts a bump and saves it to your drafts for review.

This routine is independent of [Email drafting](/features/inbox-management/email-drafting), so you can run one without the other.

## Connect another inbox

At the top of the drawer, each connected inbox shows as a chip, with a **+ Add account** button beside them. Click **+ Add account**, choose **Google** or **Outlook**, and follow the prompts to link another inbox. Settings are per-account, so pick the chip first, then set the timing.

<Tip>
  Looking for post-meeting follow-ups? That's part of the Meeting Recording routine. See [Meetings](/teammate/meeting-library#post-meeting-follow-ups).
</Tip>

## Next Steps

<CardGroup>
  <Card title="Email Drafting" icon="pen" href="/features/inbox-management/email-drafting">
    How Lindy drafts replies in your voice
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/teammate/routines">
    Manage follow-up bumps and your other routines
  </Card>
</CardGroup>


# Daily Brief
Source: https://docs.lindy.ai/features/meeting-assistant/daily-brief

A personalized daily briefing on your day, meetings, and anything else you care about

<div>
  <div>
    <video />
  </div>
</div>

<Note>
  **Personal routine** — runs for you alone, in your own Lindy. Your brief covers your day and your meetings, and only you receive it. Routines that run for the whole team are [Workspace routines](/teammate/routines).
</Note>

## Start Every Day Knowing What Matters

Lindy can send you a daily brief on anything you prompt it to cover. Tell it exactly what you want: your schedule, who you're meeting, industry news, priorities. It arrives every morning before your day starts, in Slack or as a text on your phone.

## What You Can Include

Tell Lindy what to cover in your brief. Common topics:

* **Your schedule**: every meeting on your calendar with times and attendees
* **Meeting context**: who you're meeting and what you've discussed before
* **Industry news**: headlines and updates relevant to your work
* **Priorities**: a summary of open tasks, emails, or follow-ups
* **Weather**: local forecast for the day

For example:

> *"Brief me about my day, who I'm meeting with, and news regarding my industry."*

Lindy reads your calendar, pulls relevant context, and delivers a clean summary without you having to ask.

## What It Looks Like

<Frame>
  <img alt="A daily brief in a Slack DM from Lindy, marked as a daily 8:00 AM routine, with sections for your day, who you're meeting, and industry news" />
</Frame>

## How You Receive It

Lindy delivers your brief at your preferred time each morning: a Slack DM, a text to your phone (SMS / iMessage), or Lindy chat. There's nothing to check, it just shows up.

## How to Set It Up

Daily brief is a built-in **routine**. On the **Routines** page, open the **Personal** tab, find the **Daily briefs** card ("Prepares you for your day"), and toggle it on. Click the card to tune it.

<div>
  <div>
    <video />
  </div>
</div>

<Steps>
  <Step title="Write your prompt">
    Describe what you want Lindy to cover each morning. Be as specific as you like — topics, format, level of detail.
  </Step>

  <Step title="Set your time">
    Choose when Lindy texts you the brief. Most people set it 30–60 minutes after they wake up, so they start the day already on top of what matters.
  </Step>
</Steps>

## Next Steps

<CardGroup>
  <Card title="Meeting Prep" icon="clipboard-list" href="/features/meeting-assistant/meeting-prep">
    Automatic briefings before each meeting
  </Card>

  <Card title="Meetings" icon="video" href="/teammate/meeting-library">
    How Lindy records and summarizes your meetings
  </Card>
</CardGroup>


# Meeting Prep
Source: https://docs.lindy.ai/features/meeting-assistant/meeting-prep

Automatic pre-meeting briefings with attendee research, past context, and agenda

<div>
  <div>
    <video />
  </div>
</div>

<Note>
  **Personal routine** — runs for you alone, in your own Lindy. Your briefing covers the meetings on your calendar. Routines that run for the whole team are [Workspace routines](/teammate/routines).
</Note>

## Never Walk Into a Meeting Blind

Delegate meeting prep to Lindy. Before every call, a briefing lands in your inbox or on your phone with who you're meeting, what you've discussed before, and what's on the agenda. You don't have to ask.

## How to Set It Up

Meeting prep is a built-in **routine**. On the **Routines** page, open the **Personal** tab, find the **Meeting prep** card ("Gives context on your meetings"), and toggle it on. Click the card to choose which meetings get prep, when you receive it, and its format.

## What's Included

| Section              | Details                                                                  |
| -------------------- | ------------------------------------------------------------------------ |
| **Time**             | When the meeting is scheduled                                            |
| **Meeting name**     | The title and subject                                                    |
| **Attendees**        | List of all participants                                                 |
| **Attendee context** | For external attendees: job title, current company, and LinkedIn profile |
| **Past meetings**    | Summary of previous meetings with the same people (if recurring)         |

You can customize the prep format in your settings at [chat.lindy.ai](https://chat.lindy.ai). Look for **Meeting prep** in the settings panel. Describe your preferred structure, tone, and level of detail in the text field, and Lindy follows your instructions.

## Which Meetings Get Prep

* **All meetings**: every event on your calendar
* **External meetings only**: skip internal team syncs, focus on client and prospect meetings

## When You Receive Prep

<Note>
  To adjust these settings, go to the **Routines** page, open the **Personal** tab, and click the **Meeting prep** card. Set the time in the **Timing** field.
</Note>

<div>
  <div>
    <video />
  </div>
</div>

* **Daily digest**: receive all meeting prep at a set time each day (e.g., 5:00 AM)
* **Before each meeting**: receive prep a set number of minutes before the meeting starts (e.g., 15 minutes before)

You can enable one or both.

## How You Receive Prep

* **Email**: lands in your inbox
* **SMS / iMessage**: sent directly to your phone

<Note>
  To change how you're notified, go to the **Routines** page, open the **Personal** tab, and click the **Meeting prep** card. Pick where prep lands in the **Delivery channel** field.
</Note>

<div>
  <div>
    <video />
  </div>
</div>

## Customize Your Prep Format

You can write a custom prompt to control exactly how your meeting prep is written — including the tone, structure, and level of detail.

<img alt="Meeting prep routine settings with the Prep instructions field highlighted" />

To update it, go to the **Routines** page, open the **Personal** tab, click the **Meeting prep** card, and edit the **Prep instructions** field.

## Next Steps

<CardGroup>
  <Card title="Meetings" icon="video" href="/teammate/meeting-library">
    How Lindy records and summarizes your meetings
  </Card>

  <Card title="Daily Brief" icon="newspaper" href="/features/meeting-assistant/daily-brief">
    A morning brief on your day and meetings
  </Card>
</CardGroup>


# Meeting Recording
Source: https://docs.lindy.ai/features/meeting-assistant/meeting-recording

Lindy records and transcribes your meetings on Google Meet, Zoom, and Teams, and delivers custom summaries to a searchable library.

Meeting Recording is documented on the **[Meetings](/teammate/meeting-library)** page, alongside the meeting library, shared folders, and post-meeting follow-ups.

<Card title="Meetings" icon="video" href="/teammate/meeting-library">
  Recording, summaries, shared folders, and everything Lindy does after a call
</Card>


# Smart Scheduling
Source: https://docs.lindy.ai/features/meeting-assistant/scheduling

Find times, send invites, and lock in meetings. No more back-and-forth.

<div>
  <div>
    <video />
  </div>
</div>

<Note>
  **Personal routine** — runs for you alone, in your own Lindy. It books against your calendar and your availability. Routines that run for the whole team are [Workspace routines](/teammate/routines).
</Note>

## Let Lindy Handle Scheduling

Just delegate the meeting. Lindy finds the time, sends the invite, and puts it on your calendar. No scheduling links, no back-and-forth emails.

## Three Ways to Schedule

However a meeting comes up, Lindy can handle it. Pick whichever fits the moment:

<div>
  <a href="#1-cc-based-scheduling-coming-soon">
    <Icon icon="envelope" />

    <span>CC-based scheduling</span>
  </a>

  <a href="#2-drafting-scheduling">
    <Icon icon="pen" />

    <span>Drafting scheduling</span>
  </a>

  <a href="#3-ad-hoc-scheduling">
    <Icon icon="comments" />

    <span>Ad hoc scheduling</span>
  </a>
</div>

## Set Your Availability

Lindy books only within the availability you set, so every option below lands on a time that actually works for you. Set your rules in plain language: preferred hours, buffers between meetings, blocked times, default meeting length, and meeting types. Update them anytime, and they apply to all three ways to schedule.

<Note>
  Meeting scheduling is a built-in **routine**. On the **Routines** page, open the **Personal** tab and click the **Meeting scheduling** card to turn it on and set your hours, buffers, and calendar rules.
</Note>

## 1. CC-Based Scheduling (Coming Soon)

CC your Lindy assistant's email address on any thread where you're trying to find time, and Lindy takes over as your scheduling assistant. It reads the thread, checks your calendar, and handles the rest: no questions, no back-and-forth.

<div>
  <span>Your Lindy assistant email is</span>
  <a href="mailto:lindy@lindy.ai">[lindy@lindy.ai](mailto:lindy@lindy.ai)</a>
</div>

<Steps>
  <Step title="CC Lindy on a scheduling thread">
    Add your Lindy email address to the **CC line** of an email where you and the other person are trying to find a time. The CC is the signal for Lindy to step in.
  </Step>

  <Step title="Lindy reads the thread and takes over">
    Lindy pulls the details from the thread (duration, date range, time of day, attendees, timezone) and fills any gaps with sensible defaults. If you've already agreed on a time, it books it. If not, it replies once with 3 open slots as clickable links.
  </Step>

  <Step title="The meeting gets booked">
    The meeting books automatically on your calendar with invites sent, exactly like Smart Scheduling above.
  </Step>
</Steps>

### Two ways it plays out

**When the time's already agreed**, Lindy books it. **When you still need a time**, Lindy proposes three slots. Either way, the Cc is all it takes.

<div>
  <div>The time's already agreed</div>

  <img alt="Three steps of CC-based scheduling: James emails suggesting a specific time, you reply with lindy@lindy.ai on the Cc line, and Lindy replies confirming it booked the meeting and sent the invite" />
</div>

<div>
  <div>You still need to find time</div>

  <img alt="Three steps of CC-based scheduling: James emails asking to find time next week, you reply with lindy@lindy.ai on the Cc line, and Lindy replies offering three available times" />
</div>

<Note>
  Lindy only acts when **both** are true: your Lindy email is on the CC line, **and** the thread shows scheduling intent ("let's find time", "can we grab 30 min?"). CC without a scheduling ask, or a scheduling ask without the CC, won't trigger it.
</Note>

<Tip>
  Want to constrain the options? Just say so in the thread ("mornings only", "next week", "30 min"). Otherwise Lindy uses your standard meeting length, working hours, and buffers.
</Tip>

## 2. Drafting Scheduling

When someone emails you about scheduling a meeting, Lindy detects the request and offers times in a draft reply on your behalf. Your recipient picks one in a single click and the meeting drops onto both calendars.

* When someone emails to schedule, Lindy offers times in a draft reply
* Recipients book a slot in one click, with no back-and-forth
* Save \~3 minutes per invite

<Steps>
  <Step title="Someone emails you asking for a time to meet">
    Lindy detects the scheduling request and takes over, with no action needed from you.

    <img alt="Incoming email requesting a meeting" />
  </Step>

  <Step title="Lindy drafts a reply with 3 available times">
    Based on your preferred hours, buffer time, meeting length, and calendar availability, Lindy drafts a reply with three open slots as clickable links.

    <img alt="Lindy's draft reply with 3 available time slots" />
  </Step>

  <Step title="They click a time and it's instantly booked">
    When the other person clicks a link, the meeting is automatically added to both calendars. No back-and-forth, no scheduling tools, no manual entry.

    <img alt="Meeting booked on calendar after clicking a time slot" />
  </Step>
</Steps>

## 3. Ad Hoc Scheduling

When you want Lindy to handle scheduling on your behalf, just ask. Text or message it and it finds the time, reaches out, and locks it in.

<Frame>
  <img alt="Texting Lindy 'Set up time with Matt to review the proposal' and getting back 'Done. Reached out to Matt with a few options.' alongside Lindy's drafted Gmail reply with time slots" />
</Frame>

### Add or Update Events on the Fly

Use Lindy to add events to your calendar or change them with one line of text:

* "Add a meeting location"
* "Pick a restaurant for the client dinner"
* "Swap the venue and notify attendees"
* "Move my 2pm to Thursday"
* "Cancel my call with \[name]"

Send Lindy a screenshot of a text conversation and it pulls the meeting details onto the right day.

### End-to-End Outreach

Or send Lindy on a mission and let it run the whole loop:

> "Find time with Bob on Saturday"

It reaches out, proposes times, locks the meeting in, and adds it to your calendar.

### Recurring Routines

Set up recurring workflows with one text:

> "Every week, audit my calendar and make sure I have a 45-min walk break at least once a day"

### Internal Calendars

Lindy can check any teammate's calendar that's shared with your workspace, so you can ask it to find time between people on your team without any back-and-forth.

<Frame>
  <img alt="Texting Lindy 'help me find 15 to meet with Alice' and getting back an 'Added Thursday' card with a Proposal follow up event Thursday 10:30 - 10:45 AM, You + Alice, created by Lindy" />
</Frame>

### How to Delegate

* **iMessage / SMS**: "Book a call with Sarah next Tuesday afternoon"
* **Web app**: chat at [chat.lindy.ai](https://chat.lindy.ai)

<Tip>
  Scheduling over text is the fastest option. Lindy already knows your calendar and preferences, so a simple text is all it takes.
</Tip>

## Next Steps

<CardGroup>
  <Card title="Meeting Prep" icon="clipboard-list" href="/features/meeting-assistant/meeting-prep">
    Get context before every meeting
  </Card>

  <Card title="iMessage & SMS" icon="message" href="/features/imessage-sms">
    Everything you can delegate by texting Lindy
  </Card>
</CardGroup>


# What is Lindy?
Source: https://docs.lindy.ai/index

The AI teammate that makes the whole team better. It lives in Slack, knows everything your company knows, and does the actual work.

<Frame>
  <img alt="The Ultimate AI Teammate, ringed by the tools it connects to — Asana, HubSpot, Zoom, Gmail, GitHub, Stripe, Zendesk, Notion, Linear, and Salesforce — above a Slack workspace where Leo asks in #growth why Google Ads CAC spiked yesterday and Lindy answers that Retargeting-Broad ate 38% of spend at 3x CAC" />
</Frame>

## The AI teammate that makes the whole team better

Lindy Teammate lives in Slack and knows everything your company knows. Everyone gets a private Lindy in their DMs. The whole team shares one in channels.

Most teams already have AI, and almost none of it adds up: private chat histories, one person's clever setup living in one person's tab, everyone starting from zero every time.

Lindy is the one they share. Skills, routines, and recorded meetings belong to the workspace, not to whoever set them up, so one person teaching it something leaves the whole team better at their job.

## Finished work, not just an answer

Ask from Slack and Lindy doesn't hand you something to go do. It updates the forecast tab, writes the recap doc, enriches the contact record, files the notes where the team already looks. Write actions always wait for your approval, so nothing ships without you.

## What the team shares

Four things belong to the workspace, not to whoever set them up. This is the part that compounds.

<CardGroup>
  <Card title="Skills" icon="graduation-cap" href="/teammate/skills">
    Named playbooks for how you work. Install a built-in or write your own, and Lindy reaches for the right one on its own
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/teammate/routines">
    Standing work that runs on a schedule or a trigger, for one person or the whole team
  </Card>

  <Card title="Files" icon="files" href="/teammate/files">
    Lindy's memory, in plain files you can open and edit
  </Card>

  <Card title="Meetings" icon="video" href="/teammate/meeting-library">
    Every call recorded, transcribed, and filed into folders anyone can question
  </Card>
</CardGroup>

Open any of them to the team and a new hire inherits months of context on their first day.

## Use cases

Not just quick answers. Lindy helps your team tackle more.

### Find answers

Ask across Slack, meetings, and your tools. Lindy digs up the answer and the file or decision behind it.

<Frame>
  <img alt="Lindy in #launch: asked where the team landed on the launch date, it answers the 21st, decided in #product Tuesday, with the docs already updated" />
</Frame>

### Build decks

Hand Lindy the deck. It pulls from your meetings and tools and comes back with slides, charts, and commentary, ready to present.

<Frame>
  <img alt="Lindy in #all-hands: asked to bring together the all hands deck, it pulls this month's meetings from three tools and returns a 12-slide All Hands deck with charts and commentary, ready to present" />
</Frame>

### Investigate

Ask why a number moved. Lindy traces it across analytics, code, and tickets to the root cause, with the fix ready.

<Frame>
  <img alt="Lindy in #growth: asked why signup conversion dropped, it traces the cause across four tools to a broken email verification step after Tuesday's deploy, writes up the root cause, files a ticket, and flags the deploy in #eng" />
</Frame>

### Pull reports

The daily or weekly numbers, pulled from your ad, CRM, and finance tools into a live report, with anything off-target flagged.

<Frame>
  <img alt="Lindy in #metrics: asked for this week's ad spend report, it pulls spend from three tools and returns $8.4k spend, 3.1 ROAS, and $38 CPA, with Retargeting Broad flagged at $81 CPA, 2.1x target" />
</Frame>

### Handle busywork

The CRM updates, the handoff doc, the follow-ups. Lindy runs the multi-step work nobody wants to.

<Frame>
  <img alt="Lindy runs a deal-won handoff: updates HubSpot, creates the Notion doc, posts to customer-success, schedules the kickoff, and sends the welcome email" />
</Frame>

### Catch up

Been out, or dropped into a busy channel? Lindy gives you the TL;DR and exactly what needs you.

<Frame>
  <img alt="Lindy summarizes the #launch channel: launch moved to Thursday, design and legal signed off, and flags that you need to approve the email by tomorrow" />
</Frame>

## Connected to everything

<div>
  <a href="/integrations/overview"><span>1,000+ tools.</span> <span>Gmail, Slack, Notion, HubSpot, Salesforce, Snowflake, plus any MCP server.</span></a>
  <a href="/integrations/overview"><span>It knows how they fit together.</span> <span>One answer, cross-referenced from three tools, not three separate lookups.</span></a>
  <a href="/integrations/credentials"><span>It works inside them.</span> <span>From your analyst's warehouse to your rep's CRM, with each person's own credentials.</span></a>
</div>

## Security by design

Compliant, private, and in your control. Three separate promises, and Lindy keeps all of them.

<div>
  <div><Icon icon="shield-check" /><div><span>Compliant</span><span>AICPA SOC 2, GDPR, HIPAA, and PIPEDA. Enterprise adds SSO, SCIM, and HIPAA with a signed BAA.</span></div></div>
  <div><Icon icon="lock" /><div><span>Private</span><span>Encrypted in transit and at rest, never sold, and never used to train models. Your DMs and personal context stay yours.</span></div></div>
  <div><Icon icon="user-shield" /><div><span>In your control</span><span>Nothing irreversible without your approval. Lindy preps the work, you approve it, then it ships.</span></div></div>
</div>

[See how we protect your data →](/resources/security)

## Works wherever you work

<div>
  <a href="/teammate/setup"><Icon icon="slack" /> Slack</a>
  <a href="/features/imessage-sms"><Icon icon="message" /> iMessage</a>
  <a href="/features/chrome-extension"><Icon icon="chrome" /> Chrome extension</a>
</div>

## Up and running in minutes

<Steps>
  <Step title="Add it to Slack">
    One click from the Slack marketplace. The whole team gets Lindy at once.
  </Step>

  <Step title="Authorize your tools">
    Connect your tools and Lindy sorts out the permissions. No API keys, no IT ticket.
  </Step>

  <Step title="@mention it">
    Tag Lindy in any channel or DM, and it starts working.
  </Step>
</Steps>

<CardGroup>
  <Card title="Quickstart" icon="rocket" href="/start-here/quickstart">
    Get your team running in minutes.
  </Card>

  <Card title="Pricing" icon="tag" href="/pricing">
    Simple per-seat pricing.
  </Card>
</CardGroup>

## Built for the whole team, private by default

Your DMs and email stay yours. Meetings are private unless you share them. Your data is never sold or used to train models.

* **SOC 2 Type II** compliant
* **HIPAA** compliant
* **GDPR** compliant
* **AES-256** encryption

[Learn more about security](/resources/security)

***

## Need help?

* **Email:** [support@lindy.ai](mailto:support@lindy.ai)
* **Join a group onboarding session:** [luma.com/getlindy](https://luma.com/getlindy)


# Credentials
Source: https://docs.lindy.ai/integrations/credentials

Save an API key once, keep it for yourself or share it with the workspace, and let Lindy use it without anyone pasting it into a chat.

<Frame>
  <img alt="The Credentials page in Settings, listing stored credentials with their host, visibility, and status" />
</Frame>

Some tools don't hand you an OAuth button. They hand you an API key. A credential is where that key lives: you save it once, Lindy uses it when it needs it, and nobody has to paste the key into a message again.

Credentials are what Lindy reaches for **when it runs shell commands and code**. If you've asked it to hit an API directly rather than through a connected tool, this is where the credential for that call comes from.

A credential starts as **yours**. Save a key and only you can use it, until you choose to share it with everyone in the workspace.

## Adding a credential

<Steps>
  <Step title="Open Credentials">
    Go to **Settings**, then **Credentials** under **Workspace**.
  </Step>

  <Step title="Add a new credential">
    Click **Add credential**, then fill in the name and the value.
  </Step>

  <Step title="Save">
    The credential is available to your agents right away.
  </Step>
</Steps>

The name is how you and Lindy refer to the key later, so make it obvious what it opens. Existing credentials follow `SCREAMING_SNAKE_CASE`:

| Good                    | Why                                       |
| ----------------------- | ----------------------------------------- |
| `NOTION_API_KEY`        | Names the tool and the kind of credential |
| `STRIPE_RESTRICTED_KEY` | Distinguishes it from a full-access key   |
| `key1`                  | Tells you nothing six months from now     |

## Reading the list

Each row tells you two things: what the credential is, and whether it's working.

| Column                        | What it shows                                                                                               |
| ----------------------------- | ----------------------------------------------------------------------------------------------------------- |
| **Name and service**          | The credential's name, the host it applies to, and who can use it: **Only me** or **Shared with workspace** |
| **Authentication and status** | Whether it's **Available to agent**, whether it's **Active**, and when it was last updated                  |

A rotated credential is easy to spot: its updated time moves, its name doesn't.

## Rotating and sharing

Open the **...** menu on any credential row.

<Frame>
  <img alt="The actions menu on a credential row, offering Rotate value, Share with workspace, and Revoke" />
</Frame>

| Action                   | What it does                                                                                                                                                                        |
| ------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Rotate value**         | Replaces the key with a new one. The name stays the same, so nothing that refers to the credential needs to change.                                                                 |
| **Share with workspace** | Hands the credential to everyone in the workspace. The row flips from **Only me** to **Shared with workspace**, and other people's agents can use it without ever seeing the value. |
| **Revoke**               | Removes the credential. Anything relying on that key stops being able to authenticate, so rotate rather than revoke if the tool is still in use.                                    |

<Tip>
  Rotating and sharing are separate decisions. Rotating a shared credential keeps it shared: everyone simply starts using the new value.
</Tip>

## What Lindy shows you, and what it doesn't

A saved credential's value is **write-only**. You can see that a credential exists, what it's called, who it's shared with, and when it was last updated. You cannot read the value back: not in the app, not through the API, not by asking Lindy.

| You can see              | You cannot see         |
| ------------------------ | ---------------------- |
| The credential's name    | The credential's value |
| Its host and visibility  |                        |
| When it was last updated |                        |

<Warning>
  Because values can't be read back, Lindy has no "show me the key" escape hatch. Keep the original somewhere you control, like a password manager. If you lose it, rotate the credential with a fresh key from the tool it came from.
</Warning>

## Credentials and integrations

Credentials and [integrations](/integrations/overview) solve the same problem from different ends.

|                          | Integration                               | Credential                             |
| ------------------------ | ----------------------------------------- | -------------------------------------- |
| **How you connect**      | OAuth, or an API key entered during setup | An API key you save yourself           |
| **Scope**                | Personal, or shared with the team         | Personal, or shared with the workspace |
| **Guardrails apply**     | Yes                                       | No                                     |
| **Value readable later** | No                                        | No                                     |

If the tool you want is already in the integrations list, connect it there. Reach for a credential when the thing you're calling has no integration of its own.


# MCP servers
Source: https://docs.lindy.ai/integrations/mcp

Point Lindy at a hosted MCP server and it builds actions from the tools that server publishes.

<div>
  <div>
    <video />
  </div>
</div>

The [built-in integrations](/integrations/overview) cover the tools most teams use. MCP covers the rest. If a product publishes an MCP server, you can hand Lindy the URL and it gains that product's tools without waiting for a native integration.

Lindy connects to hosted servers that expose a public HTTPS streamable-HTTP endpoint. On connect it reads the server's tool catalog and creates an action for every tool whose schema it supports. There is no action-picking or field-mapping step: everything supported arrives switched on, and you turn off what you don't want afterwards. A small server might add three tools; a large one adds well over a hundred.

## Adding an MCP server

The only thing you must have is the server's URL. Everything else in the dialog is optional.

<Steps>
  <Step title="Get the server URL">
    The product you're connecting publishes it, usually in their docs under MCP. It looks like `https://mcp.example.com/mcp`, and it has to be reachable over public HTTPS.
  </Step>

  <Step title="Open the Add menu">
    Go to **Integrations**, click **+ Add**, and choose **MCP**. The other option in that menu, **Integration**, is for the built-in tools.
  </Step>

  <Step title="Fill in the server">
    In **Connect MCP server**, paste the **Server URL** and set a **Display name**.
  </Step>

  <Step title="Add a credential only if the server needs one">
    Servers that allow anonymous access, and servers that run their own OAuth flow, need nothing here. If yours authenticates with a static credential instead, open **Advanced** and send it as an **Authorization** bearer token, a custom header, or a query parameter.
  </Step>

  <Step title="Connect">
    Click **Connect**. The server appears in your list with its host and its tool counts.
  </Step>
</Steps>

<Tip>
  A **Display name** is worth setting. Connections are identified by hostname otherwise, and several products serve more than one server from the same host, so two entries can look identical in the list. `Linear production` beats a bare hostname.
</Tip>

<Note>
  Lindy shows two numbers: the tools the server reports, and the tools available in Lindy. They differ when a server publishes tools whose schemas Lindy doesn't support. Zero available means the endpoint is wrong, the catalog is empty, or none of the tool definitions are compatible.
</Note>

## After you connect

Open the server from **Integrations** to reach its settings. Every connection you hold to that server appears as a chip across the top, so one product can carry more than one: a personal connection and a shared one, each with its own settings. A chip marked with a people icon is shared with the workspace. Its **...** menu is where you rename or remove that connection.

Three cards sit below.

### Availability

**Availability** decides who the connection serves.

<Frame>
  <img alt="A connected MCP server's Availability dropdown, open on Only you and Your workspace" />
</Frame>

| Setting            | Who can use its tools                               |
| ------------------ | --------------------------------------------------- |
| **Only you**       | Your Lindy alone. Every new connection starts here. |
| **Your workspace** | Everyone in the workspace, and Lindy Teammate       |

### Guardrails

**Guardrails** decide whether Lindy asks before it uses the server.

<Frame>
  <img alt="A connected MCP server's Guardrails dropdown, open on Always allow and Ask for approval" />
</Frame>

| Setting              | What Lindy does                         |
| -------------------- | --------------------------------------- |
| **Always allow**     | Calls the server's tools without asking |
| **Ask for approval** | Asks first                              |

This one is personal. Your choice affects only you, and it overrides whatever the workspace has set as its default, so two people on the same shared server can run it differently.

### Actions

**Actions** lists every tool Lindy built from the server's catalog, each with the description the server publishes and a toggle. They all arrive on.

Turn off the ones you don't need. **Disable all** clears the list in one click, which is the fast way to keep two tools out of a hundred. This is worth doing on a large server: every enabled tool is a tool Lindy has to consider on every task, and a hundred unused ones are noise.

## Who can change what

Sharing is the connection owner's call. Workspace owners and admins set team policy and can revoke sharing, but they cannot grant it or reconnect the credential on your behalf.

|                                   | Connection owner | Workspace owner or admin | Other members |
| --------------------------------- | ---------------- | ------------------------ | ------------- |
| Use the tools                     | Yes              | Once shared              | Once shared   |
| Set Availability to the workspace | Yes              | No                       | No            |
| Revoke sharing, set policy        | Yes              | Yes                      | No            |
| Reconnect the credential          | Yes              | No                       | No            |

Guardrails are the exception: that setting is per person, so anyone using a shared server picks their own.

## Turning a server off

Setting a shared connection's **Availability** back to **Only you** removes its tools from everyone else's Lindy in that workspace. The connection itself survives and keeps working for you, and the same server connected separately elsewhere is unaffected.

Reach for the **Actions** toggles first if the problem is noise rather than access. Dropping to **Only you**, or removing the connection from its **...** menu, is for when the team should not be calling that server at all.


# Integrations
Source: https://docs.lindy.ai/integrations/overview

Connect Lindy to the tools your team already uses, and control what it can do with guardrails.

<Frame>
  <img alt="The Integrations page: an Add button, a Browse all integrations banner, and enabled tools like Browserbase, Datadog, DeepWiki, and GitHub showing their connected accounts" />
</Frame>

Lindy connects to **1,000+ tools**: Gmail, Slack, Notion, HubSpot, Google Drive, GitHub, and the rest of your stack. Open **Integrations** to see what's connected, or click **Browse all integrations** for the full catalog.

## When a tool isn't in the list

Lindy supports **MCP**, so any MCP server your team runs plugs straight in.

If a tool has no integration and no MCP server, Lindy still isn't stuck. It can drive the browser the way a person would, or write its own integration against the tool's API.

Two more things are worth understanding: whether a connection is yours or the team's, and what Lindy is allowed to do with it.

## Personal and team connections

| Scope        | Who can use it            | Who can change it |
| ------------ | ------------------------- | ----------------- |
| **Personal** | Just you                  | You               |
| **Team**     | Everyone in the workspace | Owners and admins |

A personal connection is private to you. Your Lindy uses it for your own work, your DMs, and the web app.

An owner or admin can share one of their personal connections with the whole workspace. From then on, everyone's Lindy reads that tool as that account and acts with its permissions. Members can see team connections but can't change them.

## Guardrails

Guardrails decide what Lindy can do without asking. This is the setting that matters most for Teammate. Each integration has one:

| Setting              | What Lindy does              |
| -------------------- | ---------------------------- |
| **Always allow**     | Writes without asking        |
| **Require approval** | Asks in Slack before writing |
| **Don't offer**      | Never writes with this tool  |

Two things to know:

* **Reads are never guarded.** Checking your calendar or searching your email always just works. Guardrails only cover writes.
* **Guardrails apply in shared Slack threads only.** Your web app chat, Slack DMs with Lindy, and iMessage and SMS aren't guarded.

<Note>
  A guardrail covers every account under an integration. You can't yet set one rule for your work Gmail and a different one for your personal Gmail.
</Note>

## Approving a write in Slack

When Lindy needs approval, it posts **Approve** and **Deny** buttons in the thread. The person who asked can approve their own request, and so can any workspace owner or admin. Anyone else gets a private note to ask one of them.

**Approve** allows that one action and changes nothing else. **Always allow** changes the rule going forward: workspace-wide if an owner or admin clicks it, or just for that person if a member does.

## Connecting and managing

Search for the tool you want and connect it with OAuth or an API key. Every action for that tool turns on at once, so there's no action-picking step. For tools that support more than one login, like Gmail, you can add further accounts under the same integration.

Each connection shows whether it's healthy, needs reconnecting (usually an expired token), or isn't set up yet. From a connection you can rename it, share it with the workspace (owners and admins only), or disconnect it. Removing the last account of an integration removes the integration from your list.


# Pricing
Source: https://docs.lindy.ai/pricing

Simple per-user plans for the AI teammate your whole team shares, with credits pooled across the workspace. Plus, Pro, Max, and Enterprise.

## Simple, per-user pricing

You pay per user, and everyone on the workspace shares one pool of credits.

## Plans at a Glance

| Plan           | Price             | Credits     | Usage      | Best for                                 |
| -------------- | ----------------- | ----------- | ---------- | ---------------------------------------- |
| **Plus**       | \$30/mo per user  | 3,000/user  | Standard   | Getting started                          |
| **Pro**        | \$100/mo per user | 15,000/user | 5x Plus    | Daily delegation                         |
| **Max**        | \$200/mo per user | 35,000/user | \~11x Plus | The heaviest workloads, all day          |
| **Enterprise** | Contact us        | Custom      | Custom     | Teams with security and compliance needs |

## What's a Credit?

Credits measure the work Lindy does, about **one cent each**. You only spend them when Lindy is actually working, and bigger jobs use more.

| Work              | Credits     | Examples                                                                                                                 |
| ----------------- | ----------- | ------------------------------------------------------------------------------------------------------------------------ |
| **Everyday asks** | 2–250       | Answers, summaries, lookups, updates in your tools, closing out a meeting, drafting a reply                              |
| **Deep work**     | 250–1,000   | Researching a competitor and writing the report, triaging a day's support queue, turning a week of calls into a proposal |
| **Big builds**    | 1,000–2,500 | Dashboards and decks from your CRM and analytics, internal tools shipped end to end                                      |

Lindy picks the right model for each task so credits go further, and you can choose the model yourself if you'd rather.

## Compare Plans

| Feature                                       |             Plus             |              Pro             |              Max             |          Enterprise          |
| --------------------------------------------- | :--------------------------: | :--------------------------: | :--------------------------: | :--------------------------: |
| Slack-native teammate in threads and mentions | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> |
| Scheduled routines                            | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> |
| Persistent workspace context                  | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> |
| iMessage with Lindy, 24/7                     | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> |
| Manages your inbox and drafts in your voice   | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> |
| Meeting scheduling, prep, and follow-up       | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> |
| Meeting recording and note taking             | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> |
| Thousands of integrations                     | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> |
| Model selection, all models                   | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> |
| Computer use                                  | <Icon icon="circle-xmark" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> | <Icon icon="circle-check" /> |
| Connected inboxes                             |               2              |               3              |               5              |               5              |
| SSO and SCIM                                  | <Icon icon="circle-xmark" /> | <Icon icon="circle-xmark" /> | <Icon icon="circle-xmark" /> | <Icon icon="circle-check" /> |
| HIPAA with a signed BAA                       | <Icon icon="circle-xmark" /> | <Icon icon="circle-xmark" /> | <Icon icon="circle-xmark" /> | <Icon icon="circle-check" /> |
| Dedicated support and enablement              | <Icon icon="circle-xmark" /> | <Icon icon="circle-xmark" /> | <Icon icon="circle-xmark" /> | <Icon icon="circle-check" /> |

## How Credits Work Across a Team

Credits are pooled at the workspace level. Each seat adds its plan's allocation to one shared balance the whole team draws from, and admins can cap how much any one person pulls.

Need more before your cycle resets? Admins can top up shared credits any time at **\$10 per 1,000 credits**, in 1,000-credit blocks. If the pool runs low, Lindy pauses credit-using actions and tells you. Nothing breaks, and there's no surprise bill.

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="How do credits work?">
    Credits are how Lindy measures work, and bigger jobs use more. Every seat adds its allocation to one shared pool the whole workspace draws from, so the team pulls from the same balance.
  </Accordion>

  <Accordion title="Do unused credits roll over?">
    Your plan's credits refresh at the start of each billing cycle and don't roll over, so every month starts fresh. Purchased top-up credits are the exception: they carry over and don't expire.
  </Accordion>

  <Accordion title="What happens if we run out of credits?">
    Nothing breaks, and there's no surprise bill. Lindy pauses credit-using actions until your credits reset at the start of your next cycle. Need more before then? Admins can top up, or move to a plan with more credits, any time.
  </Accordion>

  <Accordion title="Who actually needs a paid seat?">
    Anyone who uses Lindy takes a seat, whether they sign up directly, join your workspace, or @mention Lindy in Slack. Someone new to Lindy who joins through Slack gets a 7-day free trial before the seat is billed. People who already have a Lindy account, or who sign up directly, are billed right away.
  </Accordion>

  <Accordion title="How does billing and seat management work?">
    Teammate is one workspace subscription: every seat is on a single bill and all credits pool together. Admins manage seats and credit allocations in one place. Remove a seat any time and it stays active through the cycle you've paid for, with no mid-cycle proration, and Lindy won't re-add anyone an admin removed.
  </Accordion>

  <Accordion title="Can we change plans?">
    Upgrades take effect immediately. Downgrades take effect at the end of your current term. Credit and seat allocation changes are always immediate. Manage everything from your [account settings](https://chat.lindy.ai).
  </Accordion>

  <Accordion title="Will Lindy do anything without my approval?">
    No. Anything with outside impact waits for approval, such as sending an email, updating a ticket, posting to another channel, or publishing a doc. Read-only lookups from approved sources don't require approval.
  </Accordion>

  <Accordion title="Is our data secure?">
    Yes. Your data is encrypted, never sold, and never used to train models. Lindy is SOC 2 and GDPR compliant, and Enterprise adds SSO, SCIM, and HIPAA with a signed BAA.
  </Accordion>

  <Accordion title="Is there a free trial?">
    Yes. New teammates who join through Slack get their first week free, so your team can try giving Lindy real work before any seat is billed. Direct signups are billed right away.
  </Accordion>

  <Accordion title="What happens if we cancel?">
    Your workspace stays active through the cycle you've paid for, with no mid-cycle proration. After that, credit-using actions stop.
  </Accordion>

  <Accordion title="Does a returning teammate get another free trial?">
    The free week is one-time per teammate. If someone leaves and comes back, they pick up right where the team left off, with immediate access, going straight onto a billed seat.
  </Accordion>

  <Accordion title="What payment methods do you accept?">
    Lindy accepts all major credit and debit cards through Stripe.
  </Accordion>
</AccordionGroup>

## Next Steps

<CardGroup>
  <Card title="Get Started" icon="rocket" href="/start-here/quickstart">
    Set up Lindy in 2 minutes.
  </Card>

  <Card title="Set up Lindy" icon="slack" href="/teammate/setup">
    Give your whole team a shared Lindy in Slack.
  </Card>

  <Card title="Billing" icon="credit-card" href="/teammate/lindy-teammate-billing">
    Seats, trials, and your shared credit pool.
  </Card>

  <Card title="Security" icon="shield-halved" href="/resources/security">
    SOC 2 Type II, HIPAA, GDPR. Your data is protected.
  </Card>
</CardGroup>


# Changelog
Source: https://docs.lindy.ai/resources/changelog



To see our latest updates, please visit our [changelog](https://www.lindy.ai/changelog).


# Security
Source: https://docs.lindy.ai/resources/security



For an overview of our security practices, please visit our [security page](https://www.lindy.ai/security).


# Best Practices
Source: https://docs.lindy.ai/start-here/best-practices



<Note>
  **These are for your personal Lindy** — the one in your DMs that knows your inbox, calendar, and meetings. The more it knows about you, the less it has to ask. The Lindy your team shares works differently: see [Slack Commands](/teammate/slack-commands).
</Note>

## Pin Lindy in iMessage

So it's always one tap away.

<div>
  <video />
</div>

## Make Sure to Tweak Your Settings

Configure Lindy's behavior through the web interface, or simply ask her in plain language — she'll update the settings for you and tell you where to fine-tune.

<Frame>
  <img alt="Texting Lindy 'auto-archive all my uber emails' and getting back 'done. i'll file those automatically from now on. you can tweak any of this in settings too'" />
</Frame>

## Give Lots of Feedback

Lindy gets better the more you use it. If it gets anything wrong, just share quick feedback and it'll learn from it.

<Frame>
  <img alt="Lindy says 'heads up, new invoice from deel' and user replies 'no need to flag invoices — finance has those covered.' Lindy: 'got it, i won't flag those going forward'" />
</Frame>

## Text Lindy Like You'd Text a Human Assistant

Tell Lindy the outcome: it handles the back-and-forth.

<Frame>
  <img alt="Texting Lindy 'I need 15 min with Bob this week' and getting back 'done. Thursday 2pm, invite sent ✅'" />
</Frame>

## Get Things Out of Your Head

"Remind me Friday." "Tell me when Sarah replies." "Follow up with Acme if they go quiet for a week." Hand it the loop, then forget it.

<Frame>
  <img alt="Texting Lindy 'remind me to call the bank friday — and tell me if Sarah hasn't replied by end of day' and getting back 'got both. i'll ping you friday, and flag Sarah if she's quiet by 5'" />
</Frame>

<div>
  <Tip>
    **Start small.** Pick one time sink, let Lindy own it, then keep adding.
  </Tip>
</div>

## Use Voice Memos

The easiest way to brain dump on Lindy. Hit the voice button in iMessage and talk like you're handing off to a human assistant.

<Frame>
  <img alt="Voice memo iMessage to Lindy ('Okay I'm out most of next week, here's what needs to happen...') with Lindy replying 'got all that. added 5 to-dos and i'll cover your inbox while you're out'" />
</Frame>

It's the fastest way to do what comes next — dump a brain-load of info Lindy needs about you.

## Give Lindy Lots of Information (Over Voice Memo)

The more Lindy knows about you, the better it can help. Open iMessage, **hit the voice button**, and brief it like a new hire: five minutes covers a lot.

<Frame>
  <img alt="Texting Lindy 'couple things to know about me — top priority this quarter is the acme deal, and loop sarah in on anything finance related' and getting back 'got it, saved both. i'll keep these in mind going forward'" />
</Frame>

**On mobile?** Just cover the basics below and send more voice notes over the next few days.

**On desktop?** Open iMessage on your phone and go through as many sections as you want.

<div>
  <h3>Start Here</h3>
  <p>Four things Lindy needs on day one:</p>

  <ol>
    <li>Your name, role, and company</li>
    <li>What you spend most of your day doing</li>
    <li>Things eating too much of your time</li>
    <li>Your work hours and time zone</li>
  </ol>

  <p>Everything below is optional. Share it whenever, in any order.</p>
</div>

<div>
  <h3>Daily Basics</h3>

  <ul>
    <li><strong>Calendar:</strong> Protected blocks, preferred meeting length, buffer time, ideal meeting windows.</li>
    <li><strong>Meetings:</strong> Which meetings Lindy should join or skip. Post-meeting tasks that eat your time (follow-ups, CRM updates, Slack notes).</li>
    <li><strong>Email:</strong> Most important contacts, emails to alert you about, emails to auto-archive.</li>
    <li><strong>Briefings:</strong> Text or voice recap, time to receive them, content to include (news, quotes, etc.), whether you want an end-of-day brief.</li>
  </ul>
</div>

<div>
  <h3>All About You</h3>

  <ul>
    <li><strong>Priorities:</strong> Top priorities, projects to protect time for, KPIs you're tracking.</li>
    <li><strong>Personal:</strong> Partner/kids/family names, recurring obligations, favorite restaurants, dietary restrictions, go-to gift ideas.</li>
    <li><strong>Working style:</strong> What a good day feels like, how direct you want feedback, routines Lindy should support, times you do your best thinking.</li>
    <li><strong>Tools:</strong> Your productivity stack, where tasks live today, how aggressive reminders should be, recurring annual reminders.</li>
  </ul>
</div>

## Next Steps

<CardGroup>
  <Card title="iMessage & SMS" icon="message" href="/features/imessage-sms">
    Text Lindy like a friend from your phone
  </Card>

  <Card title="Inbox Management" icon="inbox" href="/features/inbox-management/email-triage">
    Let Lindy run your inbox
  </Card>

  <Card title="Meeting Assistant" icon="calendar" href="/features/meeting-assistant/meeting-prep">
    Prep, notes, and follow-ups on autopilot
  </Card>

  <Card title="Ad Hoc Tasks" icon="wand-magic-sparkles" href="/features/ad-hoc-tasks">
    Research, reminders, and on-demand tasks
  </Card>
</CardGroup>


# Quickstart
Source: https://docs.lindy.ai/start-here/quickstart

Get Lindy into your team's Slack, then connect your own email, calendar, and phone. Two minutes.

<Frame>
  <img alt="A Slack message where Maya asks @Lindy to take support triage today, and Lindy replies that it's on it, pulling urgent support tickets" />
</Frame>

Two quick parts: get Lindy into your team's Slack, then connect your own email, calendar, and phone.

That sets up both surfaces. In **channels**, the whole team shares one Lindy you summon with an `@mention`, and the work it does is visible to everyone there. In your **DMs**, you get a private one that runs your inbox, meetings, and scheduling. Same Lindy either way.

## 1. Get your team on Lindy

<Steps>
  <Step title="Add Lindy to Slack">
    An admin installs Lindy from Slack's **Add to Slack** screen. The installer is linked automatically.
  </Step>

  <Step title="Everyone links with one tap">
    The first time a teammate DMs or @mentions Lindy, it replies with a **Connect Slack to Lindy** button. Tap it, confirm, and you're linked. Your original message runs on its own once you're connected.
  </Step>
</Steps>

For the full picture (how to talk to Lindy, guardrails, and what it can do), see [Set up Lindy](/teammate/setup).

## 2. Set up your account

<Steps>
  <Step title="Connect email and calendar">
    Connect your Google or Microsoft account so Lindy can run your inbox, prep and take notes on meetings, and handle scheduling.
  </Step>

  <Step title="Add your phone">
    Add your phone number (or connect Apple Messages) so you can text Lindy from anywhere. You'll verify with a code.
  </Step>

  <Step title="Connect your tools">
    Connect the tools you use, like Notion, HubSpot, Linear, and 1,000+ more, so Lindy can work across your whole stack. See [Integrations](/integrations/overview).
  </Step>
</Steps>

<Check>
  Your data is encrypted, never sold, and never used to train models. Lindy is SOC 2, GDPR, and HIPAA compliant. [Learn more about security](/resources/security).
</Check>

## Try it

Ask Lindy in Slack, a DM, or by text:

* *"What's on my calendar today?"*
* *"Draft a reply to \[name]'s email"*
* *"Schedule 30 minutes with \[name] next week"*
* *"Summarize yesterday's meeting with \[name]"*

## Next Steps

<CardGroup>
  <Card title="Set up Lindy" icon="slack" href="/teammate/setup">
    The full team and account setup
  </Card>

  <Card title="Home" icon="house" href="/teammate/home">
    Where you talk to Lindy and see what it's done
  </Card>

  <Card title="Meetings" icon="video" href="/teammate/meeting-library">
    Recording, notes, and your shared library
  </Card>

  <Card title="Pricing" icon="tag" href="/pricing">
    Seats, credits, and the shared pool
  </Card>
</CardGroup>


# Team Setup
Source: https://docs.lindy.ai/start-here/team-setup

The two ways people join your workspace, plus admin controls, credits, and ownership

<Frame>
  <img alt="Lindy for Teams: a row of five avatars, four teammates and the Lindy face, with a cursor clicking Lindy" />
</Frame>

## Adding People to Your Workspace

There are two ways someone joins. An admin invites them from team settings, or they add themselves by @mentioning Lindy in Slack. Either way they take a seat on your workspace billing and draw from your shared credit pool.

| How they join                 | Who starts it         | When the seat is billed |
| ----------------------------- | --------------------- | ----------------------- |
| **Invite from team settings** | An admin              | Right away              |
| **@mention Lindy in Slack**   | The person themselves | After a free first week |

### Invite from team settings

<Steps>
  <Step title="Open the invite dialog">
    Click your **workspace name in the top-left** and choose **Invite a member**.
  </Step>

  <Step title="Add their details">
    * Enter one or more **email addresses** (separate multiple emails with spaces)
    * Pick a **role**: Member or Admin
    * Pick a **plan**: Plus, Pro, or Max

    | Plan     | Price             | Credits it adds to the pool |
    | -------- | ----------------- | --------------------------- |
    | **Plus** | \$30/mo per user  | 3,000                       |
    | **Pro**  | \$100/mo per user | 15,000                      |
    | **Max**  | \$200/mo per user | 35,000                      |

    Enterprise isn't offered here: it's a custom plan, so [contact us](mailto:support@lindy.ai) instead. See [Pricing](/pricing) for what each plan includes.

    <Frame>
      <img alt="Invite members dialog with Email addresses, Role, and a Plan dropdown listing Plus at $30, Pro at $100, and Max at $200 per month per seat" />
    </Frame>
  </Step>

  <Step title="Send the invite">
    Click **Send invite**. Their plan is added to your workspace billing, and your workspace credits increase to reflect the additional plan. Existing members and permissions stay the same.
  </Step>
</Steps>

### @mention Lindy in Slack

Once Lindy is installed in your team's Slack, anyone can add themselves just by talking to it. No admin step, and no invite to wait for.

<Steps>
  <Step title="They @mention Lindy, or send it a DM">
    The first time, Lindy doesn't answer yet. It replies with a single DM containing a **Connect Slack to Lindy** button.
  </Step>

  <Step title="They tap Connect">
    They confirm while signed in to Lindy, which binds their Slack identity to their Lindy account. If they don't have one, Lindy creates it under your workspace.
  </Step>

  <Step title="Their original message runs">
    The message that started it all is replayed automatically once they're linked, so nothing is lost.
  </Step>
</Steps>

<Frame>
  <img alt="A Slack DM from Lindy telling Priya she mentioned it in #launch, with a Connect Slack to Lindy button and a note that her original message will run once she's connected" />
</Frame>

<Note>
  **Admins stay in the loop.** Every admin gets an email when someone joins this way: who they are, that their first week is free, and a one-click link to remove them. If you remove a seat and that person @mentions Lindy again, it tells them it can't help and pings an admin. It won't quietly re-add them.
</Note>

For how seats and the shared credit pool work, see [Billing](/teammate/lindy-teammate-billing). To get Lindy into Slack in the first place, see [Set up Lindy](/teammate/setup).

## Admin Controls

Admins can control which features are available to users across the workspace. Toggle each feature on or off to manage access.

Go to **Settings** and choose the **Settings** option under Workspace.

| Feature               | What It Controls                                            |
| --------------------- | ----------------------------------------------------------- |
| **Meeting Recording** | Allow users to record meetings and generate summaries       |
| **Email Drafting**    | Allow users to have Lindy draft replies in their voice      |
| **Email Triaging**    | Allow users to have Lindy triage and prioritize their inbox |

## Managing Members

To manage existing members, click your **workspace name in the top-left → Settings → Members and Groups**.

<Frame>
  <img alt="Workspace settings showing Settings, Teammate, and Members and groups under the Workspace section, with an arrow pointing to the selected Members and groups item" />
</Frame>

### Allocating Credits

Admins and owners can set credit limits for each teammate, capping how many credits they can use each month. Click the **…** menu on a member's row and choose **Edit credit limit**.

<Frame>
  <img alt="The Members table with a row menu open, showing Edit credit limit and Deactivate membership" />
</Frame>

<Note>
  We can only stop credit usage after the limit has been exceeded, not at the exact threshold. For example, if a teammate's limit is 100 credits and they've used 90, a task that costs 50 credits will still run to completion — but no further credit usage will be allowed afterward.
</Note>

### Transferring Workspace Ownership

Owners are the only ones who can manage the payment method, change the workspace name and logo, and delete the workspace. Owners can transfer ownership by clicking the role dropdown next to a member's or admin's name and changing their role to **Owner**.

<Frame>
  <img alt="The Members table with a role dropdown open on a member's row, showing the Member, Admin, and Owner options, where Owner reads Transfer ownership of the workspace" />
</Frame>


# Artifacts
Source: https://docs.lindy.ai/teammate/artifacts

Live pages Lindy builds and hosts for you: dashboards, reports, prototypes, and internal sites, each on its own link you control.

<Frame>
  <img alt="A teammate asks Lindy in Slack to build a dashboard of marketing spend across channels for the last two weeks; Lindy pulls the spend, builds it, and replies that it is published to the workspace so anyone on the team can open it" />
</Frame>

Ask Lindy for a dashboard, a report, or a page and it doesn't hand back a file to open. It builds the thing, hosts it, and gives you a link on its own `lindy.link` address.

Anything that renders in a browser works: live dashboards, weekly reporting, call prep pages, design prototypes, generated assets, one-off internal sites.

## Every artifact starts private

A new artifact is private. Signed-in members of your workspace can open the link. Anyone outside it gets **This artifact is private**, even with the exact URL.

That default is deliberate. Artifacts get built out of your real work: inbox content, meeting notes, revenue numbers. Copying the URL never bypasses the permission.

<Note>
  Private means private to your workspace, not to you alone. A teammate who is signed in can open any artifact in the workspace, which is why a link you paste in a channel just works for the team and not for anyone outside it.
</Note>

## Sharing one publicly

Ask Lindy to publish it: **"make that dashboard public"** or **"give me a shareable link."** Lindy asks you to approve first, same as any other write action, and returns the public URL once you do.

<Warning>
  Public means public. Anyone with the link opens the page without signing in, and there is no share-with-one-person mode. Publish only what you would be comfortable with anyone seeing.
</Warning>

Ask Lindy to unpublish it and the link goes offline, back to workspace-only.

## Keeping one up to date

Ask for changes and Lindy rebuilds the page on the same URL, so a link you already shared keeps working and shows the current version.

That is the point of a hosted page over an exported file: the people you sent it to see this morning's numbers, not the copy you emailed on Tuesday.

## What teams build with them

| Artifact               | What it replaces                                        |
| ---------------------- | ------------------------------------------------------- |
| **Live dashboard**     | The spreadsheet someone refreshes by hand every Monday  |
| **Call prep page**     | Ten browser tabs opened five minutes before the meeting |
| **Weekly report**      | A recurring deck nobody updates after week three        |
| **Design prototype**   | A static mockup you can't click through                 |
| **Internal one-pager** | The doc that gets forked into four stale copies         |

## Relevant Docs

<CardGroup>
  <Card title="Ad-hoc tasks" icon="wand-magic-sparkles" href="/features/ad-hoc-tasks">
    Ask Lindy for a piece of work and get the finished thing back
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/teammate/routines">
    Have Lindy refresh an artifact on a schedule
  </Card>
</CardGroup>


# Files
Source: https://docs.lindy.ai/teammate/files

Browse and manage the files Lindy uses: a versioned file system you can see into, edit, and share with your team.

<Frame>
  <img alt="The Files page in the left sidebar, with the Personal and Workspace switcher and the memory and skills folders" />
</Frame>

Files is a browser-based explorer for Lindy's own files, on the **Files** page in the left sidebar. Think of it as Lindy's hard drive that you can see into. Lindy saves files here as it works, and you can add, edit, and organize the files it uses.

The point is transparency. Instead of a black box, you can inspect, verify, and correct exactly what Lindy has produced or knows. Everything is versioned, so nothing is ever silently lost.

## Personal, team, and system files

A switcher at the top of the explorer flips between your scopes:

| Scope        | Who can see it             | Who can edit it             |
| ------------ | -------------------------- | --------------------------- |
| **Personal** | Just you                   | You                         |
| **Team**     | Everyone in your workspace | Workspace owners and admins |
| **System**   | Everyone                   | No one (built in)           |

**Personal** files are private and scoped per workspace, so nothing leaks between the workspaces you belong to. **Team** files are shared knowledge for the whole workspace; regular members get a read-only view with a lock banner, and owners and admins can edit. **System** files ship with Lindy and can't be changed.

## Adding files

<Steps>
  <Step title="Create in the explorer">
    Use **New file** or **New folder** to make something from scratch, then rename, move, or organize it however you like.
  </Step>

  <Step title="Drag and drop to upload">
    Drop files, or entire folders, onto the explorer. Folders are walked recursively, so subfolder structure is preserved. You can drop up to **100 files** at once.
  </Step>
</Steps>

<div>
  <div>
    <video />
  </div>
</div>

<Note>
  Two things to know: empty folders can't be saved (Lindy tracks files, not empty directories), and on a name conflict Lindy either overwrites or keeps both by adding a numbered copy.
</Note>

## Teach Lindy with files

Files aren't just storage. They can extend what Lindy can do.

* **Skills** live in a `.skills/` folder. Each skill is a folder with a `SKILL.md` (a name, description, and instructions), and the folder name is the skill name. Lindy sees the names and descriptions of enabled skills, and pulls in a skill's full instructions on demand when it's relevant. Skills layer across scopes: your Personal version overrides the Team's, which overrides the built-in System one. Browse and install ready-made skills from the [Skills](/teammate/skills) page and marketplace; installing one copies it into your Personal or Team files.
* **Memory** lives in a `.memory/` area, where Lindy keeps durable knowledge it can rely on across tasks.

## Editing and saving

Files open in a viewer with **Preview**, **Raw**, and **History** tabs. Editable text files open in an inline code editor.

<Note>
  Saving is explicit: changes only apply when you click **Save**, and Lindy warns you before discarding unsaved edits. Read-only files (Team files for non-admins, and system files) show a lock banner instead.
</Note>

## Versions and syncing

* **Every save is a version.** Full history is kept, and you can restore an earlier revision any time. Even deleting a file keeps its earlier versions.
* **Changes sync live.** When Lindy writes a file mid-task, the explorer updates in near-real-time. Edits to `.skills/` refresh what Lindy knows on its next turn.

## Relevant Docs

<CardGroup>
  <Card title="Skills" icon="graduation-cap" href="/teammate/skills">
    Turn files into capabilities Lindy picks up on its own
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/teammate/routines">
    Have Lindy produce files on a schedule
  </Card>
</CardGroup>


# Home
Source: https://docs.lindy.ai/teammate/home

Where you talk to Lindy and see what it's been doing for you. Ask anything, finish your setup, and watch the page fill in as Lindy works.

<Frame>
  <img alt="The Home page: a greeting naming the next meeting, a chat box, upcoming and past meetings, and Need to know, What I've been up to, and Recent learnings cards" />
</Frame>

Home isn't a dashboard of buttons to configure. It's where you talk to Lindy and see what it's been doing for you. Everything on the page is built around that.

## Talk to Lindy

The box at the top is your **personal Lindy**, connected to your own integrations like email, calendar, and the other tools you've linked. Ask it anything and it takes the request on as a task.

Type `@` to point Lindy at a specific meeting, folder, or tool. Around the box, a set of cards shows what Lindy has been up to and what needs your attention.

## Your activity and context cards

As Lindy starts working, these fill in. Empty cards stay hidden or show a friendly "getting to know you" state until there's data.

<CardGroup>
  <Card title="Upcoming meetings" icon="calendar">
    Today's meetings, with a **Join** button for video calls.
  </Card>

  <Card title="Past meetings" icon="circle-play">
    Recorded meetings with recaps. Until Lindy joins one, this stays empty.
  </Card>

  <Card title="Need to know" icon="circle-exclamation">
    Top items pulled from email, Slack, and meetings that you should act on. Clickable, and dismissable.
  </Card>

  <Card title="What I've been up to" icon="chart-simple">
    Stats like emails triaged, drafts written, and estimated time saved.
  </Card>

  <Card title="Recent learnings" icon="lightbulb">
    Things Lindy has learned about you. Add, edit, or delete any of them.
  </Card>

  <Card title="How to reach me" icon="at">
    Lindy's email ([lindy@lindy.ai](mailto:lindy@lindy.ai)) and your assigned Lindy phone number, ready to copy.
  </Card>
</CardGroup>

## The sidebar

On the left: **Home, Chat, Meetings, Files, Routines, Skills, and Integrations** (which ones show depends on your setup), plus search, a **New chat** button, the workspace switcher, and your credit balance at the bottom.

## Make it yours

Use the **Customize** menu ("Show on home") to show or hide cards, and dismiss any card with its **X**. Your layout preference syncs across devices, including the Chrome extension's new-tab page.

<Tip>
  New here? Finish the setup checklist (connect email and phone), then start typing in the chat box or click a suggestion tile. Everything else on the page fills itself in as Lindy works.
</Tip>

## Relevant Docs

<CardGroup>
  <Card title="Set up Lindy" icon="slack" href="/teammate/setup">
    Get Lindy into your team.s Slack and connect your tools
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/teammate/routines">
    Recurring work Lindy runs on a schedule
  </Card>

  <Card title="Files" icon="files" href="/teammate/files">
    Browse and manage the files Lindy uses
  </Card>

  <Card title="Meeting Library" icon="video" href="/teammate/meeting-library">
    Group and share your recorded meetings
  </Card>
</CardGroup>


# Billing
Source: https://docs.lindy.ai/teammate/lindy-teammate-billing

How Lindy Teammate is priced: a seat for each person, a free week for new teammates, and one pool of credits your whole team shares.

Lindy Teammate is priced per person. Each teammate gets a seat, and your whole team draws from one shared pool of credits. New teammates who join through Slack get their first week free.

## Pricing

| Plan           | Per seat                              |
| -------------- | ------------------------------------- |
| **Plus**       | \$30/user · 3,000 credits             |
| **Pro**        | \$99.99/user · 15,000 credits         |
| **Max**        | \$199.99/user · 35,000 credits        |
| **Enterprise** | [Contact us](mailto:support@lindy.ai) |

## How someone becomes a seat

A person takes a paid seat when they:

* Sign up to Lindy directly
* Join your workspace by signing up
* @mention Lindy in your team's Slack for the first time

<Note>
  The free week applies to the Slack path. Direct signups and people who join by signing up are billed right away.
</Note>

### The Slack trial

1. Someone new @mentions Lindy in Slack.
2. Lindy sets up an account for them under your workspace.
3. Every admin gets an email: who joined, that they're free for a week, and a one-click link to remove them.
4. The new teammate gets a Slack DM to finish setting up their own Lindy.
5. Remove someone's seat and, if they @mention Lindy again, it tells them it can't help and pings an admin. It won't quietly re-add them.

A seat stays billed until an admin removes it. You keep it through the end of the current cycle, with no mid-cycle proration.

## Your shared credit pool

Credits belong to the workspace, not to each person. The pool adds up:

* Your base plan's credits
* Each teammate's seat (a Plus seat adds 3,000, a Pro seat 15,000, and so on)
* Any top-ups an admin buys

### Spend caps

Admins can cap any one teammate's draw from the pool. Hit the cap and Lindy pauses that person's credit-using actions, with a clear message, until the next cycle or a higher cap. Leave it unset for unlimited draw.

### Top-ups

Admins can buy extra workspace credits any time, apart from seats: **\$10 per 1,000 credits**, in 1,000-credit blocks. Top-ups are a one-time buy and never touch your base plan's credits.

## What every plan gets

Every plan, trial seats included, gets all models. There's no upsell wall on model choice.

A few things depend on your plan:

* SSO, SCIM, audit logs, and HIPAA/BAA on Enterprise
* Live onboarding on Pro and up
* Connected inboxes: 2 on Plus, 3 on Pro, 5 on Max

## Relevant Docs

<CardGroup>
  <Card title="Set up Lindy" icon="slack" href="/teammate/setup">
    Get Lindy into your team's Slack and link everyone
  </Card>

  <Card title="Routines" icon="bolt" href="/teammate/routines">
    Recurring work Lindy runs on a schedule
  </Card>
</CardGroup>


# Meetings
Source: https://docs.lindy.ai/teammate/meeting-library

Lindy records and transcribes your meetings on Google Meet, Zoom, and Teams, and delivers custom summaries to a searchable library. Share folders with your team, have Lindy organize and sort your meetings, and set custom follow-up actions so nothing falls through the cracks.

<Frame>
  <img alt="A meeting library with shared folders for Onboarding Calls, Sales Calls, Product Roadmap, and Marketing Meetup, with a cursor opening Sales Calls" />
</Frame>

Every meeting your team has, in one place anyone can just ask. No more *"how'd the call go?"* or hunting for a recording. Lindy records, transcribes, and summarizes the meetings you attend, and files them into folders you can open up to your whole team.

## Share a folder with your team

Recording the call is the easy part. The shared folder is what pays off.

Open a folder to your team and every call inside it becomes something anyone can question. A new rep gets through last month's sales calls without watching a minute of video. Ask what customers said about pricing and the answer comes back from six meetings at once, with links to the moment in each one.

* **Anyone with access can ask:** from the Meetings page, in Lindy chat, in Slack, or by text.
* **Answers span the whole folder:** *"What objections came up this week?"* draws on every meeting in it, not one call at a time.
* **New people catch up on their own:** send them the folder instead of five recordings.
* **It stays current without upkeep:** describe what belongs once, and matching calls file themselves.

A folder set to **Only you** is an archive. A folder set to **Entire team** is how the rest of the company stops asking you what happened on the call.

## Turn on recording

Recording is a built-in **routine**. On the **Routines** page, open the **Personal** tab, find the **Meeting Recording** card, and toggle it on.

<Frame>
  <img alt="Routines page, Personal tab, with the Meeting Recording card highlighted among the built-in routines" />
</Frame>

Connect your Google Calendar or Microsoft Outlook calendar, set your notetaker display name and summarization instructions, and Lindy records from your next scheduled call.

## How recording works

When recording is on, Lindy sends a notetaker to your Google Meet, Zoom, or Teams calls. It joins **visibly, as a named participant** (you choose the display name), records the call, and writes a transcript and a summary with action items, decisions, and key quotes.

<Note>
  Because the notetaker joins visibly, everyone on the call can see it's there. Still let participants know they're being recorded, as your local laws require.
</Note>

## Recording settings

Control recording from the **Meeting Recording** card:

* **Turn recording on or off.** A workspace admin can turn it off for everyone.
* **Which meetings Lindy joins automatically:** all meetings, internal only, or external only.
* **The notetaker's display name.**
* **The recap email, and who gets it:** all participants, internal people only, or just you.
* **How the summary reads:** free-text instructions to shape its tone and structure.
* **Where the recap is delivered:** email, SMS, Slack DM, or Lindy chat.
* **Follow-up actions** in plain English, like *"share the action items in Slack."*

For a one-off call that isn't covered by your auto-join setting, Lindy can send a confirmation link so an attendee approves recording that specific meeting.

## Post-meeting follow-ups

After every meeting, Lindy extracts the action items and sends a follow-up email. Decisions get documented, next steps are clear, and everyone knows what they own.

1. **Meeting ends**: Lindy processes the recording and transcript
2. **Action items extracted**: Lindy identifies decisions, next steps, and owners
3. **Follow-up sent**: an email goes out with the summary and action items

Set who receives it in the **Meeting Recording** routine: all participants, internal people only, or just you.

### Custom follow-up actions

Beyond email, tell Lindy to take extra actions after meetings. In the **Meeting Recording** routine, use the **Follow-up Actions** field to describe what Lindy should do.

<Note>
  **Lindy works with your existing tools** — Notion, Slack, Todoist, and hundreds more. Just tell it what to do (*"Add action items to Todoist"*) and it handles the rest. The first time it uses an app, Lindy asks you to connect it.
</Note>

<Frame>
  <img alt="Meeting Recording settings with the Follow up actions field highlighted, showing a custom action and the field for adding another" />
</Frame>

A favorite: have Lindy DM you in Slack right after the meeting ends, with the still-outstanding action items and a heads-up on anything that needs your attention.

<div>
  Send a Slack DM with action items
</div>

Other examples:

* "Update the CRM with notes from every sales call"
* "Create a Notion page with the meeting summary"
* "Send action items to the project lead if they weren't on the call"

<Tip>
  This covers post-meeting follow-ups. Lindy can also draft follow-up bumps when someone hasn't replied to an email you sent — see [Follow-up Bumps](/features/inbox-management/follow-up-bumps).
</Tip>

## Your meeting library

Every recorded meeting lands in the Meeting Hub at [chat.lindy.ai/meetings](https://chat.lindy.ai/meetings). Browse them as tiles or rows, search by title, participant, or date, and switch between a **Personal** and **Team** view.

Open any meeting for its **Summary**, **Transcript**, **Video**, and a **Chat** scoped to that call, plus rename, copy, download, and share.

<Frame>
  <img alt="The Meetings page: a Folders sidebar with All, Personal, and Team views, recorded meetings as tiles, and an Ask me anything box" />
</Frame>

## Organize with folders

A folder is a collection of meetings a group can see and query, like **Sales calls**, **Customer feedback**, or **Acme onboarding**. One meeting can live in several folders.

<Steps>
  <Step title="Create the folder">
    On the **Meetings** page, click **Create folder** and give it a name.
  </Step>

  <Step title="Set who can see it">
    Choose the visibility: only you, specific people, or your entire team. Pick **Entire team** unless there's a reason not to. That's the setting that makes the folder worth having.
  </Step>

  <Step title="Describe what belongs (optional)">
    Turn on **Automatically add meetings to this folder** and describe the rule in plain language: *"any sales call,"* *"any meeting with customer feedback,"* or *"all calls with Acme."* Lindy files matching meetings for you, based on the transcript. No tags, no upkeep.
  </Step>
</Steps>

<div>
  <div>
    <video />
  </div>
</div>

<Tip>
  When you create a folder, Lindy suggests meetings to add right away, matched from your recent calls against your description.
</Tip>

### How auto-add respects each person

Auto-add is per person, so a shared folder never pulls in someone else's meetings without their say-so. Each member of a shared folder chooses how the rule applies to their own meetings:

* **Automatic** — matching meetings are added silently.
* **Review** — matches show up in a *"Suggested for this folder"* strip to accept or dismiss.

If the folder's rule changes, everyone is asked again before their meetings are affected.

## Talk to your meetings from anywhere

You don't have to be on the Meetings page to use what was said on a call. Ask from wherever you already are.

* **A public Slack channel:** @mention Lindy in #team-sales and the answer lands in the thread, where the whole channel can see it.
* **A DM:** ask one-to-one when the question is only yours.
* **The Meetings page:** open a call for **Chat with this meeting**, or open a folder for one ongoing chat across every meeting in it. *"What objections came up this week?"*
* **A text:** same question, from your phone.

By default Lindy looks at your own meetings, and only widens to shared ones when a shared folder is involved.

<Frame>
  <img alt="A Slack thread in #team-sales: asked to summarize decisions and next steps from the Little Field enterprise call, Lindy replies in-thread with three sections — SSO with Microsoft 365 plus SCIM for user provisioning, the standard SaaS agreement with a 25-seat order form as the next step, and folder-level chat landing best in the product preview" />
</Frame>

Open any call and **Chat with this meeting** sits right under the recording, with a few starting points if you don't know what to ask.

<Frame>
  <img alt="A recorded meeting open to its Summary tab, with a timestamped key quote from Ray Delgado about Lindy flagging, drafting, and sending emails rather than only summarizing, and a Chat with this meeting box offering to draft a follow-up email, summarize next steps, or list objections and responses" />
</Frame>

Ask for what you actually want and the answer comes back structured, drawn from the call itself.

<Frame>
  <img alt="The Chat with this meeting panel: asked to summarize the key decisions and next steps from an enterprise call, Lindy answers with a Key decisions and next steps list" />
</Frame>

<Note>
  If answering in a public Slack channel would need private meeting context, Lindy moves that part to a DM or tells you it can only answer privately.
</Note>

### It doesn't stop at answering

From the same thread or chat, hand off the work that comes out of the call:

* *"Draft a follow-up email to Sarah based on what we agreed."*
* *"Write up the handoff doc in Notion."*
* *"Update the HubSpot deal with what we heard on pricing."*
* *"Create a task for each action item."*

Write actions always ask for confirmation before they run, so nothing happens silently.

## Privacy and access

A meeting belongs to its participants first, not to the workspace admin.

* **Only you** — private to you (and system admins).
* **Specific people** — only the teammates you add.
* **Entire team** — everyone in that workspace.

<div>
  <div>
    <video />
  </div>
</div>

Access means viewing the folder and its meetings and adding or removing meetings. Renaming, editing, or deleting a folder stays with its owner. Meetings inherit their folder's access, and everything is scoped to the workspace the folder lives in, so nothing leaks across workspaces. Your personal meetings stay private unless you share them or opt a meeting into a folder, and admins can't silently push private meetings into shared visibility.

## Relevant Docs

<CardGroup>
  <Card title="Meeting Prep" icon="clipboard-list" href="/features/meeting-assistant/meeting-prep">
    Get context before every meeting
  </Card>

  <Card title="Smart Scheduling" icon="calendar" href="/features/meeting-assistant/scheduling">
    Lindy proposes times and books meetings for you
  </Card>

  <Card title="Files" icon="files" href="/teammate/files">
    The file explorer for everything Lindy uses
  </Card>

  <Card title="Routines" icon="clock-rotate-left" href="/teammate/routines">
    Recurring work Lindy runs on a schedule
  </Card>
</CardGroup>


# Routines
Source: https://docs.lindy.ai/teammate/routines

Saved instructions that tell Lindy to do recurring work on its own: daily briefs, meeting follow-ups, weekly digests, and anything you set up.

<Frame>
  <img alt="A routine that runs every Monday at 9:00 AM: research socials, hiring, SEO and press at 9:00, write up what changed this week at 9:04, and post the report to #marketing at 9:08" />
</Frame>

A routine is a saved instruction that tells Lindy to do recurring work on its own. Each one is three parts: a **trigger** (when it runs), a **prompt** (what to do, in plain English), and a **destination** (where the result goes). It isn't a separate bot, it's automation attached to your Lindy, which is what makes Lindy proactive: briefing you, prepping you for meetings, and tracking follow-ups without being asked.

Open the **Routines** page from the left sidebar to review what's running, toggle routines on or off, and add your own with **New**.

## Personal, Workspace, and Discover

Three tabs at the top of the page:

* **Personal** — run just for you, by your own Lindy. Anyone can create them.
* **Workspace** — run for the whole team through Lindy Teammate in Slack. Only workspace admins can create and manage these (everyone else sees them marked *"Needs admin"*), and Teammate has to be set up first.
* **Discover** — a library of ready-made templates you can add in one click.

<div>
  <div>
    <video />
  </div>
</div>

## Built-in routines

Lindy ships with a set of routines you can turn on or off with a toggle, per connected account:

| Routine                   | What it does                                |
| ------------------------- | ------------------------------------------- |
| **Daily briefs**          | Prepares you for your day                   |
| **Email drafting**        | Drafts email replies in your voice          |
| **Email labeling**        | Keeps your inbox organized                  |
| **Urgent email alerting** | Alerts you to time-sensitive emails         |
| **Follow-up bumps**       | Drafts a bump when sent emails get no reply |
| **Meeting Recording**     | Joins your meetings and takes notes         |
| **Meeting prep**          | Gives context on your meetings              |
| **Meeting scheduling**    | Coordinates meetings and proposes times     |

Flip any of them on or off any time. Turning one off stops it without removing it.

## Add a template from Discover

Discover has ready-made templates, grouped by area (Recommended, Email & comms, Calendar & meetings, Work, Workspace). Each card shows a status:

* **Ready** — add it in one click.
* **Needs setup** — shows exactly what's missing (like Gmail, Google Calendar, Slack, or meetings) with a **Connect** action right there.
* **Needs admin** — a team template you can add once a workspace admin sets it up.

Click any card to preview its trigger, scope, and prompt before you add it. A few good ones to start with:

* **Morning briefing** — preps you for the day
* **End-of-day review** — wraps today, preps tomorrow
* **Weekly wrap** — summarizes your week
* **Promise tracker** — tracks follow-ups you promise in email
* **Post-meeting follow-ups** — drafts a follow-up after client meetings
* **Calendar audit** — suggests meetings to decline or move on heavy days
* **Channel digest** — posts a combined digest of Slack channels to the team

<div>
  <div>
    <video />
  </div>
</div>

## Create your own

Click **New** to open the create drawer. The easiest path is to type it in the **Describe your routine** box, like *"Every weekday at 9, summarize my unread email and Slack mentions."* Lindy fills in the name, trigger, and schedule for you. Suggestion chips and a shuffle button are there if you want ideas, and **Advanced settings** lets you set the trigger, schedule, delivery channel, and name by hand.

<Frame>
  <img alt="The Routines page with an arrow pointing to the New button in the top right, above the Personal, Workspace, and Discover tabs and the built-in routine cards" />
</Frame>

You can also just ask Lindy in chat: *"Every Monday at 9, check my inbox for emails from investors and alert me."*

## Triggers and delivery

* **Triggers.** Run a routine on a **schedule** (daily, weekly, or monthly, the most common), or on an **event**: an email received or sent, a Slack message, a calendar event about to start, a meeting ending, and more. A **Smart Filter** narrows event triggers in plain English, like *"only emails that promise a follow-up,"* so it doesn't fire on everything.
* **Where results go.** Personal routines deliver to your default proactive channel, Lindy chat, a text message (if your phone is verified), or a Slack DM. Workspace routines post to a Slack thread reply or a specific channel.

<Note>
  Defaults: new routines run **daily at 9:00 AM** until you change it, and deliver to your default proactive channel. Team routines default to a Slack thread reply, and scheduled team digests must target a channel.
</Note>

## Run this as a script

A normal routine is an alarm that wakes Lindy up to think through your instructions again on every trigger. **Run this as a script** turns those instructions into Python that runs instead.

Click **Convert** and Lindy writes a script from the routine's current instructions, then switches the routine off so you can inspect and test it. Turn it back on and every trigger runs the script first.

From there, each run can:

* **Finish on its own** — the run ends without waking Lindy: faster, cheaper, predictable.
* **Leave Lindy a note** — Lindy wakes up, reads the original instructions plus the note, and handles the part that needs AI or tools.
* **Crash** — Lindy wakes up to repair and test the script, instead of blindly redoing the routine's work.

**Works well:** *"Check this public status page every 5 minutes and alert me only when it changes."* The script checks the page and remembers the last value, so most runs end quietly and Lindy only wakes when something changed.

**Doesn't:** *"Summarize my unread Gmail."* Scripts don't carry your Lindy credentials or reach your connected Gmail, Slack, or Calendar accounts, so this one would wake Lindy every time anyway.

<Note>
  Available for personal routines only, not workspace routines.
</Note>

## Test with a dry run

A dry run fires a routine end to end on your real data and shows you exactly what it would have done, without doing it. Real triggers, real reads, real judgment, and nothing sent, posted, or written. Use it before you trust a routine to run unattended.

Ask Lindy in chat:

* *"Dry-run my morning briefing."*
* *"Test my promise tracker before I turn it on."*

A dry run tells you three things a glance at the setup can't:

* **The trigger matches what you meant.** Event triggers and Smart Filters are easy to write too broadly. A dry run shows you what actually fired.
* **The judgment is right.** Read the classifications and drafts, not just the summary. A routine that picks the wrong emails will keep picking the wrong emails, quietly.
* **Quiet days behave.** Narrow the window to a period with nothing in it and confirm the routine stays silent instead of inventing filler.

<Note>
  If a routine remembers things between runs, dry-run it twice. The second run has to behave sensibly reading what the first one left behind.
</Note>

### What a dry run can't cover

The delivery step itself. Sending the email, posting to the channel, or writing to a shared sheet are the actions a dry run exists to suppress, so it can't prove they work.

When you want that leg tested too, point it somewhere safe:

* **Deliver it to yourself** instead of the real recipient.
* **Write to a copy** or a sheet only you use.
* **Read the payload** Lindy would have sent, and approve it without sending.

### Script routines

A routine you converted with **Run this as a script** has two layers, and each is tested separately.

* **The script** runs on its own with sends switched off. It does the real reads and the real LLM steps, then prints what it would have delivered. When something is wrong here, the fix belongs in the script, then run it dry again.
* **The routine around it** is what a dry run covers: the trigger firing on schedule and the instructions handing off to the script correctly. The script can look perfect and still never fire.

## Edit and manage

Tune a routine from the Routines page, or just ask Lindy:

* *"Change my morning routine to 9am instead of 8am."*
* *"Pause my follow-up bumps."*
* *"What routines are active?"*

## Relevant Docs

<CardGroup>
  <Card title="Skills" icon="graduation-cap" href="/teammate/skills">
    Reusable playbooks Lindy picks up on its own
  </Card>

  <Card title="Home" icon="house" href="/teammate/home">
    Where you talk to Lindy and see what it's done
  </Card>
</CardGroup>


# Set up Lindy
Source: https://docs.lindy.ai/teammate/setup

Get Lindy into your team's Slack, link everyone, and connect your email, calendar, and phone.

<Frame>
  <img alt="Lindy in #growth: asked why signups are down this week, it traces the answer across four tools and finds that Tuesday's CSS change buried the mobile signup button, with mobile down 61 percent" />
</Frame>

Setting up Lindy has two parts: an admin adds Lindy to your Slack workspace, then each person links their account and connects their tools.

## 1. Set up your team

<Steps>
  <Step title="Install Lindy into Slack">
    From Lindy (signed in), open **Integrations** in the left sidebar. **Set up Lindy Teammate in Slack** sits at the top of the page. Click **Install Slack app**.

    <Frame>
      <img alt="The Integrations page in Lindy with a Set up Lindy Teammate in Slack card at the top and an arrow pointing to the Install Slack app button" />
    </Frame>

    Slack's standard approval screen opens so you can approve the bot's permissions. Pick your workspace, then click **Allow**. As the installer, you're linked to your Lindy account right away, with no extra step.

    <Frame>
      <img alt="Slack's Allow the Lindy app to access Slack screen, with the workspace picker and an arrow pointing to the Allow button" />
    </Frame>

    Once it's installed, Slack shows under **Enabled** in your Teammate settings. Open it to confirm the workspace and a status of **Installed**, and to control whether Lindy auto-joins public channels.

    <div>
      <div>
        <video />
      </div>
    </div>

    Right after install, Lindy sends you a welcome DM confirming it's connected and explaining how to start.
  </Step>

  <Step title="Teammates link with one tap">
    Everyone else links themselves. The first time a teammate DMs or @mentions Lindy, it doesn't start working yet, it sends one DM with a **Connect Slack to Lindy** button. They tap it, confirm while signed into Lindy, and their Slack identity is bound to their Lindy account. The message they sent is replayed automatically once they're linked, so nothing is lost.
  </Step>
</Steps>

## 2. Set up your Lindy

Once you're linked, connect your own tools so Lindy can work for you:

<Steps>
  <Step title="Connect email and calendar">
    Connect your Google or Microsoft account so Lindy can run your inbox and schedule meetings.
  </Step>

  <Step title="Add your phone">
    Add your phone number (or connect Apple Messages) so you can text Lindy. You'll verify with a code.
  </Step>
</Steps>

## How to talk to Lindy

* **DM the bot** to start or continue your own rolling task. Replies come back in the DM.
* **@mention Lindy in a channel or thread** and it replies inside that thread, never as a new top-level message. Invite the bot to the channel first if it isn't there. Once it's replied, a clear follow-up can continue the thread without re-\@mentioning.
* **Slack's AI sidebar** works too; replies stay in that sidebar thread.
* **Auto-join:** the bot can join public channels when linked teammates join, and leave when the last one does. This is configurable.

<Frame>
  <img alt="A teammate @mentions Lindy in #sales to ask what customers pushed back on this month, and Lindy replies in the channel with the sources it searched" />
</Frame>

## What Lindy can do

* **In shared channels and threads:** web search, image generation, public Slack search, and Notion (if your team has connected it). Lindy keeps answers public-safe: it summarizes rather than pasting private data into a public channel.
* **In your DMs and your own threads:** the full toolset, including calendar scheduling, email, SMS, reminders, and meeting reads.
* **Extras:** private summaries when you're pulled into a long thread, and follow-up nudges for asks that haven't gotten a reply.

## Guardrails and approvals

Each connected account has one setting: **Always allow** or **Ask for approval**, applied to every action that writes or sends. Read-only actions never need approval. Approval is enforced in shared Slack threads; your personal DMs keep their existing confirmation behavior.

## Relevant Docs

<CardGroup>
  <Card title="Home" icon="house" href="/teammate/home">
    Where you talk to Lindy and see what it's done
  </Card>

  <Card title="Pricing" icon="tag" href="/pricing">
    Seats, credits, and the shared pool
  </Card>
</CardGroup>


# Skills
Source: https://docs.lindy.ai/teammate/skills

Teach Lindy how you work: reusable playbooks it picks up on its own when a request calls for them.

A skill is a playbook you teach Lindy: a named set of instructions for a procedure you repeat, like *how I write my weekly report*, *how I triage my inbox*, or *how I prep for a customer call*. Describe the process once, and from then on Lindy picks the right skill whenever a request calls for it. You never have to remember to invoke one.

Think of skills as everything Lindy can do, plus what it can learn from you.

<div>
  <div>
    <video />
  </div>
</div>

## How to Set It Up

<Note>
  Open **Skills** from the left sidebar to see every skill Lindy has, create new ones, edit their instructions, and turn them on or off.
</Note>

## Create a skill

<Tabs>
  <Tab title="In chat">
    Tell Lindy how you want something handled, like *"When I ask for my weekly report, pull the numbers from the dashboard, lead with the top three changes, and keep it under a page."* It saves the process as a skill and uses it from then on.

    <div>
      <div>
        <video />
      </div>
    </div>
  </Tab>

  <Tab title="On the Skills page">
    Click **New skill**, give it a name and a description, and write the instructions. The description matters: it's how Lindy decides when the skill applies.

    <div>
      <div>
        <video />
      </div>
    </div>
  </Tab>
</Tabs>

## Three kinds of skills

<CardGroup>
  <Card title="Your skills" icon="user">
    Personal to you. Lindy uses them only for your requests.
  </Card>

  <Card title="Team skills" icon="users">
    Shared across your workspace, so everyone's Lindy works the same way. Managed by workspace admins.
  </Card>

  <Card title="Built-in skills" icon="wand-magic-sparkles">
    Ready to use out of the box. Browse the library and install the ones you want.
  </Card>
</CardGroup>

<div>
  <div>
    <video />
  </div>
</div>

You can customize any built-in skill by making your own version, then editing it like a skill you wrote yourself.

## How Lindy picks a skill

Lindy always sees the list of available skills, just their names and descriptions. It loads a skill's full instructions only when the skill is actually relevant to what you asked. That way it has the right expertise on hand without slowing anything down.

<div>
  <div>
    <video />
  </div>
</div>

## Good to know

* **Early access**: Skills is rolling out gradually behind feature flags, and isn't available to everyone yet.
* **Turn skills off, don't delete them**: flip a skill off on the Skills page when you want Lindy to stop using it but might want it back.
* **Descriptions do the routing**: if Lindy isn't picking a skill when you expect, make its description more specific about when it applies.

## Relevant Docs

<CardGroup>
  <Card title="Routines" icon="bolt" href="/teammate/routines">
    Standing instructions that run on a schedule
  </Card>

  <Card title="Ad Hoc Tasks" icon="wand-magic-sparkles" href="/features/ad-hoc-tasks">
    One-off jobs you hand to Lindy on the spot
  </Card>
</CardGroup>


# Slack Commands
Source: https://docs.lindy.ai/teammate/slack-commands

Slash commands for managing your Lindy connection, context, and usage right inside Slack.

There are two ways to interact with Lindy in Slack: **@mention** her when you want a response, or use a **slash command** to manage your connection.

## @mention Lindy for a response

@mention Lindy in a channel or thread whenever you want an immediate response. It replies right inside that thread.

<Frame>
  <img alt="A teammate @mentions Lindy in #metrics to pull this week's ad spend report; Lindy pulls spend from three tools and replies in the channel with a Paid spend card, a flagged campaign, and a button to open the full report" />
</Frame>

Once Lindy has replied in a thread, you don't need to keep @mentioning her. Lindy reads the thread and disambiguates whether your next message is aimed at her or at the other people in the conversation, so a natural follow-up keeps the thread going without the extra @mention.

## Slash commands

Run these in any Slack message box to check your connection, tune how much context Lindy reads, or manage your account. Type the command and press enter, the response is only visible to you.

### Admin commands

Workspace admins use these to check the connection and control the **context lookback**, how far back in a conversation Lindy reads for context when it's brought into a channel or thread.

| Command                        | What it does                                           |
| ------------------------------ | ------------------------------------------------------ |
| `/lindy admin status`          | Show this workspace's connection status.               |
| `/lindy admin convogap status` | Show the current Slack context lookback.               |
| `/lindy admin convogap 10`     | Set the Slack context lookback, in minutes (here, 10). |
| `/lindy admin convogap reset`  | Reset the context lookback to the default.             |

<Note>
  A longer lookback gives Lindy more of the preceding conversation as context, at the cost of pulling in older, possibly less relevant messages. `reset` returns to Lindy's default window.
</Note>

### Personal commands

Anyone can run these for their own account.

| Command           | What it does                                             |
| ----------------- | -------------------------------------------------------- |
| `/lindy usage`    | Show your Slack diagnostics for the last 7 days.         |
| `/lindy usemodel` | **Coming soon.** Run your next task on a specific model. |
| `/lindy unlink`   | Unlink your Slack account from Lindy.                    |

<Warning>
  After `/lindy unlink`, Lindy stops responding to your DMs and @mentions until you link again. The next time you message the bot, tap **Connect Slack to Lindy** to reconnect.
</Warning>

#### Run one task on a specific model

<Note>
  `/lindy usemodel` is coming soon and is not available yet. Here is how it will work.
</Note>

Type `/lindy usemodel` in any Slack message box and press enter. A modal opens with a model dropdown. Pick the model you want and it applies to the next task you ping Lindy with. That one task runs on the model you chose, and everything after it falls back to the default.

Use it to:

* Test the same task on two different models and compare the output
* Force a specific model for a single gnarly task

The override is one task only. It sets the model for the task started by your next Slack ping, holds for that whole task, then resets. A confirmation message shows which model was set, visible only to you.

## Relevant Docs

<CardGroup>
  <Card title="Set up Lindy" icon="slack" href="/teammate/setup">
    Add Lindy to Slack and link your account
  </Card>

  <Card title="Team Setup" icon="users" href="/start-here/team-setup">
    Invites, admin controls, and credits
  </Card>
</CardGroup>