Skip to main content
All CollectionsBest Practices
Best practices for Blueprints on Kula
Best practices for Blueprints on Kula

Follow the guide for optimal outcomes

Kulanaut avatar
Written by Kulanaut
Updated over a year ago

Once you land on the Kula Flows creation screen, you are not met with an empty canvas. You get a number of pre-created Kula Flows under Blueprints.

Clicking on New Kula Flow in the top right corner of the screen, you arrive at this screen:

You can select the ‘Start from Scratch’ option and choose an empty canvas to create a flow from the ground up. However, if you focus on the left navigation, you see pre-saved Blueprints.

What are Blueprints?

Blueprints are pre-created Kula Flows with defined triggers, pre-populated messages, and personalization variables. You can select any Blueprint and get started with the message flow and get to adding candidates, within a couple of clicks.

The Blueprints are clubbed under 2 categories:

  1. Kula Blueprints

  2. Org. Blueprints

Kula Blueprints

These are the pre-created Blueprints saved in your Kula workspace by the Kula team. These Blueprints on top of the highest-performing Kula Flows across our customers and are then worked upon by our in-house industry experts in recruitment and copywriting.

The Kula Blueprints are available from Day 0 of your Kula workspace, hence dramatically decreasing the recruiter ramp-up time and contributing to the ROI from the get-go.

Org Blueprints

The Org Blueprints are created by your colleagues in your Kula workspace. For instance, there is a Kula Flows that is getting the most opens, replies, and interests - you wouldn’t want it to be restricted to a single recruiter. To make that tribal knowledge universal to the entire company, you can save that Kula Flow as an Org Blueprint. Now all the recruiters in your organization have access to that particular Kula Flows. They can use the same Kula Flows, tweak it as per context and role, and repeat the same success for all the open roles.

The Org Blueprints can only be accessed by the members of the same Kula workspace and are not shared with any other Kula account or workspace.

Did this answer your question?