← The Official SaaStr Podcast: SaaS | Founders | Investors
The Official SaaStr Podcast: SaaS | Founders | Investors
SaaStr 846: 10 Things to Know Before You Deploy Your First AI SDR with SaaStr's CEO and CAIO
01:05:48
Loading summary
Transcript54 lines
- [00:01]
A
Welcome to the official Saster podcast where you can hear some of the best Saster speakers. This is where the cloud meets up today on the Saster podcast. This is a mistake that both raw startups, scaling folks and very large companies we talk to make the mistake. The raw startups, you know, they've raised a token amount of money, they want a tool to magically get them customers. It can do that if you've already proven you can do it yourself and you feed what works to the AI sdr. If you can't, the odds it works are extremely low. Right? And then some of the on the other end of the spectrum, some of the largest leaders we've talked to, folks, multi billion dollar public companies and bigger, just want to turn on a tool and not train it with what works. Now of course they could. They are. Obviously you've got 2.5 billion in revenue, you've got at least a few SDRs that have performed, but maybe it's bought by a marketing team, maybe it's bought by a different team, maybe it's bought with a different perspective, but they just want to turn something on and the cost there may not be that important to the latter category if you're big, but their results are terrible. They don't reproduce the best 10% of their team inside the and if you do nothing else the first 30 days, your job is to reproduce the human playbook works inside the training or the UI UX of the A store. If you don't do that, it won't work. Hey everybody. Saster Annual will be back May 2026. The world's largest SaaS and AI gathering for executives with 68 VP level and above attendees, 36% CEOs and founders and 25% were AI first professionals. It's the very best of S tier attendees and decision makers that come to Saster Annual and AI Summit each and every year. Lock in your spot today. Use my code Jason100 for exclusive savings. Get your tickets at podcast.saster annual.com or just use code Jason100 when you check out. See you there. Saster annual and AI summit 2026. It will rock.
- [01:55]
B
Hello everyone. Glad to have you and your agents with us here today. Day we thought we would do something fun since now we have, you know, more than 20 agents in our full stack, we've deployed more than one AISDR and so somebody asked us this question the other day and we thought it'd be fun to go through it live as well. Which is, you know, what are the top 10 things you should know before rolling out your very first AISDR if you haven't deployed one yet, or maybe this is your next deployment and you want to know what you know tips and tricks to avoid and what to do to make it successful. So that's the context of today. We'll go through these 10 as always at our beginning, if you want to see some of the tools and agents that we use, they are on Sasser AI agents, you can go there. We link to a lot of our agents that we use there. Yeah, I think some of this we've covered, but I think it's important to know if you're going to roll out your very first aisvr just because that is our use case that we have multiple actually AISDRs. Now I'll preface in saying that you probably only need one and then to point number one that I'll drive right into you probably only need one vendor to do this. Like we have multiples for a lot of different reasons. But most of what you will need to do slash want to do with your agents. You'll probably be fine using just one vendor versus using the four or five that we have for outbound and I'll kind of explain why. So just coming into it first, the tool doesn't really matter. Like you're going to see today. I interchange different screenshots from our different AI SDRs that we have. But you don't need to again, you don't need to use multiple vendors. I would pick one that does the majority or bulk of what you want to do with an AI SDR agent and roll it out from there. You may need multiple in the sense if you know if your outbound agent truly only does outbound and then you need to add an inbound agen that truly only does inbound. So maybe at the max you end up with two, but I would say you don't need as many as we have today. We just have it hyper segmented with different platforms that do different specialties pretty well. So that's not our school of thought. But I will say, you know, the tool doesn't really matter as much as the strategy and also just making sure that your human playbook works first. So we famously said before like you know, we're not going to roll out our. We didn't roll out our first human like AI. We didn't roll out our first AI SDR until we knew exactly what was working with our human sdr, what was working or maybe not working as well in our playbook. So that we could give our agents just the very best context of what's working. Who should we be reaching out to? What messaging works with that? What segmentation should we be doing to roll out to the aisdr? Because you have to remember that when you roll it out to an AI versus a person, it's going to take all your context word for word. Right. Like it's going to use that to build out its brain. It's going to use that to reach out to prospects. It's going to use that to follow up with any of your inbounds. Like anything you do, it's going to be 100% based on the context you give this AI SDR agent. And for those purposes, you really should know what's working before you do that. Like I've seen some companies we talked to which are like million dollar, you know, AR companies, some are over 100 million. We're just rolling out a SDR and I'm like, okay, well how are you training it? They're like, oh, you know, we're just test, we're testing, copy that we haven't used before. We're trying something new. I think that's the wrong way to go about it. I think you should have something that marginally works and then use the AISDR to get scale out of it.
- [05:43]
A
Yeah. Or maybe to summarize the two, those two types. Because we hear this so often, right. If you haven't gotten any outbound to work, buying an AI to do it isn't, it's not going to help you. You have to prove it. Any of the agents we use, any of the dozens of agents we use, we are taking a playbook that at least works a little bit. It doesn't have to be perfect, you don't have to have a 90 close rate, but something that is proven copy cadence segment. But you have to have been able to close some customers yourself. You basically have to have at least done founder led sales before you can hand it off to an agent. It has to work. They have to take you. And the ultimate goal here is to clone the best person on your team. If it's just you clone you. If you have four folks on your sales team and one is crushing it at outbound or only one can really pull it off. All you want to do is clone all these products. Really do in the beginning is clone that person. Right. With more knowledge. Would you agree, Amelia?
- [06:36]
B
Yeah, I would agree 100%. I think a lot of these tools too. If you haven't looked at them or maybe you haven't fully run one yet and you're just going to deploy one. A lot of what you'll see is sometimes I think the vendors will try and steer you somewhat in the wrong direction, which is why I don't think the tool matters as much as long as you know, like you should be using it at the very start for things that are already working. Like a lot of vendors will tell, even some of our vendors will tell you, oh, you can just use it for pure outbound. It's fine to test things, but then when you go look at the response rates, of course it's going to be lower than something that's working, something that you know, that you want to give scale to. Maybe something that you know your human AES or SDRs won't do. Like I do think that's, that's a little bit of a trap to be wary of is I do think sometimes the vendors will try and say that they've had good success with other customers on doing, you know, new use cases, just rolling out brand new, you know, just completely cold outreach and yeah, to some degree does that work? Sure. But you might be disappointed with it too if you only do it that way versus scaling out something that you know already works.
- [07:40]
A
Yeah, And I want to stay on track. But, but the interesting thing is going to Melee's point, you move forward. This is a mistake that both raw startups, scaling folks and very large companies, we talk to make the mistake. The raw startups that you know, they've raised a token amount of money, they want a tool to magically get them customers. It can do that. If you've already proven you can do it yourself and you feed what works to the AI sdr. If you can't, the odds it works are extremely low. Right. And then some of the, on the other end of the spectrum, some of the largest leaders we've talked to, folks, multi billion dollar public companies and bigger, just want to turn on a tool and not train it with what works. It's the same, it's average. Now, of course they could. They are obviously if you've, if you've got 2.5 billion in revenue, you've got at least a few SDRs that have performed. But maybe it's bought by a marketing team, maybe it's bought by a different team, maybe it's bought with a different perspective, but they just want to turn something on. And the cost there may not be that important to the latter category if you're big, but the results are terrible. They don't reproduce the best 10% of their team inside the app. And if you do nothing else the first 30 days, your job is to reproduce. To Amelia's first point, to reproduce. The human playbook works inside the training or the UI UX of the A. If you don't do that, it won't work. Or at least you're you. It'll work as randomly as spooling up some email cadence tool from five or six years ago.
- [09:02]
B
Yep. I would say, yeah. The magic, or the magic unlock of these tools is using it in a way different than those older tools. Right. Like different away than like the outreaches or like the sales laughs of the world. Like those were purely, you know, spool up Duke old outbound at scale, kind of see what results you get. And I think because of that, that's why people try and do the same thing with something that's an AISTR agent. But remember, it's an agent, it has a brain. Like it has context. It's some of them, you know, like ours can see what's on your website. They can put that context into the email. It's think of it more as like a living, breathing agent versus just an outbound email sequencing tool. Right. Like that's also the wrong way to go about it. But I think that's why people do that. I think because they were just so used to doing that previously. Number two, I would say if you're rolling out your first asdr, yeah, A lot of folks I think get caught up too in deploying their first aisdr and what are the use cases we're going to tackle? Right. Like, I think naturally a lot of folks are like, okay, I've got outbound, maybe it's cold outbound, maybe it's slightly warmer inbound. Or for us, you know, we, we all have leads we've never followed up with. And I think this is where the AISDR agent can really shine, is to have it do the quote unquote, unglamorous work that your humans probably don't want to do or maybe gripe and moan about doing every week when they have to do it. And so the nice thing about the agent is if you give them the right context specifically for these leads, so you know, you can give it a set of context or prompting the 1. The screenshot I have here is from Agent Force that's reaching out to prospects we, our human team had never followed up with. Right. Where speed matters here. And because they had never done it, now we have an Agent that just does it 24 7. It'll pick the best time to email this person because it lives in Salesforce. It can see their Salesforce context and then it can follow up with them. Now the open rates have been pretty good on this but also like you know, the meetings and booking rates have been a little lower than maybe some of our other AISDRs. But that's because these were old leads. These were leads our team had never followed up with. So not only had it been a few more than a few days since somebody followed up with them, in some of these cases it was more than a few weeks that nobody had ever followed up with them. So in this case I give it a pass on that because of the set of leads that we gave it. But just know it's still a good, it's still a very good exercise to do. Like what we've gotten out of it has still been very useful for like reactivating folks, getting people like re engaged with us. Right. Sometimes that may not turn into a meeting because it is a, an old lead that somebody didn't want to follow up with. But at least now the agent followed up with them. Like we finally were like okay, this person has gotten a follow up yes, from our agent. But they've gotten in a way that makes sense and is a way at scale where we could follow up with all these leads 247 and try and re engage them versus just leaving them to die completely. Right. Which is often the case before you have an aisdr. Sometimes you have a lot of leads that just end up dying or they, they time out. Right. Because just speed to deal is obviously so important right now in the age of AI that if you leave them to timeout then obviously that can affect the entirety of the deal cycle and the customer cycle. So I think this is a great place where the AISDRs can shine. Whether it's inbound, outbound or even just having an AISDR that does ongoing customer engagement. I still see a lot of folks struggling to use their AISDR for that. And we use it all the time, every day. Like I have agents that are just sub agents going off in our tools that are reaching out to current customers of ours, current sponsors of ours to make sure they have everything they need. And it's such a great way to do it because again the agent is 24 7. It does it automated. It's not going to forget folks. Like a really great use case we have right now for example is I showed a couple weeks ago, I Vibe coded our entire SaaS responsors portal. And what the portal and we'll do now is I helped build a little like custom micro agent for it where it will run every couple days. It will see who hasn't logged in to their clerk login when we've invited them to our sponsor portal and then I'll just send them an email like, hey, you haven't logged in yet. Do you need help getting your login? Should I resend it? Things like that, things that we would normally have to do ourselves. And so again, that's a really unglamorous workflow, but something that is so perfect for an agent to just do on its own. And also low risk. Right. Like it's just looking to see have they logged in, have they used the product, have they used the tool and then sending them an automated workflow on that. Again, fairly unglamorous, but something that we pre we literally had to do this last year. Like I was telling Jason last week, like I was looking at the amount of hours our actual or events production agency had done for January and February for this year for Sastry annual that's coming up in May versus the amount that our agency had done last year in January and February for the Sasser annual that was last May. And it's crazy because it was less than a tenth of the hours. Again, not that I don't still need people and I still need them to do some things that the agents can't do. Like sometimes the agents just aren't good at, you know, calling the food truck people. Like I just, I need a human to still do that today. But it's crazy to see that like how much of that unglamorous kind of monotonous style of work or customer check ins like that, that an AI agent can just do really well. Like not only has it saved us in raw spend with some of our, you know, contractors and agencies, this I would say the sponsors are a lot happier that they have more regular check ins. They get a response faster. They're getting, you know, more proactive messaging from us to do things like login, submit the brew graphics, things like that. Whereas back in the day we'd have to be more reactive of who's late, who's missing. Right. Because we were just trying to keep up with everything. Yep.
- [14:59]
A
In terms of the use cases Emelia's talking about here, small accounts churn customer follow ups, inbound leads, re engagement campaigns, for the most part we are using the current for third party agents that we use Right. We are using Agent Force from Salesforce Qualified, which Salesforce is buying. We're using Artisan, which we use all the time as a core outbound agent. And recently we've used Monaco, which is a new hot one, to do Raw outbound. They've done most of this. The stuff Amelia's talking about, that is niche but important to us. A sponsor portal reaching out to those customers, reaching out to those partners proactively. That doesn't exist off the shelf the way we needed it, so we had to build it ourselves. We vibe by this ourselves, the our automated VP of marketing and our sponsor portal. It just wasn't. The off the shelf tools are so dated. We couldn't do it. But we did that. They're cool, but we did them reluctantly. And if we could have bought it, we would have. Like, you don't want to build this stuff over many long weekends and you don't want to maintain it. But just to highlight what we built and what we use. But we'd much rather buy.
- [16:02]
B
Yeah, we'd much rather buy. We did a session, I think two weeks ago that we went over the 9010 rule of how we determine how we build versus buy. If you want to hear our deep dive on that. And then to that point too, on our AI VP of marketing. One of the sessions we're going to do at Sastry Annual during the Deploy Summit on Tuesday. So everyone's just going to show how to build their agents. I'm actually going to rebuild that agent live. So if you want to come to that, we're also going to live stream it. But if you want to come to that, I'm just going to rebuild what I did with our AI VPM completely live. So fingers crossed so nothing goes wrong. But I'm going to do that there to show folks how to do it. So that'll be fun. Okay, Tip number three, if you're rolling out your first AISDR is to segment ruthlessly. And I do mean that word ruthlessly. Like we do it to the point where again, the tool doesn't even matter at that point. They all sort of function in the back end the same way. Having used, you know, we use four tools in our daily rotation, but I've tried maybe over a dozen AISDR tools. They all have some version of this functionality where you can tell it who you want it to reach out to and then you can give it specific context for that segment versus giving it an all in one brain. It's actually something where like our inbound qualified Agent, which is, you know, becoming a salesforce agent, didn't had kind of like a big brain, which I'll show you in this deck later. And then I actually started segmenting more with that one too. It was like, okay, well, in our inbound, we actually have so many buckets. First. I was like, okay, well, there's, you know, they're inbound to the website, so I'll just consider that the inbound bucket. And I was like, no, actually, that's wrong. Like, we have folks that are inbounding and they're brand new to Saster. We have folks that are inbounding that came there because they saw an ad on one of our social media platforms. We have folks that are inbound to the website because they were a prior sponsor or they're a current customer. I was like, actually, there's a lot of buckets within inbound. So we've actually now even segmented our inbound agent, whereas I previously was only segmenting our outbound agent. But either way, you should segment ruthlessly so that the context you give the agent is tighter. It's exactly what you want to say to that person versus if Jason comes to the website and he just has one big brain, then you know your agent's going to act off. Okay, he's coming to the website. What is he maybe looking at? Is he looking at, you know, your pricing page? Is he looking at a features page? Whereas if you segment that, it's okay, Jason is on the website. He's actually a former laps customer and he's looking at the pricing page now. Let me give him context to say what's new with the product? Right. Maybe he's turned in 2022 and you can, you have that in Salesforce and you can pull up that context to your inbound agent. Like, hey, a lot has changed, you know, with your product since then. You can highlight those new features to that person with something like an inbound agent. And so that's where the segmentation helps add a lot of context and just have a lot better of a conversation between the agent and the human being that's interacting with this agent. Same thing goes for inbound. We segment ruthlessly to the point of I am updating these segments literally every day. I literally will go through like our. Our website visitors. I'll re segment folks that are opening emails. I'll segment folks again. I'll do folks that are have. That are already customers of ours, but maybe haven't logged in when they need to. So I ruthlessly segment and Then I make sure that the context I give each agent is hyper tailored to that person, to that audience to make it have a better response rate versus just having it be one big brain of an AI agent.
- [19:41]
A
And hey Emil, just one question on this point. None of the AI tools we use today, which are all great, but none of them can really use AI to auto segment in a way that can deliver these results, is that accurate by any of the tools we use or any of the tools we've tried. You just. This screenshot is nine segments, right? But if we're doing a thousand contacts, we probably have effectively 100 segments, right? Maybe not can it, but I should be able to build these on its own, right? In theory. But today, I'm just asking today. And all these products are getting so much better. But as we, as we do this, no one can create these types of segments autonomously that you have to sign up to do this yourself. Like a marketing manager would, right?
- [20:23]
B
Yeah, you do. Yeah, like a. Yeah exactly. Like an op source center, like a marketing manager, you can't. You have to have the wherewithal to know to segment versus a lot of them by default. To that point JSON will do it just as one big brain. Like it'll say okay, just run one campaign and keep adding leads to it. Right? That's the wrong way to go about it. Again, not that it won't work to some some effective degree, but we have seen now because we've run these for 10 months now, it just works a heck of a lot better to have it segmented and have the context that you're giving the agent hyper specific to that segment. Okay, number four con. And this is, this is what we have found to be true kind of early on, but it's still true today, which is consistency beats brilliance. And what we mean by that is it does not need to be the best email on planet earth. And you should not expect the email or the best message. If it's a messaging agent or the best text message or the best phone call, it does not need to be the best. I will tell you, we've said this is just artisan, but it sent 40,000 messages. Okay, I think our qualified is later on this deck that sent like a hundred thousand messages because that's an inbound. And then with Salesforce we're probably close to like 200,000 messages sent. Now will I raise my hand and say these are the greatest emails since sliced bread? No, of course they're not. They're at scale like our AI does A pretty good job and a solid output of what the emails are. And you'll see, you'll see here like there's ebbs and flows in that chart. And that's because I'm reloading the agent, right? You'll see it's, it spikes every, it spikes up every couple days when I reload it because we hyper segment and then it spikes down when that sequence starts to finish itself. And so again, just consistency here and again using, using all the points one through three, right? Of like the very best messaging you already know will work, the very best subject lines, getting hyper segmented with it. And then when you weigh your inconsistency that will give you so many great results versus a human that is inconsistent, that maybe doesn't or ignores the training and context, right? Because when you're giving your AI SDR the training in context, it will remember it every time. Sometimes it will try and iterate it on its own. So that's something you need to be mindful of to make sure it's not goal seeking too much. And you know, it's, it's still speaking to folks in the way you want it to. But this is something just to know here of the consistency that you're going to get with an aisdr. It's going to be worth the trade off of maybe the email not being the most perfect email on planet Earth. But sometimes, you know, perfect is always the enemy of good or even the enemy of just getting it done. Like I see so many folks that just have like AISDR paralysis because they're like, well, you know, I started using one of the tools you guys use and my output wasn't that great. It was okay. And I'm like, well one, you could always make it better, right? Getting hyper segmented and then getting hyper specific with content. Use content that works and then see what you get. Like you'll probably get it to pretty good. And pretty good I would say is the bar. It does not need to be brilliant, it does not need to be the best email on planet Earth or, or even an email that you might write yourself. It just needs to be pretty good to get this person down the path you want them to go. Okay, number five is for us, at least with the amount of agents we have, you need at least one, but ideally two essential humans to run all this and to deploy your AI sdr. You can't have zero people. And certainly it's become harder for us even right now with like a lot of my time being split between act Like Saster annual production versus like that was time I, I typically had spent before March managing agents. Even that has gotten like a little bit harder for us here at Zastor. And so having 0.5 of my workload is actually not ideal either. But you know, the anal is a time sensitive matter. So just something to keep in mind here is ideally you need two folks internally to run this, even if you can just find one. But then you will need to find a backup, right? Like, not that your agents are going to leave, but what if that human leaves? You do need to have like a backup system and a plan to keep all your agents running. And so it's essential to have at least two folks working on this monitoring the agents. Because if not, you'll see, like I just showed in that, you know, artisan chart, your agents can sit idle. Like, unless it's an inbound agent where you have like ours is on full automatic, that one doesn't idle as much. But our inbound agents and many of your inbound agents, because of how we do this tooling, which I do think is the best way to do it, your agents will sit idle if you don't give them new segments, new context, new people to go out to. It will finish its sequence in a couple days and then it will sit there until you give it the next one. And so I think that's why it's essential to have two folks to backfill each other to make sure your agents are always optimized, that is otherwise, you know, you're wasting a lot of time and money if they're just idling all the time. I will say too, the reason I showed a screenshot on this one of Monica is like, Monica is a very interesting, like, interesting, distinct use case. We're actually not their perfect icp. Their use cases more for folks that are starting up and maybe don't have. Maybe you've got some messaging figured out and you have, let's say 20 or 50 customers, but you want to get the next, you know, 100 customers. Theirs is great because theirs will actually fill your pipeline more automatically based on lookalikes. So that's what I really like about it is I haven't had to. That one hasn't sat idle for us because it's just refilling the pipe. When it finishes the sequence, it'll grab another lookalike company close to our audience. It'll see, you know. Okay, did, did Snowflake reply to you? They did. Okay, great. I'm going to go, go. You know, Outbound to another company's like Snowflake. Okay. Did OpenAI respond to you? They did. Okay, great. Now I'm going to go out to other companies that are like an OpenAI, which there aren't many of, but it'll do things like that to keep the pipeline full, which I think is pretty cool. Versus some of the other agents we've tried. So they don't all do that. It's just something to be aware of. Again, agnostic of the tool. Something to maybe ask your tool provider too if you're worried about your agents maybe sitting idle too much or if there's anything else you can do to make sure data is always flowing into your agents. Like right now, I don't, I don't know if I'll be able to finish this preannual, but right now I'm trying to see how I can actually get some of our, our agents all hooked up together to talk to each other more regularly to solve this problem. But again, it's kind of a later down the road problem once you have your agent fully deployed and it's starting to work for you. Okay, number six, and this is hyper important. Read everything I would say in the first 30 days and then read almost everything every day after that. So if you're rolling out your first AISDR agent, you are going to want to read everything and maybe you're going to want to read everything before you hit publish or send or whatever the equivalent is in your tool before it goes out to somebody in your, you know, outbound or inbound list or whatever it might be. You're going to want to read everything during that initial deployment to catch things like, you know, some. Sometimes I think our agents would spell sester incorrectly. Not that it was wrong, but there's two capital S's and sometimes it would lowercase it. And so I would make a rule in the agent to say, you know, always capitalize faster as you know, the S's are capital. And then I would write in rules like always use Zaster in the subject line because we have a bit of a brand and so typically it works better if Saster's in the subject line versus it looking more generic. There were other things that we would catch in the first, you know, messages at scale of. Sometimes it would, you know, because again, our events are timed and we use a lot of these for our events. Sometimes it would use the old dates because it would just scrape the Internet and then it would find like the old dates. And so it was super important just to read everything. I also think it's, it's the only really way to learn it is to see what does your agent actually output. Like if you're only putting, if you only care about the inputs and you're not caring about the outputs, you're only seeing half the picture. Like you do want to see what your agents are saying, what they're doing. And like, I just took the screenshot from Tuesday and this is an important nuance here that I'll just explain. This workflow through. This is from our qualified inbound agent. Somebody was asking about adding an additional ticket to Sasser Annual later this year. And this is, this is again not a hard conversation for Amelia, AI or inbound agent to answer, but just a nuanced one. Right? Because it requires knowing, okay, who is this person? How many tickets have they already bought? What price did they buy it at? Because then they need a retroactive discount. So basically what it did is it the agent asked them those questions and looked it up to see if it was in Salesforce, asked them a few clarifying questions of, okay, is this third person from your same company? And then, great, what's your email address? Because then we can send you the code for it. And so again, fairly hyper nuanced, but something that we read through and we go through just to see where our agent needs help. Even still Today, like even 10 months later, I am still reading things that our agent is doing to make sure it's accurate, to make sure it's what we want it to say to folks and to make sure we're represented in the right way with our agents. Also, because so many people see them, that it's also just good to make sure it's saying things that are accurate and not going off the rails. Right. Again, rarely have our agents gone off the rails or hallucination stuff, but they have. It happens every, every now and then. And so for me it's something where every day I'm just, you know, even if I only have 10 minutes, I'm just doing like a speed run to be like, okay, what is our inbound? I'll just go through like a couple inbound conversations, see if I spot check anything. Same thing. I'll go through our outbound agents. I'll see if I, if I see anything in their messages that's maybe off or maybe needs a tweak. And then if there is, then I'll just add that to the AI's context so that it's continually improving with you. Right. So that's something you're, you're going to have to do ongoing no matter what. I would say a heck of a lot more in the early days, but you're still going to have to do it every day after. Okay, number seven, if you are deploying an AI sdr, your first time would be to budget at least two weeks of RAM time, specifically two. With an outbound agent, they can take a little bit longer, especially if it's warming up anything like specific IPs or domains or dedicated email addresses. Sometimes that process just takes two to three weeks in and of itself. Regardless of the tool you use, regardless of what you're going to do next with it, sometimes they just have that built in RAM time. And then the other factor of the two week RAM time is nothing is set and forget. I know some of our, even some of our vendors I think sometimes are guilty of saying things like this and if they give you an FD sometimes, you know, it's a heck of a lot easier for sure. But as you've just seen in steps one through six, nothing is ever truly set and forget. You do need to make sure you are constantly checking in on your agents. Again a lot in the beginning and still ongoing every day thereafter. But you know, the iteration and like the context and training you're going to give your agents just takes a lot of calibration and testing. And it is real, it is a real time investment. It is again, something where typically I have, sometimes I have a little bit more time in a day than another, but it's something where every day I have to, no matter what, even if I can, if, even if I can only sneak in a 15 minute speed run at the end or beginning of the day to go through what's going on with our agents. And that's kind of it. That's still every day, right? That's still like having a short one on one with like a human counterpart. And so you've got a budget at least two weeks in the beginning of almost nothing else. And I think that is sometimes surprising to folks is you gotta almost put everything else aside to really make this work. Because if you're, if you're watching or listening to this and you're like, okay, I haven't really thought about 1 through 6, but I'm already pretty far along with a vendor that I think I want to use for an aisdr. And then you get that product, you get into the back end and you're like, oh shoot, I do need to do those steps one through six, probably steps One through six will take you about two weeks to do, right? Like figure out what copy works, what subject lines work, what time of day works. Hyper segmenting your base and then multiplying those steps of one through four by each segment. Okay, great. Now actually do the deployment either with an FDE or with their team. That alone with some other meetings will probably take you two weeks. Just right there as you put everything together and then work through. Okay, do I want this AISDR to flow information back to something like a salesforce? Do I? Is it going to live in the silo? How is it going to interact with other things? Okay, once I've added an outbound aisdr, do I want to add an inbound one? Do I want to add one for customer success? There's just all these things that kind of snowball. And so it's not even really the implementation that takes the longest bit of time. It's a little bit of the mental overhead and tax it takes to set all this up. There's obviously some real steps here that we've outlined that you will need to do when you roll out your first aisdr. But anything we have found takes at least two weeks. Even Monica, which is super great and has, you know, it's really good at the agent refilling itself and keeping our pipeline up to date, that part is really nice. But even the beginning, I think we got it down to like one and a half weeks. It still took us one and a half weeks to get it all set up. Right. Like, nothing we have found is instant. So I would be wary of anything that you see is like an instant AI sdr. Oh, roll it out today. I'd be wary of that for a lot of reasons. And two, I would say a lot of this is the prep that only you can do. Right. Like, most of these vendors, regardless of the tool will help you out. Some of them will give you an fd. Most of them, more of them should. But regardless of that, I would say budgeting at least two weeks of RAM time is fairly standard now with all the prep that you'll just need to do, too, to make sure it's successful. Okay, number eight, we get asked this quite a bit, I think because we're one of the few folks that have a voice agent along with our chat and email agents. I will say we don't use, like, a text messaging agent at this point. I know a few of our vendors are actually playing around with that, so we'll see how that goes. And so we have a We have a voice agent too who's multimodal, so she has video as well. But what we found, because she's been. She. Amelia AI. Amelia AI are like a chat and video agent, has been live since about November. Jason's AI, if you talk to his Delphi, you can do it in also in chatter voice. You can. That's been rolled out for almost a year now. And what we have found for the last year is that most people still prefer to to chat with an AISDR over chat or over email versus either phone, voice or video. I think it's some of it's just a comfortability thing, right? Like, like literally I was on the phone with somebody yesterday. I was doing a speaker's call for their speaker zest renewal and she went to Zastra Annual to look at stuff. She goes, is this, she's like this AI agent just popped up and it looks like you. I was like, yeah, it is me. That's a million AI. I literally went to the qualified studios to record that and do motion capture of her so that I would have a full multimodal agent, which is a fun thing to do. I was like, but still, most people want to talk to her in a chat format. I was like, some do like the video because then, you know, you don't have to type. And some folks really like that, that they can. They feel like they're actually talking to someone. A few of the folks who talked to Amelia AI before our London event came up to me at our London event last December and they were like, oh, hey, I talked to Amelia AI. I had a conversation with her and I'm like, that's fantastic. That is exactly what it's there for. She's there 247 to answer questions, to route people, to just be helpful in a way that no human can be because she's on 24 7. So it's nice to have an extra layer where if people want to interact with her video, they can. And I think the important learning here is let people pick like you. I don't think you need to strictly be chat only or text or email only, or that you need to be only video. Like we let people choose. If you want to chat with one of like a million AI or Jason AI, you can chat with them. If you want to use the video, you can have a video call with them. If you want to just do a text based conversation with them, you can just do a text based conversation with them. And so I think it's just important to let people pick Their preferred format and whatever they're comfortable with and let them interact with your agent from there versus trying to maybe force them down one road or another.
- [38:06]
A
Yeah, this is, and this, this particular use case is us using qualified which has. I don't even know what they use. They don't use Synthesia. Someone asked. They use I think a more cost effective vendor. Right. Underline.
- [38:16]
B
I mean it's called Tavis.
- [38:17]
A
Yeah, yeah, that's what they use. The 85% of the 15% that want to speak with the digital you do they do we have a sense do they go as far deep or do they revert to chat?
- [38:31]
B
Do you happen to know they stay in video mode? I think because they want to talk
- [38:35]
A
to the video version.
- [38:36]
B
Yeah, they want to talk to the video. Yeah. It's like because she default. Her default is chat. Right. So like her default is like you can, I'll show you. You can just go.
- [38:46]
A
Yeah, yeah, I know it.
- [38:47]
B
But yeah, okay. Yeah, you can just go to anyone on this call though. Can just go to sasrado.com you'll see her. This is her.
- [38:54]
A
So. So people do do it. Yeah, I, I do think there's, you know and this 8515 was pretty. Our first day agent was this general agent called Delphi that that does, you know, still use hundreds of thousands of times where people can shout digital version of me. These were the rough, I think these are the rough 85, 15 ratios too. For voice versus chat. They actually deprecated video. Unfortunately they didn't think it worked well. But I do think there's a, I do think there's a benefit that it looks trustworthy and modern and connects with you. So I do think there's a benefit. But I maybe are learning for B2B use cases. It may be more indirect than direct. Right. Yeah. If you're not ready to start off with voice, don't kill yourself. Like just get the basic chat going and then down the road once it's dialed in and it's working, if you want to have some fun and add it like it's cool. But it doesn't need to be a day one implementation. The video voice.
- [39:43]
B
Right, Right. And we are qualified, had already been on for maybe at least a quarter by the time we added the voice and video component to it. So it was already up for a bit when we started the process of, you know, going to their studios, recording a million AI, deciding what we wanted her, how we want her like voice and video interactions to be versus chat. Maybe this is obvious to everyone, but I'll just say it for context, is you have to have a lot more guardrails though, in a voice slash video agent than you do a text based agent. Maybe for obvious reasons, but because it's a live avatar sometimes, like the wild card of this. We were like, well, we, we think we know what people will ask her, which is, you know, we have at least a quarter of data of what people have been chatting with her about. And so that's how we trained the voice and video agent. And then we're like, but then people started asking her more personal questions about me. And so that was learning. They were like, oh, well, can I talk to real Amelia too? Or they'd be like, oh, what's Amelia's email address? Which she does give people in certain context, not just if you blatantly ask her, but. Or they'd ask other questions like, oh, where's. I think people are like, where's she from? Or like, what's her LinkedIn? And. And so they just started asking more personal questions because again, I think some people thought it was actually me like chatting back to them in the voice component, which is okay. But yeah, I was like, no, that, that's still a, it's a slightly different brain than our, our, our chat interface of qualified. Because obviously again, we were like, we're just going to have to put in more guardrails because what we want her to do is still steer the conversation towards the same goals. And sometimes when you're talking in person, you can get off track or you can get distracted or you start asking Amelia AI about real Amelia. And so we had to put in just more trading in context and guardrails for Amelia AI to be like, okay, it's fine if they start asking those and you can answer it like this way. We literally told her what to say, but then also try and get them back to whatever they were doing on the website. Like if they were trying to buy a ticket, try and steer them back to buying a ticket. If they were trying to book a meeting, show my meetings booker to just book a meeting with them. And so we had to put again, just like additional things you don't necessarily need to do in chat in the video format, but I think people have fun with it, to be honest. Again, for folks that prefer this format. But yeah, it was not something we rolled out day one. It's. We already knew what was kind of working in our inbound agent had already been up for more than a quarter. And then we started to tackle the video and voice component. But it's fun and I'm actually figuring out a way for Amelia AI to be live at Saster Annual. So you guys, if you guys have not talked to her on the website, you'll have another version of her that will be at Saster that you can talk to. Okay. On that though actually what's interesting about Amelia AI is you could probably guess by now it is a very person dependent deployment which actually we would recommend avoiding for other folks for many reasons. And I think, you know, if you look at things like Amelia AI or the JSON AI that's live on the site, those are so tied to us. Like those are not only our entities. Like the JSON AI talks like JSON. Like it's kind of crazy, like an azure personality. A bit of Amelia AI kind of talks like Amelia. It has obviously video that I captured that was me. And so I think having these implementations that we have, I'm not sure actually that you, you should do that unless, unless asterisk like us. You're right, you're on the exact team, right? Like you're the founders, you're invested in business, you're on the exact team. And there's, there's less of a risk to do it that way. But I would say, you know, I always, I famously roast qualify for doing this all the time. Like their Piper agent is based on one of, one of their original AES who's still there now. She's like been promoted. I'm like, but what if real Piper ever leaves? Like I actually don't even know how that works of like do they have her likeness? Because it's also on billboards. Like it's on their website. Like these are just things you may not have thought about yet in a, in a very person based deployment where if that, if there's any chance that person might leave, obviously there are some inherent risk in that. Now you can do things to obviously safeguard yourself from that. If there's somebody you really want to base your AI agent on to make sure you have, you know, maybe the rights to the agents if they ever leave the company, etc. That gets tricky. Obviously there hasn't been like rulings on that kind of stuff yet. That hasn't happened yet in real life. So we'll see whatever happens with that down the road. But just know it's, it's kind of tricky when you build these agents so closely deployed on persons and personalities, right? Like our Personas are tied to these two agents that we have live on the website. And so I would say that's something that's a risk there. But also it's a risk that like a lot of what is running Amelia AI, like, I don't think, I think David has, David from our sales team has logged into Qualified ones to set up the meeting flicker in his calendar. And the other day we logged in for maybe the second time in 10 months so that he could adjust his calendar settings because he had it cutting off too early in the day. But other than that, I'm like, he, he doesn't have like that tribal knowledge that I have of. I know who our FD is at Qualified. I know who it is at Agent Force. I know where to tweak the context. Like again, having person dependent, maybe it's obvious, but you can quickly fall into a trap here if it's too dependent on one employee's maybe voice or knowledge of the context that's being fed to the agents, et cetera. And then I just put some screenshots here of like this also becomes obviously more of a risk the longer you have an agent. So now that our, this, these screenshots are from Qualified. But you can see like even on March 10, I didn't scroll down all the way just between, you know, 9:00am to 10:00pm Those are a million video chats. That's just video. There's more than a whole page that is maybe that screenshot's maybe 20 deep. And then there's the rest of the page before 9am like, so my AI was shown to maybe 30 people in that day. Right. That becomes risky if you're like, okay, what does that person have released? But now 30 people have already talked to her AI agent the whole day. Plus in the entirety of time. If you actually look at our whole funnel, we've had more than 1.5 million sessions just overall, just in qualified, not counting our other agents with, you know, text based communication or video communication. And so it just becomes a real risk if you don't have some sort of like backups or documentation for these agents going forward. Because the more you use them, you'll see like we've had qualified up, you know, we rolled it out last August or So, so maybe 6ish months now, but 6 months at 1.5 million sessions, that's a lot of sessions. That's a lot of exposure to not only an AI agent is it a lot of exposure to, but it's a lot of exposure to an agent that's dependent on not only Amelia AI being Amelia but real Amelia giving her context and making sure she has all the right data to push back to folks. So it's a lot. So it can scale pretty fast. And so I think the speed is sometimes something folks don't account for when they roll out their first agent because you, you don't realize how fast it is. Right. Like once you get past your two week, maybe implementation period, once you deploy your agent and your agent is fully deployed, that thing will just go. Right. Like it's just gonna go every day, constantly. This is 1.5 million sessions. That's on one website, by the way. That was not counting. That was just like Saster annual. That wasn't +saster +aster London. Like it just can scale so quickly. That is something you want to be mindful of too, because I feel like folks don't maybe fully understand that they can quickly spin themselves up and have like, again, almost infinite conversations at scale with people.
- [47:53]
A
Amelia, I don't know. It's not the point. You raised one that comes up a lot. If you had to spitball how much data, how you said 1.5 million sessions went into qualified since we've started, right?
- [48:07]
B
Yeah.
- [48:08]
A
How much, how many sessions? How much data do you need for most of these products to work versus do you need to get bigger and be a bigger startup until there's enough data generated for them to be effective?
- [48:20]
B
Yeah, I put it on the next slide here because it is our last point of your data slash. Your fundamentals have to work before you have an AI agent qualified in particular, just on this agent, you can see it scrapes our website every couple days. So every couple days and you can force it. Like you could do it every day, but I have it scraping saster.com every couple days. Saster Annual, I think once a week. Sastor London I think I turned off for now because we're not promoting that event at the moment. And then you'll see I also have like custom snippets. I've uploaded custom PDFs, custom Q& A that I've loaded into it. So it now has all together, it has almost 6,000 pieces of context that it's working off of. So that's a lot. Most people don't have 6,000 pieces of content or context to feed the agent. I would say a bare minimum. If that's the question. Again, I would focus on what works. But you're going to quickly find with any agent you roll out, whether it's sales or an AI SDR or not, you need more Data than you think you. Even for me, I've needed more data than I thought we had and we had a lot of data. Case in point, like these agents have to answer questions and if you want them to answer questions autonomously, guess what, you have to do a brain dump and say, okay, let me answer all the questions I think a customer would ask. If I haven't documented that yet, which I think most people haven't, to be honest. Some, maybe some of you have, but it just becomes this snowball of almost every day you're going to find a scenario like that where you're like, oh, folks are starting to ask my agent about XYZ things. So now I have to train it on that. Oh, now they're asking about, you know, maybe this particular product feature. And I don't have documentation about that. Now I have to make it, then give it to the agent, then let it deploy you.
- [50:25]
A
Definitely the documentation. If you had to spitball how much traffic to my website for something that relies on inbound and data capture, how much traffic do I need for my website and for an outbound agent, how many at least slightly qualified leads folks that took an actual that you've collected, how big a list do you have to have, Right. Have created to feed it for both those inbound and outbound actions to be effective?
- [50:53]
B
Yeah, I would say for the inbound piece for like website traffic. Because a lot of this is obviously based on our website traffic. If you have less than, let's say 10 to 20,000 visitors a month, it's probably not worth it.
- [51:07]
A
That's a lot for a startup.
- [51:08]
B
It's a lot. I know, yeah.
- [51:10]
A
10 to 20,000 people. Everyone kind of exaggerates, you know. See clearly.
- [51:14]
B
I know.
- [51:14]
A
But not a lot of folks have 10 folks might not to your marketing site. Right. You might not have 10,000 visitors for your first 18 months as a startup. Right. It's entirely possible. So you would pass or you would just pass for in. You wouldn't pass for outbound necessarily, but you would pass for something. I would pass for like a qualified. The way we use it. You would pass into your base 100.
- [51:34]
B
I would pass if you have less than. And I owe 10 to 25k seems like a lot. But honestly we have more than that. And if you look at specifically at our, you know, Obviously we have 1.5 million sessions just on one website in six months. So we have a lot more than that. But if you look at how that funneled down. Right. Of what it does with people of okay how many completed conversations does it have now? How many a million AI conversations is it having? Then how many, you know, this and that and how many meetings were booked like that all obviously dwindles down the funnel. And so I think if you don't have that volume at the very top, you're not going to get the results you want at the very bottom.
- [52:13]
A
Okay, just a challenge. And then, and then summarize what you've learned on Outbound. So that makes sense. But let's imagine I have no humans responding to my website, to any leads or Outbound. Do I really need 10,000 visitors a month? Do I? I mean, maybe we do for some of the tools we use, but I'm not. Intellectually it makes sense. There's a different level where going to some of your early sets, if it's just not getting done, I want an agent that is available 247 to answer prospects and customer questions. Right. Even if I don't have the volume. But maybe that's a different question.
- [52:47]
B
No, that's okay. I think it's a good nuance. I would say that's maybe the ideal volume. But if you don't have that and you do want something where again, getting it done is better than not having it at all, then just do it. Right? Like if you, if you have any inbound volume at all but you don't have the traffic, just do it. But if you're like, I'm in a boat where I don't have the volume and I, I don't have the volume of traffic and I don't get a lot of inbound anyway, then I think that's the, that then that's maybe a slippery slope to thinking, oh, maybe an AISDR will fix it like magically for an inbound agent. Like it won't. If there's, if there's truly, if you have like a double handicap there, if there's, if there's not enough something going on there, then maybe focus somewhere else. Yeah, maybe focus on Outbound first or maybe focus on current customers first before you tackle inbound.
- [53:37]
A
Got it.
- [53:39]
B
Outbound is interesting, I would say, you know, I like to keep ours hyper segmented, but if you think about just the pure math, right, like let's just, I keep ours to about a thousand or so per campaign and then let's just say a campaign takes about a week and a half to run, right? Because it's going to do a first email, then it's going to wait a couple of days and a second one, that's going to wait a couple of days and then send a third one. That is like our cadence that we do with most of our outbound agents. So if, if you know a thousand people take a week and a half, then you could do it in a month with like 4,000 people. Right? Because if you're doing just at the bare minimum, let's say one sequence and you're loading it up once a week, you let it run for a week and a half, then yeah, I would say you could probably do it with like less than 5,000 contacts. I think the issue people run into is after the first month they're like, what do I do now? They're like, I ran through, I had this list of like 5,000 or maybe 10,000 people I want to go out to. And then after a quarter I exhausted all those leads. So I think the Drew magic actually on Outbound is not figuring out, it's just continually figuring out who you want to reach out to. Whereas like I have almost endless folks I always want to reach out to. But I think for startups who are maybe starting out, you may not have that. Right. And so it's just something to think about within AISDR is like, are you going to be able to continually feed it just like you would a sales team? Right? Like you used to have to feed humans leads all the time. The AISDR is no different. You got to keep feeding it leads in this. Not only the same way, but more. Because actually humans are way slower at Outbound than me.
- [55:26]
A
Through this though, let's imagine you're a startup, but you're, it's not day zero, but you're only at a couple million revenue. You have a small list you've built from Inbound, right, From your website and then you're using Clay or other tools and you're kind of hand building a target list. Right. Is that going to work for a sort of a pre brand startup? If I build up a list of a couple thousand folks from an enrichment tool, do some of these tools do it themselves? Like, will they automatically build the list for you? How does that work if you don't have a massive list already?
- [56:00]
B
Yeah, some of them, some of them are really good at lookalikes, right? Like Artisan has a lookalike feature, Clay has a lookalike feature. Like if you have, let's say a list of just a thousand people, then build look alikes all day long. Like, I'm not at that point where I want to. Like you can, you saw it, Monica was Doing it for like new target accounts. But for the other stuff I'm doing more manually. Yeah, I. But if you're not in that boat, then use lookalikes all day. Like, they're pretty good at it, right? Like the Monica one's pretty good at it. I've tried, I've tested it more recently and client is pretty good at it. Like I gave it, I think I was telling you, like, I gave it a list of folks who came to our CMO summit last year, which is like an invite only thing we do as part of Shaster. I said for this purpose, actually give me a lookalike of CMOs because I only had like a list of, okay, the top thousand CMOs that I had narrowed it down to from like past CMO summits. CMOS in our database, you know, used to be over like 40 million. So it was a smaller pool than just our whole database of cmos. And then you'd have to. Then you also had to be at, you know, a somewhat agentic company. And so for that purpose I was like, give me a lookalike because my list is less than a thousand people and I want people who look exactly like this ICP already. And then I sent it out actually last week. I happen to use Clay. You can use whatever vendor you want to do your lookalike. I happen to use Clay. And we had actually doubled the amount of CMOS attendees in a week just by using a local like. So I do think the local, like audiences for outbound can work pretty well if you only have like a set of a thousand people. Just make sure you give it a thousand really good people. Like, don't give it like, oh, this Joe Schmo company churned. Or there are. I only have like customers that I maybe don't want the same DNA of. Like, give it your best customers and then make it look alike. But I do think for outbound you can get away with having a smaller list. And maybe that's a better place to start with before you scale out the inbound is to use a lot of those lookalike lists to start building out outbound. And then you can do other things like layer and ads, whatever. But that, that for us, like even that just use case and scenario right there worked really well because I had a. I had a much smaller list than I normally have to work with and it still worked.
- [58:16]
A
So if you, if you do it yourself with a human, you prove the copy and context that works, that gets meetings. Right. If your list is then too small, build you can get to initial scale for it to work with a thoughtful copycat list. Right? I mean, yes, classic crappy copycat lists are a low effort thing, like buying a purchase list. But if you do it, if you spend the time to do it right, you really target the ICP that works and then customize the copy. That's a hack to getting scale. If you don't have it yet in the early days, right. Is do it, do that really well.
- [58:49]
B
But I to your point, like, I think when I had Clay copycat gave me like 2500 more CMOs and I was like, that's probably too many. Like, so I went through, I went through it one by one. It took me a couple hours. I think it was Saturday. I went through it one by one while I was watching something on tv and I deleted all the people I didn't want because I was like, you know what, the list is pretty good, but there's like 2,000 people here I probably don't want. So I deleted a bunch. I like hyper pruned it to get it to the best quality. But then, you know, that's how I doubled our attendees for that particular thing in a week. So it can work really well. But yeah, it does take some time to go through it. And like I literally, like there were companies I hadn't heard of. I was like, I'm gonna click them, make sure they're an AI, they're make sure their revenue is right. Like double check. It's the right person. Click their LinkedIn and make sure they actually work there. Like that can take for a list of 2,000. That can take a couple hours. And I did nothing else for those couple hours. But it did work. Right. So I think if you're willing to put in the work, that's a good hack.
- [59:51]
A
Okay, do we have. I know, I know, we're over and people will leave, which is fine. But do you have 10 more minutes? I. I can ask you something. A few. There's a few good questions in the chat. You want me to ask you to wrap up?
- [59:59]
B
Yeah, yeah.
- [59:59]
A
This one's a good, a good basic one. I think this was great as is how many people and visit and leave when they realize they're talking to an AI agent. And in prior sessions we. You've presented some rough data that says we think people prefer to talk to our agent in many cases. Right?
- [60:17]
B
Yeah.
- [60:18]
A
But what is how many leave the chat or interaction or digital Amelia digitization when they realize it's an AI?
- [60:25]
B
At least a couple people a Day?
- [60:27]
A
Yeah. Do they ask to talk to a human? Is this a big deal?
- [60:32]
B
No, they just asked to talk to a human. So I'll go over an inbound case, and then I'll go over an outbound case. So in our inbound, I can. It. It tells me immediately because I have a slack set up. Like, it will tell me immediately in qualified. If there's somebody who's asking to talk to real Amelia. If I'm in a meeting, I will say, give them my email or whatever and I'll talk to them later. I can't talk to them right now. Like, Amelia, I could, but I can't come to the phone right now. And. And then there's a couple times a day I'll see at the end of the day, like, I have it, you know, flagging of, like, if there's a trigger of. Somebody got frustrated. It's funny. Like, first I started out with like, oh, I'm going to flag. In our inbound agents, when people say something good. Now I'm like, no, I actually just want a flag if they say something bad, because then I need to take an action. If they say something good, great. Like, I don't even care about that anymore. I actually only care now if they say something bad or if they need an escalation and they still need help. So now I kind of swap those filters, but it's pretty funny. So at least a couple times a day, I'll get somebody where either they had an escalation or they got frustrated talking to the AI. And then I think I said this to you a couple of weeks ago. There's also this weird mix of people who try and trick our AI now. And I don't know what's up with that.
- [61:46]
A
All the way to prompt injection and everything if someone tries to break them. Right?
- [61:50]
B
Yes. And so that is a weird phenomenon where I would say in the last couple weeks, that's picked up more. I see more of that in our agents across the board. So I don't know who on social media started that trend of, like, hey, if you're talking to an agent, you can't get what you want. Try and, like, break its prompt or break its brain. And I'm like, one that's not very nice. Like, I know Amelia AI doesn't have feelings, but real Amelia reads the Amelia AI conversations and she has feelings. And that's not very nice when I read those. So those ones I will delete. Like, it'll send it to me, and I'll see somebody try to break the prompt. And I'm like, you know, I'm just gonna ignore that person. I'm sorry, but, like, I'm not gonna garner a response when you are rude to my AI, so I'm just not gonna respond to you, which is my right as a human. But, yeah, I would say, you know, I could probably count on my hand, though, the amount of times our inbound agent flags in one day that it needs a human. Or somebody got frustrated by it. But yeah, I would say lately it is this weird trend that people get frustrated because they try and prompt, inject it, and then it doesn't work, so then they get really mad. But for the most part, 99% of people are happy to talk to Amelia AI because we are busy. Like, I. I can't come answer your questions about tickets or where the hotel room block is or when did. When does the ticket code expire? Or when do prices go up and what's the next price and where's the venue? Because I forgot, even though we told you a thousand times, like, most people are happy to have that answer in real time, or they're happy to also book a meeting with, like, me or David in real time. They don't have to go back and forth with a Scheduler. Like, again, 99% of folks are happy, maybe 1%, slash, a handful of folks are mad on the inbound side. Now, on the outbound side, I probably at the same degree, I can count on one hand, I will get an angry email per day of, hey, stop emailing me. Or this email wasn't very good. But on the flip side, I also get a handful of emails every day that were like, thanks, this was such a good email. What do you use for this? So those really balance out at the end of the day on the outbound side, for the most part. Again, 99% of folks, though, happy to have the information and the emails all in real time, even with an AI.
- [64:04]
A
Yeah, Yeah, I think we can wrap there. I think that's a good question. A lot of folks have fear that people won't talk to the AI. There is maybe. I think you hit it. But if you could add anything else, then we could wrap. There is some sort of line, a quality line where an agent adds more value than a mediocre human. We've talked about that. It's not the best. It doesn't add more value than talking directly to Amelia or me or David. None of our agents actually are that good today. For the most part, they should be maybe toward the end of the year. But they're not as good as talking to three of us. But they are better than talking to a decent human or a mediocre human. They just know more. So what we found is if and it's. It might be hard to quantify that, maybe it isn't. But if you get above a certain line, if you invest the time to train your agent, if you read the email exceptions every day, if you upload all the documents, you're going to find this concern that folks don't want to talk to an AI is misplaced because the interaction will be better than a mediocre human. And just it's. I don't know if it was in these 10 points, but in some ways you're competing with mediocre humans here on this whole AI SDR journey. Again, you're not competing with the best SDR you could hire in the whole world, but the best SDR in six months wants to be an ae. The best six months in nine SDR in nine months might want, might leave and go to a better company. The turnover in SDRs is the highest of anything in go to market. So there's. There's the notional pretend competition of the best person you ever worked with and then there's the reality that if you get above the bar, you're going to find, and you invest the time you're going to find, people are happier to talk to that AI than to most humans.
- [65:34]
B
Yep.
- [65:34]
A
It just is. It just is. So, anyhow, this was great. Thank you Amelia, for driving this. Thanks everyone for joining and we'll keep it going and see everyone at Saster AI Annual in May.
- [65:45]
B
Thanks everyone.