Sunny Rekhi explains how forward deployed engineering works at Decagon, whose customer support agent handles enterprise email support. The role splits into configuring the agent's instructions and human-handoff rules, and product-style work anticipating enterprise needs. Key themes: the thin line between forward deployed and product work; scaling the function from 50 to 500 people; restraint in defining what belongs to the customer; proving value quickly in the first weeks of a multi-year relationship; and upstreaming custom integrations into the platform so custom work becomes self-serve. # Video Identity Observations — "How Forward Deployed Engineering is done at Decagon — Sunny Rekhi" ## Explicit Self-Description - **Speaker role and affiliation**: Sunny Rekhi states, *"I'm Sunny. I'm the CTO of Forward Deployed Engineering here at Decagon."* - **Company product claim**: *"Decagon is a 24/7 AI customer service agent… multilingual, omni-channel"* that replaces phone menus and slow email support with *"a human-like agent."* - **Company scale claim**: *"A year ago we were at 50 people. Now we're at 500,"* described as *"canonical hypergrowth."* - **Customer scope claim**: Works **cross-vertical** across *"really large enterprises"* and *"mid-market brands,"* naming **Hertz** as a customer and referencing approvals: *"These are a subset of what I was approved to talk about."* ## Intended Audience - **Engineers in forward-deployed roles**, confirmed by an opening poll: *"can I get a show of hands of who here is an engineer or is in a forward deployed motion at all?"* - **Practitioners at agentic AI companies**, implied by framing such as *"I imagine this is the case for a lot of agentic companies."* - **Job seekers**, addressed via a direct recruiting moment: *"if you are interested in a new role, sunny@decagon.ai is my email."* ## Claimed Scope of the Channel/Content - **Operational practices at a specific company**: how Decagon structures forward deployed engineering (agent builders vs. agent software engineers), scoped to a single talk rather than a channel-wide promise. - **Lessons and mental models for the field**: e.g., *"Custom becomes self-serve… this has become like a guiding ethos for us,"* and the advisor-vs-executor framing. - **Enterprise sales/deployment practices**: requirements gathering, proving value fast, and staffing *"industry experts"* per vertical. ## Observable Presentation Patterns - **Recruiting embedded in technical content**: an explicit email plug appears twice (opening and closing: *"Again, my email is sunny@decagon.ai"*). - **Promotional case evidence**: Hertz used as a named success story — proactive lease-renewal outreach built after landing inbound support workflows. - **Transparency about marketing constraints**: *"there were way more I wanted to add in there, but our marketing had got mad at me,"* indicating curated customer disclosure. - **Self-assessment of company strengths**: *"we're known in the industry to move really really fast on customer asks"* and *"we've earned trust with customers that we are advisors, not just executors"* — creator claims, not independently demonstrated in the material. ## Notes for Synthesis - No curated metadata was supplied; identity evidence is entirely from title and transcript. - Transcript contains inconsistent product name spellings ("Degagon," "Deckagon," "Akkio gone," "Decky on") — apparently transcription artifacts, not channel self-presentation. - Content demonstrates a **practitioner-talk format** (conference-style, ~10-minute talk with audience interaction) rather than produced marketing material, though promotional elements are woven throughout. # Delivery Observations — Sunny Rekhi, "How Forward Deployed Engineering is done at Decagon" ## Tone & Overall Manner - **Conversational, informal conference talk style.** Opens with an audio check and audience interaction: *"Coming guys, can you hear me just fine? All good? Okay, awesome."* - **Self-deprecating asides** appear early: *"Okay, so I'm in my minority."* (after a show-of-hands poll) and later *"I put this slide here not to sort of toot our own horn."* - **Repeated audience-oriented framing** — he addresses the room's profession directly and tailors lessons: *"for those of you who work especially in the Fortune 500"*, *"I'd encourage everyone in this audience to... keep this top of mind."* ## Verbal Habits & Fillers - **Heavy filler usage** ("uh," "um," "you know," "like"), consistent throughout, e.g., *"Um but once we are there and our agent is learning about the customers..."* - **Frequent word/syllable repetition under emphasis**, a very stable pattern: - *"the scarce skill is actually exercising restraint"* - *"it's the same bar, it's the same reporting structure"* - *"we we we broke apart this agent software engineering role"* - *"Custom becomes self-serve. Custom becomes self-serve."* (explicitly repeated aphorism) - **Stuttered restarts**, e.g., *"the the the the delineation between what is historically forward deployment versus product engineering is super super blurred now."* - **Filler mid-name slips:** the company name appears as "Degagon" / "Deckagon" / "Akkio gone" / "Decky on" in the transcript — likely delivery slips or transcription noise (uncertain which). ## Structural / Teaching Habits - **Numbered enumeration** to organize points: - *"Number one is taking that AI customer service agentic brain and making it work for your enterprise... And then on the right side is..."* - *"Thing number two, we've earned trust with customers..."* - Closing recap: *"Number one, obviously you have to... But number two... And three, mind that funnel..."* - **Concrete customer examples** to ground abstract points — the Hertz lease-renewal story: *"Hey, we already have like these integrations to your back-end systems. What other communications are you doing with customers?"* - **Analogies to familiar experience:** *"we've all had the experience of calling into your favorite brand and being told to press one for billing, press two for membership options."* - **Meta-commentary on his own slides/structure**, e.g., *"In fact, it's so important I wish I had a slide for it"* and *"you'll see this in the bottom of the slide here."* ## Recurring Phrases & Themes - **"Front line"** as a recurring metaphor: *"forward deployment engineers are the front line for customer product asks"*, *"you're on the field"*, *"taking knowledge from the field and bringing it back into the product."* - **The advisor-vs-executor dichotomy**, repeated nearly verbatim: *"you're you should treat yourself as an advisor rather than just an executor"* and later *"we've earned trust with customers that we are advisors, not just executors."* - **Scale/compounding framing** recurs: *"how do I make this one ask benefit the remainder of the customers?"*, *"making every deployment faster than the last one."* ## Humor & Asides - **Light jokes woven in:** - *"there were way more I wanted to add in there, but our our marketing had got mad at me."* - *"What's the expression? Kitchen sink or the entire kitchen? Something like this."* - **Two explicit recruiting plugs**, framed as "shameless": *"shameless plug, if you are interested in uh a new role, sunny@degagon.ai is my email"* — repeated verbatim-ish at the close. ## Uncertainty Notes - Some transcript artifacts (e.g., *"Degagon"*, *"Akkio gone"*) may reflect transcription errors rather than the speaker's delivery; I can't confirm from the text alone. - Audience reactions ("[snorts]") suggest live laughter at hypergrowth points, but audience tone beyond this is unobservable. # Observation Record: How Forward Deployed Engineering is done at Decagon — Sunny Rekhi ## Speaker - **Sunny Rekhi**, self-identified as **CTO of Forward Deployed Engineering at Decagon**. ## Company Context (as stated by Rekhi) - **Decagon** is a "24/7 AI customer service agent" — replaces phone trees and slow email support with human-like responses; multilingual, omni-channel. - Deployment model: **land** by automating complex inbound support workflows, then **expand** into revenue-generating workflows. - Example: **Hertz** — after landing on support, Decagon began proactively reaching out to customers for lease renewals/extensions. - Company grew from **50 to 500 people in one year** ("canonical hypergrowth"). - Customers span large enterprises to mid-market brands across verticals (finance, tech, etc.); the speaker notes only a subset shown was approved to discuss. ## Two Kinds of Forward Deployed Engineering at Decagon 1. **Agent configuration** — tuning the agentic brain per customer: instructions, brand tonality, actions taken on users' behalf, intents to hand off to humans; largely done in the UI. 2. **Front-line product funnel** — FDEs relay enterprise product asks back into the product: > "I know in 2 weeks enterprise B is also going to have the same ask. And this happens with stunning regularity." ## Key Claimed Positions - **FDE = product engineering**: identical bar, reporting structure, often same team; the historical delineation is "super super blurred now." - **Org evolution**: early on, "agent software engineers" did everything; at 500 people, split into two lanes: - **Agent builders** — "Decagon pros" with model intuition, working in the UI, flagging off-UI needs. - **Agent software engineers** — front-line, incorporating enterprise requests back into the product. ## Reasoning and Lessons Expressed - **Restraint as the scarce skill**: with AI coding tools (Codex, Claude Code), the temptation is one-off fixes; Rekhi argues the scarce skill is restraint and building so future customers benefit. Ethos: agents must be **owned by the customer**, not a "black box of prompts and patches" — "far too brittle." - **Define success up front**: scope success metrics, channels, and outcomes at first conversations — ideally in writing — before building; front-loaded requirements gathering matters more in the AI era. - **Staff industry experts per vertical**: knowledge compounds; shared language, credibility, faster ramp-up; goal is "making every deployment faster than the last one." - **Custom → self-serve funnel**: e.g., after ~25 custom CRM integrations, they built a self-serve integration mechanism; manual work must be upstreamed into the product. Stated as guiding ethos. - **Prove value fast**: avoid multi-month time-to-value; land quickly, then expand across the customer's support and revenue workflows ("all of our customers are a multi-year partnership"). - **Advisor, not just executor**: Decagon ingests historical support data to recommend highest-ROI automation, "sometimes that's not actually what the customer had reached out about." ## Why Decagon Succeeded (per Rekhi) 1. Known for moving **really fast on customer asks** — "very hard-working group of folks." 2. Earned trust as **advisors, not just executors**. 3. **Productizing custom work**. ## Change Over the Past Year - From fitting at "a lengthy lunch table" to designing the **system**: rigorous cross-deployment knowledge sharing, field-to-platform feedback loops, agent compounding across customers. ## Closing Themes 1. Make the agent do what the customer wants. 2. Feed learnings back into the product. 3. Mind the funnel — scale so every future customer interaction improves. ## Notable Details - Shameless plug for hiring: sunny@decagon.ai (email repeated at close; spelled inconsistently in transcript — "degagon"/"deciagon" appear to be transcription artifacts). - Rekhi noted being "in my minority" audience-wise regarding engineering/forward-deployed attendees. ## Qualifications / Unresolved Elements - Founder-age recollection is hedged and self-corrected: "in their early 20s... Oh, sorry, late 20s." - Hertz and other customer examples limited by marketing approval ("our marketing had got mad at me"). - Rekhi frames claims as his perspective/lessons ("I think," "this has been a really good learning for us"), not settled industry facts, though he suspects the custom-to-self-serve ethos generalizes across all forward deployment motions. # Speaker Attribution Record ## Video **Title:** How Forward Deployed Engineering is done at Decagon — Sunny Rekhi **Video ID:** `01a15ca8-36e5-7b94-bab8-ea622634c8d2` ## Speakers ### Primary (only substantive) speaker - **Sunny Rekhi** — self-identified: *"I'm Sunny. I'm the CTO of Forward Deployed Engineering here at Decagon."* - Role: **Creator / presenter** (talk delivered live before an audience) ### Audience - Unnamed live audience; speaker polls them ("show of hands") — **no speaking role** attributed to any attendee. ### Third parties referenced (not speakers) - **"The previous speaker"** — alluded to by Sunny; identity not given in transcript. - **Decagon founders** — referenced indirectly ("it was started by I think now they're in their early 30s... late 20s"); no names given. ## Referenced Sources & Claims - **Hertz** — third-party customer claim: Decagon handles inbound support workflows and proactive lease-renewal outreach for Hertz. - **Customer logos on slide** — described as "a subset of what I was approved to talk about"; speaker notes marketing limited disclosure ("our marketing had got mad at me"). Names not stated in transcript. - **Decagon company facts (per speaker):** 24/7 AI customer service agent; company grew from ~50 to ~500 people in a year; ingests customers' historical support data to advise on ROI. - No external publications, studies, or documents are cited. ## Promotional Segments (flagged) - **Hiring plug:** *"shameless plug, if you are interested in a new role, sunny@decagon.ai is my email"* — repeated again at the talk's close. - **Product/company promotion:** Descriptions of Decagon's capabilities, Hertz success story, and customer logo slide function as promotional content. ## Transcript Quirks / Uncertainty - Company name appears variously as **Decagon, Degagon, Deckagon, Akkio gone, Decky on, deciagon.ai** — inconsistent spelling in transcript; email given as both `sunny@degagon.ai` and `sunny@deciagon.ai`. - No timestamps, curated metadata, or comment availability info provided. \>\> Coming guys, can you hear me just fine? All good? Okay, awesome. Just so I can contextualize this talk a little bit, can I get a show of hands of who here is an engineer or is a forward and in a forward deployed motion at all? Okay. Okay, so I'm in my minority. Okay, awesome. Uh sounds good. So yes, um I'm Sunny. I'm the uh CTO of Forward Deployed Engineering here at Decagon. And today I'll talk about what it is that we do, why we have a forward deployed motion, how it has changed over time as we've gone from 50 people to 500 people over the course of a year. Um how it changes if you're working with a Fortune 20 versus a more mid-market brand. Uh thank thank you all for coming. I hope it's useful. And um yeah, let's get started. So, Okay. Uh okay, so just to give context on what Decagon is. Um for those of you unfamiliar, Decagon is a 24/7 AI customer service agent. So, we've all had the experience of calling into your favorite brand and being told to press one for billing, press two for membership options, etc. Or you email into your brand because you need urgent support and you hear back in two or three business days. Decagon replaces all of that. So, instead you pick up and you call your brand of choice and you get a human-like agent who is helping you. You email in, you get a human-like reply right away. So, that's what Decagon does in a nutshell. Um multilingual, omni-channel, etc. Um and then importantly, and again I you know I I I I say this to to help contextualize what our forward deployed motion does. But, you know, we land in our customers to help them with the kinds of complex support workflows that today have to go to humans. Um but once we are there and our agent is learning about the customers and has a relationship with the customers, then we also work with our customers to figure out, "Hey, how can we actually make you more money?" So, one example, you'll see this in the bottom of the slide here, but Hertz, you know, we're all familiar with. Hertz came to us because they had these kind of complex inbound support workflows that indeed it to be offloaded it to an agent. But once we were there, uh it turns out, "Hey, we already have like these integrations to your back-end systems. What other communications are you doing with customers?" And one that Decagon now does for them is to reach out proactively to a customer when it's time to renew their car lease or extend it or whatever, and they can do that from within Decagon. So, it is you land We typically we land and help them deflect these sort of inbound support cases, and then we expand into, you know, how do we make you more money? Um Now, we work cross-vertical. We also have really large enterprises, more mid-market brands. These are a subset of what I was approved to talk about. Uh there were way more I wanted to add in there, but our our marketing had got mad at me. We have, you know, the the top left we have our financial institutions, the bottom right we have our, you know, your favorite tech brand. Uh and this is relevant because, as I'll talk about briefly, uh the kind of forward deployment you have to do is vastly different based on both the size of the enterprise and also the vertical. Okay. So, I imagine this is the case for a lot of agentic companies, but Decagon has effectively two kinds of forward deployment engineering. Number one is taking that AI customer service agentic brain and making it work for your enterprise. So, the same way that you train a human, you give it instructions on what to do when a user asks X, how you respond back to it, what sort of brand tonality you have, what actions do you take on behalf of the user. All of this like configuring of that human of the of that \[clears throat\] agent brain is one form of our forward deployment motion, where we work with the customer, we figure out what does success look like for you, how do you want the agent to speak, what sort of user intents do you actually want the agent to hand off to a human instead. That's the left half of this diagram. And we have a team, which I'll talk about briefly, who is like really good at configuring the agent. Largely, this can also happen within the UI. And then on the right side is um the the previous speaker alluded to this as well. Forward deployment forward deployment engineers are the front line for customer product asks. And it is their job to figure out, "Hey, enterprise A made this ask. I know in 2 weeks enterprise B is also going to have the same ask." And this happens with stunning regularity. So, I want to make sure when I solve enterprise A's problem, I'm solving it for B, C, D, and E before they've even had a chance to express it. So, there's the two kinds of forward deployment engineer that we have internally, configuring the agent and then making sure all the problems that you interact with the enterprise that that come up in that in in in in the context of conversation also get brought back into the product. Which brings me to a really important point. In fact, it's so important I wish I had a slide for it, but uh at Decagon, forward deployment engineering is identical to product engineering. Uh it's the same bar, it's the same reporting structure, uh often like the same team, because the the the the delineation between what is historically forward deployment versus product engineering is super super blurred now. Uh when I'm speaking with a Fortune 20 and they express a pain point, that is often a product feature that needs to get built and prioritized. And so that line between I'm a forward deployed person and I'm a person who works on the product um is gone. Uh it's the same it's the same person and and that's represented in our in our in our org chart. So, um early on, I mean, Degagon is is an example of sort of canonical hypergrowth. A year ago we were at 50 people. \>\> \[snorts\] \>\> Now we're at 500. And uh the scale is not slowing down. So, actually shameless plug, if you are interested in uh a new role, sunny@degagon.ai is my email. Please let me know. I'll make sure your your resume \{slash\} profile gets front of my people. Anyway, back to the back to the talk. Um so, historically we had agent software engineers and they did it all. They did that configuring of that agent brain sitting side by side with our customer. Uh this is again things like what is the tonality of the agent, what sort of voice do you want it to have, both literally the voice, but also the the way it speaks. Um how do I integrate it into your back-end systems so that it could take action on behalf of the users? This can be something simple like I want to reset my password, so the agent needs to have back-end access into your, you know, authentication system. And it can be something sort of far more complex than that. And they also did some of that like platform work like customer A has this feature request and then building that back into the product. Now that we're 500 people, uh we start thinking a lot more about how do we design the Degagon system so that it can scale. And effectively we we we broke apart this agent software engineering role into two specialized lanes. One is the agent builder and these are like Degagon pros. They have a lot of intuition for the various models that power our platform. How do you make them work for the use case that the enterprise requires? Um largely living within the UI to the extent possible, flagging when things need to go off UI and how do we bring that into the product. And then secondly, we have agent software engineers. Again, these are the front-line enterprise makes product request. Making sure that gets incorporated back into the product. And um, this is I think like a super super uh, important insight, uh, which is there is routinely this temptation of Okay, customer A made this request and they're so important to us and they want it done ASAP and maybe I'll just go prompt Codex and Cloud Code to just do it for me. But the scarce skill now that AI coding is so good, the scarce skill is actually exercising restraint. Uh, and saying, you know, really thinking about how does this going to scale to sort of future customers? And part of this is our ethos. Like we we build agents to be owned by the customer and so if it turns into a black box of like prompts and patches and that's not good for us or them. It's far too brittle. Um, but also, uh, when you're a forward deployed person, this is this is kind of uh, this is incumbent upon you to to be exercising this restraint of like, let me not do the easy one-off thing, but rather make sure whatever I am building is architected in a way that future customers benefit from. So this will come up in in the remainder of my 10 minutes here, which is uh, always thinking about how do I make this one ask benefit the remainder of the customers? Um, so I I I put this slide here not to sort of toot our own horn, but to actually talk about what it looks like to achieve success. Uh, and in in our case, we've learned like early on when you're scoping the deal, like literally when the very first conversations, you want to figure out ahead of time what does success look like for the customer. And really narrowing that down, ideally getting it in writing so that there is like no miscommunication along the way. Like and when I say what does success look like, I mean what are the metrics you're trying to hit, what sort of channel that you want support on, maybe that's a phone call, maybe that's email, maybe that's text, maybe it's WhatsApp, whatever. But really narrowing like what is your pain point, what is the ideal outcome you want, and then we can race to go build that out. Um but I think again, back to sort of lessons for forward deployed folks, uh there especially when you're dealing with a large company, there's a temptation to just get started. And uh and this is partly a reflection of how AI coding has changed engineering generally, but now there's a lot of effort that has to go up front in requirements gathering, making sure you're aligned on what actually has to get built uh before before going to do it. Uh this has been a really good learning for us. So, uh we try now, given that we have like a a ton of customers across various verticals, we have found it's really helpful to have industry experts that get staffed, the same kind of deal. So, if I am working on financial service A, B, and C, when financial service D company comes around, ideally I have a core core group of folks who have experience with those customers uh working with this new logo. And the idea here is like a lot of that knowledge compounds. Like A, you can like speak in the lingo of this customer, and therefore there's a lot more credibility there. There's a lot more There's a lot like a much faster ramp up. And \[snorts\] uh a lot of the agent building, sort of the way you think about success carries over. So, uh this has been very helpful for us, and and ultimately it's all about, you know, uh making every deployment uh faster than the last one. Um I mentioned earlier that as a forward deployed and and by the way, I say forward deployed engineering, but really it's just like all forms of forward deployment. I mentioned earlier that one of the big things you have to do is to always think about how do I solve this customer problem in a way that extends to other customers. The other thing that I think is always helpful to keep top of mind is how do I make it so that I'm empowering the rest of the business to solve this problem? And this is specifically if you're an engineering. So, for example, uh Deckagon's ethos is you should be able to configure this agent completely via natural language. And so, if you ever have an engineer needing to do something that needs to get upstreamed back into the product. Uh and so, this is sort of a funnel that we have of like, "Look, Deck front forward play engineering, they're the front line for customer asks." Um but really it should get it should get sort of scaled across the business. And one example of this, and I mentioned it later as well, is like, let's take an integration. Let's say Deckagon needs to integrate into like some some CRM. Uh early on in our history, we were actually like building custom integrations time and time again. And then we thought enough is enough. After like the 25th one, we're like, "I don't know how many more are coming up." Uh so, let's just like build it a self-serve way. And now what took an engineer custom code writing can now be self-served by the customer or built by our agent building team. So, it's all about how do you scale the work that you're doing. Um also very relevant, depending on the kind of forward deployment work you do, is especially in the enterprise, wanting to prove value as fast as possible. For those of you who work especially in the Fortune 500, you're going to get hit with the entire What's the expression? Kitchen sink or the entire kitchen? Something like this. Uh but the idea is how do you prove value as fast as possible? So, in our case, Deckagon can become arbitrarily complex. You can support all sorts of channels, all sorts of very complex user intents. We try to figure out how do we demonstrate value ASAP and not have like a multi-month deal or sorry, multi-month uh time to prove value. And once we're there and we're adding value, then we expand, right? Because ultimately all of our customers are a multi-year partnership. And so, we want to make sure we're we're helping you across your entire support flow and in your revenue generating workflows, but it's important as a forward deployed person to figure out, how do I prove value right away and build your build your motion around that. Um So, customers will often come to you come to folks and say, uh I want you to do XYZ. And and often they're right. But, I think as a forward deployed engineer or forward deployed person of any sort, you're you should treat yourself as an advisor rather than just an executor, right? You're you're both. So, um you're also on the front line of, "Hey, how do I make AI work for the enterprises?" And you have so much knowledge because you're seeing it repeated across every single customer. And so, what we do at Akkio gone is we actually ingest your historical support data uh and we tell customers that hey, like if you automate this first or this first, this is where actually you'll see the highest ROI. Um and sometimes that's not actually what the customer had reached out about. Uh and I imagine there's analogs to this across all sorts of verticals, but it's important to keep in mind that your job isn't just an executor. It is of course to be an executor, but it is also to be an advisor. Uh and to not underrate the fact that you have this domain expertise by being forward deployed across many companies so that you have this knowledge base that's really valuable for the customer to tap into. Every time at Akkio gone, someone has to do something manually, we try to make sure it gets upstream back into the product. So, I mentioned the integration earlier, but this is I think a good mental model for folks to have if you're on the front lines. How do we smoothen out that path? Custom becomes self-serve. Custom becomes self-serve. Um this has become like a guiding ethos for us uh and I suspect it is the case across every kind of forward deployment motion. So, I'd encourage everyone in this audience to to um to to keep this top of mind. Like, okay, I'm doing this I'm doing this one-off thing. Presumably other people in the company also are bringing it back into the product. Okay. So, um Decky on is really interesting in that it was started by I think now they're in their early 30s, but it was I think at the time they're in their early 20s. Oh, sorry, late 20s. Um and so, what did what did we do right uh to to sort of deserve the place that we have? And I think one is we're known in the industry to move really really fast on customer asks. And part of this is just like it's a very hard-working group of folks. Um so, that's like a big reason that we got here uh is that we just move really fast deal by deal. Thing number two, we've earned trust with customers that we are advisors, not just executors. So, we'll we'll we'll we'll we'll be able to tell you based on what we're seeing across all the customers, based on the data you give us um what is going to be the highest ROI for you. And then number three, we've been really good at um making sure we productize custom work. But, the way we think about this has changed a lot in the last year because again, a a year ago we were 50 people, could all fit on, you know, a lengthy lunch table. And now we're 500. So, now we think a lot about designing the system. So, every time now now we're very rigorous about sharing knowledge across deployments, but uh making sure you extend uh the field the people in the field feed information back to the platform, making sure the agent compounds every single time it interfaces with the customer. So, if the agent interfaces with customer A, you improve that for customer B. And it's all about sort of taking knowledge from the field and bringing it back into the product. Uh and so, just to wrap up here, uh sort of the a few of the few of the themes. Number one, obviously you have to make sure you can figure that agent, do whatever the customer wants. But number two, uh make sure that it gets fed back into the product. And three, mind that funnel that I mentioned earlier. You're on the forward, you're on you're on the field, but you want to make sure it scales and make sure it improves uh every every uh future customer interaction. Uh again, my my email is sunny@deciagon.ai. I'll also be out here. Folks have questions. Thank you for coming to talk and I hope this is helpful. \>\> \[music\]