The below transcript has been auto-generated for your convenience. Please reference the source video/audio for direct quotes or to clarify any errors.

Speaker 1: (00:00)
Hello. Hello, I am Connor Jeffers. I am a white male. I have a beard and glasses, and I'm wearing a white shirt with, looks like little blue black roses on it that I found in my closet this morning. Uh, really excited to be here. I'm, I'm the founder and c e o of apps. Today. We are a HubSpot Elite Solutions partner, uh, and we build all sorts of stuff on HubSpot. So we've been doing these workshop series. Uh, as a reminder, this is a workshop, so if you guys have things you are trying to build or questions about some of the examples we give, please throw them in the q and a. We'll spend the back half of the webinar, uh, live, answering how you can build some of the stuff on your list or different ways you could tackle and solve different types of problems. Uh, and we find that that to be some of the most, uh, beneficial parts of the whole thing. Actually, jump back one, uh, for our producer here for a second, cause I wanna make sure that Jack gets to do an intro as well. Uh, and then I'll touch a little bit more on format. So, Jack, I'll hand it to you.

Speaker 2: (00:52)
No, thank you, Connor. So my name is Jack Pronouns are he, him. And, uh, I'm a white male wearing a black hoodie. Uh, and just got my haircut today, so I have a, a nice haircut. I, I think, in my opinion, anyway, . So

Speaker 1: (01:03)
It looks great, Jack.

Speaker 2: (01:04)
Thank you. Thank you. Uh, , um, been in HubSpot for, uh, a little over five years. I've spent two and a half years working post-sale on the tech consulting team, and I spent the other half of that working pre-sale and our, our pre-sales team. So I was a solutions engineer for a good chunk of that time, and I've recently moved into a more specialist role focusing solely on the operations hope. So, it's, uh, it's been really interesting and only about two weeks in that role now, so it's going well.

Speaker 1: (01:28)
Sweet. Uh, well, let's talk through same format if you've been to our other workshops or if you're excited about C M s and other parts of, uh, of HubSpot, the same sort of format we'll follow for future ones. So we're gonna go through a couple of pre-baked examples, uh, that we have together. Uh, we'll talk through how they work, why you'd use them, how you might build them, and give you kind of get your brain juices flowing on awesome ways for Operations Hub to work with Service Hub. Uh, and then what we're gonna do is do q and a and, and comments and talk through some of the use cases that you guys have. So do throw those in the q and a, whether questions about some of the examples that we're giving or something else you are trying to build. Our favorite parts of these workshops are people bring cool, interesting, fun problems to us, and we get to live, talk about, oh, that's super cool.

Speaker 1: (02:11)
Here's how I think about building that, and sort of help you on the right direction. Um, so welcome, welcome, uh, as a starting point. We want to cover, why are we talking about this? Why, why is this fun and interesting and exciting? So when we think about service and Operations Hub, operations Hub is my favorite hub. Uh, and the reason for that is Operations Hub lets you connect to and automate anything using HubSpot. So whether you're trying to extend some of what HubSpot's automation or custom functionality is inside of the portal itself, um, or you're trying to get HubSpot to work with or interact with other systems, other tools, whether web-based applications or proprietary systems, operations Hub helps you do all of those things. Uh, so if you're using Service Hub and you want to do stuff that you're struggling to do in basic HubSpot or you, you have other systems or technologies that perhaps your customer experience touches, which we find almost everybody does, uh, operations Hub will help you do that.

Speaker 1: (03:07)
So ev inevitably the end goal of Operations Hub, uh, going back to sort of our flywheel on our next slide, um, is being able to sort of leverage these together and ultimately connect your service to the rest of your customer experience and make it really awesome to be a customer of your company and deliver awesome custom experiences to all the different customers that you support. Um, so let's go through a couple of examples. So one that we're gonna touch on, on the top end and something we run into all of the time for some of the larger organizations that we might be doing Service Hub implementations for, uh, is complex ticket routing. So we'll have a couple of different examples of of what that really means. Um, but out of the box, right, HubSpot has sort of, you can set a specific person or you can round robin a ticket or you can rotate it amongst a team, has really powerful assignment functionality.

