正在加载视频...

视频加载失败

Our Customer Support team gets thousands of questions a week. So we built a Custom Agent to help. It searches everything, responds with citations, and gets the team to the right answer fast. When it can't find one, it files a task so we can document the gap. And...

16,506 次观看 • 6 个月前 •via X (Twitter)

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Excited to have Little Plains featured as a Notion case study. We've been tinkering with their product since we started the agency and earlier this year we got to demo some of our custom agentic workflows to Ivan Zhao and their leadership team. I remember reading a deep dive they did on Every 📧 and Dan Shipper, and being inspired by how advanced yet approachable these workflows felt. This has felt full-circle, and one of the reasons I'm so pumped to running a studio again. How we use Notion We use the software today as the contextual intelligence layer of our agency. Almost everything flows in and out of it, while also residing there: client briefs, meeting transcriptions, talent inquiries, custom new business proposals, finance, our internal agent hub, and our new site's repository management. The APIs and MCP connectors let the rest of our stack read from it, so the context travels with the work. Four specific ways we're using it today: Client project homes Every engagement starts with a custom deep research agent we built. It takes everything we have on a new client, plus public information and market research, and writes a full deep dive on the company, the founders, the space, and where the real opportunity sits. It lands as a Notion doc, saves out as Markdown, and loads into a shared team project in our LLM, so anyone here can chat with the entire repository of context from day one. That same Notion page then carries the brief, goals, meeting notes, decisions, and open questions through strategy, design, Figma, Flora, and client review. One home, so the original idea survives the handoffs. New business proposals We take the new business meeting transcriptions, using the potential client's own words and nuances, and input them into a custom template we've developed. We can shape the story, scope, timeline, team, case studies, and budget in Notion, then integrate each part of the proposal into Sanity to power the client-facing microsite. Alex Leiphart, our Head of Product, calls it an intelligent CMS driving the back end of every proposal, with a front end that wows clients time and time again. Talent intake We had a talent post go viral recently with over a quarter million views and over 2,500 submissions. Luckily, we had built a Notion-powered workflow where applicants submit role, portfolio, availability, timezone, and interests. An agent pushes it into Slack, where our leadership reacts with their custom emoji, and the agent drafts an email with that person's calendar link and updates the master talent database. With all this info, we can go back into Notion to filter by timezone, rate card, availability, capabilities, or our own notes. It's helped a lot for a small team dealing with a huge inflow. Agent hub Before anyone at Little Plains builds or operates an internal agent, they write down what it's for, how it works, what information it can use, and where a person stays in control. Those briefs, and the agent's associated information, live in one hub so the whole team can see what's being built and why. Structure is what makes the experimenting sustainable, whether you're a relative novice at agentic work or a pro-grade engineer. A rising tide raises all boats. Thanks to Alex Leiphart, Caroline Bel-Kher and the entire LP team for this. Read the full piece:

Emmett

20,066 次观看 • 18 天前