Speaker 0: Yeah. So what I’m gonna do is I’ll just introduce you, and then I’ll, um, leave stage because I think that’ll take me off of it. And then from there, um, you’ll just be able to take it away.

Speaker 1: Got it. Cool. And you could see my full screen from this?

Speaker 0: Yep. I think we’re good. I think we’re live. Okay.

Speaker 1: Cool.

Speaker 0: Hello, everybody. I hope you are having a great day in MarDreamin. Um, today, thank you for joining us. Um, I hope that folks have had a very productive and joyful, uh, time thus far, uh, with MarDreaming, and now it’s day two. Uh, what I would like to do now is introduce our amazing speaker today, which is Chris Ferraro from trey.io, and he’ll provide us some great insights on reinventing lead life cycles management. So take it away, Chris.

Speaker 1: Yep. Thanks, Gabe, for the intro. Uh, really excited to chat today, and it’s been a a great overall event so far. Um, just a little background on this presentation before we get started. I want it to be really interactive, and we’re gonna leave plenty of time at the end for Q and A. So feel free to drop your questions in the chat along the way, and we’ll make sure that we get to them in the end. So, um, before we get into the actual topic, little background on me. Um, I started my career in sales, and, um, um, now since transitioned to product marketing at Trey. So at Trey, we are a low code automation platform. The topic today is reinventing lead life cycle management in the age of RevOps. And we’re gonna cover a few different focus areas here. One, the rise of revenue operations. Two, why we think lead life cycle management is really the lowest hanging fruit where you can make the most impact in your revenue operations function. Why your funnel is leaking, and some of the challenges there when it comes to losing leads, and then a new approach to lead life cycle through low code automation, as well as some customer examples, um, with customers who have adopted this approach and have become really successful. And as mentioned, we will leave a ton of time at the end for Q and A. So feel free to drop those questions in the chat, and we will make sure to get to them. So the rise of revenue operations. So 2022 and going into 2023, we’re seeing a really unprecedented investment in the revenue operations function. Well, what is revenue operations? Um, it’s really the confluence of marketing operations, sales operations, and customer service operations to drive transparency, accountability, and predictability into your revenue function. When you think about the economic times that we’re in right now, it’s become especially top of mind. Whether you’re a public company, whether you’re private, whether you’re reporting to a board of directors, they wanna see a really predictable revenue stream quarter over quarter, and they wanna see operational excellence. So companies that have invested in revenue operations are realizing a lot of different gains, and that’s across marketing spend, increases in sales, productivity, even, um, increases in customer satisfaction post sales due to a a report that we pulled from BCG Global. I know what you’re thinking. This is such a vast surface area within marketing operations. I have tons of different use cases within sales operations. I have a lot of different use cases, quote to cash, territory management within service operations. I could wanna automate a lot of different processes related to renewals, for instance. So where do you even start with all of this? Well, we think that the number one place that you should start is by improving your lead life cycle. Um, and the reason why is modern B2B buyer expectations for vendor interactions are increasing rapidly, and they’re really changing. B2B buyers are now expecting a truly frictionless B2C like buying experience in every SaaS evaluation. We’re seeing that companies are basing a large part of their buying decision on how well you communicate with them throughout the sales cycle as well as the time and speed to lead, uh, it takes for you to engage prospects. So forty two hours is the average time it takes B2B companies to respond to an inquiry or request. Meanwhile, 78% of prospects are buying from the company that responds to their inquiry first. And we’re seeing a 20% increase in sales from personalized versus generic campaigns. So there’s a lot on the line here, and there’s a lot that we’re losing along the way. So we think that we have a perfect funnel. Right? The buyer comes in. They’re not aware of your product. They read some sort of content or syndication. They input their data. They’re captured as a lead. That lead starts engaging with your sales team. They go through your sales process, and voila, they become a customer. Um, if only it were that easy. Um, in the current marketing operations and sales operations and overall RevOps landscape, we have a bigger tech stack than we’ve ever had before. Whether you’re capturing leads via list uploads, um, scraping them from LinkedIn, taking data from Clearbit, there’s more complexity involved than ever before. And then you’re trying to compare incoming lead data from data that already exists in your CRM. You’re reconciling those differences. You’re dealing with duplicative data. And along the way, you’re trying to record that into a single source of truth. If you get anything wrong in that single source of truth, you could have huge problems where your sales team is reaching out to leads who you’re already in touch with. Your sales team is reaching out to leads with incorrect information. And we find that all of this manifests into a really significant revenue loss. 20 to 30% of revenue is lost per year due to these inefficiencies. And what are the approaches that we take today? Well, one is manual processes. Right? You have someone go through and manually upload leads via lists, check for potential duplication, and make changes accordingly. This is super difficult for a lot of reasons. It’s really not scalable, and it’s prone to a lot of human error. Then you have point to point solutions. So maybe you’re lucky enough to have a few developers on your team. Maybe you’re hiring an ISV, or maybe you have to, you know, talk to central IT and get on their waiting list. And you have that those development resources scraped together and cobbled together point to point integrations between different technologies in your marketing tech stack. But a lot of times, once those developers leave, there’s sort of this black box that’s created. And when vendors release new versions, APIs, requests, you’re on the hook for all of that maintenance, which creates a lot of technical debt. And then you have out of the box integrations. So with plenty of marketing automation platforms, there are native capabilities. But once you grow in terms of complexity, in terms of business logic, in your lead life cycle management process, a lot of times you outgrow these native integrations, and it’s just not custom enough to fit the changing needs of your business. So when we talk about the lead life cycle, what are we actually saying? Well, there’s four main steps of the process. First, you’re capturing the lead data from third party sources. So, again, that could be list uploads. That could be a landing page from Eventbrite. That could be different forms generated on your website. Then you’re cleansing that data before creating it. So you’re making sure that it fits a standard object model, and you’re making sure that there’s no inaccuracies in the data, and it’s enriched in the best possible way with as much relevant and timely data as your sales team needs. And then you’re recording that information into your single source of truth, which oftentimes is CRM like Salesforce, and you’re following up and engaging, um, customers at the right time with the best possible message. If you’re able to execute on this flawlessly, what you’re doing is you’re recapturing that 20 to 30% of lost revenue by exceeding buyer expectations at every touch point. And the best way to do that is through low code automation. So what do we mean by that? Well, we mean the ability to seamlessly integrate via API integrations into your best of breed tech stack today and tomorrow. As we mentioned before, your technology stack is growing, and it’s ever changing. So you need to be able to plug and play all these applications and have them function cohesively and talk to one another. Next, you have to have the flexibility to handle complex business requirements and large spikes in volume. What if you are expecting thousands of leads from a specific conference, um, and they’re all coming in the same day? Do you have the infrastructure to support that? What if you have to set 300 different business rules for your lead life cycle management workflow? Does your tool have the ability to handle all of that complexity? Right? And the third is transparency into bottlenecks. So do you have a single layer where you can really understand and have visibility into any problems that arise throughout your lead life cycle? Or do you have to go into every individual application and try and triage and find what’s wrong? That’s the real power benefit of low low code powered automation, especially a cloud first approach to low code powered automation. So how does low code break into each of these four areas that we mentioned before in the lead life cycle process and make them easier, more flexible, and scale to your business needs? Well, first, it’s capturing information. Right? You need to be able to capture lead data from all of these different sources. I was actually talking to a customer today who had 10 different sources that they use to acquire leads, including forms, including content syndications, blog posts, partner channels, etcetera. But underneath a lot of those main ways to capture leads, there could be thousands of different versions and copies. So how do you have a platform that allows you to ingest leads from any source, rapidly stand up new sources as you try to break into new channels, geographically or from a technology perspective, and simplify all of these uploads? You’re gonna have to have a platform that’s flexible enough to support all of these different requirements, but then also allows you to templatize at scale, which is what low code powered automation allows you to do. So when you think about all of these different ways to capture leads that you see on the right, using API integrations and using a low code platform will allow you to connect into all of these services and easily capture leads regardless of what the source is or where it’s located. The next piece is making sure that you’re preemptively cleansing this lead data. So you wanna get ahead of the curve. Right? If you end up just stuffing leads into your CRM, they’re incorrect or missing information, then down the line, you’ll have sale first of all, unhappy sales team. But second of all, a sales team that’s reaching out to prospects with incorrect information, which is very dangerous for a variety of different reasons. It could compromise a current deal. It could leave a really bad taste in your prospects now. So the best way to prevent those data quality issues is to do so before they’re written to a source of truth and synced across your systems. Using a low code automation platform, you you can actually connect into all of these email validation platforms to ensure that emails are correct, and you can create a standardized object model to normalize the data to acceptable values and create custom business logic that’s filtering out unmarketable leads. So you’re essentially using low code to reduce all of these inaccuracies as well as ensure that there’s a standard object model that can then be inputted into your CRM. And that leads me to the next piece here, which is consistently recording all of this lead data into your CRM. Once you input data into Salesforce, Zoho, Pipedrive, or HubSpot, it’s then going to be routed to your sales team. So you need to make sure that you have all of the right enrichment processes in place. Are you connecting to Clearbit? Are you connecting to ZoomInfo? Do you have all their up to date contact information? So it can then be routed to the right individuals. All of this to be achieved through low code automation by quickly integrating other systems into your business processes, having an idea of exactly where the lead sits in the funnel, and then as mentioned before, the ability to troubleshoot issues easily across your tech stack, um, whether it’s at the individual business logic step or at the workflow level. The final piece here is orchestrating engagement. So once you’ve collected all of that data on your prospects and your leads and your leads have that information in the CRM system, you want to make sure that you’re engaging them in the right ways. So you can actually use low code automation platforms to connect into your Outreach or your SalesLoft and work through custom campaigns based on the data they’re enriched with. So let’s say you have a prospect that you know just attempted a webinar. You can then send them to a custom campaign in Outreach or in sales offering group specifically designed to nurture them, um, with content and information and insights from the webinar. All in all, you have greater control over the sales outreach process, and you could listen for and aggregate intense signals from multiple sources. So when we talk about all the money that’s at stake and really how it comes down to being able to follow-up with leads in a timely way as well as being able to follow-up with them in a personalized manner, you’re able to do all of that in one platform with low code automation. So you’re probably not gonna start here. There’s a lot of fragmented processes and probably some manual steps along the way, at least from the get go. But this is what the future could look like with a low code automation platform. So imagine being able to intake lead information, validate whether that information is correct, search for existing records. If there is an existing record, update that information. If not, create a new lead, enriching that data with all of up to date contact and engagement information, at attributing that, uh, lead data with the right account, scouring, and then routing to the right leads. And we’ve seen that customers who have readily adopted low code automation platforms even at a at a high scale. Um, so we had one customer that I talked to recently who has a sales team that scaled to 5,000 sales reps, um, and they get 80,000 inbound leads per month. Through implementing a low code automation platform, they’re actually able to go from intake all the way to sequencing from a sales team in under three minutes. So when you think about the ROI and the time that’s saving the sales team as well as just the overall operational efficiency, it’s very significant. And low code automation platforms are really focused on the user experience and democratizing access to all of these integrations and connectivity between systems. Um, and it’s doing so with the right governance and security in place and scalability so you can feel confident that it can scale needs of your business. But don’t just take my word for it. Here are the here are some of the results that were realized by leading customers who actually chose to adopt a low code automation approach to speeding up various RevOps processes. So Jellyvision was similar to kind of what we’ve talked about today. They were able to increase their lead response time by 3x. AdRoll was able to leverage low code automation to accelerate their sales insights, and other customers have done everything from increasing speed to onboarding to reporting and quote to cash. So I know that that was a lot of information, um, and I I did wanna leave a very significant amount of time for questions at the end. So are there any questions from anyone who’s been listening in? I’m gonna open the floor now, and then I think Gabe is gonna help us moderate through that as well.

