Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

Most AI support bots aren't actually solving problems. They're assigning homework. Customer: "I need an invoice." AI: "Go to Billing → Settings → Invoices." Customer: 😑 That's not resolution. That's directions. The new shift happening in AI support isn't better answers. It's agents that can actually finish the job....

396,250 görüntüleme • 2 ay önce •via X (Twitter)

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

🚨 THIS IS ACTUALLY INSANE Your AI agent can have access to the web. But if it can't reliably read what’s actually on the page, that access is almost useless. We looked at Firecrawl as the web layer for AI agents and the numbers are hard to ignore. The setup is simple: Give it a URL, search query, or website. Firecrawl handles the ugly part — crawling, scraping, rendering, extracting, and turning web content into something an AI model can actually use. The headline numbers: → 173,000+ GitHub stars → Search, scrape and interact with the web at scale → Supports web pages, PDFs, DOCX and other content → Structured data extraction for AI workflows → MCP support for connecting it directly to AI agents The workflow looks like this: Search → Scrape → Crawl → Extract → Feed the agent Three things stand out: 1. Scraping becomes an infrastructure layer Instead of maintaining your own pile of HTTP clients, parsers, browser automation and retry logic, you can treat web access as an API. 2. Agents get more than raw HTML The goal isn't just downloading a webpage. It's turning messy web content into clean context that an LLM can reason over. 3. The same layer works across different agent workflows Research agents. RAG pipelines. AI search. Competitive intelligence. Web-data extraction. The interesting shift: AI agents don't just need better models. They need better access to the information those models are supposed to reason about. Firecrawl is building that layer. Save this repo.

Vikas gupta

18,053 görüntüleme • 3 gün önce

