The Ins and Outs of Integrating Zendesk and NetSuite for Ecommerce – Register

The Ins and Outs of Integrating Zendesk and NetSuite for Ecommerce – Register2020-06-25T18:50:10+00:00
ON DEMAND WEBINAR

The Ins and Outs of Integrating Zendesk and NetSuite for Ecommerce

Watch Now

Deb Morgan Deb Morgan Director of Solution Consulting
CELIGO
Ebru Saglam Ebru Saglam Product Marketing Manager
CELIGO

There’s been a spike in Ecommerce share of global retail in lieu of recent events, businesses need to be prepared at handling the increasing number of customer support requests efficiently. Today, customer service is part of the whole brand experience and it is one of the major factors influencing whether the customer will keep doing business with a brand or not. By integrating Zendesk with NetSuite ERP, support reps can get full visibility into customer orders, RMAs and financials, leading to better omnichannel customer experience.

In this webinar, we look at the challenges of handling the growing number of support requests for Ecommerce businesses and learn how integrating Zendesk and NetSuite can help resolve issues faster and improve the overall customer experience.

Topics include:

  • Typical challenges customer support organizations face
  • How to improve customer experience with integration
  • Common integration use cases for NetSuite and Zendesk
  • Overview of the Zendesk - NetSuite Integration App
  • Q&A

Watch Today!