Speaker 0: Thank you for the great presentation, Chris. Um, as Chris mentioned, he wanted to leave plenty of time. It looks like we have, um, north of twenty minutes for questions and answers. If folks have questions, feel free to drop them in the Q and A session section rather, and I will read them to Chris, and we can, uh, go through those in that way.

Speaker 1: Well, I I do think I just saw one come in from Lexi. Um, is it okay if I take that one, Gabe?

Speaker 0: Yeah. Go ahead.

Speaker 1: Yeah. So examples of low code automation platforms. Um, well, I’m gonna have to plug my company, Trey. Trey.io is a low code automation platform that’s designed for scale, and it we have a specific focus, um, on RevOps as well, and we’re leading a whole campaign in that direction. Um, as far as low code automation, there’s kind of, like, two ends of the spectrum. You have the the Zapiers of the world where they’re, um, almost no code and usable by any business user, and then you have maybe the MuleSofts or the TIBCOs, or the Dell Booms of the world that are very heavy code base where you’re gonna need specialized expertise to own and operate them. Think of Tre as a bit of a a middle ground there where you do need a basic understanding of APIs and data structures to be successful, but you don’t need to be a full blown developer. So you’re getting the power to address all of these different use cases via low code. But then if there is a really complex requirement needed, um, you can fulfill that with code, uh, in the form of a JavaScript step or or something of that sort.

