iMessage Shortcuts for iPhone 13 Pro

32 Min Read
32 Min Read
Man in a gray rat-inspired hood reacts to a phone beside blue and green message symbols.
Quick actions in Messages help you reply, find information and correct recent messages.

iMessage shortcuts on iPhone 13 Pro are quick actions inside Messages that help you reply to a particular bubble, correct a recent message and find information without scrolling through an entire conversation. Start with the action that removes your current difficulty; the available menu depends on your iOS version and whether the message uses iMessage.

For everyday conversations, learn inline replies and search before building an automation. They solve two common sources of wasted effort: answering the wrong question and hunting for something already shared. Editing and Undo Send are useful backups, but their limits make them poor substitutes for checking the recipient before sending.

This guide focuses on managing a conversation rather than creating keyboard abbreviations or installing downloadable shortcuts. The examples use a fictional meetup conversation so you can see how the actions differ without treating an illustration as a real exchange.

How do you answer the right message quickly?

Use an inline reply when your answer needs to stay attached to a specific question. Use a Tapback when acknowledgement is enough. Both keep the connection between your response and its subject visible, but only a written reply can explain a changed time, an exception or a condition.

The word “shortcut” has several meanings on an iPhone. Messages is the app; iMessage is one service it uses; Shortcuts is a separate automation app. None of the eight methods below requires importing a shortcut, granting a third-party app access to contacts or subscribing to a messaging service.

Check the message context before following an iMessage-only instruction. Blue outgoing bubbles identify iMessage; green ones can represent RCS, SMS or MMS. A green conversation can still have useful messaging features, so color alone does not tell you every available action. Apple explains the service distinction in its comparison of iMessage, RCS and SMS/MMS.

  • A specific question needs an answer: use Reply on that bubble.
  • A simple acknowledgement is enough: attach a Tapback.
  • An important detail is wrong: decide whether Edit or a clear follow-up is appropriate.
  • You need information from earlier: search the conversation or browse its shared attachments.

These are local decisions about the conversation in front of you. A newer phone advertisement may show features unavailable on iPhone 13 Pro, especially Apple Intelligence functions. This guide uses ordinary Messages actions; it does not depend on Writing Tools, generated replies or natural-language search.

There is also a useful boundary between speed and certainty. A gesture that saves two taps is worthwhile only if it leaves the intended recipient, message and meaning clear. When several similar bubbles are on screen, take the slower visible menu route until you can reliably select the right one. The shortcut succeeds when it removes a step without removing necessary context.

Reply inline instead of sending an ambiguous answer

An inline reply is most useful when several subjects are active at once. In the illustrative meetup, Alex asks “Which entrance?” while another person asks about the arrival time. Sending “North entrance” as an ordinary new message can work, but attaching it to the entrance question removes the need for everyone to infer what you meant.

  1. Open the conversation and locate the exact message you want to answer.
  2. Touch and hold that bubble, then choose Reply.
  3. Read the quoted context above the reply field. Make sure it is the intended question.
  4. Type the answer and use the send arrow.

Checkpoint: your answer should appear connected to the selected message. If the quoted question is wrong before sending, leave that reply and select the correct bubble rather than trying to explain the mistake inside another unrelated response.

The mechanism is simple: the reply carries a visible reference to its parent message. This matters more as a group becomes busy. It does not create a private side conversation. Everyone in the group can read the reply, including an answer addressed to one person. Apple’s send and reply guide documents the action and its group visibility.

Common mistake: choosing a nearby message because the bubbles look similar. Repeated “Yes” or “Okay” messages are especially easy to confuse. Use the wording of the question as your checkpoint, not just the sender’s avatar. If precision matters, make the answer self-contained: “Use the north entrance beside the ticket desk” is clearer than “That one.”

Easier option: use touch-and-hold rather than relying on the swipe-right reply gesture. A menu makes the choice visible and can be easier to learn. On software that supports the gesture, swiping right on a bubble is another entry point to the same action; it does not produce a different kind of answer.

Illustrated steps show selecting a question, choosing Reply and sending a connected answer.

Illustrated guide: attach your answer to the question it addresses; a group reply remains visible to everyone.