New short course: Serverless Agentic Workflows with Amazon Bedrock. Learn to build and deploy serverless agents in this course created with Amazon Web Services and taught by Mike G Chambers, a Senior Developer Advocate at AWS specializing in GenAI. (Disclosure: I serve on Amazon's board.) Generative AI applications are becoming more complex, sophisticated, and agentic. Agentic applications have workloads that can be hard to predict in advance -- for example, what tools will it decide to call? -- and a serverless architecture helps you efficiently providing on-demand resources. This course teaches you to build and deploy a serverless agentic application. You’ll learn to create agents with tools, code execution, and guardrails, and build responsible agents for business use cases: - Build a customer service bot for a fictional tea mug business that can answering questions, retrieve information, and process orders. - Connect your customer service agent to a CRM to get customer info and log support tickets in real-time. - Explore how you invoke the agent, and see the trace to review the agent’s thought process and observation loop until it reaches its final output. - Attach a code interpreter to your agent, giving it the ability to perform accurate calculations by writing and running its own Python code. - Implement guardrails to prevent your agent from revealing sensitive information or using inappropriate language. By the end, you will have built a sophisticated AI agent capable of handling real-world customer support scenarios. Please sign up here!

Andrew Ng

81,048 görüntüleme • 1 yıl önce

NEW: Introducing Octane AI Agentic Commerce Quizzes - Increase sales with AI. What is it? A sales quiz AI agent that makes 1-1 personalized sales experiences for every single customer. In real time. Powered by our new AI model CORE-1. Examples: 📸 Want to ask your customer to take a selfie and your AI agent automatically recommends them a full outfit from your catalog? Octane AI agents can do that. 🪞 Want to have an AI agent hand pick out each product for a personalized skin care routine? Want them to upload a selfie to detect their skin tone? Octane AI agents can do can that. 📊 Want to create an incredibly detailed report with graphs and tables and graphics thats generated by AI for each customer? Octane AI agents can do that. We give you the building blocks and you can build anything. And you can build it fast because our AI will do the heavy lifting for you. This is v1 and a representation of where our commerce and quiz technology is headed. Available today to everyone at 🆕 What we are launching today: • Smart Quiz Builder: Have an AI agent plan out and build your Octane AI quiz for you. It can even write custom HTML for beautiful results pages and progress bars. • Smart Products: It can take forever to setup the recommendation logic for a quiz. For those of you who need help, simply add smart products to your Octane AI quiz and your very own AI agent will hand-pick products for each customer who takes your quiz. It’s amazing. • Smart Copy: Instead of showing everyone who takes your quiz the exact same copy, use AI to personalize the quiz for every single person who takes it. Explain why these specific products are perfect for specifically them. • Image Analyzer: Let your customers upload or take a photo during the quiz and have AI analyze it. You can use this for anything from skin tone detection to picking out outfits! • Shopping Assistant: An AI agent that lives on your store that can help your customers at the right time. We have been building quiz software for almost 10 years now and AI is enabling us to make quizzes even more powerful. This is just the v1 of what we will be releasing in this area. We are so excited to see what you create with these new agentic products. Get creative, we think you will be surprised at how many interesting experiences you can create with Octane AI now.

Matt Schlicht

290,863 görüntüleme • 9 ay önce

What does it actually mean to be AI native? There was no clear guide on the internet for how to become AI native so we built the definitive one (60 min masterclass): 1. An AI native org has 3 layers: people for strategy and taste, agents for execution, and a shared context layer that makes the entire company readable to agents. 2. AI eats the middle of your work. You used to spend 80% of your day on execution. Now agents do that. Your job is the bookends: deciding what to do and judging whether it's good enough. 3. Everyone is a manager now. Your output is the output of your agents. If your agents produce garbage, that's on you. You set them up wrong. 4. Using ChatGPT doesn't make you AI native. That's like having a website and calling yourself a tech company lol. 5. No AI native org without AI native people. Most companies skip straight to the tools. That's why it fails. If your people don't understand how to manage agents, the tech doesn't matter. 6. Making your company "readable" to agents is the real work. Every process, every decision, every piece of knowledge needs to exist in a format an agent can consume. Most companies are nowhere close. 7. Speed without signal is just expensive chaos. You need the system to move fast AND know if you're moving in the right direction. 8. The skill chain is how agents get good at your specific workflows. Skills build on skills. The more you invest in them, the more your company compounds. 9. The moat is the system. People managing agents, agents reading from rich context, the whole thing getting smarter every week. That compounds. Your competitor can copy your tools. They can't copy your system. Full episode with Theo Tabah from LCA on The Startup Ideas Podcast (SIP) 🧃. This is the stuff we normally keep internal but all the sauce is yours. Theo Tabah is the brains behind advising the world's biggest companies on AI and building AI products. Your fav CEO's first call for figuring out AI. You are in for a treat Become AI native in under 60 minutes Watch

GREG ISENBERG

84,760 görüntüleme • 3 ay önce

🚨 this chinese guy makes over $1,000,000 a year… by building AI agents. no employees. no massive startup. he just keeps building. while most people are still asking ChatGPT random questions, he’s using Claude to build software that solves real problems. this is what people call vibe coding. he opens Claude and says: “build me an AI agent for real estate businesses that creates property videos.” Claude writes the code. builds the interface. adds subscriptions. helps deploy the app. within a day, he has a working product. then he starts building the next one. that’s the part most people don’t understand. he isn’t trying to build one billion-dollar company. he’s building dozens of AI agents, each solving one problem for one industry. → an AI agent for dentists → an AI agent for ecommerce brands → an AI agent for podcasters → an AI agent for real estate businesses each one automates work that people normally do by hand. each one is built with simple prompts. each one can become a real business. the crazy part? you don’t need to be a software engineer anymore. you need to know how to think like a builder. how to spot problems. how to explain solutions to AI. and how to ship. that’s exactly why i’m reading this article: “How to Actually Build Your First AI Agent.” because this is the skill that’s creating the next generation of builders. the people who learn to build AI agents today won’t just use AI. they’ll own the tools everyone else ends up paying for.

MIKE

39,041 görüntüleme • 2 ay önce

“There is no competitor to ServiceTitan until the demo I saw from you guys today.” I got that DM this week from an owner who runs three home services brands. He sent it a few hours after seeing what we’ve been building. We started building AI agents three years ago with a text agent that captured leads and booked jobs. As we kept building, we learned that the system underneath the agent determined how much work the agent could do. Traditional systems of record were built for people clicking through workflows and entering data. An agent sitting on top of one faces major constraints on how much work it can complete. We wanted agents to run workflows from beginning to end, so we built the FSM around them. Larry was our first AI Employee. Because he operates inside our system, he can answer the call, book the job and put it directly on the dispatch board. An AI sitting on top of a traditional system might answer the same call, but often has to hand the rest back to the office staff. In a busy business with thousands of customer interactions, the difference between completing half the work and all of it is massive. Then we started thinking about how AI could impact the entire operation. That led us to build Operator, an orchestrator agent that can work across the schedule, jobs, invoices, payments, customer records and years of conversations. Business owners can give it work in plain English and let it carry that work across the system. As customers have started using Operator, they’ve realized they can ask it to do almost anything. One customer had 2,010 rows of equipment sitting in a spreadsheet. Operator went through the entire file, identified 78 rows that were air filter sizes instead of equipment, and attached the remaining 1,931 units to the correct customer properties. Now when a tech shows up, they already know what equipment is at the house. You can tell Operator: “Here’s our equipment list. Put every unit on the right customer record.” Another owner wanted a price book built from his own history. Operator read 455 past invoices and turned 306 free-text line items into a catalog organized around the work his company performs. He asked: “Read our past invoices and turn them into a starter price list.” One HVAC owner got access before our demo call. He asked Operator who owed him money that day and had payment reminders going out before we got on the phone. This is where we think AI is headed. You tell it what you need done, and it works across your business until the job is finished. If you want to see it, DM me.

Eric Rea

16,801 görüntüleme • 18 gün önce