Optimize your outside sales automation in Onboarding forms with airSlate SignNow

How to create outlook signature

client onboarding it's always one of those things it's a very timec consuming process there's tons of opportunity for repeatable process that's there and it also seems to be an area at least for most msps that I've encountered that frequently have steps that just simply get missed because people fail to follow process so to address that we basically started with a form here that allows you to select you the client that you like to work with so in this case I have a test project open for BW iation right now once you select the org you've got various tasks that we have built automation for uh to complete some of those different Auto you know some of those different onboarding steps so let's say for example I wanted to set up my agent deployment processes so I click the action I select the project ticket that's responsible for that particular item and then at this point it's a simple set up the GP Target the location that we want to use and optionally you can create a download link with the fixed uh variable expiration date that you could use so rather than the default 24 hours you could extend that up to 90 days based on this workflow so this is the form side once that is submitted everything dumps into this workflow so what we have is basically we come through we parse the information out of the ticket that we're working we have a subw workflow here to update the project ticket status because there are no built-in actions already to manipulate Project tickets they're on a different endpoint than service tickets so we've got that set up and then we move into a decision tree so all of these are evaluated based on the form input so if you select the onboarding task to enable asset sync then this is the process you're going to run which runs into this subw workflow here so we have just basically a simple subw workflow that at least for us in our environment we uh use direct SQL queries we have error handling built into all of these so at the end of each subw workflow we dump a success State and an error message alternatively if we have an error we set that success state to false and then we out put those things through the subw workflow so once we output those we take the results for that subw workflow and based on the results for those items we determine what our ticket note will be so if we're successful great we're successful we close the ticket if we're not successful we note the specific error message from the action that actually failed so the target for this process won't be me or my team we're putting this into the hands of other Engineers other technicians they're not going to be able to look at these things and immediately know where the problem went or where the problem occurred so the error handling here allows us to know exactly where this step was and at that point we can work to address it so all of these include some of the basic Core Concepts like just simple HTTP calls or API calls others do fullon deployments like cyber CNS in this case this subw worklow is going to reach out to cyber CNS and if the tenant doesn't exist already it's going to create the tenant it's going to grab all the pieces of of information that we need to set that up and deploy it to all of our devices it's going to create service accounts as necessary and document those in it glue and then of course we have all our standard error hand Ling that we capture here so that would be the entire workflow for the Cyber CNS deployment we have similar concepts for you know lion guard and things like that but I think the one that I'm most proud of is Agent deployment so basically with this we identify a domain controller on the network and we find that screen connect session and then we run a Powershell script that actually builds the uh group policy that we would need for agent deployment and allows you to specify the Target location for those agents that is awesome so the way that works I'm sorry that's ous so the way that works is basically a Powershell script template that we have here so we populate everything to unfortunately Microsoft doesn't give us a lot of options to manipulate group policy through Power Powers shell so what we were able to do is create the policy in one place export that policy so we have our backup ID for the policy we exported and then we come down to this area and we B we look through the schedule task XML data and do pattern recognition so we replace the pattern with our new location ID so this is built off of the labtech Powershell modules well and of course clean up after ourselves again output as much as we can so that we have all the error handling in place and we move on to our next task unfortunately I didn't get everything I wanted done in this workflow before this call other things came up so I still have three uh placeholder items that are here one creating individual users uh one setting up the active directory plug in and automate because we always forget to do that and then another that will generate a report out of active directory so we can make recommendations on accounts that may need to be disabled or evaluate password policies and things of that nature so I've started working on the creation for individual user accounts the way this will work is it's going to reach out to our own domain controller and it's going to basically query all of our security group memberships for our technicians it'll cycle through each technician and create their account on the client's domain and based on that person's role associate the uh required permissions and that's pretty much what this does in a nutshell