Speaker 1: (03:55)
But sometimes we run into customers who actually need more complex ticket routing than what you're sort of able or, or want to be able to do with HubSpot outta the box. And so this'll be an example for both of the ones I'm gonna go through for new tickets are created, and we'll have a workflow that gets triggered. And so this maybe either a brand new ticket comes in, it could be a ticket, hits a certain status, so maybe you have an escalation process and HubSpot, and once a ticket sort of reaches a certain level of, of escalation or a certain s l a, you want to enroll it into this workflow. Um, sort of different ways that you might manage and route these, but in case sort of round robin or something specific is a little bit challenging, uh, operations Hub is gonna help you do that.

Speaker 1: (04:36)
So one example here, uh, on our next slide is out of office rep management. So we run into this all the time where perhaps I have a large, uh, call center or a large, uh, rep floor or even a smaller one where I have four or five agents and I have ticket volume. And whenever someone is out of office, either because they have p t o, maybe they're out sick, uh, they're just unavailable for whatever reason, uh, we want to skip them in our routing. So default and HubSpot, what you would need to do is you could go to your workflow and you could adjust that workflow for that particular day and say, oh, Jack is out sick today. So don't, don't distribute this to Jack. Um, if you have a large number of agents, this gets to be really, really onerous, uh, and really complex to manage.

Speaker 1: (05:17)
And so Operations Hub is here to help you. So what you can do using Operations Hub is we would use a coded action, uh, and we would pull from, so if you have an H R I S system or perhaps a Google Calendar where people are adding their P T O or their sick days and sort of logging that information, we can have our coded action go and reference the H R I S system, find out who is out on P T O, who is out sick, and then round robin amongst all of the agents that are actually in office and available to be taking tickets today. And right now, um, you could do the same thing with an integrated Google Calendar where we've done some workarounds where someone just manages it out of Hub DB because that's what they have access to. Uh, but our favorite examples of this is, is when we can actually connect directly to the H R I S system that manages the P T O and we can just filter and, and sort based off of who is out on P T O.

Speaker 1: (06:05)
So really, really awesome way if you struggle with high volumes of tickets and agents are getting assigned tickets, but that person isn't available, and being able to sort of automate at scale the ability to handle who's in office and actually available to be taking tickets. And you could extend this same concept, uh, in a handful of different ways depending on where that list of agents that are available SIM think similarly to skills-based routing or different types of agents that have different certifications or skillsets. Uh, really, really awesome ways to extend some of routing your ticket to the best agent to actually handle it. Um, another example using something very, very similar, uh, is capacity-based routing. So we run into lots of situations with customers where perhaps they have large volumes of tickets and the tickets take different amounts of time to actually solve. So we have a customer who sells servers and server space, and sometimes their tickets are, I need my password reset for my admin user, and sometimes their tickets are, there is a rogue SQL query running on my server and I need someone to go find that SQL Query and turn it off so that it stops taking up all of our run time.

Speaker 1: (07:09)
Uh, and that ladder ticket might be a lot more complicated to solve and take a lot more time for an agent to actually handle, but when those tickets are coming in, maybe we have a form field or something on that ticket form that's telling us what the customer thinks the level of difficulty is. Uh, but customers tend to mark everything as urgent, uh, cuz all customer problems are urgent in their eyes. And so what we wanna be able to do is actually route the ticket based off of how many tickets different agents have. And so the way that this works is when a ticket enrolls in your workflow, you would hit the C R M A P I and you would pull all of those open tickets, you would group them by which agent it is assigned to and sort based off of who has the least number of tickets assigned, and then you would assign tickets to that agent until they become full and then someone else shows up at the top of that sort list.

Speaker 1: (07:57)
Um, you can do something really similar here if you use sizing on some of your tickets. So rather than just number of quantity, maybe you have a field that indicates, you know, how complex of an issue is something or scored by that. Uh, and you'd be able to then say, this agent either has the highest quantity of tickets, or maybe you want to set a threshold and say, no agent should have more than 20 at any given time. Whatever your business logic is, you will be able to build it into that custom coded action and then be able to say, only assigned tickets to the agent who has the least number, has the lowest score of complexity, or perhaps has the, uh, perhaps has the, uh, least number of tickets for the least amount of time. So you can start powering really complex routing, uh, and this is Operations Hub is awesome for you to be able to extend some of what you're doing and assign them to the right person. Um, so this next example, uh, Jack, I could speak to this one, but I, this one may have come from you, uh, or I can take it,

