0:00 Vapy 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 it. 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 Cloud 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 going to work. I'm going to go through an entire call with our voice AI receptionist and then I'm going to show you guys the results of what happens at the end of the call. So, I'm going to 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
0:45 built at my house. >> 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 Sherville, Indiana. >> Perfect. We definitely serve Sherville. 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, or are you still figuring that out? >> We're thinking around 15,000. 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? Yeah, my name is Jon Snow. My phone number is
1:31 and my email is John [email protected]. >> Thank you, John. Let me check our availability for a 30 minute on-site deck estimate in April. Is there a day of the week that works best for you? >> Uh, quick question before we book. Do you have uh 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 materials. Shall I check April dates for you? >> Can we actually do a date in March? >> We have openings the week of March 9th, Monday through Friday from 8:00 a.m. to 5:00 p.m. Is there a specific day and time you prefer for your estimate? >> Can we do Monday? I think it's March 9th at 10 a.m. Please, >> you're all set for Monday, March 9th at 10 a.m. Mike Thompson will meet you for
2:17 your deck estimate. Thanks so much, John. Anything else I can help with today? >> Nope. Thank you so much, Rachel. >> Goodbye. >> I mean, 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 10:00 a.m. for Jon 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 call data got logged. The only thing I noticed right away is Sherville 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 got to check is that if we got an email sent to us for an end of call report. Hopping into our email, we
3:03 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 cents. 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 Deeprooted 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
3:48 specific tools. Here's the official announcement of Vapy 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 web hook. So, you can easily connect it into NADN without manually configuring any web hooks. 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 Claude Code, Gemini CLI, Codeex, 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 want to install the MCP and the skills for yourself, all you got to do is go here. These are the instructions. What I would do is just copy and paste this entire blog post, put it into Claude Code or whatever coding platform you're using, and then have it install it for you. Okay, so I
4:35 wanted to show you guys how to quickly install this MCP server and the 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 Vappy MCP and install the eight skills. You can send it off, put it in edit automatically mode, and then it'll kind of 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 Vappy and getting your API key. Now, I'm not going to send this off because I've already installed the MCP and skills, but I did want to show you guys how easily you can do this for yourselves with the help of Claude Code. Now, you'll know these skills are installed because you can just do something like /create and you'll see /create call create squad create assistant. So, you'll see some of those in there and then also if you do /mcp status, you'll be able to see that the MCP server vapy docs is available and
5:20 you can use the MCP server. That's how you'll verify everything was set up correctly. Now that we have our Vapy MCP set up and the eight tools that go along with it, here's our empty claw code project. We just have a claw.md file. Every single project should start with one of these. Gives it an overview of everything that we're going to 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 claw.md 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 going to go ahead and start off building this voice agent inside of Cloud Code. Okay, so the first step is to actually start off the entire process. So, we're going to kick off a prompt that says, "Let's build a voice agent." What should happen is our cloud.md file is
6:05 instructed to help us set up the Vappy 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 cloud.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 thev 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 Vappy API key. So it says, should I run the Vappy setup API key? And then I'm going to put the command. We need to set up our Vappy API key. Everything else is set up. I'm going to go ahead send this off, put it up in bypass permissions mode, and I'll get back to you guys with how we're going to set this up. Cloud Code is letting us know how to set up this Vappy 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 going to go grab our API key, paste it in here, and let Claude Code set up all the files. If you've never set up your
6:51 Vappy dashboard yet, this is what it'll look like when you create an account. All you're going to 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 ourv file up here. We also created agit ignore which just means all our variables arev 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. 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 going to need to get the spreadsheet ID and put it in thev file. Now that this is all done, we're
7:37 actually going to 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 cla MD file to have different phases. So every time we complete one phase, we 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 going to get to work on phase two. So this is actually pretty cool because of the way I have my cloud code set up in order to protect my environment variables like my API keys and anything that's in thatv file. I actually have to go back grab it from thev 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 going to 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
8:23 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 configs JSON up here and then also enabled two functions and call and transfer. Now we're going to hop into Vappy to make sure all that was actually created so you guys can see how sweet this is. In our Vappy dashboard, we're going to go over here to the tools 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, the transfer to mic 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 Vappy 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 going to tell Cloud Code to start phase three. Begin phase three. Phase three is
9:08 now kicking off. It's going to 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. All right, so we finished up phase three. We actually created our entire assistant. Her name is Rachel for BuildRight Receptionist. This is the model that we used. OpenAIG GPT4.1. Vappy Clara is the voice that we used. So, all this stuff just happened in Vappy. We're going to go confirm it here in a second, but I do want to scroll up a little bit here and show you guys everything that it did. So, it confirmed that phase 2 was complete. And then it went through the Vappy create an assistant tool, which is the one of this 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 cuz that's how I have it set up. But other than that, everything is set up. Let's go check it out in Vappy. Okay, so back in Vappy now, we're just going to verify that Cloud Code did everything that it said it did. It build
9:54 out Rachel, the build receptionist, OpenAI GPT 4.1 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 got to be careful with these agents. You know, you want you want to 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 Fappy. Gave us a max token count of 300, the temperature 0.7. 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 and 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 4. Once
10:41 again, it's going to check the current project state to see what it's built. It's going to 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 Claude 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 Vappy phone number and assigning it to Rachel. Thank god I don't have anything connected to this, but that would be really crazy if it did. What's really happening is it's just creating a free Vappy phone number that Vappy provides. Okay, so Vappy finished up phase four, which is just as simple as creating the phone number and assigning it to Rachel, our assistant. We're going to go ahead 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. Buildright construction mainline. Did he connect it to Rachel? Yep, Rachel, assistant build receptionist with the inbound phone number. So, I can make inbound and
11:26 outbound calls. This is like I just can't believe I'm doing this in Claude Code and it's actually doing it in Bappy. 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 was a little bit heavier where we actually created the web hook and the NAND workflow that's going to capture our end of call report and send us an email. We created the server URL for Vappy and connected it. And then we also created the N&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 VS 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. Now, we're going to 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
12:11 first one will be step 6.1, which is an outbound test call. Claude is going to use its Vappy create call tool to have Rachel call our phone. Then, we're going to do an inbound test call, and then we're going to make sure everything works with our NAND workflow. So, let's go ahead start phase 6.1, and let's get this call and see what happens. Here comes the call. Let's answer that and see what happens. >> Construction, this is Rachel. How can I help you today? >> Hey, Rachel. I'm looking to uh build a new patio. >> 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 Point 463307. >> Perfect. Crown Point is right in our service area. When are you hoping to start your patio project? This season, next month, or are you just exploring options for now? Uh, let's do next
12:58 month. >> 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? >> Uh, I'm still figuring that out. >> No worries at all. We'll help you explore options. 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 >> and my email is [email protected]. >> Thank you, John. I'll check our calendar for the next available 30 minute on-site estimate in Crown Point. Would you prefer a weekday or Saturday morning appointment? >> Can we do this Saturday morning? >> We have openings this Saturday morning. Is there a specific time between 9:00 a.m. and 1 p.m. that works best for you? >> Uh, no. Let's do 9:00 a.m. >> You're all set for your on-site patio
13:44 estimate. Saturday, March 7th at 9:00 a.m. 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. >> Wow. So, for a first shot, and we didn't really change the prompt to 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 9:00 a.m. appointment on March 7th, which is a Saturday, was booked at johnacample.com. Obviously, we're not going to send an email to that cuz it doesn't exist, but we know that our receptionist had access to our calendar and was able to book an actual an appointment. Hopping into our Google sheet here, we can see that everything was populated correctly. The only thing I noticed was that the call
14:30 duration didn't fill in and we didn't get an email getting our end of call report. So, I know that the end workflow failed, but that's no problem cuz we're just going to 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 want to make it clear that AI cannot oneshot everything. it could pretty much do 80% of the work, but you're going to have to go in there and fix some problems or just have Claude Code help you fix those problems. So, what had happened was our NEN 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
15:15 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 want to 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 want to 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 6 months of me being there. You'll get access to courses that teach you how to master NAN, 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
16:02 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 Claude Code in the new Vappy MCP and skills. Now, I want to 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 10 to 20 minutes in Cloud Code and having a natural conversation. 20 minutes, no dashboard, no docs, just me telling Claude 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
16:48 has over 280,000 skills built by the community. Companies like Stripe, Notion, Verscell, they've already adopted it. Even OpenAI's tools support this format. This isn't just a clawed thing anymore. It's becoming the universal standard for teaching AI how to use software. Imagine when every single SAS tool you use has a skill. Niden 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 going to 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. Hey, if you're still here or if you're new here, something like I 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
17:33 uncomfortable, please feel free to click off the video and I'll see you next week. If not, stay along. I'm going to go ahead pray for you guys right now and send you off on your day. 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 want to pray a blessing over them that you protect them. Pour the blood of Jesus Christ over them in protection. Lord, I want to pray a blessing for them for their businesses, for their families. um if they're content creators, whether they're, you know, AI enthusiasts, 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 to help serve their clients. 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,
18:20 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. Now, go have a great rest of your day and I'll see you guys next
