turning dms into sales.
in this region the dm is the checkout. treat it like a sales channel, not an inbox.
reply within the hour, ask one qualifying question, give a price or a range, and propose the next step. most lost enquiries are lost to delay, not to price.
a large share of gulf purchase decisions run through a direct message. someone sees a reel, taps through, asks how much, and buys from whoever answers first with a straight answer. that makes the inbox a revenue channel with a response-time problem, not a customer service function.
the fix is process rather than charm. four moves, in order, and a rota that means somebody is always covering.
the reason this gets neglected is that it belongs to nobody. content sits with marketing, sales sits with sales, and the inbox sits in between — usually with whoever happens to have the password. assigning it explicitly is most of the improvement.
— 01speed beats everything.
the first hour matters more than the wording. an enquiry answered in twenty minutes reaches someone who is still deciding; the same reply at 11am tomorrow reaches someone who has already booked elsewhere. that is the entire mechanism, and it explains most of the gap between accounts with similar content and different revenue.
practically, that means coverage rather than availability. decide who answers in the evening, who answers on friday, and what happens during a shoot day. an auto-reply is acceptable only if it does something useful — states a real response time, or asks the qualifying question so the answer is waiting when a human arrives.
measure it. median first-response time is a number worth putting on the monthly report next to cost per enquiry, because it multiplies everything else you spend. an account with a two-hour median converts materially better than the same account at two days.
and be honest in the auto-reply. "we reply within one working day" is fine if it is true. what damages you is an instant automated message implying immediacy followed by two days of silence.
— 02one qualifying question, not five.
the temptation is to qualify thoroughly before quoting. it costs you the conversation. ask the single question that changes the answer — the city, the date, the size, the quantity — then give a real number.
for services, that question is usually scope or timing. for products, quantity or delivery location. for anything high-ticket, budget expectation, phrased so it does not read as a filter: "so i give you the right option, is this a one-off or a monthly thing?"
the reason for one question is momentum. every exchange loses people, and a five-question intake form delivered by message reads as bureaucracy in a channel people use casually.
write the standard answers down, including the awkward ones — the price objection, the "can you do it cheaper", the request for a discount because a competitor quoted less. a team without agreed answers improvises, and improvised discounting is how margin quietly disappears through the inbox.
— 03give a price, or a range.
"dm for price" cultures train customers to expect a number in the dm. refusing to give one loses the enquiry to whoever will, and the customer often assumes the worst about the price anyway.
if the honest answer is that it depends, give a range with the variable attached: "packages start at x for one location, y if you need two languages". that is a real answer and it filters people who were never in the bracket without insulting anyone.
and put the range somewhere public too. an account with pricing visible gets fewer, better enquiries — which is a smaller inbox and a higher close rate, the opposite of what most brands fear.
the same logic applies to availability and lead times. saying "next available shoot is in three weeks" loses the people who needed it tomorrow and wins credibility with everyone else. vagueness protects nothing; it just moves the disappointment later.
— 04propose the next step, then log it.
never end a message without a next step. a call, a visit, a payment link, a form. an enquiry that ends in "let us know if you have questions" is an enquiry that ends. the next step should be specific and small — a time, a link, a single decision — rather than an invitation to think about it.
then record it somewhere outside the app. name, what they asked, what you quoted, what happens next. dm-based pipeline is invisible to forecasting and disappears when a phone changes hands, and the fix is a spreadsheet at minimum.
finally, review the last fifty conversations once a quarter. the questions people ask are your content plan, the objections are your landing page copy, and the drop-off point is your process problem. it is the cheapest research in the business, and almost nobody does it.
one structural improvement worth making early: move the enquiry to whatsapp if it started on instagram. the reply rate on follow-ups is higher, the thread survives a phone change, and it is where the customer expects to transact anyway. a pre-filled link in your bio and in the auto-reply is the whole implementation.
if this is the problem: turn dms into sales, turning dms into sales in dubai.