Do not confuse this with replacing a typed abbreviation. If the slow part is entering a repeated phrase rather than identifying the question, the separate text message shortcuts article covers the keyboard-related topic. Keeping those jobs separate makes it easier to choose the feature you actually need.

Use a Tapback when the meaning is already complete

A Tapback attaches a reaction to a message rather than adding another written line. It fits a complete statement such as “See you at 6” when you only need to acknowledge it. It is less suitable for a question with several possible answers or a request that needs a firm commitment.

  1. Find the exact bubble you want to acknowledge.
  2. Touch and hold it to reveal the reaction choices.
  3. Choose an appropriate reaction, such as a thumbs-up.
  4. Check that the reaction is attached to the intended bubble.

In the meetup example, a thumbs-up on “See you at 6” can mean the plan was noticed. The same symbol on “Can you bring the spare tickets and arrive early?” leaves two obligations unclear. A short written answer is better there because it can distinguish agreement from partial agreement.

The practical advantage is reduced clutter. Readers can see acknowledgement beside the statement that prompted it rather than matching a later “Thanks” to an earlier line. This is an editorial reason to choose Tapback for simple exchanges, not a claim that reactions make every group more efficient.

Common mistake: assuming a symbol has a universal meaning. A question mark can express confusion, disagreement or a request for detail. If a misunderstanding would change someone’s travel, payment or responsibilities, put the important meaning into words. A reaction should not carry a qualification that exists only in your head.

Easier option: choose one familiar reaction instead of browsing emoji or stickers. The expanded selection differs across iOS versions, so the basic acknowledgement is the most portable starting point. People in the conversation can see the reaction; it is not a private signal to the sender.

Three illustrated steps attach a thumbs-up reaction to “See you at 6.”

Use a Tapback for simple acknowledgement and words for details that could be misunderstood.

Success here is visible attachment to the correct message, not an assumption that the other person interpreted the symbol exactly as intended. Apple’s Tapback instructions explain the available reactions. When the response requires explanation, return to an inline written reply.

How do you correct a message without creating more confusion?

Use Edit for a small correction to your own recent iMessage; use Undo Send when that entire message should be withdrawn and you are still within its short window. If the recipient may already be acting on the information, a clear follow-up can be more useful than quietly changing the original.

Decide by consequence as well as by menu availability. Correcting a spelling error and changing a meeting location are different communication problems. An edited word can repair the text while leaving the reader unaware that the plan changed. The aim is a shared understanding, not merely a cleaner transcript.

SituationUseful choiceImportant limit
A typo in your recent iMessageEditUp to five edits within 15 minutes; earlier versions remain accessible.
An iMessage went to the wrong conversationUndo Send immediately if availableWithin two minutes; viewing may already have occurred.
A time or place changed after people may have read itA clear follow-up identifying the new detailChanging the old text alone may not communicate urgency.
The relevant option is missingUse a direct correctionCheck service, message ownership, software and elapsed time before assuming a fault.

For example, changing an arrival instruction from “main entrance” to “side entrance” after someone has started walking there calls for an explicit update. The issue is no longer only a typo. The recipient needs to notice a new instruction. By contrast, fixing a misspelled venue name while the rest of the message stays unchanged may need no additional line. Use that consequence-based distinction before deciding that the shortest software action is also the clearest response.

Edit a recent iMessage and preserve its meaning

Editing suits an error where the intended message should remain in the conversation. For example, “Meet at 7” was meant to say “Meet at 6.” The correction changes the sentence without requiring you to remove the whole exchange, but you still need to consider whether anyone has already made plans around the first time.

  1. Locate the outgoing iMessage you sent.
  2. Touch and hold it, then select Edit if that option is available.
  3. Change the text and check the complete sentence.
  4. Confirm the edit with the confirmation control.
  5. Look for the Edited label beneath the message.

Checkpoint: the corrected text should be visible in the conversation. The Edited label is expected; editing is not an invisible rewrite. Earlier versions can be viewed, so do not use this as a way to erase the fact that something was said.

The documented limit is five edits within 15 minutes of sending. Editing and unsending require compatible software, and older recipient software can behave differently. Apple’s edit and unsend guidance explains these limits. Treat the familiar iMessage behavior as the supported starting point rather than promising that every recipient in a mixed-service group sees the same revision.