Speaker 0: Thank you. Um, do folks have other questions? So I’m seeing one from Kayla, and she’s asking, can you talk about how you or sorry. Can you talk about how you two integrate with Salesforce? How to integrate with Salesforce?

Speaker 1: Yes. Certainly. So I would say Salesforce is probably our most commonly used connector. Uh, we have 600 plus connectors, so that’s definitely saying something, um, which is why it’s great to talk to this community. We integrate with tons of endpoints in the Salesforce API. Uh, so you would just use the Tray platform to drag and drop a connector into our workflow, add certain business logic depending on your use case, and then select the API endpoints within Salesforce that you’d like to make a call to. They’re they come in the form of an operations drop down, and then you have to configure the connector, um, whether you’d want it to be, you know, a daily sync, whether you’d want it to be via webhook. Um, so really just specific to your use case. Um, but you would be able to integrate directly with Salesforce through our connector, and the drop down would showcase all the API calls that are available, um, and then the inputs required to execute on those API calls, and you’d be able to map the API output down subsequent steps.

Speaker 0: Great. And I’m seeing I I saw a couple going in. It looks like we’re using the chat and the question, um, Q and A session. So I’m gonna take one from Rob first, and he’s asking, do you find it do you find typically you can automate manual work out of lead processes completely, or do you ever see a combination of manual review and automation in a sort of hybrid approach?

