New CRM Features – Project Creation Triggering & Custom Numbering


We’ve introduced two new CRM features: automatic project creation based on sales pipeline stages, and custom project numbering.

Project Creation Triggering Based on Sales Pipeline

You can now automatically trigger the "Create Project" screen when an enquiry reaches a specific stage in your sales pipeline.

  • The trigger activates when an enquiry hits a pipeline stage equal to or greater than your selected trigger percentage.

  • If your pipeline doesn’t include that exact percentage, the system will trigger at the next available higher stage.


Example:
If you choose 40% as the trigger but only have stages at 45%, 60%, and 80%, the trigger will occur at 45%, or whichever higher stage comes next.

Note: Even with the trigger active, you can still exit the project creation popup. No project or job number will be created unless you proceed.


Custom Project Reference & Enquiry Numbering

You can request a custom project numbering or naming format to replace the default LastName_ProjectNumber.

  • This must be set up together with project triggering (it can't be used on its own).

  • You can choose a prefix (letters/numbers) followed by a number format.

Example:
Custom format like RNL-26015, RNL-26016, etc.

 

To Request Setup:

Email the RaveBuild Admin team at help@ravebuild.co.nz with the following:

  • Your chosen sales pipeline trigger percentage (e.g. 40%, 60%)

  • Your preferred custom project numbering format (if applicable), including:

    • Prefix

    • Number format (e.g. 4-digit sequence)


 

This example shows the non-custom set-up. Jasmine_447 is the Rave Default Job Numbering.

 


The Below example shows you the custom Project set-up. RNL26006 and RNL2007, where the project trigger has been met, the project creation box has popped up and then been saved. 



Custom Enquiry Numbering (Optional)

This option allows the Enquiry Reference number to automatically match the newly created Project Reference.

  • When enabled, whatever is entered in the Project Reference field will override and replace the Enquiry Reference.

  • This keeps both project and sales teams aligned with the same reference number.

  • You can still manually add text to the Project Reference later without affecting the feature.

You can choose to use only the project numbering and trigger without syncing the enquiry reference.



In the Below example, we see custom Enquiry is turned on for RNL26007 as both fields match, but it was turned off for RNL26006 as they have different references in each field. 

 

If you enable both the Custom Project Reference and Custom Enquiry Reference options, the system will enforce reference matching by restricting your ability to bypass project creation.

  • When an enquiry reaches the trigger stage in your sales pipeline, the project creation screen will appear.

  • If you choose to exit or click the back button instead of creating the project, the system will automatically move the enquiry back to the previous pipeline stage.

  • This prevents users from skipping the project creation while still keeping the reference numbers aligned.

This safeguard ensures consistent and accurate reference tracking across both your sales and project workflows.