Use case
Ask for the phone number in the thread.
The DM asks for a phone number. DripDM stores it on the contact when the reply contains one.
3 minute read
When a phone number fits
Use it for bookings, deliveries, and reminders you already send by SMS or a call.
Say why you need the number in the same message. People reply more often when the reason is plain.
Limits
The free plan stores 10 leads. That cap counts captured contact details. Paid plans do not cap leads.
Ask for a number only when someone needs a callback
For a local service inquiry, send the booking link first or explain that staff will call to discuss availability. Ask for a phone number with its country code and describe the expected purpose of the call. Avoid asking for a number merely because the field exists. Configure the completion text to acknowledge receipt, not to promise that an appointment is confirmed. Test incomplete and valid numbers with the parser before running a paid campaign.
A parsed number is not proof that it belongs to the sender or can receive SMS. Have staff verify details when arranging the callback. DripDM does not provide an SMS sender, call center, or messaging consent manager. Keep requests for promotional text consent distinct from service callbacks and transfer records only to tools your organization is authorized to use. Contact capture cannot resolve an emergency, take payment, or guarantee a time slot.
Prepare a test before asking your audience
Connect an eligible professional Instagram account through Meta login, or a Facebook Page on Pro or above. Select the intended account before editing a rule. Confirm the destination opens on a phone and that the offer matches what the caption promises. Use a second, eligible account for a real trigger test; an editor preview cannot prove provider delivery.
Inspect the public reply, private message, and destination separately. A successful public reply does not prove that the DM was delivered. Keep a record of the test time and inspect activity when something fails. Check permissions and rule scope before repeatedly triggering the same recipient. Disable a stale campaign rather than leaving an expired offer running.
Capacity, permissions, and realistic outcomes
Free includes one account, 1,000 DMs per month, 100 contacts, and 10 captured leads. Pro is $9 per month for three accounts and adds the follow gate, one follow-up nudge, scheduling, product cards, older-comment replay, and Facebook Pages. Growth is $14 for three accounts with 1,000 monthly AI credits. Business is $29 for ten accounts, five seats, and 2,500 AI credits. Paid messaging, contact, and lead quotas are uncapped in the plan configuration; Meta restrictions still apply. Sheets is a Business entitlement and needs provider authorization. Direct Meta Ads audience export is disabled, including on Business.
A comment can qualify for one private reply, subject to Meta eligibility and time limits. It does not itself open a general 24-hour conversation window. The recipient must reply before ordinary follow-up messaging can use that window. A link click or a new follow is not a substitute for an inbound message. Delivery also depends on account permissions, token health, recipient settings, and provider rate limits.
Questions
No. DripDM stores the number. You send SMS from your own tool.
No. Parsing a number does not prove who owns it or that it can receive SMS. Staff should confirm details for a callback.
Check the actual trigger, delivery activity, recipient reply, and destination separately. A scan, queued job, or link tap is not a completed sale. Use your booking or checkout system to confirm the final outcome.