> 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/outbound/viewing-completed-calls.md).

# Viewing Completed Calls

To view completed outbound calls, click the “Completed” tab on the Outbound Calls table.

\
This interface gives users the option to export completed outbound call data, clear all completed outbound call data, view a list of all completed outbound calls, and search the completed call logs.

## **Completed Calls Table**

![](/files/txg1VFmtTwtwXb09Y15Z)

Applications that have one or more completed outbound calls display information about those calls in the outbound calls table. This table contains the following fields:

1. **Phone Number**: The destination number for the outbound call.
2. **ANI**: The number in your Plum Fuse account the call is sent out as.
3. **Status**: The outcome of the outbound call. Possible values for this field include: “failed” and “completed”.
4. **Queued Timestamp**: The date/time that the outbound call was queued.
5. **Start Timestamp**: The date/time that the outbound call connected.
6. **Duration**: The elapsed time of the outbound call.
7. **Actions**: Shows detailed information for the outbound call by pressing the corresponding button (<img src="/files/-M4u9_-ASfkL5Ec8Hu1p" alt="" data-size="line">).

### **Completed Calls Detailed View**

![](/files/-MbfV9z2cxrMCkrEaY-R)

This detailed view contains the following data:

1. **Phone Number**: The ANI and destination number for the outbound call.
2. **Status**: The outcome of the outbound call. Possible values for this field include: “failed” and “completed”.
3. **Queued Timestamp**: The date/time that the outbound call was queued.
4. **Start Timestamp**: The date/time that the outbound call connected.
5. **Attempts**: The number of attempts for the outbound call.
6. **Duration**: The elapsed time of the outbound call.
7. **Event Table**: Shows detailed events and timestamp for the outbound call.

### **Filtering Options**

Users have several options for filtering the data displayed in the Outbound Calls table. To view calls made during a specific window of time, set the desired date(s)/time(s) with the Calling Window. Only calls made during the chosen time interval will display in the table.\
\
As mentioned above, use the “Search” box to locate a specific phone number. These two filter options can also be used in tandem.

### **Exporting Completed Call Data**

To export all completed call data, click the <img src="/files/-M4u9_0iwiv21jgozrt_" alt="" data-size="line"> button at the top right corner of the table. A CSV file containing the outbound call record will download automatically.

### **Clearing Completed Call Data**

To clear the existing data from the Completed Call table, click the <img src="/files/-M4u9_06jyoXwyiygwa9" alt="" data-size="line"> button in the top right section of the table. This opens a pop-up window asking users to confirm the data deletion. Click <img src="/files/-M4u9_26yDshjCP55ynk" alt="" data-size="line"> to clear the current data.


---

# 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/outbound/viewing-completed-calls.md?ask=<question>&goal=<endgoal>
```

`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.
