> For the complete documentation index, see [llms.txt](https://messagebird.gitbook.io/applications/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://messagebird.gitbook.io/applications/automation/flows/concepts/triggers/voice-triggers.md).

# Voice triggers

Voice triggers enable the execution of a flow based on call events within the realm of voice interactions.

Within Bird CRM, you can find a set of voice related triggers that can be used to start a flow; these can be call triggers, recordings triggers or transcription triggers. These triggers serve as a starting point to build dynamic interactions and responses in the automated flow, such as routing calls, logging call outcomes, or kicking off follow-up messages once a call or recording is ready.

### Voice event triggers

Run a flow based on a Voice call event:

* **Incoming call received**: Run a flow as soon as a call comes in to one of your Voice numbers. Use this to route the call, such as forwarding it to an agent or an IVR menu.
* **Incoming Call Finished**: Run a flow once an incoming call has ended.
* **Incoming WebRTC call received**: Run a flow when a call comes in through a WebRTC connection, such as a call placed from a web or mobile app rather than the public phone network.
* **Outgoing Call Answered**: Run a flow when a call you've placed is answered by the recipient. Use this to log the outcome of an outbound calling campaign.
* **Outgoing Call Finished**: Run a flow once an outgoing call has ended, regardless of whether it was answered. Use this to trigger follow-up actions, such as sending an SMS if the call went unanswered.

### Call recording triggers

Run a flow based on call recording events:

* **Recording started**: Run a flow as soon as a call recording begins, for example, to log that a call is now being recorded.
* **Recording available**: Run a flow once a call recording has finished processing and is ready to be accessed, such as to save the recording somewhere else or attach it to a customer record.

### Call transcription triggers

Run a flow based on call transcription events:

* **Transcription started**: Run a flow as soon as Bird begins transcribing a call.
* **Transcription available**: Run a flow once a call's transcription is ready, for example, to run the transcript through an [AI flow action](/applications/ai-features/ai/concepts/ai-flow-actions.md) like detect sentiment or detect intent, or to store it alongside the contact's record.

### Set up a voice trigger

1. On the side panel, click **Flows**.
2. Click **New flow** > **Create from scratch**.
3. Under 'Trigger', select **Voice**.
4. Select one of the trigger events described above.
5. Select the Voice channel to use with the trigger.
6. Click **Save**, then place or receive a test call and click **Update test data** to pull in a real event.


---

# 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://messagebird.gitbook.io/applications/automation/flows/concepts/triggers/voice-triggers.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.