Full Webinar Transcript
Hello, everyone. Thanks for joining our webinar for ins ad outs for integrating Zendesk and Netsuite for e-commerce. My name’s Ebru and I’m a product marketing manager at Celigo, and I’m here today with Deb Morgan, who is our director of solutions consulting. So I will start the webinar talking about some of the challenges customer service organizations and e-commerce face and talk about why integration is needed and how Celigo helps and then Deb will walk us through the product. So if you have any questions, please submit them through the chat window and we will address them at the end of this session. Also, we will be recording this webinar and the recording will be shared with all of the attendees. So, first of all, Celigo is an iPaas, Integration Platform as a service company. Basically, the platform provides you with all the tools you need to easily connect any application with any other application so that that data is unified across isolated systems and business processes can be automated. And what makes our platform unique is, unlike many of the other integration platforms, ours is built for both business and technical users. So this means if you’re someone without any coding experience, you can still build and manage integrations through our intuitive user interface. So our company, Celigo, has been around for nearly a decade now and we are the larger Netsuite partner. We have more than 3,000 Netsuite customers, and we have a lot of experience with e-commerce integrations. So in addition to Zendesk and Netsuite, Amazon, Shopify, eBay, Walmart, 3PL, are some popular integrations among our customers. And today we’re going to talk about Zendesk, Netsuite integration. So in order to improve customer experience, organizations first need to understand what their customers care about, and I have here some research data and this shows what’s really important to the customers. According to some surveys, 58% of customers say customer service is very important in choice of a brand or loyalty of a brand, so this means great customer service helps with repeat business, then a 76% of customers expect their support reps to know their contact, product service information and history, and 66% of customers say they often have to repeat or re-explain information to the front reps. So this basically tells us customer reps need easy access to customer data so they can quickly resolve customer issues and avoid any frustration at the customer end. And at the end of the day, customer service organizations operate to drive issue resolution while providing great customer experience, and so what are the typical challenges customer service organizations in e-commerce face trying to fulfill these calls. So first one, not having full visibility of customers. Organizations, they often don’t have customer data in one system. For example, while support data is in Zendesk, data around sales orders may be in NetSuite. And then the second one is increasing number of support requests. So if your processes are not scalable and if you’re dependent on manual tasks to order information across systems, this will create a huge backlog with your support cases. And the last, without automation– for example, if you have to contact finance or accounting departments to gather information on an order status, this will just slow down your time to resolution. So basically all of these can lead to frustrated customers. And now let’s take a look at Celigo. So Celigo’s iPaaS, it’s called integrator.io. And our platform, it standardizes how applications are integrated across an organization, and it also creates repeatable processes to move data between different systems. And all the tools you need to build and manage integrations are available on the platform, so it comes with pre-built connectors and templates, and these basically help you to get easily started. And if you look at integration development times it is very fast compared to building code from scratch. And then also with the platform, data delivered between two systems is guaranteed meaning no data is ever lost. And also the platform simplifies monitoring, troubleshooting, and managing of integrations. And then one last thing I would like to mention here is that iPaaS also makes data governance and compliance easier. By having integrations on one platform you can easily control who can access your data on the platform. So on top of these we have our integration apps, and the the Zendesk/NetSuite integration actually comes with an out-of-the-box app here. So these are pre-built, these are fully managed, and these apps all run on the platform. So they have pre-built flows covering all the essential use cases, and then you can easily configure and deploy these without any coding. And because these apps are built on the platform– so all the iPaaS features I just mentioned apply to these. So you can easily customize these and expand these to match your specific business needs and use cases. And now, yeah. So we talked about the challenges support organizations face when there’s no integration, and then we talked Celigo’s iPaaS and integration apps. And now here is how the Zendesk/NetSuite integration app helps. So as seen on the diagram here, the app basically syncs data between Zendesk and NetSuite. So I won’t go really much into detail here because Deb will be talking more about this. This app, it is also accessible inside of the Zendesk user interface, and it provides support reps quick and easy access to their customer data from NetSuite. And so this app, it syncs customers, financials, support tickets, RMAs between the systems and then gives you a complete view of your customers in Zendesk. And then with the app, you can now create RMAs within Zendesk and automatically initiate customer returns in NetSuite. And also, as a result of all of this, you can achieve faster time to resolution and boost your customer experience, and plus you can improve resource planning, reporting, and your processes by syncing time-tracking information into NetSuite. And, of course, in addition to all of this, you can build custom flows to support your specific business use case, so it’s leveraging the iPaaS. And now I’ll be handing it off to Deb so she can walk us through the product. So let’s see here. Okay. Deb, now you’re the presenter. Perfect. Okay. I really appreciate the walk-through. I really just want to take a minute and kind of show you in Zendesk and NetSuite, really kind of recapping some of the flows that she just discussed. And the thing to keep in mind here is that different customers kind of originate transactions and records in either Zendesk or NetSuite. So we’ve really pre-built flows to support all of those different use cases. So for example, maybe your company wants to originate– all of the new customers most of the time originate in NetSuite, then once they’re created, they’re going to come into Zendesk. However, let me just pull up an example of a customer here so we can have that in front of us. I’m going to pull up a company called H-Wave. So we’re going to recap this integrator.io at the end, but I want to start out by just talking about the most common flows, right? So when a customer’s created in NetSuite, it’s going to come into Zendesk and it’s going to create one of a few things. In NetSuite, if it is a type equals company, like if it’s a customer with a company, it’s going to create a Zendesk organization. However, if it’s a type equals individual, right? It’s not a company. It’s a person, then we’re going to create a Zendesk user, okay? Now, if you are a company, in addition to creating your Zendesk customer or org, it’s also going to create new users, and these would be contacts that you have in NetSuite underneath that company. So out of the box, we can initiate these things from NetSuite, or if you need to, we have flows that could initiate any of this from Zendesk. So it really depends on your use case. We rarely see customers that want to originate a new customer from Zendesk, however, we do have a flow for that. But one thing that’s really common is if you take a look at– let’s just open Jennifer Ross here. You’re going to notice that, maybe with your customer support team, they’re actually on the phone with them and they’re using Zendesk. Maybe she’s given them a new email or a phone number if you had like, we have a flow that would allow your Zendesk team to edit this and sync that back over to NetSuite to update either the customer record or the contact records. And so we do have pre-built flows for that really depends on your use case. And I’m actually on the org and the contact record. But this applies to any of these that I’m showing you here. As you can see here, any fields that you and your company use, even if they’re standard fields, or if they’re custom fields, you can sync there’s no limit to the number of fields. We’ve already pre-mapped all of the required fields. I’ll show you that in a minute when we get into integrator IO, so out of the box I think ever mentioned, the real benefit here is that we’ve already pre-built all of these most common flows, and we even pre-mapped all of the required fields. So what are the minimum fields that NetSuite requires to even sync something between the two system so are what are the minimum fields that Zendesk requires? So we’ve already done that for all the standard fields. And we’ll show you that here in just a minute. So just to recap here, we’re going to be sinking organizations and users between NetSuite customer records and contact records. In addition to that, one of the things that’s really, really that kind of the meaty part of the Zendesk app is really sinking tickets. So this is also again, where we have multiple use cases, we have flows to support both. You can originate a ticket if your team is originating this as a support ticket here for each way. This was originated in Zendesk. So meaning that the ticket was created. And then we think that over into NetSuite as a case, if you don’t want to bring your cases over, but you just want to bring your customers over, that’s fine too. You can turn those flows off really, there’s a really flexible one to meet your needs. And this example, we originated this ticket from Zendesk. And then we push that over to NetSuite as a case, however, we do have flows that if for some reason your process where the case originates in NetSuite, then we can push that over to Zendesk as a ticket. And much like with the customers and contacts, these are actually bidirectional for not only adds but also for edits. So when we see edits on tickets that were already in place, usually that means that maybe custom fields are being updated as people are being assigned to tickets, the status is, in addition to that, actually comments that are being made internally, right? We have the difference between a public and an internal comment. And we can bring those into NetSuite. Let’s go into NetSuite, actually. And just take a quick look at this particular customer’s support ticket. Really quickly. So then we can kind of show you what that looks like on the NetSuite side. Maybe with us, we’re working in sandboxes. So they’re a little slow here. Perfect. And if I come down under this customer and I look for all their support tickets, I’m going to look for that case. Here it is right here. So what’s the legal did in this example, this ticket, as I mentioned, originated in Zendesk. And then we came into NetSuite, and we created a case. Now, keep in mind, your company might want to track it by product, or by modules or serial numbers, really any field information that you have on your Zendesk ticket, we can sync over. So just keep that in mind. And what I was going to talk about here is in addition to all the header part of your ticket, this is what’s really important. And we see variation as well. In this example, these were comments, internal comments that were made from Jennifer Ross, and she’s the one that kind of populated this. And so we’ve come in and we’ve pushed those into NetSuite. So the person using NetSuite now has that’s a mirror image of the ticket. So whether you’re sitting and using Zendesk or NetSuite, you both have visibility to the same information. You can even use NetSuite to trigger automatic emails, things like that. It’s really up to you. But we’re bringing that information in. Now this one is one where I happened to be in NetSuite and I went into this case, and I actually sent an internal comment, and that syncs back over into Zendesk. So you’ll see my comment here at the top. So it’s really designed to meet whatever kind of needs you have. But this is showing you a nice bi-directional sync between internal or either public comments. This was a public comment that came from Jennifer, those first three that I showed you, and then my own internal comment coming from NetSuite asking the team for an update. Okay. So to summarize here, we’ve talked about we out of the box can sync between customers and orders. We’re going to sync all the tickets in cases between NetSuite and Zendesk if you’d like. And then, the next thing I want to show you though, it’s really, really essential, especially I think, in the e-commerce space, but it’s really helpful to just about any customer that’s using this for our customer-facing calls. Let’s say that this customer is calling in about a particular sales order. You can come in– notice if I’m at the– I want you to pay attention here to the right-hand side. And I’m going to cover those. This is whether you’re at the org level, or whether you are at the contact level or the user level, or you’re at the ticket level. No matter which level you’re at, you’re always going to be able to see this information. And the first thing that you’re going to see is NetSuite details. This is really high-level financial information. Maybe your team doesn’t need this. If so you can turn this off. But really, it’s designed to let you know if you’re on the phone with the customer gives you a chance to see if they’re really past due. This customer doesn’t have a balance due. How much they still have sitting out on unbilled sales orders, are they on credit hold and are they overdue. So it’s really just meant to give your team visibility into kind of the financial health of the account if they’re on the phone with the customer. Okay? And that’s pulling from the NetSuite customer records financial tab. That’s where all of that information is coming from. But most importantly, you’re usually wanting to see orders. We can bring in the 30 most recent orders and the 30 most recent RMAs and we’re going to cover RMAs in a little bit more detail here. Notice when I clicked on orders, you can see that this particular customer has only had four sales orders. So they placed four orders with us. The most recent was this particular sales order. Now, notice that if I am actually depending on your process, if you are creating RMAs from NetSuite, we’re going to push them over and still give you visibility. In this case, they have four RMAs. But now we have a new feature that allows you to come in here, click on a sales order. Now this one already has an RMA. You’ll see if there’s an RMA associated with an order. It’s going to nest right underneath it. If you did not– let’s say this one didn’t have an RMA and you wanted it– you would be able to click here. It would show you exactly what was on the order. It would allow you to give it an RMA number and decide if they’re doing a full RMA or if there’s only a certain quantity. If there’s multiple lines on an order, you’ll see the exact mirror of the sales order. So you kind of define what you would like to have on your sales order. Okay? So I just want to go back here for a second and come back here. So to recap is you’re able to see all the last orders, all the most recent orders of a customer, any RMAs that originated in NetSuite, or if you’ve originated an RMA from Zendesk, you’re also going to get a status that shows that was pushed over to NetSuite and it’s been completed. So what we did was we went into that sales order– and we find that sales order for us really quickly so I can kind of show you what that looks like. This was the original sales order and you can see the related records here. There was an actual return authorization. So this right here was actually created using the Zendesk app. One other really nice thing is really about how to use search. So if I were to just search for the sales order if a customer calls in and says, “I’d like to talk to you about my order,” you can come in here and you can search. So I can come in here and I can go back to my sales orders, and I can come in here to my financials. Perfect. And I’m going to search for my sales order. So I’m going to come right here, search for that order, brings it right up. So it’s really frequent that a customer is calling in and giving the customer support person an order number. So this feature allows you to go in and search for their order easily. Okay. So really, this is designed to really kind of streamline all the most common flows. We’re going to come into Integrator IO now and show how we make all of that happen, and show you all the different options. And one of the things I want to point out, I’m going to jump right now into Integrator IO. And as Avery mentioned, this is really an IPaaS platform. I’m actually managing Salesforce and my banking, along with a number of other things on my own single login here. But today, we’re going to jump into Zendesk, NetSuite. This is pre-built, it’s pre-configured for you, but it can still allow you to add as many custom fields as you like. And let’s say that you have a unique custom object. I don’t know if all of you are aware of it. But in the last years, Zendesk has actually started allowing certain additions of Zendesk to create their own custom objects. So if you did that, and you needed to sync that information between, say, NetSuite and Zendesk, you would be able to come in and use integrator IO to create another custom flow to make that happen. So it really allows you to scale as your business changes and even as these products, Zendesk and NetSuite, add additional functionality. So to recap what we’ve talked about here is really this is sinking, you’ll notice under the organization sync, this is for NetSuite customer type equals company. This is allowing you when a new customer is added in NetSuite, we can sync that over as a Zendesk org and also if you’re doing any updates. Ao if your accounting team is making changes to that record, it’s going to sync over and keep those records syncing. Now, again, I mentioned earlier, it’s a little unusual for a Zendesk agent to come in here and create a brand new NetSuite customer. But we do have a flow for that. So if that is something that you require, we could certainly do that. The most common is that you’re going to be on the phone with a customer, they give you a new information so that you could update the record and will sync that over to NetSuite. And that’s simply if you really allow your team to do that. The user’s sync, again, is if you’re a type equals individual, and that’s great for a– instead of a company, we’re going to create a Zendesk user, same kind of process. It’s going to be ads or updates. And if your team in Zendesk is on the phone, gets new information, they can also update that. So these are all cool bi-directional syncs for customers, contacts, or end-users. We do have another really unique flow here. I don’t know if this would be needed. This is really good if you have a lot of Zendesk agents that are using Zendesk. When you onboard a new NetSuite employee, they have the ability to check a box to tell them that it needs a Zendesk agent. And if they do that, we’re able to go in and create them as a Zendesk agent for you. So we can automate that process. And let’s say that the employee leaves the company at some point. So when that employee is off boarded, then they would go in and update that to remove Zendesk agent access, they would deactivate their access. So this is another one of the flows that we’ve built to streamline kind of the process and kind of avoid all the menu effort or maybe to forget to deactivate somebody when they’ve left their company. I’m going to come back to financials, but first, I want to just cover briefly ticketing. We’ve talked about making sure if you originated a ticket from NetSuite, we can bring that NetSuite case to Zendesk ticket. We can also push updates if they’re coming from NetSuite. And then if you’re originating your tickets from Zendesk, we can also support that. So, fully bidirectional for ads or updates. This one is if you’re sending messages directly from NetSuite and you want to update it, where I added my own comment asking for an update on that one ticket. One thing we did not talk about, I just realized, is we do offer a time tracking flow. So if I come back into Zendesk, you’re going to see here that if you have time tracking enabled on your system, then when you go in – and let’s say that the rep is entering time on a ticket – they can go in and we would sync that over. So here’s your little time tracker in Zendesk. So if they want to push that over – it can either be just for tracking time or it can be used for billing time – you can sync that over. And that’s going to actually come in– let me just show you really quickly where that is going to come in on the NetSuite side. So under a case for time, this is where that information’s going to be logged. So you can create a service item in NetSuite. You would use that to define whether it’s going to be billable. And then you can set up all the different reporting segments. So department location. So just realized I had forgot to mention that. So we do have a flow here for syncing time from Zendesk. The last set of flow– so again, bidirectional tickets syncs and time tracking. And then last but not least here, we’re syncing all the financials. So we’re bringing top-level financials like the financial health snapshot of that customer. So you can know if they’re past due when you’re on the phone with them. We’re also syncing all of the sales of her history over to you, whether you’re at the user level or the ticket level. And if you’ve created RMAs in NetSuite, we’re going to sync that over as I mentioned. And then the newest flow that we’ve added is where you can actually create an RMA in the system as well and sync that over to NetSuite automatically. This is a really nice one. This one’s really popular. So really, this is really just talking about the high-level financials here. And then again, we can also bring over some of the customer top-level financials. So one last thing I want to point out while we’re on this screen is really– it’s going to apply, no matter which application you’re using or whether you’ve built custom flows on integrator.io. Really, the goal is to make it super, super simple. You’re going to notice here in this OrgSync, if I were to click on this, you’re going to see for all of these flows we’ve already pre-mapped all of the required fields. So you’re never starting from scratch. They’re always all kind of done for you. Just add your custom fields or any additional fields you might want to do. Also, if you’re doing this, you can assign a group of users. I don’t recommend you have this many with managers and admin access, but this is a shared environment. But this is a really important group of because all of our integration apps and even your flows that you built on io have some built-in notifications. These users will be notified if Zendesk goes down via email. And then NetSuite goes down. So they don’t have to be worried about it. It’s just more of an FYI. When Celigo senses that that connection’s been reestablished, anything that was in the queue is going to come over. So this is more just to let you know that things are not moving between the two systems. Also, let’s say you went in and you try to add a field mapping. And you made it mandatory on say NetSuite, but you forgot to make it a mandatory field on Zendesk. So the first time someone tried to sing something over and it didn’t have that required field. So let’s say you got an error. First of all, the user would get a notice. But let’s say they didn’t pay attention to that. These same users will get a very specific email telling you exactly which flow has failed. You would then be able to come into your dashboard and you’d be able to take a look. And it would say big red failed and tell you the number of records impacted. It allows you to come in here in this particular case, someone tried to create an RMA, but they forgot to put the total dollar amount for the RMA. So the user would have got a notice. They went in and they modified it and they saved it. So you’ll see now that that’s been updated to completed, but it memorializes it in a different color, so you’ll know that at some point, something needed to be adjusted on that. And then it moves this over to the resolve column. That’s super simple. You don’t need to be babysitting any of your dashboard that gives you confidence that you’re going to get notified if something needs your attention. One other thing is let’s say that someone did make a change and you’re worried that that might have caused a flow to fail. You’re always able to come into this audit log and see which user made changes. Did they add a field? Which flow did they change? If it’s a new field, what’s the old value, what’s the new value? So it really does make it easy for you to try to troubleshoot, especially if you’ve made some changes to your integration. And really, that’s just kind of the key things that I really wanted to touch on today. I’m hoping that this gives you a really good overview of how Selegoz platform works and all of the prebuilt integrations that we’ve built for you out of the box for Zendesk. And the last thing I want to point out is we would actually install a managed bundle in NetSuite and in Zendesk. And that’s a really good thing also because that means that when NetSuite or Zendesk are doing updates, our teams have already done beta testing to ensure that our connectors are not impacted by any of the changes that they’re pushing. So, Eber, I wanted to pause for a minute and see if there were any questions. There are no questions so far. So if you have any questions, please type them in the chat window. Okay. So let’s give folks a bit more time and we can take questions at the end of the session. Okay. Perfect. Okay, great. So I think the one other thing that I just wanted to point out is that I went in just really quickly out of the custom field. It’s super easy to do that. You could see I added them on that sweet time. So you would just go in and modify your film mapping for that particular record. You would just go in and add it. And so I mean, I think the message here is just super easy to use, prebuilt, out of the box, but still has a lot of flexibility in terms of the adding additional flats. So actually we have two questions now. So the first one is if a user orders, would the case record automatically associate with the sales order? I’m sorry. Can you repeat that one more time? I just want to make sure I understood that. Yes. If a user orders, would the case record automatically associate with the sales order? The only way that would happen is, let’s say in this particular case, is if they have indicated on the case itself, the actual order number. So if they did that, then it would reference the sales order. If they’re originating the case in Zendesk, as long as they’ve indicated on the order itself which sales order it’s related to then it would do that, for sure. That’s a bill mapping exercise. Okay. Another question is, how would I be able to begin use of the bundle? Okay. So the way it would work is let’s say that after you’ve purchased the subscription then our team is actually really nice, I wish I could show you on this, but actually, you go through a really quick wizard. You could also do a group implementation where you actually get on the phone and they walk you through how to enable each of these flows, some of them you might not be using right – this is built to support a number of different use cases – but then it would be a wizard. It’s like a six-step wizard, it would walk you through first establishing your credentials to the two endpoints for Zendesk in NetSuite, and then it actually does the bundle install for you and the wizard does that and it takes just a matter of minutes to go through the wizard steps. And so then, once you’ve done that then this is what’s going to enable all of these to display in your Zendesk, and by the way, I know the question hasn’t come up yet, but I wanted to point out since Zendesk doesn’t have an object or record for us to display not only this information but the orders, Celigo has written a custom app that allows us– a Zendesk app that allows us to display all of this information. And that’s all just a display, it’s using a NetSuite safe search, it goes in, looks for those orders and it then puts it right here from a display perspective. So just want to point that out that you don’t have to go in and create any custom fields that are pertained to the integration at all, it’s all part of the manage package and bundle. So we have, actually, three more questions here. Excellent. Ask them. So one of them is, what happens when customers are merged in NetSuite? How is that resolved in Zendesk? Okay, great. So I’ll show you, on any record that we’re doing, if you click here you’re going to see a NetSuite ID, for example, okay? And even on a user, you’re going to see a NetSuite ID. So these are one to one relationships. There we go, right there. If you have decided to merge a customer then we’re going to need– we’re going to need to know. It’s going to update when you do the merge, it’s going to change the internal ID on the NetSuite side. So if I come into NetSuite and I go into HWAY, for example, – Let’s just go back to this customer – then when you merge that, the NetSuite internal ID will change. So that’s how we have that. Did I answer your question? I hope I did. If I didn’t, let me know. Okay. So another question is, when syncing the sales order in Zendesk, are we able to add additional columns to the line items? No. Today, I think what you’re asking is, can I add additional columns here? So currently that is not possible only because there is a customs app that is written to support bringing this information in. So if I modified it for one customer it would suddenly start displaying all of those columns for another customer. In the future here, we’ll probably get rid of having to write an app now that Zendesk is now allowing some customers to create a custom object like an order object, but for now, unfortunately, we can’t support adding additional columns. However, I would like to add that we’ve had two customers recently, that I can remember, in the last month where we have a number of companies that we work with that writes custom Zendesk apps and if you write your own app to display anything that you want, either custom at the header level or the line level, then Celigo can use those and populate that. We just don’t do all the custom apps. Okay. Another question is where do you purchase subscription? And I can take this one. So you can simply– yes, you can simply go to our website and you’ll see there a contact form. So if you give us your information, our sales reps can get in touch with you. Perfect. Okay, there is actually a follow-up on the merge question. So if two customers are merge in one– sorry, if two customers are merged into one in NetSuite, are those customers merged in Zendesk? They would be merging because then your NetSuite ID– so I think that’s what you’re talking about. So in this example here, you would need to do a typical Zendesk merge. So in this example, H-Wave, if it used to be two customers and now it’s all merging under H-Wave, then in NetSuite, when you do the merge, it is going to do that for you. I think we probably see two use cases. Some people only want to see future sales orders from the merge, but they want to maintain the history of the pre-merge. So we usually kind of work through both of those use cases with you. And one other thing, too, to keep in mind is we have a really amazing support team. If you ever want to try to do something and you’re not clear about it, you can come into your integrator.io license. And first, you can even search our knowledge base to look to see if someone else has already done that, and merging is really common in there. And can you do me a favor, Ebru? Can you capture that person’s information? And we can email them some additional insight on how to merge accounts through Zendesk. I can send that to them. I can go in and download it. Sure. Yes. But then you would simply click submit a ticket, and then you can submit your question. So especially if you’re trying to make a big change and you’re just curious if you’re going about it right, you can always submit a ticket. We have a really great one. That’s answer your question, hopefully. But I will send you some additional insight. Okay. Great. So I guess that was it from the question side. Now, I will take back presenter mode. Perfect. Okay. Yeah, thank you, Deb, for the demonstration. That was great. So yeah, I just want to mention that in addition to our Zendesk integration app, on our platform, we actually support many different aspects of your business. So whether it is supporting integration with e-commerce marketplaces, trading partners, or point-of-sale systems and e-commerce storefronts, different ERPs, so basically anything you see here, we have a solution. So you can either leverage our iPaaS to build custom integrations to match your specific business use cases and for some of these, as I mentioned before, we have out-of-the-box integration apps available. So if you’re interested, you can find more about these on our website. And also, you can email us with any questions. And actually, here, you can go on our website at celigo.com and check out– like if you want to try the product for free, you can get a free flow to start experimenting and using our integration solution, or you can go to our marketplace and search for our existing templates and integration apps. And like I mentioned before, for any questions, simply email us at [email protected] or contact us through our website, through the contact forms. And we are very interested in hearing about your integration needs, the challenges you face, and our consultants would be very happy to discuss with you. So yeah, just get in touch with us, and basically, that’s it for today’s webinar. So thank you very much everyone for attending and we will share with you the recording after this. Have a nice day. Bye. Thank you, Deb. My pleasure. Thanks everyone