<p><em>Use the process template as it is or adjust and extend to your individual needs.</em></p>

<h2><a name="PostSalesProcessismadeeasywithJira"></a><b>Post-Sales Process is made easy with Jira</b></h2>

<p> ‍</p>

<p>These collections of processes may include <b>sales, marketing, and customer service tasks</b>, and they deliver the obligation your service or product has to the customer. These actions also help to improve and build upon the customer relationship.</p>

<p>Different departments need to follow up on the post-sales process as they provide a series of benefits and uses to each of them. <b>Marketing teams</b> use post-sales services to reduce customer dissatisfaction. They also keep an eye on any complaints to assess their performance and show customer commitment, which can later help build up a company’s positive brand reputation. </p>

<p><b>Product teams</b> will benefit from the post-sales process by learning from consumer data after product evaluation. As it may happen, perceived performance can differ from actual performance, and this can lead to non-satisfaction from customers. Learning from this can lead to making necessary changes to the product at the right time. This can prevent consumers from returning the product, switching to the competition, or complaining about the brand or service. </p>

<h2><a name="WhyCreateaPostSalesProcess%3F"></a><b>Why Create a Post-Sales Process?</b></h2>

<p>Companies use post-sales support as a <b>business strategy</b> as it typically leads to higher <b>customer satisfaction, brand loyalty, word-of-mouth marketing</b>, and even repeat sales. However, the post-sales process usually entails a variety of different actions that will need to be performed by different people, the most common transition being a handoff from sales teams to customer success or customer service teams. </p>

<p>To make this handoff <b>as seamless as possible</b>, and to make sure your clients are getting an excellent customer service experience, you need to carefully plan and execute a post-sales process. Here are some of the most relevant benefits of working with a post-sales predefined process:</p>

<ul>
	<li>You can see the status of all your customers and deals at a glance. This can be managed with Jira.</li>
	<li>Information becomes centralized in a single Flower process.</li>
	<li>Teams can easily keep track of their deals as well as the steps in which they are.</li>
	<li>Follow up on progress and check on the status of each client.</li>
	<li>Ownership becomes visual to everyone involved.</li>
</ul>


<h2><a name="BenefitsofaPostSalesStrategy"></a><b>Benefits of a Post-Sales Strategy</b></h2>

<ul>
	<li>It strengthens your relationship with your customers.</li>
</ul>


<p>The goal of every company out there should be that their customers are satisfied with the service they’ve purchased. An effective post-sales process will ensure that your clients are satisfied with your product and overall experience. What’s more, by providing outstanding customer service, you’ll be guaranteeing that your customers are making the most out of their purchases.</p>

<ul>
	<li>It builds your reputation.</li>
</ul>


<p>When you meet your client’s expectations and needs, you will also be making sure they feel good about their decision of buying your product. By solving their pain points efficiently, you’ll be enhancing their opinion of you. This can lead to recommendations from existing customers which can sometimes even be more influential than other promotion types, such as direct advertising.</p>

<ul>
	<li>It improves your product.</li>
</ul>


<p>By receiving feedback you can understand what needs to change and what needs to improve with your product. </p>

<ul>
	<li>It benefits your entire sales process</li>
</ul>


<p>. How? Because it keeps you centered. An effective post-sales process will allow you to understand where your process is thriving and where it needs improvement. </p>

<h2><a name="StreamlineYourPostSalesProcesswithJiraandFlower"></a><b>Streamline Your Post-Sales Process with Jira and Flower</b></h2>

<p>The <b>goal of a post-sales process</b> is to prevent you from missing any steps and to make sure your handoff from the sales department to the customer service department is as seamless as possible. By implementing a carefully designed process, your customers will receive the attention and the service they need without doubling your efforts.</p>

<p>An effective post-sales process enables you to support your customers to get the most out of your product, improve your overall customer loyalty, and gather relevant feedback that will help you improve your business and your service. After all, it’s harder and costlier to acquire new customers than to keep your existing ones happy, and you can achieve this by following through on <b>product support, customer service, customer feedback, and constant evaluation.</b></p>

<p>We know, many different steps come into place. But this is where <b>project management software such as Jira</b> can help. Because a post-sales process involves multiple steps and teams, it can be difficult to rely on a simple checklist to make sure each step is completed in due time. After all, overlooking a single step could potentially translate to unhappy customers. Luckily, a Flower BPMN process is the go-to solution in Jira when it comes to staying on track with chronological and time-sensitive tasks*.*</p>

<p><b>Sounds complicated? Just a snap with Flower.</b></p>

<p><b>Use this template for free by a little click on the link or a free download in your Flower store.</b></p>

<p>Flower is a Business Process Management S*oftware* that can help you create efficient Processes and launch workflows for your post-sales process. You can create multiple processes for multiple clients, in a way that perfectly fits your company’s needs. But the most important thing is that you won’t ever miss a step because this tool was made for managing large projects and schedules, and you can easily keep track of and update your different tasks with just a few clicks. Additionally, you will be able to share your progress with key team members, managers, and stakeholders, helping you ensure everyone stays in the loop.</p>

