> 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/notes-vs-description-fields.md). # Notes vs Description vs Recordings Mobly gives you three ways to capture context about a lead: **Description**, **Notes**, and **Recordings**. They look similar from a distance but behave differently — and they map to different things in your CRM. Use them with intention and your post-event handoff to sales gets cleaner. ## At a glance | | Description | Notes | Recordings | | ------------------------- | -------------------------------------------------------- | ------------------------------------------------------ | --------------------------------------------------------- | | **How many per lead** | One | Many | Many | | **Capture method** | Type | Type | Tap to record; auto-transcribed | | **Editing** | Overwrites the previous value | Each note is a separate entry | Recording is fixed; transcript is read-only after capture | | **Visibility in the app** | Shared — every rep on the lead sees the same Description | Per-rep — you see only your own notes in the Mobly app | Per-rep — you see only your own recordings in the app | | **Order shown** | Single field | Chronological on the engagement tab | Chronological on the engagement tab, alongside notes | | **Best for** | Static context about the lead | Quick time-stamped notes | Longer or detailed conversations you don't want to type | | **Maps in Salesforce to** | The Lead's Description field | Tasks on the Lead | Not synced to your CRM yet — transcript stays in Mobly | > **Heads up on visibility:** "Per-rep" means *in the Mobly app* — other reps don't see your notes or recordings in their app. But Notes still sync to your CRM as activity records, so people with CRM access can see them there. Write notes you'd be comfortable with your team and your CRM users reading. ## Description — one fixed blurb per lead, shared with the team Each lead has exactly one Description. **Every rep on the lead sees the same Description in the app** — it's the team's shared shorthand on this person. Editing it replaces whatever was there before. Use it for context that stays true about the lead regardless of when you spoke to them. Good examples: * "CMO, but doesn't have buying power — defers to RevOps lead Dave" * "Hot — wants to do a pilot in Q3, has budget allocated" * "Repeat visitor, third event in a row" What Description is **not** good for: a running log of interactions. The next person who edits it will overwrite what's there. ## Notes — a running log of moments, per-rep in the app A lead can have many Notes. They show in chronological order on the engagement tab. **You see only your own notes in the Mobly app** — other reps don't see what you wrote, and you don't see theirs. The CRM is the place where everyone's notes come together: each Note syncs to your CRM as a separate activity record, so anyone with CRM access sees the full picture. Use Notes when you want to capture a specific moment from your own interaction with the lead. Good examples: * "Caught him after the keynote — interested in the workflow demo" * "Booth follow-up, asked about Salesforce integration specifics" * "Phone call 2pm — sent over the pricing one-pager" ### What to know about Notes * **Notes are tied to the lead, not to an event.** If the same lead shows up at two of your events, their notes from both events show in the same chronological list. * **Mobly captures the date when a Note is added.** Per-note timestamps aren't surfaced front-and-center in the UI; if you need the moment captured in the note text, write it in. * **Each Note syncs to your CRM as its own activity record** (a Task in Salesforce). Your reps see them in the CRM activity feed for the lead. ## Recordings — capture the conversation in full When the conversation is too detailed (or too fast-moving) to type, use the **Conversation Recorder.** Tap Record on the lead, talk through what you need to capture, tap Stop, and Mobly transcribes the audio onto the lead automatically. See [Recording a conversation](/help-center/the-mobly-app/working-with-a-lead/recording-a-conversation.md) for the full how-to, including the consent reminder (always tell the person you're recording). ## Which one to use when * "What's the context on this person?" → **Description** * "What did we just talk about? — short" → **Note** * "What did we just talk about? — long, technical, multi-rep handoff" → **Recording** * "Replace the standing summary with a better one" → **Description** If you're not sure between Note and Recording: short and quick → Note. Long and you'd lose detail typing → Recording. ## Related articles * [Recording a conversation](/help-center/the-mobly-app/working-with-a-lead/recording-a-conversation.md) * [How to add a qualifier to a lead](/help-center/the-mobly-app/working-with-a-lead/how-to-add-a-qualifier-to-a-lead.md) * [How to capture a lead](/help-center/the-mobly-app/capture-and-enrichment/how-to-capture-a-lead.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/notes-vs-description-fields.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.