Speaker 1: Yeah. So we are able to, um, I think we’re able to automate a significant amount of the process. I think there’ll always be some manual workarounds. There’ll be some leads that come in in a format you’ve never seen before and things of that sort. But, um, to give you an example of a customer that that I actually talked to today, they’re they said they were able to automate 90 to 95% of the process. Um, and so before, they were dealing with a lot of, um, manual work. And to take the lead from initially getting adjusted to when a sales team person reached out to them, it would take them upwards of two days. Through automation and through leveraging tray, they were actually able to take that down to three minutes. So 99% of their leads go from point A to point B in three minutes. So some some of it will always be manual, but there’s definitely pretty significant gains.

Speaker 0: Great. And it looks like one came in from Angelica. Any unique use cases you’ve seen clients use with Trade dot I O and Salesforce?

Speaker 1: Yes. So there are a number that I can think of. Um, one that’s cool that we actually do internally with Trey is as a as a morale boost, we actually have a a sales wins channel. So when a new deal is closed won in Salesforce, then that deal gets sent to an internal Slack channel, and everyone can comment and celebrate and tag all who were involved in the deal to applaud them for their work. So I find that that’s a pretty cool use case that we use internally, especially with remote work. It allows you to stay close and connected to all of the all of your coworkers. Yeah. That’s one that that jumps out at me, but we do have so many, um, from reporting. Right? So if you wanna do a closed loss analysis in Salesforce, you can, you know, stream all of that information to Tableau from Salesforce. And then like we mentioned in this whole lead life cycle management process, once you’re enriching data, once you’re, um, getting data sorry, getting information from all of these different services, you wanna then record that into your single source of truth. A lot of times, that single source of truth is Salesforce.

Speaker 0: Awesome. And we have another one from Amir. What’s the best way to upload lists from events by removing some of the manual steps?

Speaker 1: So the best way to do it is by having a by using a tool like Tray to, um, um, define a standardized object model that, um, for list upload. So we actually we have a whole blog post that goes into it in more detail that I can send over after, but by standardizing the object model. So that way, if a lead is, like, missing information or missing a certain field, you can kind of account for that and then, um, make sure that if it’s missing or you can kind of create your own rules. So if it’s missing a certain amount of information, you can choose to not even route that lead to the sales team, or you can choose to enrich that lead with information by cross checking in DiscoverOrg, ZoomInfo, things like that. But it starts with, like, setting that standard for what should be a part of the lead. And then once it gets ingested, all of those, uh, sort of business logic steps to make sure that, um, that it’s compatible with with how you’re thinking about your business.

Speaker 0: Great. Thank you. And one from Larry. Are the cookie and engagement tracking data brought over when in when integrated to other third party incoming sources?

Speaker 1: I’m not sure I I’m not sure I follow that one. We’re making API calls to these third party, uh, sources, so you wouldn’t be, yeah, you wouldn’t be integrating in, um, to, like, their their cookie level information, um, unless, like, you’d basically just be getting so, like, if you’re integrating into, um, say, a DiscoverOrg or a ClearBit, um, you’re making an API call to that service. You’re collecting information on a certain lead, for instance, that’s already in Discover or that’s already in Clearbit. And then maybe you’re populating that into your lead to enrich the lead with information in Salesforce, and now you have their contact information. But that wouldn’t necessarily be cookie or engagement level data from that third party service. It would mainly be, um, data that would be accessible via API call to that service.