Common mistake: looking for Edit on an incoming bubble. You cannot rewrite another person’s message. Another source of confusion is selecting an old message after the time window has passed. A missing menu item does not by itself indicate a damaged iPhone or a need to reset the app.

Easier option: send one explicit correction, such as “Correction: meet at 6, not 7.” This works when the editing window is gone and is often clearer when the error changes what someone should do. Do not send several tiny corrections if one complete sentence can establish the final instruction.

Illustrated edit sequence changes “Meet at 7” to “Meet at 6” and shows the Edited label.

Editing allows up to five changes within 15 minutes; earlier versions remain accessible.

For the meetup example, assess two outcomes separately: is the text now accurate, and does the other person understand the current plan? The first is a software result. The second is a communication result. Editing can achieve the first without proving the second, which is why a consequential change deserves a direct follow-up.

Undo Send promptly, without assuming the message was unseen

Undo Send is the appropriate emergency action when the whole recent iMessage belongs elsewhere. In the illustrative example, a casual note intended for a friend goes into the meetup group. The immediate task is to withdraw that message while the option is available, rather than spending the short window composing an explanation.

  1. Find your newly sent iMessage immediately.
  2. Touch and hold the bubble.
  3. Tap Undo Send.
  4. Check for the notice that the message was unsent.

The time limit is two minutes after sending. That short interval is why Undo Send should be learned as a distinct action rather than treated as a general cleanup feature for any old conversation. A message deleted from your own view is not the same operation as a message withdrawn with Undo Send.

Common mistake: assuming removal guarantees nobody read the content. The recipient may have seen it in the conversation or a notification before you acted. Older software can also leave the original visible. A conversation notice confirms the withdrawal action; it cannot establish what another person already saw or retained.

Easier option: if the command is unavailable, send a concise clarification that identifies the mistaken message without repeating sensitive information. For example, “That last message was intended for another conversation; please disregard it.” If the content affects an immediate decision, correct that decision directly.

Illustrated sequence selects Undo Send and shows an unsent-message notice with a two-minute limit.

Withdraw a recent iMessage promptly, but do not assume that nobody saw it.

Do not spend time trying unrelated Shortcuts permissions to restore this menu. The separate Ask to Run article concerns automation settings, which are a different subject. A bubble’s edit and withdrawal options belong to Messages and its service rules.

There is no appropriate promise that Undo Send reverses disclosure. If the mistake exposed a password, payment instruction or other sensitive item, withdrawal alone does not resolve the underlying problem. Act on that specific exposure rather than treating an empty-looking bubble as proof that the risk disappeared.

How do you keep important conversations easy to return to?

Pin a conversation you use repeatedly; mark a conversation unread when you need a cue to return to an unfinished reply. A pin controls prominence in your list, while unread status signals unfinished attention. Neither is a scheduled reminder or proof that the other person is waiting.

These two actions work at the conversation level, so start in the list of chats rather than on an individual message bubble. That distinction prevents a common navigation error: holding a bubble opens message actions, while holding a conversation row exposes actions for the thread.

Keep a permanent access need separate from a temporary attention need. A conversation can be worth opening every day without containing an unanswered question. Another conversation may need one reply and then become irrelevant for months. Pinning the first and marking the second unread gives each state a useful meaning. Using pins as a backlog of every unfinished task quickly makes the top of the app harder to interpret.

Pin a recurring conversation instead of repeatedly searching for it

Pinning is useful for a household, a close contact or an active project that you open throughout the week. In the illustration, Family becomes a pinned item above the ordinary list. The benefit is a stable place to look, even as newer messages arrive in other conversations.

  1. Return to the main conversation list in Messages.
  2. Touch and hold the conversation you want to keep near the top.
  3. Choose Pin.
  4. Confirm that the conversation now appears in the pinned area.

Checkpoint: you should be able to reopen that conversation from its pinned position. Pinning does not send a message or notify the people in the thread. It changes your organization of the list, not their view of the conversation.

Choose pins by recurring use rather than by the emotional importance of every message. If all available positions are filled with rarely opened conversations, you have made the list more crowded without improving access to the chats you actually need. The useful test is whether the pin removes repeated searching during ordinary use.