Speaker 2: (08:57)
Uh, it, it, it did actually come from you and I'm happy. Maybe like, I'd love to get your thoughts as well, but to kind of maybe set the scene, um, this was just an interesting thing that I was working on quite recently and I wanted to flag it. Uh, so, uh, service Hub, obviously the kind of the, the, the, the center of the service hub is the conversations inbox where, you know, you've got different avenues of communication coming in for support, whether it's email, whether it's, uh, Facebook Messenger, whether it's, uh, live chat, um, or, or support forms. And what they'll do is they'll create threads in the inbox and you can manage the back and forth. And, um, we recently launched a a, a suite of a APIs, uh, lots in data right now, but it's publicly accessible. Anyone can access it, and it allows you to interface with the conversations inbox.

Speaker 2: (09:40)
And what's really interesting about this is that you can actually scrape content of the thread and use it for automation. So, um, this could take many shapes or forms. So for example, in my instance, uh, uh, an email would come in with some data in the body of that email, and I use some custom code to parse through the email and take that data to perform various actions within the crm, whether it was creating or updating a contact or creating a ticket and assigning it to somebody. So, um, I just wanted to flag that, uh, it, it, I can pop the link into the, the, the, uh, chat just as to where the documentation is, but it opens up some really interesting ways of, of looking at custom coded automation in the service hold, uh, sphere.

Speaker 1: (10:21)
Jack, to give you credence to this one as well, thi this one, uh, and when you and I talked about it, we're, we're currently trying to add, uh, p t o and in our system into creating time logs so we can manage capacity and other stuff, which happens in a whole bunch of systems outside of HubSpot. But this example is, I get an email, uh, that says someone has approved P T O and it's this many hours, and theoretically I could use this example to intake that email and then use Operations Hub to go and do stuff off of those. So maybe I want to add that and to some of my skip routing, but in our case, we want to generate a time log. Uh, and the cool part about Operations Hub is because we have access to this, and even though some of those things aren't happening inside of HubSpot itself, we would be able to use HubSpot as sort of the orchestration machine to build on all of that automation, uh, which I think is a really cool application of this same concept.

Speaker 2: (11:13)
Um, a absolutely, and, and, and as well as that, like I'm a big advocate for, I think the more access you have to the data via the api, the better. And, and this was just a big win, I think for, for HubSpot to, to, um, release this in public beta because it just adds more tools to the toolbox when it comes to building out bespoke, uh, processes for, for businesses. So, yeah, um, lots of cool ideas that can come off of that, I hope.

Speaker 1: (11:37)
Cool. Well, I'll go through another example here. Uh, and, uh, this'll be Auto Association. So this is actually something we run into all of the time. Uh, in fact, we run into it so much that we built an app, uh, to solve this problem before Operations Hub came out, uh, because it, it, it vexed us all of the time. Uh, I can throw the link to that app in the chat. Uh, it's called Associate, but with Operations Hub, if you have Operations Hub, you don't even need our app. Uh, you can just do this straight in Operations hub, which is really exciting. So this example, uh, is to do ticket association. So something that we run into all of the time. So the original example, I think this one's in like our app video that we, we made this for was we had a customer who was selling physical products.

Speaker 1: (12:16)
Um, they had an order number, so they had a deal that was based off of that physical product, and they would ship it to that customer. But when that customer came back and opened a support ticket, they would then open a order number and put, oh, here's the order that this ticket is for. Uh, and the challenge that we ran into was there was no way for us to link the, um, the ticket that got created to that deal. And so what would happen is agents would get that ticket, they would go find the order number field on that ticket, they would search HubSpot to find that order. They would link that order to the, to the ticket, and then they would go and do a bunch of other things based off of what they found. So one example would be if they found sort of that ticket and then that ticket was, or the order number was outside of the return window, they would notify the customer, Hey, this is actually outside of our return window.

Speaker 1: (13:01)
Here's what your other options were. And that was taking them a bunch of time. And so using Operations Hub, uh, you'd be able to actually, when that ticket's created, search HubSpot for a deal using the c r m association's, a p i that matches that particular order number, and then link that deal and that ticket together, um, using Operations Hub. So what that lets you do is say, automatically, let me link this deal to this ticket and then let me use Workflow Logic that says if there's a new ticket and the reason for the ticket is return, but the order date is more than 30 days ago, automatically email this customer and tell them they're outside of their return window. And now we just took that support action, which used to take somebody 10, 15 minutes to hunt down the right information, draft that email to that customer, send it, and close the ticket, and now it's fully automated.

