Playbooks · 5 min read
We Do Not Optimize Anything for Mobile. Your Replies Do.
Let us get the disappointing part out of the way. There is no mobile optimisation feature in this product. Nothing detects a device, nothing formats differently for a small screen, nothing adapts a reply to a phone. We do not do it.
That is not a gap waiting to be filled. It is a category error in the question. Instagram is already a phone app, the person reading your reply is already holding a phone, and there is no second version of the experience to optimise against.
What is real, and what this post is actually about, is narrower and more useful: everything your automation sends is read one-handed, in a notification, often while somebody is doing something else. That does change how you write it. Three places specifically.
The first line is the whole message, most of the time
A DM arrives as a notification before it arrives as a conversation. Plenty of people read the preview, decide, and never open the thread.
Which means the sentence you put first is doing almost all the work, and the sentence most people put first is throat-clearing. "Hi! Thanks so much for reaching out to us, we really appreciate you taking the time to comment on our post."
Nobody has learned anything. Compare:
Reads badly in a preview
Reads as an answer
Lead with the answer. Put the ask at the end and make it one ask. If the person never opens the thread, they still got what they came for, which is a better outcome than a polite message they ignored.
Write every automated reply as though it will only ever be read as a notification. Most of the time you will be right, and when you are wrong it still reads well.
Length, and the thing that happens to paragraphs
A reply that looks compact in a builder on a laptop is four scrolls on a phone. There is no preview here that shows you otherwise, so the discipline is yours.
Two habits that fix nearly all of it. One idea per message — if a reply is covering price, sizes, shipping and returns, it is a page, and a page in a DM gets skimmed to nothing. And no wall paragraphs: short lines with breaks between them survive a small screen in a way that a block of prose does not.
The thing to resist is compensating by splitting one answer across several messages. That reads as a bot performing enthusiasm, and it burns the goodwill you were trying to buy.
Links behave differently in a DM, and that is where flows die
A link you send in a DM gets opened inside Instagram's in-app browser, on a phone, by somebody who was watching reels ninety seconds ago. That is the least patient browsing context that exists.
So the page on the other end matters more than the message. A landing page that needs a login, a PDF that downloads instead of displaying, a form with nine fields, a checkout that wants an address before it shows a price — each of those is a place the conversation ends. You cannot fix any of it from inside an automation, which is precisely why it is worth knowing that this is where the loss happens rather than assuming the reply was the problem.
The practical rule: send the shortest possible path to the thing you promised. If the promise was a price list, link the price list, not the homepage.
Trigger words are typed with two thumbs
This is the one that actually costs people conversations, and it is entirely in your control.
Whatever word you put in your caption has to be typed on a phone keyboard, usually with autocorrect fighting back, often in a script the keyboard transliterates. Long words get mistyped. Multi-word phrases get half-typed. Anything with punctuation in it gets typed without the punctuation.
Matching folds case and punctuation, so Price? and price are the same thing, and it folds Latin accents too. That covers most Roman-script keywords and it is the reason short words work.
It does not fold Indic vowel signs. A Devanagari keyword matches the exact letters, so दाम and दम are two different words to the matcher, and nothing forgives the difference for you. On a phone with a transliteration keyboard people produce spelling variants constantly, which means the fix is listing the spellings rather than hoping. The localisation post goes further into this, and it is the single most practical thing to read if your audience types in more than one script.
- Short, one word, no punctuation. Something a thumb gets right the first time.
- List the variants you expect, all of them. Both scripts if your audience mixes. Ten seconds at build time beats a customer whose comment matched nothing.
- Do not use a word that already appears in your comments.
LINKandINFOare in half of any comment section and will fire on people who did not mean it. - Say it in the caption. No line, no comments, no flow. Choosing the word is the decision the whole build turns on.
What is genuinely not here
No device detection, no responsive reply formatting, no app-versus-web branching, no push notification product, no read receipts you can act on, no analytics telling you where a phone user dropped off.
And the usual list, because it is what people actually come to this page hoping for: no scheduling or publishing, no content calendar, no hashtag tool, no CRM sync — leads leave as CSV — and no WhatsApp. Official Instagram Graph API only, seven days to reply to a comment, twenty-four hours inside a DM thread and that one restarts only when the person writes again.
The honest summary is that mobile is not a feature you buy here. It is a constraint on how you write, and the entire optimisation available to you is: answer first, keep it short, link straight to the thing, and pick a word a thumb can type. The setup guide has the rest in order.
