> For the complete documentation index, see [llms.txt](https://help.getmobly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.getmobly.com/help-center/the-mobly-app/working-with-a-lead/recording-a-conversation.md).

# Recording a conversation

The Conversation Recorder lets you capture audio of a conversation with a lead and have Mobly transcribe it onto the lead's record automatically. It's an alternative to typing notes mid-conversation — you talk, Mobly listens, the transcript lands on the lead.

## Before you record

> **Tell the person you're recording.** Recording someone without their knowledge or consent is illegal in many places and a bad idea everywhere. The standard practice is to mention it at the start of the conversation: *"I'd like to record this so I can capture the details — is that okay?"* If they say no, take notes the old-fashioned way instead.

## How to record

1. Open the lead record on the mobile app.
2. Tap **Record** in the lead action row. A live audio waveform appears, confirming Mobly is capturing.
3. Have your conversation.
4. Tap **Stop** when you're done.

![Tap to record](/files/aGnmTU2EOkAr9yOCw5Q1)

![Recording in progress with timer](/files/kHPAW6jUj7u5YkPwc0HV)

Mobly processes the audio, transcribes it, and attaches the transcript to the lead's record.

## When recording is most useful

* **Long technical conversations** where typing would slow you down
* **Multi-rep handoff** — record the booth conversation; the AE picking up later can read the full transcript
* **Demos and discovery calls** where you want every detail captured

## When notes are still better

* **Quick scans** with a handshake and a 30-second exchange — typing a one-line note is faster than recording
* **Sensitive conversations** where the lead would prefer not to be recorded
* **Loud or chaotic venues** where the audio quality won't be good enough to transcribe cleanly

## After the recording

The transcript becomes part of the lead's record.

For one-line notes you'd rather type than dictate, use the Notes field — see [Notes vs Description vs Recordings](/help-center/the-mobly-app/working-with-a-lead/notes-vs-description-fields.md).

## Related articles

* [How to capture a lead](/help-center/the-mobly-app/capture-and-enrichment/how-to-capture-a-lead.md)
* [Notes vs Description vs Recordings](/help-center/the-mobly-app/working-with-a-lead/notes-vs-description-fields.md)
* [How to engage leads from the app](/help-center/the-mobly-app/engaging-with-leads/how-to-engage-leads-from-the-app.md)


---

# 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.getmobly.com/help-center/the-mobly-app/working-with-a-lead/recording-a-conversation.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.