# How to Reuse a Recent Link, Question, or Checklist in PingRoom

> PingRoom 1.6.1 can refill a recently sent link, question, or checklist in the iPhone Custom Ping composer. Here is what returns and what to review.

- Published: 2026-11-05
- Author: PingRoom
- Category: How To
- Topics: recent PingRoom attachments, reuse link in PingRoom, repeat PingRoom question, repeat PingRoom checklist, iPhone group notification
- Canonical: https://pingroom.io/blog/reuse-recent-links-questions-checklists-pingroom
- Cover image: https://pingroom.io/blog/reuse-recent-links-questions-checklists-pingroom.webp
- Cover description: An approved PingRoom avatar chooses a familiar clay link from three wooden trays while Pingo watches.

To reuse a recent Link, Question, or Checklist in PingRoom 1.6.1 on iPhone, open a Custom Ping, choose the same attachment type, and select an entry under **Recently sent**. PingRoom refills that attachment’s fields. Review them, make any changes, and send only when they still fit the current Room and moment.

The shortcut is available for links, questions, and checklists. It is not a cloud-synced history of every Ping, and this article does not claim Android availability.

## Reuse an attachment

1. Open the destination Room on iPhone.
2. Start a **Custom Ping**.
3. Open **Link**, **Question**, or **Checklist**.
4. Under **Recently sent**, tap the item you want to reuse.
5. Review the restored fields and the main Ping message.
6. Confirm the Room and recipients, then send deliberately.

If there is no recent item under that attachment type, create and send one normally first. PingRoom remembers content after the send is accepted; an unfinished or rejected attempt does not become a reusable shortcut.

## Know what comes back

| Attachment type | PingRoom restores                      | Check before sending                                                          |
| --------------- | -------------------------------------- | ----------------------------------------------------------------------------- |
| Link            | The URL and optional title             | The destination, access requirement, title, and redirects                     |
| Question        | The answer choices and who must answer | Whether the choices still cover the decision and the answer policy still fits |
| Checklist       | The item rows                          | Whether any step is obsolete, complete, unsafe, or meant for another Room     |

The restored content is editable. Reuse is useful because it removes retyping, not because yesterday’s wording is automatically correct today.

For the original creation flows, see [send a Link in a Ping](/blog/send-link-in-push-notification), [ask from the composer](/blog/ask-the-room-from-the-composer), and [attach a checklist on iPhone](/blog/attach-checklist-to-pingroom-ping).

![Two approved PingRoom avatars review a reused link, three answer pebbles, and four blank checklist strips while Pingo moves a duplicate aside.](/blog/reuse-recent-links-questions-checklists-pingroom-1.webp)

## Worked example: repeat a departure plan

Suppose two people use one Room for a recurring departure. This is an illustrative workflow, not a customer account.

The first time, send three separate Custom Pings when each one is useful:

- a **Link** to the current itinerary or official event page;
- a **Question** such as “Which entrance?” with two or three current choices;
- a **Checklist** with a few observable items such as keys, tickets, and charger.

On the next departure, open the relevant attachment tab and choose the earlier entry under **Recently sent**. Then review it:

- Has the itinerary URL changed?
- Are the entrances and answer policy still correct?
- Does the packing list belong to this trip?

That review is the work. The shortcut simply gets you back to a useful structure faster.

[Pingo](/Pingo), PingRoom’s fictional Chief Marketing Officer, moves one duplicate clay strip aside in the illustration. He is editorial scenery: he cannot inspect a private Room, retrieve anyone’s recent content, or send on someone’s behalf. The people in the Room remain responsible for the message.

## Recent means local to this account and device

PingRoom keeps up to eight recent entries for each of the three attachment types, newest first. Sending the same link, question choices, or checklist again moves it to the top instead of creating another identical shortcut.

The list is stored locally for the signed-in account. It is not shared with the Room, synchronized as server history, or promised on another device. Signing out clears local app storage, including these shortcuts.

That boundary is useful for privacy and explains why another phone may not show the same list. It also means **Recently sent** is not a record system. Use the Room’s actual Ping history when you need to see what was sent.

## Forget a shortcut without changing history

Use the trash control beside a recent item when you no longer want it offered in the composer. This removes the local shortcut. It does not retract, delete, or alter the Ping that was already sent.

Deleting a stale shortcut is sensible when a link has expired, a question should not be repeated, or a checklist belonged to a one-time event.

## Before you reuse anything

- Confirm the app is PingRoom 1.6.1 or later on iPhone.
- Choose the correct Room before opening recent content.
- Treat restored fields as a draft.
- Keep secrets, access codes, and private tokens out of notification content and URLs.
- For a high-stakes process, use its approved source of truth rather than a reused Ping.

The [PingRoom 1.6.1 release guide](/blog/pingroom-1-6-1-iphone) covers the rest of the update. [Update PingRoom on iPhone](https://apps.apple.com/us/app/pingroom/id6758355726), then test one harmless recent item in a Room you control.

_Illustrations are AI-generated editorial scenes featuring [Pingo the Pigeon](/Pingo), PingRoom’s official mascot and fictional Chief Marketing Officer, with fictional approved PingRoom avatars. The departure plan is an example, not a customer story or testimonial. The human team is responsible for product claims and decisions._