Speaker 1: (13:48)
So now we can focus our agents on tickets that really need their time and ultimately deliver a better customer experience. So the way that this works is, uh, when that ticket's created, we use the CR r m association's a p i, this code in action runs whenever a ticket's created with an order number, and we search for that ticket. So you can extend this example. So whether you're using order numbers or, uh, that customer example I gave earlier with, um, the, uh, the server space is they have server IDs. So whi which server ID are you experiencing this issue on? Maybe you go and fetch information from your system on a different object that might be in the database or link your ticket to additional folks. Um, or maybe someone else needs to be associated to this ticket, uh, and what is their information? And you can create a contact and associate them and power all of these different pieces.

Speaker 1: (14:33)
And so really, really awesome where objects come into HubSpot, maybe they, they don't have a lot of context and your agents are spending time trying to add that context. Uh, and you can automatically do that with search and association APIs and extend the power of what your Service hub does and ultimately remove some of the lift for your agents, uh, across the board. Um, so I think a really cool example, uh, it looks like yawn through the associate, that's all associate does. Operations Hub does lots more stuff. Uh, so the cool part is we built an app for that, but you can actually build that app entirely on Operations Hub, which I think extends sort of the value of Operations Hub, which is you can build all sorts of stuff on it that typically you'd have to do with custom development outside of HubSpot. Um, next example from us is connections into your product.

Speaker 1: (15:17)
Uh, so often we find customers that are, uh, either a SaaS business, and so they have a lot of customer data about who their customers are that lives outside of HubSpot. Or even if you're not a SaaS business, you might have an E R P, you might have an ordering system. Something we run into all the time is customers come to us and say, I need a really complex custom integration with my E R P or complex custom integration with my order database. And what they actually want to be able to do is deliver one part of their customer journey with context from that other system. And so you don't need to build a big complicated bidirectional integration. All you really need to do is make sure that in your automation powering this journey, you're able to connect to and push and pull information from the system where that data lives.

Speaker 1: (16:00)
So some examples, um, for this to be able to, to map into is, uh, ways you could do this. So something that we do for some of our applications is we actually have HubSpot as, uh, effectively our admin panel for everything inside of our system. And so when we want to make a change to a customer record, instead of trying to navigate into the admin panel of a software tool or navigate somewhere else, we can actually just check a box or edit a field, and then we can use a custom action to then go and push that information into another system or another database. So, um, our examples, if we go to kind of our next slide here, and these are real things that we do for our product. So, uh, we have a subscription app, subscription object inside of our HubSpot portal for all of our apps, uh, and things that our support agents do all of the time is extending free trials.

Speaker 1: (16:49)
They get customer tickets that say, Hey, I got your notification that my associate trial is ending next week, and I wanna, actually, I didn't have enough time to, uh, play with this. Can, can you extend it for me? And what used to happen in similar concepts for can you cancel my subscription? I'm no longer gonna use it, or I'm locked out of my admin panel, I need to reset my password. And so what we've done is we've created, uh, all of those as fields on our app subscription object. And so our support agents, when that ticket comes in, we can actually go and say, oh, okay, cool. You wanna extend your trial? Let me edit the free trial expiration date to two weeks from now, and then let, let's use a coded action in HubSpot to then send that information to our backend that manages those subscriptions.

Speaker 1: (17:32)
We actually send that back into Stripe, we update that stripe expiration date, uh, and now the customer's entitled to a longer period of time that they can use that free trial. And so what this does is our agents, uh, one, they don't have to have access to stripes. There's some security benefits there. Two, they don't need to contact Switch and go try to go into Stripe, search for that customer, access that customer, and be able to make a change. And they can do all of this right from HubSpot. We also can do this with automation. So we can do things like send a customer an email and say, uh, Hey, your trial's about to expire. If you need more time, just click here. And when someone clicks that c t a, we can trigger that workflow and we can send that data back to Stripe and say, update the subscription that's associated to a customer with this email, uh, and extend that, um, extend that free trial period.

Speaker 1: (18:20)
Uh, so lot of examples here for sort of how we set this up and what this looks like, but one of our favorite things about, uh, operations Hub is it sort of lets you use HubSpot as that master customer system of record, uh, and then be able to go and push and update data in other places without people having to do manual tasks. So maybe a support agent says, yep, I'll go ahead and extend your trial, but they get distracted, they don't actually go to the system and do it. And now the customer's sitting here with an expired trial and saying, someone told me this would be extended what's going on? Uh, we can eliminate any risk for those types of experiences by automating the entirety of that overall customer experience. Um, and so you can extend this to whether it is your application, maybe you need to go in, cancel an account, cancel a a, a shipment, anything that might have a, an additional system in the mix.