Speaker 0: Thank you. Just making sure I didn’t pass over anything in the chat. Do folks have other questions for Chris? Oh, there’s one that came in. From Kayla, can you start with just one step of the process?

Speaker 1: Can I start with I guess, could you confirm what what’s meant by that? What process?

Speaker 0: And I’m looking to see if there’s, uh, one of the things she said, like, just enrichment.

Speaker 1: Yeah. Sure. So one step of enrichment would be let’s say you ingest a lead, and that lead is missing their it’s it’s a personal email, right, that you get a lot of LinkedIn leads only have a personal email associated with them because that’s how people sign up. It doesn’t have a business email. Then you can actually integrate directly into a Clearbit, for instance, cross check whether that lead exists in Clearbit, then check if that lead has a business email associated with it. And if it does, you can move that information under the lead. So before it gets inputted into Salesforce, you now have the personal email as well as the business email associated with the lead, and your sales team can follow-up with them in the right way. Hope that answers that. And I think sorry. One thing just to highlight, uh, that I thought of with that question is you’re gonna have a a lot of different business rules and logic depending on how your company is thinking about your own lead life cycle management. As I mentioned, we have one customer who has 300 different, um, logical rules that that happen throughout their their lead life cycle management. So you need a ton of flex and it could even vary by geography due to compliance concerns or things like that. So what low code does is it allows you to set these rules. It allows you to be really flexible and change them if need be, um, and sort of make them really custom to what your business is trying to achieve. And that’s versus being stuck with maybe a native integration that’s good out of the box, but, um, something you may outgrow with scale or with complexity as the business continues to grow.

Speaker 0: Thank you. Thanks for that additional piece. And it looks like there’s another one from Angelica. Any cool integrations with Slack that you’ve seen?

Speaker 1: Yeah. So one cool one that we have, uh, there are a few that come to mind, actually. One that’s cool is that we facilitate is between Gong and Slack. So we listen for competitor keywords in Gong. And if a certain competitor comes up during a sales call with our reps and the prospect, then we actually send that data, that information to a Slack channel called competitors. So we we can keep track of how many times each one of our competitors is mentioned over a month to month, quarter over quarter, and year basis, and it really helps us keep a pulse on sort of the the competitive landscape. Another one that’s cool is post sales. Um, we wanna follow-up with our customer issues as quickly as possible. So when a customer fills out a Zendesk ticket, everyone on the immediate account team is notified and tagged in Slack, and they can comment in a Slack channel. So that way, they can follow-up with that issue and request as quickly as possible and escalate if need be, uh, making sure that they’re adhering to the right SLAs and solving the problem as efficiently as possible.

Speaker 0: Wow. That’s awesome. Like, that’s, uh, our company lives on Slack, so that would be very useful.

Speaker 1: Yep. Yeah. There’s there are just so many different use cases when you think about it. Um, even intent data. So, like, if a lead if a lead goes, uh, goes on your company’s, um, G2 page, for instance, you can then and and you’re capturing that data via Bumper or one of the other intent data tracking services. You can then send that to a Slack channel. Um, we have a intent data Slack channel, and it immediately tags the Salesforce account owner who’s associated with that record as well as the SDR. So you’re basically getting real time notifications when a prospect who’s associated with one of your accounts has, uh, visited your G2 page, which is pretty cool, and that’s helped in a lot of ways. Um, another one that’s cool is funding announcements. So you can track funding announcements. Um, I believe we we track it on Crunchbase. And so if if I was a sales rep and I had a territory, and one of my accounts in that territory had a new funding announcement, I could then get a Slack message with all the information on that announcement. So I have maybe a reason or impetus to reach out to them and also have a potential value proposition around their funding and further investment in the business.

Speaker 0: That’s awesome. Uh, I know with our organization, we use Slack mostly for internal messaging. Um, but it’s really cool. One of the pieces that you said is that, um, you’re also able to tag, like, account owners. So it’s serving, like, the business, um, purposes as well to notify folks that there’s actions to be taken. Yep.

Speaker 1: Exactly. Mhmm.

Speaker 0: Like, that’s way cooler than, like, the activity timeline in Salesforce because, you know, a lot of users may not enter Salesforce every day, but, uh, folks are always on Slack when it’s used in the company.

