> For the complete documentation index, see [llms.txt](https://docs.plumvoice.com/fuse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.plumvoice.com/fuse/tutorial/deployment.md).
# Deployment
## **Deploying An Application**
After designing a call-flow, adjusting settings, and uploading audio prompts, the application is ready to be deployed to a phone number. First, click on the [Deployments](/fuse/deployments.md) link at the top of the screen. Next, click on the yellow 
button. This brings up a form that provides a drop-down menu with all of a user's applications in it. Select the application to be deployed. Next, select the *version* of the application to deploy. The default setting is the most recent revision. Finally, select the phone number(s) to deploy the application to from the provided 'Deploy to' list.
{% hint style="info" %}
**Note**: all Fuse accounts receive one test phone number by default when they are setup.
{% endhint %}
## **Managing Deployments**
At this point, the application appears on the list of active deployments. Users have several management options (
) after deploying an application.
* **Edit** (
) : This allows users to edit the deployment settings. Use this option to pick a different application revision or to update the phone number(s) the application is deployed too. This is helpful if more phone numbers have been added to the user account since the app was initially deployed.
* **Outbound Queue** (
) : Use this to view the outbound queue for the deployed application.
* **Delete** (
) : Use this option to completely delete the application deployment.
It is common to have multiple deployments for the same application. Typically one deployment is for a specific production revision that is deployed to your production phone number. Staging a new revision for QA testing often warrants its own deployment. Finally, a deployment for active development enables users to test the latest application revisions.
## **Testing**
For initial application development, Plum recommends saving a test deployment to the 'latest' revision. This ensures that the most recent version of the application always runs when testers call the test phone numbers. There is no need to edit the deployment settings after each application revision if 'latest' is selected in the deployment form.
After deploying your application, try calling the phone number associated with it. Users should hear a prompt that says “Hello, World!” and then disconnects.
See the [Deployments](/fuse/deployments.md) section for more detailed information.
## Logs
Click on the [Logs](/fuse/logs.md) link at the top of the page to access all available logs for a user's application(s). Fuse automatically generates two different documents for calls to or from an application: detailed logs and call detail records. By default, Fuse retains these documents for 5 days and 1 year, respectively.
Use the detailed logs to discover the precise events that occurred on an individual call. These include end-user input, prompts, branching logic, and debugging webservice integrations.
There should be a log file for the recent test call made to the basic application. Click on the item in the list on the 'Logs' page. This brings up a short log detailing when the call took place. Whenever a caller encounters a prompt in their call the log displays the text of that prompt along with a link to listen to the audio file the caller heard.
Detailed logs and call detail records are helpful when building complex applications because they allow users to easily trace the call-flow and to debug webservice integrations. Fuse lets users download individual call logs and export call detail records for a specific time frame.
Consult the [Logs](/fuse/logs.md) section for more details.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://docs.plumvoice.com/fuse/tutorial/deployment.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.