Speaker 1: (19:06)
Uh, and you can power all of that directly from HubSpot, which ultimately leads to a simpler experience for your internal teams, making you more productive and effective as well as a better customer experience. Because there are no errors, everything's instantaneous, and you can extend kind of the power of service hub across the board. Um, so those are kind of the examples that, that we'd pre put together to get people thinking and, uh, thinking about some of the stuff they're trying to do. If you have questions on these particular use cases, we're happy to chat through those. Um, also if you have anything you are working on or how would I do this? How would I solve this problem? How would I build this particular experience? Um, throw it in the q and a, we'd love to touch on it, we'd love to talk about it. Uh, and we'll spend sort of the rest of the time that we have here, uh, with questions that we get, talking through some of the examples that you guys might have or some of the problems you're trying to solve, um, with Service Hub or anything else with Operations Hub.

Speaker 1: (20:01)
Uh, there's one that I saw in the chat that didn't make it straight into the q and a, uh, that I can go and touch on from Brandon Ksh, which is, how do we define when an agent is full? So I think that this related to some of our capacity-based assignment. Um, so the answer is, is sort of up to you, uh, how, how, uh, how, how do you wanna define it? Apple that I gave was just directly off of ticket count. Um, so maybe we just wanna assign a, a ticket to the agent that has the least number of tickets that are open, that are currently assigned, but I could similarly do it where maybe you have a sizing field on tickets that tells you how, how hard or how complex is that ticket? Or maybe it's the agent that has, uh, the least number of tickets that were opened the least amount of time ago. So you want, you wanna make sure that you're not sending a ticket to somebody who is working on an issue that's been open for a couple of days. Um, or you wanna score it based off level, level of complexity. Uh, the best part of all of this is, uh, because it's all coded, you, you can really build whatever you want and define that concept of full in whatever way makes the most sense for, for your particular business or your particular problem.

Speaker 1: (21:08)
Uh, question from Jesse. Uh, so this is for, for the out of office rep management. Will that integrate directly with Google Calendar? Uh, or is there a service that has to run in between HubSpot and G l? Um, so th this answer is a little nuanced only because it'll, it'll vary dramatically based off of how you actually do it. So let's say you don't have an H R I S system. You don't have a formal P t o requesting policy or, or a system that stores that data and all your reps do, or is add sort of a calendar event. Something we see all the time as folks manage P T O by saying, if you're gonna be out of office, uh, add the event to either your calendar or add something to the P T O shared calendar. And so in that example, you could go straight to, to Google Calendar and just grab who, who has events on that calendar and what email addresses are in Bates.

Speaker 1: (21:54)
Um, or if you're logging often at, like, we use Rippling internally as our H R I S, so rippling actually creates events on Google Calendar. So as opposed to going to Google Calendar, we could go straight to rippling cause that's sort of where the data originally lives. Um, and so whether you're grabbing it, but you don't need an additional service or an additional place, your reps will need to get that event either onto Google Calendar or in your P t O system for that data to exist in a way that you can access it. But the best part of Operations Hub is you, you don't need any middleware or service or really like a P T O integration. What what you need is just an action in that workflow. Um, so I think that you just asked clarification there, which is, will this live in the workflow with a round robin type assignment? Uh, exactly. So basically you'd have a workflow that says, whenever a ticket's created, run this workflow, and that workflow would say, who is out of office? Skip those people, route it either in a round robin fashion or maybe combined with some of those capacity based, uh, examples that we touched on as well.

Speaker 1: (22:55)
Jack, is there one in the chat that you I haven't, I was, I was speaking so I didn't read any of these. If you wanna take one and then I can grab one.

Speaker 2: (23:01)
Yeah, yeah, there was, there was what I saw from Ashley, uh, and she basically just asked, is there a way to build light items on a deal with a custom coded action based on a specific deal property? And, uh, correct me if I'm wrong, Ashley, but my, my kind of understanding of what you're trying to do there is you have a deal in HubSpot and you've got, let's just say a, a dropdown property product one, two, and three, depending on what option I select as a user, something happens in the background and a line item is associated to that, to that deal as product one. Uh, and if that's the case, yes, that can be done. Um, that would just be done using our line items API and our association's api. So you'd simply trigger a, a deal workflow when that property is updated, and then you'd use the custom coded action to find the matching line item and associa it to the, to the deal. Uh, and it's, it works quite well and it avoids people having to go through, um, the entire kind of line item setup process.