Common mistake: expecting a pin to change notification delivery. A prominently positioned conversation can still be quiet for other reasons. Conversely, pinning an active group does not make its interruptions more appropriate. Organization and alerts are separate decisions.

Easier option: start with one recurring conversation. You do not need to fill every slot. Apple’s Messages documentation allows up to nine pinned conversations, but the maximum is a capacity limit rather than a target. Leave space for the conversations that genuinely benefit from quick access.

Illustrated steps pin the Family conversation and move its icon above the ordinary chat list.

Pinning keeps a recurring conversation easy to open without notifying its participants.

In the meetup scenario, a temporary event group may deserve a pin while arrangements are active. A family thread may remain useful for much longer. This distinction gives pinning a selection rule: prioritize the conversation you expect to open again, rather than the last conversation that happened to arrive.

Mark unread as a personal cue, not a message to the sender

Marking unread is useful after you open a question but cannot answer it yet. Perhaps the meetup group asks whether you can bring something, and you need to check before replying. An unread indicator gives that thread a visible unfinished state when you return to Messages.

  1. Go back to the conversation list.
  2. Swipe right on the conversation row.
  3. Use Mark as Unread if the swipe reveals the button; a full swipe may apply the action directly.
  4. Check for the unread indicator beside the conversation.

Checkpoint: the row should look unread in your list. This does not undo a read receipt that has already been sent. It also does not create a notification at a future time, so it should not be your only safeguard for a deadline that cannot be missed.

The distinction matters because “unread” describes an organizational state on your side, not a claim that your eyes never saw the message. Use it honestly as a cue to return. Trying to use it to conceal that a message was opened confuses a list-management action with the separate behavior of read receipts.

Common mistake: letting many old unread threads accumulate. The signal becomes less useful when everything carries the same state. Apply it to a specific unfinished exchange, then return to the actual question rather than replying merely to clear an indicator.

Easier option: use this cue for one pending conversation at a time while learning the gesture. The observable result is a visible marker, not a guarantee that you will remember. Apple’s keep track of messages guide describes unread and conversation organization features.

Illustrated right swipe on Weekend plan adds a blue unread dot beside the conversation.

An unread marker is a cue to return; it does not retract a read receipt.

Neither pins nor unread markers require private shortcut sharing. If your next task is distributing an automation rather than managing a chat, the private sharing shortcut article is the relevant separate topic. A pinned conversation is not a shared automation and should not be treated as one.

How do you find an old detail or shared attachment?

Use search when you remember a person or a distinctive word. Browse the conversation’s shared items when you remember the type of material, such as a link, more clearly than its wording. Choosing the route from what you remember is faster than guessing a date and scrolling.

In the meetup example, “entrance” is a better text-search clue than “okay.” A venue link is a better candidate for the Links category than for a vague keyword search. The useful distinction is between finding a sentence in context and finding an item that was shared.

Before you search, choose the smallest clue that distinguishes this occasion from earlier ones. In a group that meets every week, the word “Friday” may recur too often to help. “North entrance” or a venue name carries more identifying information. If you only remember a visual item, begin with shared content instead. This is a choice about retrieval strategy, not a requirement to memorize the conversation or keep a separate written log.

Combine a person filter with a distinctive keyword

A search works best when the clue narrows the possible matches. If several conversations mention dinner, adding the person or group prevents unrelated results from competing for attention. The illustration uses Alex and “entrance” to locate the original arrival instruction.

  1. Open the Messages conversation list and locate its search field. On iOS 26 it is at the bottom; on iOS 18 or earlier, pull down on the list to reveal it at the top.
  2. Enter the person’s name and select the relevant Messages with or conversation filter when offered.
  3. Add a distinctive word from the detail you need, such as entrance.
  4. Open the matching result and read the surrounding exchange.

Checkpoint: the result should belong to the intended person or group and the correct occasion. A matching keyword is only a locator. It does not establish that the instruction is still current, especially when a later message changed the plan.

Search is an information-retrieval tool rather than a summary of the final agreement. In our example, the result “Use the north entrance” may be followed by “Actually, that door closes early.” Reading that nearby context prevents a technically successful search from producing the wrong real-world action.