<h3><a name="CustomizeyourFlowerBPMNtemplateforJira"></a><b>Customize your Flower BPMN template for Jira</b></h3>

<p>This BPMN sample process is a best practice example as it is lived in many companies. Your customer onboarding process will vary in detail depending on your industry and product portfolio.</p>

<p>With Flower BPMN Modeller you can easily adapt this template to your needs or simply start with this template and make changes later.</p>

Post Sales Process

<h1><a name="CustomeronboardingismadeeasywithJira"></a><b>Customer onboarding is made easy with Jira</b></h1>

<p>Customer onboarding, or client onboarding, is the process of proactively guiding new customers through your product to get them started and stay engaged. It is a series of steps and resources that make it easy for customers to incorporate a new product into their routine.</p>

<p>This Process template is[ |https://flower-bpm.com/templates/sales-index][<ins>part of our Sales Processes collection.</ins>|https://flower-bpm.com/templates/sales-index]</p>

<h3><a name="UsefulCustomerOnboardingTips"></a><b>Useful Customer Onboarding Tips</b></h3>

<p>General customer onboarding best practices to consider:</p>

<ol>
	<li>Know Your Customers</li>
	<li>Clarify Expectation</li>
	<li>Show Them Value</li>
	<li>Keep Communication Flowing</li>
	<li>Create Customer-Centric Goals</li>
	<li>Measure Your Success</li>
</ol>


<p>In addition to best practices, there are a few things that will make your onboarding practice a positive experience for your customers.</p>

<ul>
	<li><b>Make it a personalized experience.</b> Each customer has a unique set of concerns. The more you can tailor your solution to their needs, the easier it will be to achieve wins — and loyal customers.</li>
	<li><b>Break everything down.</b> Disseminate information slowly and selectively. Only ask a new user to accomplish one task at a time and provide clear instructions on how to do it.</li>
	<li><b>Be with your customers every step of the way.</b> Be available to your customers if they get stuck or have trouble. If you can, dedicate several customer services or success representatives to new customers. It will make their onboarding experience better and allow you to see where your process falls short.</li>
	<li><b>Celebrate the small wins.</b> Acknowledge every milestone along the path to customer-defined success to encourage a continued relationship.</li>
</ul>


<h3><a name="Whoisinvolved%3F"></a><b>Who is involved?</b></h3>

<p>The user onboarding process for SaaS-based businesses should be an organization-wide effort. It isn’t the responsibility of just one department or team. The following roles are modeled as swim lanes in BPMN. Flower automatically maps those to your Jira teams and projects.</p>

<ol>
	<li><b>Product Management and Development</b><br/>
No one understands the complexity of your product better than your developer and product management team. They know the ins and outs of your platform and how they can be applied to specific use cases. It's a good strategy to involve them in the onboarding process to gather feedback and make the product even more intuitive and user-friendly.</li>
	<li><b>Customer Success</b><br/>
The responsibilities of a customer onboarding specialist include helping customers with the installation and configuration of the product, minimizing time-to-value for users, and addressing the customer‘s tech concerns.</li>
	<li><b>Customer Support</b><br/>
Customer support supervises the product management and customer success team. They are there to help find any weak link in the onboarding process and help resolve issues as soon as possible. They are also responsible for providing feedback to the product and customer success team to help them further enhance their performance. Nowadays, more and more customers are going the digital onboarding route. You want that process to be as seamless as possible; the <b>Technical Support Team</b> is invaluable in this case.</li>
</ol>


<h3><a name="Thecustomeronboardingprocessstepbystep"></a><b>The customer onboarding process step by step</b></h3>

<h4><a name="Signupprocess"></a><b><em>Sign-up process</em></b></h4>

<p>It’s tempting to think that customer onboarding doesn’t start until a customer has signed up for your product. But we believe the sign-up process is the first step of that journey.</p>

<ul>
	<li><b>Keep your sign-up process as short as possible.</b> You want to make it as easy as possible for people to sign up for your product. How much of the information you ask for is nice-to-have rather than essential? Ask for the information that you need to get the customer set up and using your product, then ask for more information later when it’s needed.</li>
	<li><b>Need a lot of information to sign up? Split it over multiple pages rather than asking for everything on one.</b> Asking for sign-up information across multiple pages correlated with a modest increase in conversion rates. So if you need a lot of information from your customers when they sign up, make it feel like less by splitting it across multiple pages.</li>
	<li><b>Make it easy to sign up with a service they already use, like Jira, Slack or social media.</b> This removes almost all the friction from the sign-up process and means new customers can sign up with a single click, which is a huge benefit.</li>
</ul>


<h4><a name="Welcomeemail"></a><b><em>Welcome email</em></b></h4>

<p>After a new customer signs up, the next step in your onboarding process is to send them a welcome email. This email should direct them straight back to your product so they can start using it and getting value from it.</p>

<h4><a name="CreateaCRMrecordandlinkyourcustomertoJiraservicedesk"></a><b><em>Create a CRM record and link your customer to Jira service desk</em></b></h4>

<p>To be able to invoice the customer later, an entry must be made in the ERP system. In your company, there will also be a lot of other systems such as CRM, Jira Service desk, etc.</p>

<h4><a name="Deliveryourserviceorproduct"></a><b><em>Deliver your service or product</em></b></h4>

<p>Service Delivery is much like it sounds: it’s the delivery of a product or service to a customer.</p>

<h4><a name="Provideyourcustomerwithaproducttour"></a><b><em>Provide your customer with a product tour</em></b></h4>

<p>Share resources that’ll help them get started. This could include a product tour video, links to help center articles, or product FAQs.</p>

<h4><a name="Followupcommunication"></a><b><em>Follow up communication</em></b></h4>

<p>Your onboarding process aims to keep your customers engaged so the process doesn’t end after your customer has logged in that first time.</p>

<p>After your welcome email, you may want to send additional follow-up emails, offering tips and pointers to help your customer make use of your product and prompting them to log back in.</p>

<h4><a name="Ensuringthequalityoftheservice"></a><b><em>Ensuring the quality of the service</em></b></h4>

<p>Customer service quality assurance is the practice of monitoring the quality of customer conversations. Regular conversation reviews help you measure and improve your team’s performance and overall support process. </p>

<h4><a name="Postsales"></a><b><em>Post sales</em></b></h4>

<p>Does the closing of the deal now mean it's over? The answer is no. You need to follow several steps to provide a great experience and ensure your new customer is satisfied with the service. These process activities can include sales, marketing, and customer service tasks and are designed to fulfill your service or product's commitment to the customer. These activities also help to improve and develop customer relationships.</p>

<h3><a name="CustomizeyourFlowerBPMNtemplateforJira"></a><b>Customize your Flower BPMN template for Jira</b></h3>

<p>This BPMN sample process is a best practice example as it is lived in many companies. Your customer onboarding process will vary in detail depending on your industry and product portfolio.</p>

<p>With Flower BPMN Modeller you can easily adapt this template to your needs or simply start with this template and make changes later.</p>

Customer On-boarding



<p><em>Use the process template as it is or adjust and extend to your individual needs.</em></p>

<h2><a name="SaaSsignupflowismadeeasywithJira"></a><b>SaaS sign-up flow is made easy with Jira</b></h2>

<p>SaaS sign-up flow is the first encounter your customer or user has with your digital product, and this is why it has a major impact on the impression of your product built in the customers’ minds. This BPMN process template can easily be adapted to your needs.</p>

<h3><a name="Whoisinvolved%3F"></a><b>Who is involved?</b></h3>

<p>The user onboarding process for SaaS-based businesses should be an organization-wide effort. It isn’t the responsibility of just one department or team. The following roles are modeled as swim lanes in BPMN. Flower automatically maps those to your Jira teams and projects.</p>

<ol>
	<li><b>Product Management and Development</b><br/>
No one understands the complexity of your product better than your developer and product management team. They know the ins and outs of your platform and how they can be applied to specific use cases. It’s a good strategy to involve them in the onboarding process to gather feedback and make the product even more intuitive and user-friendly.</li>
	<li><b>Customer Success</b><br/>
The responsibilities of a customer onboarding specialist include helping customers with the installation and configuration of the product, minimizing time-to-value for users, and addressing the customer‘s tech concerns.</li>
</ol>


<h3><a name="AstepbystepguidethroughtheJiraprocess"></a><b>A step-by-step guide through the Jira process</b></h3>

<ol>
	<li>Your Process starts with a new customer requesting your service. For starting your process automatically you can integrate your interface by using Zapier to trigger the process start every time the specific action occurs. In some cases, the process might be also started by a Sales Representative manually.</li>
	<li>Then the Payment Information will be collected automatically by the integrated Flower form or any other tool you integrated via Zapier before.</li>
	<li>After this step, the SaaS agreement will be sent to the customer. This will be done automatically by a tool integrated via Zapier.</li>
	<li>In the 4th step, the signed SaaS agreement will be collected from the customer.</li>
	<li>In the next step, the Engineering department will spin up dev, stage, and Prod Environments.</li>
	<li>In the next step, an individualized Welcome email will be sent to the customer, including a Production link and training material. This will be done by Zapier Integration.</li>
	<li>Customer Expectations will be set, including required data and next steps.</li>
	<li>In the next step, there has to be decided if Production data is available. Depending on the decision you either have to start the Subprocess “Data load process” or continue with the “Sign-up process”.</li>
	<li>In the next step, the KB materials will be sent to the customer automatically by Zapier Integration.</li>
</ol>


<h3><a name="CustomizeyourFlowerBPMNtemplateforJira"></a><b>Customize your Flower BPMN template for Jira</b></h3>

<p>This BPMN sample process is a best practice example as it is lived in many companies. Your customer onboarding process will vary in detail depending on your industry and product portfolio.</p>

<p>With Flower BPMN Modeller you can easily adapt this template to your needs or simply start with this template and make changes later.</p>

Sales BPMN Process Models

START YOUR FREE FLOWER TRIAL TODAY!