Capture the email in the thread.

Steps

Keep the ask in one sentence.

A connected assistant can list the leads this flow stores. Lead capture stays a setting on the rule. The setup is on /how-to/connect-your-agent.

• Write why you need the email in the same DM.
• Turn on lead capture for that rule.
• Test with a real email from a second account.
• Watch the 10-lead cap on the free plan.

Make the data request part of a clear offer

Decide what information you need and why before enabling lead capture. An email for sending a requested resource is different from consent to an ongoing newsletter. A phone number for a requested callback is different from blanket marketing permission. State the purpose in the message and avoid collecting extra personal details just because a conversation permits it. DripDM stores captured contact information; it does not replace your privacy notice, retention process, or the permissions required by your later marketing system.

A workflow to try

Create a resource invitation and choose whether the link arrives immediately or after a clearly explained email ask. Test from an independent account using an email you control. Inspect the contact and lead record, not only the visible message. Check the requested resource still opens on mobile. On Business, test the connected Sheets destination separately and verify the expected row before making it part of the live process. Keep the sheet private to the people who need it.

Checks before you change the setup

A comment gives one eligible private reply; asking for an email can earn a recipient response and open the standard conversation window. Do not queue a second message merely because the first ask was sent. On Free, watch the 10-lead allowance alongside contacts and DMs. If a record is missing, distinguish an unmatched trigger, an unrecognized reply, a product cap, and an external destination problem. Exports and external copies also need their own deletion and access handling.

Write down the lead’s purpose and later destination

For each captured field, record why it is needed, where it is stored, who can access it, and what happens next. A callback request should reach the responsible person, while a newsletter request should follow the email system’s subscription process. Test both storage and fulfillment with information you control. Keep sheet access restricted and do not treat deletion from the contact list as proof that prior exports were erased. If a person declines the data ask, avoid coercive repeated messages. A useful lead flow connects a clearly disclosed request to a maintained process, not just an address appearing somewhere in the workspace.