Common mistake: choosing a common word and then assuming the first result is the answer. Names, place fragments and distinctive nouns generally make better clues than acknowledgements. Avoid requiring exact punctuation when a shorter meaningful word can find the exchange.

Easier option: begin with the distinctive keyword alone if the person filter is not offered on your software. Then narrow by the recognizable conversation in the results. The full method does not require natural-language search or Apple Intelligence; standard keyword search is sufficient.

Illustration combines an Alex conversation filter with “entrance” to find a matching message.

Narrow your search with a person and a distinctive word, then read the surrounding exchange.

Apple’s Messages search instructions explain the version-dependent field position and filtering. If an expected result is missing, do not conclude that the phrase was never sent. It might belong to another conversation, be an image rather than searchable text, or no longer be present in your message history.

Browse shared links when the item matters more than its wording

The shared-items view is useful when you remember receiving a venue page, document or photo but not the message that accompanied it. Opening the relevant category changes the search problem: instead of scanning conversational text, you inspect the material shared in that thread.

  1. Open the conversation with the relevant person or group.
  2. Tap the name or group heading at the top.
  3. Find the shared-content categories and open Links, or the category appropriate to your item.
  4. Select the intended item and check its destination or contents.

Checkpoint: the opened item should be the one you intended, not merely a similar preview. For the fictional venue link, confirm the actual venue name and the information on the destination page. An attractive card or familiar-looking title does not establish that the page is current or trustworthy.

This route complements keyword search rather than replacing it. Search is stronger when you need the sentence that qualified an instruction. Shared-item browsing is stronger when you need to reopen the actual page or file. If the conversation contains several links to the same venue, the surrounding messages can still be necessary to establish which one applies.

Common mistake: treating the shared-content screen as an archive of everything that ever existed. Its usefulness depends on the items available in your conversation history. A missing card is not proof that the sender never shared the item. Ask for the specific item again when it is important and unavailable.

Easier option: use the relevant category before trying to remember a filename. A visual preview can be a better clue than a generic document name. Keep attention on the item itself; there is no need to install a shortcut just to reopen something already shared.

Illustrated steps open Alex’s conversation details and select a Venue details link.

Browse the conversation’s Links category, then check the page you open.

After finding the item, choose the appropriate next action based on its contents. For a venue page, check the location and opening details. For an attachment requesting money or account access, independently confirm the request before acting. Finding a message accurately does not authenticate the sender’s claim or the linked website.

Frequently asked questions

Do I need to download a shortcut for these actions?

No. These actions are part of Messages. A download is relevant only when you want a separate automation with a clearly understood purpose. A link described as an iMessage shortcut is not automatically necessary or trustworthy simply because it arrived in a message.

Will these instructions look identical on every iPhone 13 Pro?

No. The installed iOS version can change menu placement, icons and search layout. Follow the action names and checkpoints in the text. The illustrations simplify the interface to teach the sequence rather than reproduce a particular software build pixel for pixel.

Can a green conversation still have reactions or read receipts?

Yes, depending on the service and software involved. Green bubbles can represent RCS as well as SMS or MMS, and RCS can support features that ordinary SMS does not. Check the actual conversation and available menu rather than using bubble color as a complete feature checklist.

Does iPhone 13 Pro need Apple Intelligence for these methods?

No. The ordinary reply, reaction, organization and retrieval actions described here do not require Apple Intelligence. Do not use instructions for AI-powered message rewriting or natural-language search as proof that those additional features are available on this model.

Is Send Later the same as marking a conversation unread?

No. Send Later schedules an outgoing message; marking unread leaves a cue in your own conversation list. Apple’s Send Later feature requires iMessage and compatible software, starting with iOS 18. An unread indicator by itself sends nothing and does not establish a future reminder.

What should you set up first?

Start with the action that fixes your current friction: Reply for an ambiguous exchange, search for a lost detail, or one pin for a recurring conversation. Then learn Edit and Undo Send as time-limited recovery actions. A useful shortcut leaves you with a clearer conversation or the correct item in hand; it should not add a new app or workflow unless the task actually needs one.

Mia reviews phone setup steps and user-friendly guidance.
Article link copied