> ## Documentation Index > Fetch the complete documentation index at: https://docs.lindy.ai/llms.txt > Use this file to discover all available pages before exploring further. # Use cases > What teams actually ask Lindy for, by role. Scroll for ideas, then try the closest one on your own tools. Every one of these is a single message: an `@mention` in a channel, or a text to Lindy. ## EA Inbox management, scheduling, prep, meetings.
A text thread with Lindy at 8:12 AM: it says good morning, notes a nice day at 67 degrees, flags the big call with Nike today and that it already sent them a reminder to confirm, and reports 42 new emails triaged overnight with replies drafted, only John urgent and wanting to meet today. The reply asks Lindy to send the prep and book the time with John
## Sales Lead enrichment, follow-ups, CRM updates, pipeline management.
In #sales, Bruno says the team just closed Meridian and asks Lindy to run the handoff. Lindy runs it across five tools: marks Meridian closed won in HubSpot, drafts the customer handoff doc, posts deal notes in #customer-success, schedules kickoff for Thursday 2:00 PM, and sends the welcome email to four recipients
## Support Ticket triage, routing, drafted replies, escalation.
In #support, Ian says overnight tickets came in hot and asks Lindy to triage and get replies ready. Lindy triages 38 tickets across Zendesk, Intercom, and Slack: routes 31 by topic and severity, drafts replies from the help center, escalates 2 refunds with full context, and notes 5 are waiting on you while the rest can send as-is
## Engineering Ticket triage, bug investigation, code review, oncall.
In #eng-oncall at 2:14 AM, Jonathan says checkout errors are spiking and asks Lindy to look before he wakes up. Lindy investigates across GitHub, Slack, and Snowflake: reproduces the 500 on staging, traces it to the payments retry loop, and opens PR #2841 with a fix and a test, showing the diff that stops retrying a captured payment
## Marketing Dashboards, reporting, attribution, competitive tracking, customer stories.
Jonathan asks Lindy to build a dashboard of marketing spend across channels for the last two weeks. Lindy pulls the spend, builds it, and publishes it to the workspace for anyone on the team to open: $48.2k total spend, 3.4x blended ROAS, Meta as top channel, with a daily spend bar chart
## People Onboarding, tickets, screening, feedback.
In #onboarding-at-lindy, Sarah asks what she needs to set up in week one. Lindy checks Notion, Trello, and Workday and answers: I-9 verification due today, Workday forms before payroll, benefits close in 30 days, and confirms access is already granted
## Meetings Ask about any call, then act on what you learn.
Ryan asks Lindy for the top objections from this week's sales calls. Lindy answers pricing, security, and setup time, with a link to view the three calls. Sarah asks Lindy to turn these into battle cards for the team, and Lindy shares an Objection battle cards doc on Google Drive
## More examples Not tied to a role. Anyone on the team can ask for these. ### Find answers Ask across Slack, meetings, and your tools. Lindy digs up the answer and the file or decision behind it. 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 ### Build decks Hand Lindy the deck. It pulls from your meetings and tools and comes back with slides, charts, and commentary, ready to present. 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 ### Catch up Been out, or dropped into a busy channel? Lindy gives you the TL;DR and exactly what needs you. 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 Get it into Slack and link the team. Teach it the ones you repeat.