Speaker 1: (23:56)
Yep, hun. A hundred percent. We, we do something really similar where we run into customers who either have, uh, lots of line items, but the pa maybe a simple package, right? So maybe you have your, like your premium boat rental package, and that comes with, you know, a captain and clearly I want to go on vacation. I don't know where this example came from, uh, , it comes to the captain and a cooler full of beers and whatever else. Uh, and you can automatically use that workflow to add all those line items to the deal, either based off of a single deal dropdown or maybe a combination of values. Um, something we've seen is to, to sort of build, uh, we're, we're working on kind of like a full C P Q app, uh, cuz we run into this problem a lot, um, but to build almost like a CPQ type experience where maybe you remove rep's ability to add custom line items, uh, and then based off of the deal stage prompts that sort of say, what, what's the package? What are the tiers? Fill out these dropdowns, uh, that are required fields on stage change. And then you could use those fields on stage change to power that workflow that then adds all the line items directly onto the deal, which sort of makes sure you always have the right blend of products for everything you might tackle. So Operations Hub is awesome for those examples where you maybe wanna take a simplified input, but you want to orchestrate a whole bunch of downstream actions off of that input.

Speaker 2: (25:15)
Um, there, there was one other question as well from, um, Alison, if, if it's okay to take that one, uh, Connor, go for it. Um, and it was, can we root live chat conversations in the same way we can root uh, tickets? So right now, no. You, you can't In full transparency, uh, the way typically you'd set up the conversations inbox is that you would assign users to that inbox and then it's, it's a Ryan Robin for these specific conversations. The tickets which are created off the back of a conversation can be rooted dynamically and kind of represent the, the, the lifecycle, if you will, of a support case. Um, but to answer Alison's question specifically, uh, despite us launching, um, or releasing those beta APIs, there isn't a way right now to update the, the owner of a conversation. So we can retrieve the, the, we call them actors in, in the context of a conversation. We can retrieve that data, but we are unable to update ownership yet. What I would say is that this is, uh, uh, a beta API and certainly will be built upon, and it's highly likely in the future, that type of thing will be, will be possible, but for now it's not. And it's a great question.

Speaker 1: (26:21)
The one I saw on here, uh, from an anonymous attendee is we're looking for a way to route our round robin meeting assignments based on specific form criteria, uh, i e potential enterprise criteria. Any thoughts? Uh, so I think you should be able to do that example without any custom code, uh, just using, um, C R M Pro, uh, and Workflow Logic. So you should be able to say, and you may not even need, uh, CRM Pro, depending on whether you need to round robin or just assign agents. So let, let's say you have either, uh, a team, right? So you'd create a team in HubSpot, you'd add a bunch of users to that team, uh, and those are your enterprise AEs. Uh, and so your enterprise AEs, you wanna assign enterprise leads to, uh, you just have a workflow that when a form is submitted, uh, powers that workflow.

Speaker 1: (27:08)
It says, well in the dropdown, what's the company size? Uh, and then route the, uh, those submissions and assign a contact to whichever team or whichever person you sort of define. You want to assign those to. Um, that kind of example you should be able to do without any custom code, uh, using the standard workflow actions, um, without needing Operations hub or to custom code anything. Uh, we, we do that a lot, uh, for all sorts of folks that have marketing forms and sales teams, and everyone has sort of different logic. Um, our, our example is we have a form where people submit and then say, do, do you need app support or are you trying to talk to our services sales team? Uh, and we route those to different folks depending on what that dropdown is. And, and you should be able to do that out-of-the-box. Uh, HubSpot workflows. Um, another one B by the way, guys, we're the thank you is not stop asking questions. Please keep asking questions. Uh, we just wanted to throw up, uh, emails if you guys want to reach out to us directly on any of these, more than, more than happy to as well. Uh, but we'll keep taking these with everybody live. Um, also, uh, there's one in here from Brandon, Jack, I don't know if you've read it, uh, and maybe wanna take it or I can, I can speak to you too,

Speaker 2: (28:18)
But yeah, yeah, sure. So I think Brandon, uh, so consistent talking point with service agents. So where should I, like, where should, uh, yeah, so where should conversations? Is it, where should I have conversations? Just where should I live Conversations?

