Most closes fail because the post
gave the reader nothing to respond to.
A call to action only works when the post above it has already been useful. Assuming it has, the phrasing of the last two lines decides whether you get a hundred reactions or eleven comments worth reading, and the second of those is worth considerably more to both you and the algorithm.
Six rules for the last two lines.
Ask for something the reader can answer from memory
A good close requires no work. 'What was the first thing you cut when budgets tightened last year?' can be answered in nine seconds. 'What are your thoughts on B2B marketing?' requires an essay nobody is going to write.
Aim at a specific group
Addressing fewer people produces more replies. 'If you run a services business under twenty people' tells a specific reader that the question is genuinely for them. A question aimed at everyone is aimed at nobody.
Make disagreement safe
The strongest closes admit uncertainty. 'I can argue this both ways and I would like to be talked out of it' produces long, substantive comments, which are the comments the system weighs most heavily.
One ask, at the end
Two asks split the response and usually produce neither. Put it last, on its own line, after the post has already delivered.
Earn it first
A close only works when the post has already been useful. If the post gave the reader nothing, no phrasing will rescue the ask. Most weak CTAs are actually weak posts.
Sometimes the best close is not a question
A flat, quotable final line gives readers something to reshare rather than something to answer. Reshares with commentary travel further than comments do. Vary which one you are going for.
The banned list
Weak or strong?
Twelve real closing lines. Decide before you commit, then read why. Getting these wrong here is considerably cheaper than getting them wrong in the feed.
“Thoughts? 👇”
Pick the outcome, then the shape.
Decide what the post is for before you write the last line. The four outcomes below call for genuinely different closes, and trying to get all four at once reliably gets none.
You want long comments from people whose view you would actually value. Aim the question at a defined group and make it answerable from memory.
If you [specific role or situation], how did you handle [specific moment]?
I have not resolved [named uncertainty]. If you have, I would like to hear how.
What did you cut first when [constraint] hit? Ours was [your answer], and I still think it was wrong.
Where does this break? I can see one case and I suspect there are three.
Fill the brackets with something only you could write. A pattern with generic contents is still a generic close.