Speaker 1: For sure.

Speaker 0: Uh, so we got another question. Uh, you can share or maybe more of a comment. You can share G2 data in real time with your team?

Speaker 1: Uh, yes. So I believe it’s it’s G2 data that’s it’s intent data. So it comes through Bambora, I believe. And, um, and then we connect Bambora to Slack. So once Bambora picks up the intent on our G2 page, then it would go to our our Slack channel and notify all the team and everyone involved. And I actually do think we have we have an integration directly with G2 in addition to Bambora. So, um, we do connect to the G2 API. Um, now that I’m thinking about it, so that would be a direct API con like, real time connection that that we set up that notifies us in in Slack.

Speaker 0: Looks like we have another question. Uh, what about project management tools? We use Asana here at Circante. What can I do with Asana and Salesforce integration?

Speaker 1: Yeah. That’s a really good point. So, um, I think Asana, Jira, a lot of project management tools, that’s that’s a pretty fundamental and core use case that we see at Trey. As far as applications between Salesforce and Asana, um, I’m not familiar with a direct use case there. I can think of a few with Asana and Slack. So, um, let’s say you’re on the product team and you’re preparing for some sort of a launch and everyone has their own deliverables and you’re working on a Slack channel with everyone involved, you could get programmatic, um, updates once someone has, say, finished a part of their Asana project. That could send a webhook to Slack notification that, um, some part of the project is finished or a notification on where you’re tracking towards your goals, and you’re getting that in Slack without ever having to go into Asana. It’s helpful because a lot of companies are just running on Slack and, you know, you have a ton of different SaaS applications. So you’re able to kind of stay, um, and see through that one pane of glass sort of all the interactions that are going on with different stakeholders and across different projects.

Speaker 0: Thank you. We have a few minutes left if folks have additional questions.

Speaker 1: One thing just to, uh, you know, shamelessly plug at the end as we’re waiting for any additional questions, We do have if you wanna get more in the weeds on the trade.io platform and actually understand what it looks like, what the features are, we’re doing a demo jam tomorrow. So we have some really great members of our team, Neil’s and Austin, who are doing that. It’s tomorrow at 9:55 AM eastern if anyone wants to tune in there.

Speaker 0: Great. That sounds like a great opportunity to be able to see, uh, see it in action or the application of, um, trade.io.

Speaker 1: Definitely. I think it’s good it’s good paired with this session because you’re getting sort of the the high level, um, what the problem we’re solving is and then what the value is of our platform. But there are going to be some use case specific questions like, great. That all makes sense at a high level, but what does it actually look like? What are the tools that you have to accomplish this? And that’s really what that session’s gonna hit on. So, um, definitely recommend for anyone interested.

Speaker 0: Awesome. And I know you mentioned Slack a couple of times. Um, how would it integrate with is it able to integrate with, like, Microsoft Teams? And have you seen any use cases around that?

Speaker 1: Yes. So we do have a a out of the box integration with Microsoft Teams. Um, a lot of the use cases would would kinda be similar to Slack, uh, just with Teams instead. I’ve seen, um, plenty of different use cases. Teams has a bot as well as, uh, the Slack bot. So there are some cool use cases there, um, where you can actually, like I saw one where you could surface a a card in Microsoft Teams for users within the organization to actually fill out, like, product feedback. So if you’re part of an organization and you hear from a customer that X feature needs to be improved, um, it was a connection between the Teams survey bot, who would give you the survey to fill out with all of that information, and then directly to product board. So your own product organization could actually action all of that feedback and make improvements based on, um, what you’ve been putting into that survey and customer sentiment.

Speaker 0: Great. Thank you. And we’re running up on about a minute left in our session. Uh, do folks have any other additional questions? Uh, quick questions I should ask because, uh, this will cut off this will cut us off right at the time. Okay. I’m starting to see the thank yous. Oh, go ahead.

Speaker 1: Oh, I was gonna say before we we get cut off and sorry to cut you off, dude. But, uh, thanks again for, um, for tuning in. Really appreciate it. If you do need to get in touch, my email is right there, chrysta ferrara at trudio. Also, feel free to connect with me on LinkedIn. Um, definitely open to connecting there. Um, and, yeah, if you do have time tomorrow, check out the Trade Demo Jam or visit us online at trade.io.

Speaker 0: Thank you. And MarDreamy’s is coming up shortly. So if you’d have time, please pop into that and enjoy the rest of it.