Speaker 1: (28:33)
I think, I think live is log, like where should I log?

Speaker 2: (28:36)
Oh, sorry. Log conversations or, um, abound calling in by comes up consistently as a reason. They should be on the contact record instead of conversations since something pops up. Can, how does operations expand the power of conversations inbox so that the agent can genuinely just live there? Do we need to have access to the contact room? Yeah, it's a, it's a good question. So, um, so Operations Hub will definitely enhance the features of Service Hub when you think of it on the broader scale. But when it comes to the conversations inbox, we don't really have any way to use Operations Hub to manipulate the, the interface that we are presented with in the conversations inbox or add additional functionality that, you know, otherwise would be available in the conversations inbox. Where I see for now, server or operations hub really helping is for any incoming, uh, or even outgoing messages from the conversations inbox, you could leverage those threads in the context of the wider C r m.

Speaker 2: (29:31)
Um, I know that's not specific to your use case. I, I, I, I get it. Ideally you'd have someone just living in the conversations inbox and not having to jump back and forth between a, a contact or a ticket or a company in the c R m, but, but right now that that's still kind of a, an aspect of what they'd need to do. We're obviously always gonna show the, the, an overview, contact their company past feedback, past, uh, tickets and that type of thing from inside the conversations inbox. Uh, but anything else outside of that would likely wire them having to click into the specific record.

Speaker 1: (30:03)
I saw one in the, uh, in the chat from, uh, Nancy Brik or Breezy, uh, which is, can these work with our homegrown E R P C R M for email subscriptions or with our website admin for passwords? Um, so the answer is if those systems have the ability to either receive webhooks or they have APIs that allow for a web system to interact with them, uh, the answer is yes. Uh, so, so if those tools have those, or maybe your IT team, something we see a lot for, uh, in-house e R P systems is maybe the, the E R P is on site and doesn't have sort of web access, but they've built, whether it's a, a data warehouse or some sort of server that lives on top and extracts data or receives data from that system. And so you'd be able to interact with that, uh, web system as opposed to the E R P directly.

Speaker 1: (30:53)
Um, but I, if there are APIs, um, or if your system can receive web hooks and then interpret them and, and take actions upon receipt, um, you should be able to connect to HubSpot using Operations Hub, using those coded actions. Um, and that's something we do for a lot of different clients that, that we work with is, is that particular type of problem. So I, if you wanna chat directly about the system you're using and what's possible, more than happy to shoot me an email. Um, but the, the answer is if it has APIs, then yes, uh, if it doesn't know with an asterisk on maybe , depending on what else might be, uh, going on, uh, we don't have anything else that I'm seeing in the q and a. Uh, if you do have things that you wanna talk about or ask, please submit them, you'll get to the, the top of the list.

Speaker 1: (31:40)
Um, but other than that, ya Yan talked a bit about some upcoming ones. The next one that's happening is on c m S Hub. Uh, I actually will not be on that one, but Emily from, uh, the Aptitude eight team who is our, our C M S expert, uh, will be on that one in, in my stead. Uh, so I'll miss, I'll miss folks that have been on consistently, uh, but I'll see everybody at, at sort of the full c r m uh, example in a month or so from now as well. Jan just threw the signup link in the chat, so do come to the c m s one. Uh, c m s is awesome. Uh, if you are c m s curious, I, I honestly can't recommend it enough. Uh, the things you can do with C M S Hub are incredible, uh, especially with tie-ins to the rest of, uh, of HubSpot overall. Cool. Uh, I'm not seeing another other q and a thank you everybody so much for, for coming. Uh, feel free to connect with me on LinkedIn. Send me an email if you're working on any of these projects. Um, we're always taking on new customers, we're always hiring. If you're, if you're somebody who, uh, is involved in the hub study ecosystem and you're interested in these types of problems, we'd love to talk to you, uh, as well. Um, and Jack has incredible LinkedIn content, uh, and I highly recommend giving Jack a follow as well.

Speaker 2: (32:52)
Cool. Yeah, I'd love to connect with anybody, uh, who would like to. So, uh, I'd lovely to speak to you all today.

Speaker 3: (32:58)
Yeah, thanks everyone. Uh, and see you in two weeks. Thanks and bye.

Speaker 2: (33:02)
Cheers. Bye-bye.