> For the complete documentation index, see [llms.txt](https://help.mypipeline.co.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.mypipeline.co.in/workflows/marking-calls-as-completed.md).
# Marking Calls as Completed
In this Article you will learn how to create a Call Completed Trigger to ‘Mark Calls’ to your leads as completed when answered. This process will ensure that you can set-up MyPipeline to mark calls correctly that go to voicemail, instead of marking them as completed. Please follow along to learn how to accomplish this!
Part 1:
Step One: Phone Numbers
* Navigate to settings
* Click on Phone Numbers
* Go to your desired phone line and set the ‘Call timeout’ to 20 Seconds. This will take out most instances of a ‘voicemail box’ being processed as an ‘answered call’.
\
\
\
Note: The Call Connect feature is helpful to improve accuracy in call reporting. When Call Connect is toggled on, the receiver must press a key to connect the call. This also will rule out any ‘Voicemail box’ being picked up as an answered call. If you choose to turn this on, make sure to change your whisper message to include direct to the receiver to click a key.
\
Step Two: Workflow
* Navigate to the Automations tab > Workflows
* Create a New, Blank Workflow
* Create a name for the workflow. (Example: Call Status: Completed)
* Add a “Call Status” trigger and add a filter for the call status desired.
* Make use of an “Add Tag” action and mark the contact with the tag that represents each call status of your choice. (Example: completed)
* Publish the workflow and save it.
* Repeat this process for every call status you are wanting to mark leads for, or, make use of the “If/Else” action to create branches based on workflow triggers, and add multiple triggers for each status instead.
\
\
---
# 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://help.mypipeline.co.in/workflows/marking-calls-as-completed.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.