WEBVTT 00:00:00.000 --> 00:00:46.235 Vappy just made creating voice agents so much easier. They just released their official skills for Claude Code. That means you can now build an entire voice agent from scratch without ever visiting the Vappy dashboard. Without reading a single page of documentation, you just tell Claude what you want and it builds I've been building voice agents for quite some time now, and this is just a massive shift in this space. By the end of this video, you'll know how to set up the Vappy MCP, install all the eight skills that they just introduced, and then also build your own voice agent in Claude Code. But before we hop into the video, let's show a live demo of what Claude Code built out for us. How this demo is gonna work, I'm gonna go through an entire call with our voice AI receptionist, and then I'm gonna show you guys the result of what happens at the end of the call. So I'm gonna go ahead, call our receptionist here, and go through booking an appointment. Build Right Construction. This is Rachel. How can I help you today? Hi, Rachel. I'm looking to get a deck built at my house. 00:00:46.635 --> 00:00:56.315 That sounds exciting. What city or ZIP code are you located in? I just want to make sure you're in our service area. Yeah. I'm in Cherville, Indiana. Perfect. We definitely serve Cherville. 00:00:56.570 --> 00:01:12.405 When are you hoping to get your deck project started? Are you thinking this season, next month, or just exploring options right now? Uh, we're hoping to have it done by early summer, so maybe start in April. Great. That gives us a good timeline to work with. Do you have a budget range in mind for your deck project, 00:01:12.485 --> 00:01:16.005 or are you still figuring that out? We're thinking around 15,000, 00:01:16.005 --> 00:01:24.085 uh, but we're flexible depending on materials and everything like that. Thanks for sharing that. Can I get your name, phone number, and email address so I can book your on-site estimate? 00:01:24.700 --> 00:01:27.820 Yeah. My name is John Snow. My phone number is 00:01:31.500 --> 00:01:34.540 and my email is johnsnow@example.com. 00:01:34.540 --> 00:01:42.165 Thank you, John. Let me check our availability for a thirty minute on-site deck estimate in April. Is there a day of the week that works best for you? 00:01:43.685 --> 00:01:54.165 Quick question before we book. Do you have an idea of what a composite deck usually runs? Great question. Mike will be able to give you an accurate quote during your on-site visit since pricing depends on size and material. 00:01:54.650 --> 00:02:04.970 Shall I check April dates for you? Can we actually do a a date in March? We have openings the week of March 9, Monday through Friday from 8AM to 5PM. 00:02:05.050 --> 00:02:08.890 Is there a specific day and time you prefer for your estimate? Can we do Monday? 00:02:10.365 --> 00:02:15.645 I think it's March 9 at 10AM, please. You're all set for Monday, March 9 at 10AM. 00:02:15.805 --> 00:02:21.165 Mike Thompson will meet you for your deck estimate. Thanks so much, John. Anything else I can help with today? 00:02:21.405 --> 00:02:23.165 Nope. Thank you so much, Rachel. 00:02:23.485 --> 00:02:23.805 Goodbye. 00:02:26.670 --> 00:02:27.470 I mean, 00:02:27.790 --> 00:05:16.750 sometimes you really can't tell if that's a real person or not. Enough of me rambling. Let's go check the results. Taking a peek at our Google Calendar, we can see that our deck estimate at 10AM for John Snow was set up here properly. So we know that our agent had access to our calendar, was able to check the availability, and actually book an appointment. We also see that in our little CRM here, all the called data got logged. The only thing I noticed right away is Cherville got misspelled, so that's a fix that we would have to make. April early summer timeline, but the budget was correct. The appointment date is correct. Are they qualified? Yes. Any notes? And then we also get the call duration here. One more thing we gotta check is that if we got an email sent to us for an end of call report. Hopping into our email, we can see that we've got an end of call report. We got the caller's phone number, total cost of the call, which ran about 24ยข. We have the full transcript of the call, and then we could also listen to the call recording. And keep in mind, I did about 80% of everything you just saw right here in Cloud Code. First, I'll explain what these Vappy skills are and how you can connect it into your Cloud Code, and then we'll get into the live build. If you've ever had the thought cross your mind about how your business can leverage AI automation and you just don't know where to start, that's totally okay. You're not alone. That's exactly what we do here at Deep Rooted AI. There's no need for you or your staff to learn any of this stuff. Custom AI solutions, ongoing support tailored to exactly how your business runs. Use the link in my description to visit my website and book a discovery call with me today. So what are Vappy skills? And if you caught my video last week, you kind of already know, but skills are essentially knowledge files that teaches your AI coding assistant how to use specific tools. Here's the official announcement of Vappy introducing their skills and their MCP. These are the eight skills that are available. So set up your API key, create an assistant, create a tool, create call, create squad, create a phone number even. This is some really cool stuff. This is the most important one in my opinion, set up webhook. You can easily connect it into any of them without manually configuring any webhooks. And then the cool part is anything beyond these eight skills, the MCP connector can go query the documents and find anything out for you and then actually do that as well. MCP and the eight skills work across all agents. So whether you're using Cloud Code, Gemini CLI, Codex, whatever you're using, you can install this MCP and all the skills that go along with it to build your own voice agent. If you wanna install the MCP and the skills for yourself, all you gotta do is go here. This is in the instructions. What I would do is just copy and paste this entire blog post, put it into Cloud Code or whatever coding platform you're using, and then have it install for you. Okay. So I wanted to show you guys how to quickly install this MCP server and these skills. I literally took the entire blog post link. I said, take a look at this blog post, then follow the instructions on how to set up the VAPI MCP and install the skills. You can send it off, put it in edit automatically mode, and then it'll kinda ask you questions and get your API key and then set everything up. So it's as easy as telling Claude code to do it. You don't need to do anything manually yourself besides going to VAPI and getting your API key. Now I'm not gonna send this off because I've already installed the MCP and skills, but I did wanna show you guys how easily you can do this for yourselves with the help of Cloud Code. Now you'll know these skills are installed because you could just do something like slash create, and you'll see slash create call, create squad, create assistant. So you'll see some of those in there. And then also if you do slash MCP status, 00:05:16.910 --> 00:09:23.060 you'll be able to see that the MCP server VAPI docs is available, and you can use the MCP server. That's how you'll verify everything was set up correctly. Now that we have our VAPI MCP setup and the eight tools that go along with it, here's our empty Claude code project. We just have a Claude dot MD file. Every single project should start with one of these, gives it an overview of everything that we're gonna be building inside of this project, and gives it, you know, some instructions on where to start and where to finish, what the end result is, and things like that. So I'll scroll through this a little bit. You guys can check this out. I know it's probably hard to see everything, probably very hard. Anyways, you guys understand what a cloud dot m d file is. If you don't, highly recommend going to watch some of my other videos to have a full understanding of what we're actually doing here. But now we're gonna go ahead and start off building this voice agent inside of Claude code. Okay. So the first step is to actually start off the entire process. So we're gonna kick off a prompt that says, let's build a voice agent. What should happen is our Claude dot m d file is instructed to help us set up the VAPI API key first before we get into any building. You'll see that Claude prompted us letting us know that we have a fresh project. The only thing that we had was the claude.md file, and then it gave us the six phases that we have to work on while building out this voice agent. Phase one, setting up the dot ENV file, getting all our API key set up. It says before we start, I need a few things from you. We have everything here set up already except for this VAPI API key. So it says, should I run the VAPI setup API key? And then I'm gonna put the command. We need to set up our VAPI API key. Everything else is set up. I'm gonna go ahead, send this off, put it up in bypass permissions mode, and I'll get back to you guys with how we're gonna set this up. Cloud Code is letting us know how to set up this VAPI API key. This will be one of, like, two times that we even have to go to the dashboard to set this up. So we're gonna go grab our API key, paste it in here, and let Cloud Code set up all the files. If you've never set up your VAPI dashboard yet, this is what it'll look like when you create an account. All you're gonna do is hop over to the left here, API keys, and we're actually going to copy over the private key. You just need to click on this little eye. It'll show you the private key. You'll take that key and paste it into Cloud Code. It'll help you set up the rest of the files. Now we've got our API key. It's time to put it in the prompt, send it off, and watch the ENV file get created. Okay. Our API key was validated and saved in our dot ENV file up here. We also created a dot git ignore, which just means all our variables are dot ENV files. Any API keys, if we push it out to GitHub, they don't go along with it. They just stay inside of our Cloud Code instance. So this is just for some security stuff and protection. Make sure you're always protecting your API keys. Our Google Calendar, Google Sheets is connected. And then once we actually create the Google Sheet for this AI receptionist, we're gonna need to get the spreadsheet ID and put it in the dot ENV file. Now that this is all done, we're actually gonna go ahead into phase two and start building out this voice agent. Okay. So the way that I have this set up in order to avoid something called context route, I set up this CloudMD file to have different phases. So every time we complete one phase, you can just clear the chat window and start the next phase. So in order to start this next phase, all I need to do is type in, hey. Start phase two. And then send that off. I actually put a slash there, but that's fine. And now we're gonna get to work on phase two. So this is actually pretty cool because of the way I have my Claude code set up in order to protect my environment variables, like my API keys and anything that's in that dot ENV file. I actually have to go back, grab it from the dot ENV file, and paste it because Cloud Code does not have access to it. It's kind of annoying a little bit when you're doing this on bypass permissions mode, but, again, protection over your API keys is everything. So I'm gonna go ahead, paste those in, and then I'll get back to you with the results from Cloud Code. Okay. So Cloud Code just finished up phase two. It created a Google Calendar check availability tool. It created a Google Calendar create event tool, a log lead tool. It saved all tool configs to the tool config JSON up here, and then also enabled two functions and call and transfer. Now we're gonna hop into VAPI to make sure all that was actually created so you guys can see how sweet this is. In our Vappy dashboard, we're gonna go over here to the tool section, and we can see here that all five tools were created. All of the parameters were set up. It even gave us descriptions. It even put in the Google Sheet settings along with the calendar ID settings. It transferred to Mike tool call and then the end tool call function as well. I mean, this is this all happened from Cloud Code. I didn't go into the Vepi dashboard. You guys saw it. That's this is so wild. Anyways, let's go continue with phase three. And just like we did last time, we're just gonna tell Cloud Code to start phase three. Begin phase three. Phase three is now kicking off. It's gonna go check what it built in phases one and two, and then I'll get back to you guys with the results, and we'll go through everything that it did. Alright. So we finished up phase three. We actually created our entire assistant. Her name is Rachel for Build Right Receptionist. This is the model that we used, OpenAI GPT 4.1. 00:09:23.060 --> 00:09:58.820 Vappy Clara is the voice that we use. So all this stuff just happened in Vappy. We're gonna go confirm it here in a second, but I do wanna scroll up a little bit here and show you guys everything that it did. So it confirmed that phase two was complete, and then it went through the Vappy create an assistant tool, which is the one of those eight tools that we installed earlier, and then it did the entire thing. We had to just put in a phone number for the transfer call, but everything else was updated. We had to update our ENV file locally just because that's how I have it set up. But other than that, everything is set up. Let's go check it out in VAPI. Okay. So back in VAPI. Now we're just gonna verify that Cloud Code did everything that it said it did. It build out Rachel, the build right receptionist, OpenAI GPT 4.1, 00:09:58.820 --> 00:10:20.690 assistant speaks first. It gave it a first message. It wrote the entire system prompt for this, which looks pretty in-depth. Obviously, you know, you gotta be careful with these agents. You know, you want you wanna go make sure verify everything before, you know, pushing this to production or something like that. But for the sake of this demo, I think it looks good. It's just crazy that it can write that and inject it right into VAPI. Gave us a max token count of 300. The temperature is 0.7. 00:10:20.690 --> 00:10:40.955 Let's see some of these inline tools that it gave us. So we got some tools here. It connected the three tools that we created. It also enabled the end call function, which is pretty cool. And then if for the summary, there's nothing. I don't think it did anything over here. But, yeah, configured our entire voice agent all from Claude code. Let's go ahead and keep working on it, get to phase four. You guys already know the vibe. Claude, build phase four. 00:10:41.435 --> 00:12:26.595 Once again, it's gonna check the current project state to see what it's built. It's gonna confirm that phases one through three are complete with everything that it did in those phases. You guys start to see a little bit of a pattern here. We're just confirming the work. We're letting Cloud Code do everything. We're verifying it. And if we need to make any changes, it'll make those changes for us. Man, I got worried for a second. It said buying a VAPI phone number and assigning it to Rachel. Thank god I don't have anything connected to this, but that'd be really crazy if it did. What's really happening is it's just creating a free VAPI phone number that VAPI provides. Okay. So VAPI finished up phase four, which is just as simple as creating the phone number and assigning it to Rachel, our assistant. We're gonna go ahead and verify that in Vappy and then get back to working on phase five. The phone number settings, we can see that the phone number was created, build the right construction main line. Did he connect it to Rachel? Yep. Rachel assistant build the right receptionist with the inbound phone number so I can make inbound and outbound calls. This is, like I just can't believe I'm doing this in Claude code, it's actually doing it in VAPI. I know MCPs have been around for a while and all these skills, but it still just blows my mind every single day. I'm starting to sound like a broken record here, but let's continue with phase five. Okay. So this phase is a little bit heavier where we actually created the webhook and the n eight n workflow that's gonna capture our end of call report and send us an email. We created the server URL for VAPI and connected it, and then we also created the n eight n workflow, which looks like this. We went ahead and imported it. Super simple workflow just to capture the end call report. We'll hop back into Versus Code here, and then it just tells us, you know, how to deploy it, what to set up here, and then, yeah, we're good to go. And now we're gonna go on to phase six, which is testing. Onto the last and final phase. Okay. Claude came back with a couple of tests for us to verify. The first one will be step 6.1, which is an outbound test call. Claude is gonna use its VAPI create call tool to have Rachel call our phone. Then we're gonna do an inbound test call, and then we're gonna make sure everything works with our NNAN workflow. So let's go ahead, start phase 6.1, and let's get this call and see what happens. 00:12:27.955 --> 00:12:34.755 Here comes the call. Let's answer that and see what happens. Instruction. This is Rachel. How can I help you today? Hey, Rachel. I'm looking to 00:12:35.920 --> 00:12:37.200 build a new patio. 00:12:37.680 --> 00:12:47.280 That sounds exciting. We'd love to help with your patio project. Can I get the city or ZIP code where the work would be done? Yeah. Crown 0.463307. 00:12:47.680 --> 00:12:52.835 Perfect. Crown Point is right in our service area. When are you hoping to start your patio project? 00:12:53.075 --> 00:12:58.915 This season, next month, or are you just exploring options for now? Let's do next month. 00:12:59.395 --> 00:13:07.970 Great. We can definitely help with that timeline. Do you have a budget range in mind for your new patio, or are you still figuring that out? I'm still figuring that out. 00:13:08.370 --> 00:13:11.010 No worries at all. We'll help you explore options. 00:13:11.250 --> 00:13:17.965 Can I get your name, phone number, and email address to set up your estimate appointment? Yeah. My name is John. My phone number is 00:13:21.565 --> 00:13:23.965 And my email is john@example.com. 00:13:23.965 --> 00:13:28.845 Thank you, John. I'll check our calendar for the next available thirty minute on-site estimate in Crown Point. 00:13:29.570 --> 00:13:32.290 Would you prefer a weekday or Saturday morning appointment? 00:13:32.610 --> 00:13:36.930 Can we do this Saturday morning? We have openings this Saturday morning. 00:13:37.090 --> 00:13:41.010 Is there a specific time between 9AM and 1PM that works best for you? 00:13:41.490 --> 00:14:00.430 No. Let's do 9AM. You're all set for your on-site patio estimate. Saturday, March 7 at 9AM. Mike Thompson, our owner, will meet you. Thanks, John. Anything else I can help with today? No. That'll be it. Thanks so much for calling, John. We look forward to meeting you Saturday morning. Have a great day. You too. Goodbye. 00:14:01.870 --> 00:16:49.990 Wow. So for our first shot, and we didn't really change the prompt too much, I think that was a really successful test. Let's go check out our calendar, our Google Sheet, and make sure everything functioned as it should. Inside of our calendar, we can see that our 9AM appointment on March 7, which is a Saturday, was booked at John Example dot com. Obviously, we're not gonna send an email to that because it doesn't exist, but we know that our receptionist had access to our calendar and was able to book an actual appointment. Hopping into our Google Sheet here, we can see that everything was populated correctly. The only thing I noticed was that the call duration didn't fill in, and we didn't get an email getting our end of call report. So I know that the NNN workflow failed, but that's no problem because we're just gonna go hop back into Cloud Code, figure out what happened, and get that fixed, and then we'll test again. Okay. So I'm glad this happened because I wanna make it clear that AI cannot one shot everything. It could pretty much do 80% of the work, but you're gonna have to go in there and fix some problems or just have Cloud Code help you fix those problems. So what had happened was our end and end workflow wasn't set up properly. So I went through a little bit of a process of getting that fixed up for us with some testing. You guys can see it here. Uh, there's just a couple of things that we needed to change. And then now we're at the point where everything works properly. I did a couple of tests off camera, and we're good. But now we have two more remaining tests, which is an inbound test call, and then verify the email notification arrives in Gmail. I went ahead and already did that. So let's go ahead, hop in our Gmail, and check out what that email looks like. So we created a little HTML for the email just to break down the call that we had, and this is what it looks like. Build right construction call report, the caller number, the duration of the call, how much the call cost, and then anything else that you need. It also provides a listen to the recording. So if you wanna go listen to the call recording and then be able to make changes to the prompt or do whatever, you'll have access to do that as well. I just wanted to showcase that really quick because these agents aren't perfect, but they can really save you a ton of time. If you wanna learn how to start making money with AI or just begin your AI journey, I highly recommend that you join my friend Nate's school community AI automation society plus. It's where I started back in August, and I've learned so much in the past six months of me being there. You'll get access to courses that teach you how to master n eight n, learn everything you need about Cloud Code, and even how to run your own AI automation agency. You'll also join a community with over 3,000 members actively making money with AI. Use the link in my description to join today, and I hope to see some of you in there very soon. So we just built an entire voice agent from scratch using Cloud Code and the new Vappy MCP and skills. Now I wanna send you away with my three biggest takeaways from playing around with these skills. Number one, skills change the game for Vappy builds. The old way was hours in the dashboard, searching through the documents, debugging any JSON schema. The new way is spending ten to twenty minutes in Cloud Code and having a natural conversation. Twenty minutes, no dashboard, no docs, just me telling Cloud Code what I wanted. Number two, this is what happens when a company actually gets it. Vappy didn't just write the documents and hope for the best. They packaged their entire platform into skills so Claude could build with it natively. That's the difference between a tool that you have to learn and a tool that knows how to use itself. And number three, this is just the beginning of the skills takeover. The agent skills standard now has over 280,000 00:16:49.990 --> 00:17:24.070 skills built by the community. Companies like Stripe, Notion, Vercel, they've already adopted it. Even OpenAI's tools support this format. This isn't just a Claude thing anymore. It's becoming the universal standard for teaching AI how to use software. Imagine when every single SaaS tool you use has a skill, and it end skills. Stripe skills. Your CRM has skills. Your AI assistant just becomes an expert in everything. As always, if you've gotten any value from this video, drop a like, hit that subscribe button. It helps me out a ton. I'll be dropping videos every single Tuesday and Friday. Leave a comment down below on what type of voice agent you're you're gonna build after watching this video. If you've made it this far, thank you so much, and I'll see you in the next one. 00:17:24.470 --> 00:17:41.055 Hey. If you're still here or if you're new here, something like they do at the end of all my videos is pray for you guys, my audience, and send you off with a blessing. I know this might be a little bit weird for some of you. If that's the case and you're uncomfortable, please feel free to click off the video, and I'll see you next week. If not, stay long. I'm gonna go ahead and pray for you guys right now and send you off on your day. 00:17:43.055 --> 00:17:59.740 Heavenly father, thank you so much for this day. Thank you so much for the person on the other side of the screen taking time out of their day to watch this video. Lord, I just wanna pray a blessing over them, that you protect them, pour the blood of Jesus Christ over them in protection. Lord, wanna pray a blessing for them, for their businesses, for their families, 00:18:00.060 --> 00:18:03.705 if they're content creators, whether they're, you know, AI enthusiasts, 00:18:03.705 --> 00:18:10.345 business owners, whatever the case may be. Lord, I just pray that you protect them, protect their business, give them the wisdom to make the right decisions 00:18:10.585 --> 00:18:12.105 to help serve their clients. 00:18:12.425 --> 00:18:40.915 And, Lord, I just pray that you give them strength and and obedience to you. Lord, I just pray that anything that they go through, tough times, good times, that they give you the glory, Lord, because that's ultimately what we're here to do is glorify you. And I just thank you for all the opportunities that you've brought my way and that you will continue to bring my audience's way. Lord, I thank you for everything. I thank you for your sovereignty in our lives. I praise you for being the king of kings, the lord of lords, and I pray all this in the name of Jesus Christ. Amen. 00:18:41.773 --> 00:18:44.493 Now go have a great rest of your day, and I'll see you guys next week.