> 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/engaging-with-leads/how-to-share-content-from-the-app.md).

# How to share content from the app

{% embed url="<https://getmobly.wistia.com/s/huqll0h2zaucvd1>" %}

Send a product sheet, a case study, or a one-pager to a lead while you're still talking to them. Mobly's Send Content flow uses your phone's email or SMS app to send the file, and logs the activity automatically.

> Files come from your team's Content library. Admins manage that library in the Hub — see [Managing event content](/help-center/the-hub/managing-events/managing-event-content.md).

## Send content to a lead

1. Scan a lead or open an existing lead's details. Tap **Send Content** below the other engagement buttons.
2. Choose how to send: **Email**, **SMS**, or **Other**.
   * If Mobly doesn't have the lead's contact info yet (enrichment hasn't finished), you'll be prompted to enter it. The info you enter is saved to the lead.
   * **Other** uses your phone's native sharing menu — AirDrop, Slack, save to local files, Notes, etc.
3. Pick the file(s) you want to send.
4. **For Email:** the lead's email address is copied to your clipboard automatically. When your email app opens, paste it as the recipient. **For SMS:** the lead's phone number is copied the same way.
5. Send from your phone's email or SMS app and come back to Mobly. You'll be prompted to log the activity. Keep **Include content in activity log** toggled on so the specific files shared are tracked.

   Shared content also appears in the lead's **Activity Log**.

## What syncs to your CRM

When you log the activity, Mobly logs the send to the lead's activity history. This syncs to your CRM's activity log for CRMs that support activity logging — HubSpot, Salesforce, and Zoho. See the [CRM comparison](/help-center/integrations/crm/comparison.md#activity-logging) for the full matrix.

## Send content vs Pulse sequences

Send Content is for **right now** — you've got the lead in front of you and you want them to walk away with something specific. For automated email follow-up that goes out hours or days later, use [Pulse sequences](/help-center/pulse/setting-up-a-pulse-sequence.md).

## Related articles

* [Managing event content](/help-center/the-hub/managing-events/managing-event-content.md) — admin-side library
* [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/engaging-with-leads/how-to-share-content-from-the-app.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.