# Launching project ## Creating Project History Regularly creating project versions is crucial for tracking significant updates, informing colleagues, and ensuring functional backups in case of issues or errors Each project version can be individually trained and deployed, allowing for detailed version management. For more detailed information, refer to the [Project Version History](broken://pages/NbR5bCBZnYtNWpMVaK3n) page.

Saving project version - example

To create a new project version, follow these steps: 1. **Create a Project Version:** Generate a new version of your project by providing a brief description and outlining new improvements that are not intended for production. 2. **Utilize Older Trained Versions:** Your previously trained and deployed versions can continue operating while you're working on creating newer versions. This ensures continuity even during the development phase. 3. **Revert if Necessary:** If any issues arise, you always have the option to revert back to a previous version. Detailed instructions for this process are available on the [Project Version History](broken://pages/NbR5bCBZnYtNWpMVaK3n) page.
Consistent creation of project versions helps in maintaining a clear track record of changes, allows for ongoing development, and ensures the ability to revert to stable versions in case of unforeseen complications. *** ## Import / Export project Each project version can be individually trained and deployed, allowing for detailed version management. For more detailed information, refer to the [Project Version History](broken://pages/NbR5bCBZnYtNWpMVaK3n) page.

Saving project version - example

To create a new project version, follow these steps: 1. **Create a Project Version:** Generate a new version of your project by providing a brief description and outlining new improvements that are not intended for production. 2. **Utilize Older Trained Versions:** Your previously trained and deployed versions can continue operating while you're working on creating newer versions. This ensures continuity even during the development phase. 3. **Revert if Necessary:** If any issues arise, you always have the option to revert back to a previous version. Detailed instructions for this process are available on the [Project Version History](broken://pages/NbR5bCBZnYtNWpMVaK3n) page.
Consistent creation of project versions helps in maintaining a clear track record of changes, allows for ongoing development, and ensures the ability to revert to stable versions in case of unforeseen complications. *** ## Training and testing project Training your project version is an essential step to thoroughly test the Conversation Flow before deployment, ensuring optimal utilization. Initially, we made a minor enhancement in the '[Answer' node](/digital-agent/conversation-flow/nodes-explained/answer-node.md), particularly with the intents **"Yes"** and **"No"** by incorporating chat button options. Before initiating training, we added chat buttons specifically tailored for these intentions. Our goal was to emphasize the **"Yes"** option by highlighting it as our primary button choice. The training process is straightforward. After verifying the flow logic, simply click the **"Train the button"** option. Upon successful completion of training, a chatbot interaction bubble will appear in the bottom right panel. Feel free to engage in a conversation with your newly created chatbot.

Training project + answer node improvement

Step-by-step for a small improvement 1. Access the example project and navigate to the 'Answer' node. 2. Identify the intent that you wish to transform into a button format. 3. Modify the intent and select the checkbox labeled "Use as button." 4. Optionally, configure your button settings according to your preferences. 5. Ensure to save changes in both button configuration and intent configurations.
{% hint style="info" %} Utilizing primary and secondary buttons can effectively guide users through the desired flow within the conversation, enhancing the overall user experience. {% endhint %} *** Deploying project We're here to guide you through the deployment process. If you need assistance, please refer to the contact information provided.
Assigning a new phone number to your assets is an essential part of this process.
Step-by-step of project deployment 1. E**nsure Conversation Flow Training:** Verify that your conversation flow is adequately trained before initiating deployment. 2. **Initiate Deployment:** Click on the "Deploy Version" option within your project. 3. **Assign a Phone Number:** Associate the created phone number with your deployment. 4. **Configuration Options:** Customize your deployment by specifying: * A friendly name for your deployment number. * Voice settings, including temperature, technology, speed, and supported languages. * Preferences for call recordings and background music (upload custom tracks in assets). * Whitelisting or blacklisting specific numbers as needed. 5. **Confirm Deployment:** Click "Confirm" to execute and deploy your project. 6. **Test Your Conversation Flow:** Run a test call to ensure the effectiveness of your deployed Conversation Flow.
{% hint style="info" %} Ensure your project is trained and has an assigned phone number in assets before deployment. You can refer to our step-by-step guide in the "Create First Project" chapter for assistance. {% endhint %} Minor adjustments may be required in the project to successfully deploy your voicebot. *** ## Deploying project Deploying your project into production is a pivotal step in enhancing customer satisfaction through its use. We're here to guide you through the deployment process. If you need assistance, please refer to the contact information provided.
Assigning a new phone number to your assets is an essential part of this process.
Step-by-step of project deployment 1. E**nsure Conversation Flow Training:** Verify that your conversation flow is adequately trained before initiating deployment. 2. **Initiate Deployment:** Click on the "Deploy Version" option within your project. 3. **Assign a Phone Number:** Associate the created phone number with your deployment. 4. **Configuration Options:** Customize your deployment by specifying: * A friendly name for your deployment number. * Voice settings, including temperature, technology, speed, and supported languages. * Preferences for call recordings and background music (upload custom tracks in assets). * Whitelisting or blacklisting specific numbers as needed. 5. **Confirm Deployment:** Click "Confirm" to execute and deploy your project. 6. **Test Your Conversation Flow:** Run a test call to ensure the effectiveness of your deployed Conversation Flow.
{% hint style="info" %} Ensure your project is trained and has an assigned phone number in assets before deployment. You can refer to our step-by-step guide in the "Create First Project" chapter for assistance. {% endhint %} Minor adjustments may be required in the project to successfully deploy your voicebot. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.borndigital.ai/digital-agent/conversation-flow/launching-project.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.