How Discord hobby community hosts can keep requests tidy

Q: Can Askarr keep a history of movie and show requests?

Askarr’s plans include a request history with live status. A message back from Radarr and Sonarr lets the site show when a title was added and downloaded. People request a movie or show on Askarr, and their own Radarr and Sonarr add it.

Keep Discord hobby community requests in a clear list, with simple rules for recording ideas, tracking decisions, and closing finished requests.

By VLClean · 2026-11-12

VLClean is published by the makers of Askarr and Watcharr, which are compared here alongside other tools.

Choose a shared place to record requests, give each request a clear description and status, and explain who updates it. Keep decisions beside the original request so members can see what happened without searching through conversations. Separate movie and show requests from requests about community activities, rules, or roleplay.

Option	Request method	Cost details
Askarr	Request a movie or show on Askarr, and your own Radarr and Sonarr add it. ^[1]	The Free plan costs $0 and allows 10 requests a month. ^[1] Card fee: not published.
Shared request list	Record each suggestion with its status and decision.	Own fee: not published. Card fee: not published.
Request form	Collect the details needed to review a suggestion.	Own fee: not published. Card fee: not published.
Shared message thread	Collect suggestions in a designated conversation and maintain a current list.	Own fee: not published. Card fee: not published.

What you need before you start

Decide what belongs on the request list. A hobby community might collect ideas for roleplay settings, character activities, discussion topics, or movie nights. Write a short description of the list’s purpose so members know where an idea belongs before submitting it.

Prepare the titles or types of content that are allowed, so people know what kinds of requests fit the community. Keep the request rules simple, such as whether people can suggest any activity or only ideas connected to the current theme.

Choose where people will send requests. The choice can be a form, a shared list, or another method that gives members a clear place to submit ideas. Decide who will review requests and who will keep the record current when a decision changes.

Agree on what each status means before using it. Suggested labels include received, needs details, under review, planned, and closed. Decide whether closed means completed or declined, or whether those outcomes need separate labels. Prepare a short example showing a useful request, its current status, and the next action.

Step by step

Pick a place where community members will send requests, such as a form or a shared message thread, and tell everyone to use that place. Write a short note explaining what belongs there. If suggestions arrive elsewhere, move the useful details into the list and tell the sender where to follow progress.

Choose the details worth recording. Start with a short title, a description of the request, who submitted it, its current status, and the next action. Add a decision note when needed. Avoid collecting personal details that have no practical purpose in reviewing or completing the request.

Write down who looks at each request and whether it needs approval before anything happens. For a roleplay activity, identify who decides whether it fits the setting and who would organize it. Keep that responsibility visible so a request does not remain waiting because everyone assumes someone else is handling it.

Check for an existing request before creating another entry. If someone has already suggested the same activity, add any useful new details to that record. Keep separate requests when their outcomes differ, even if they share a theme. A request for a discussion topic and a request for an event may need different decisions.

Review new requests on a regular day and update the list as decisions happen. Ask for missing details, mark accepted ideas as planned, and record a short reason when an idea is declined. Keep the decision beside the request so members can understand its outcome without searching through unrelated conversation.

Close completed requests and move older records out of the active view. Keep enough history to recognize repeated suggestions and explain earlier decisions. Ask members what confused them about submitting or following a request, then edit the instructions. If the list becomes hard to scan, simplify the labels or remove fields that nobody uses.

Tools that can do it

Askarr

Askarr is made by the team that publishes this site, VLClean. Askarr is a hosted website that works with existing Radarr and Sonarr. ^[1] People request a movie or show on Askarr, and their own Radarr and Sonarr add it. ^[1]

You add Askarr to Radarr and Sonarr one time, and they then pick up your requests from it. ^[1] Askarr never connects to your Radarr or Sonarr and never receives their API keys. ^[1] Askarr’s plans include a request history with live status. ^[1] A message back from Radarr and Sonarr lets the site show when a title was added and downloaded. ^[1]

Shared request list

Use a shared list to record requests for community activities, roleplay ideas, or changes to community rules. Give each request its own entry and keep its description, status, and decision together. Before choosing a service, check who can edit entries, how members can view progress, and whether older records can be kept apart from active work.

Request form

Choose a form when submissions need a consistent set of details. Ask for the proposed activity, a short explanation, and any information needed to make a decision. Decide where submitted answers will be reviewed and how members will hear the outcome. Check those steps before sharing the form.

Shared message thread

Use a shared message thread as the submission location if that matches the community’s routine. Set a short format for requests and nominate someone to maintain the current list. Decide where the final decision will be recorded, especially when discussion moves away from the original suggestion.

Common mistakes to avoid

Avoid sharing a request method without explaining the rules. Members need to know what types of ideas can be requested and who decides what happens next. Include an example so a short suggestion does not turn into a long exchange about missing details.

Avoid treating every comment as a separate request. Clarify the outcome being requested before adding an entry. When several people suggest the same thing, keep the useful details together so reviewers do not have to reconcile competing records.

Avoid changing a status without explaining the next action. A label such as under review says little unless someone is responsible for the decision. Record who needs to act and what information is still needed.

Avoid deleting the history as soon as an idea is declined or completed. Keep a brief outcome that explains why the request closed. Review what information remains visible, especially when a suggestion includes personal circumstances or private discussion. Keep the active list focused on work that still needs attention.

Things to check before you choose

Check whether the chosen method covers the kinds of requests the community actually receives. Will it record roleplay proposals, event ideas, or movie and show titles? Can members see the current decision without asking a host to explain it again?

Check who can submit, who can edit, and who can read older requests. How will corrections be handled? Where will a moderator record a decision that should remain private? Decide how a request moves from submission to review and then to completion before inviting the community to use the method.

For a movie or show request process, check how title searches and progress updates work. Askarr allows title searches by pasting a TMDB, IMDb or TVDB link. ^[1] Askarr also offers a dashboard demonstration with sample data and a throwaway demo account, without signing in. ^[1]

Frequently asked questions

How should a shared request list record roleplay suggestions?

Give each suggestion a short title, a description of the intended outcome, and a current status. Record who will review it and what needs to happen next. Keep the final decision beside the original suggestion, including a brief reason if the idea is declined or postponed.

What details should a request form collect for hobby activities?

Ask for the proposed activity, why it belongs in the community, and any details needed to decide whether it can happen. Explain where the outcome will appear. Before adding another field, consider whether its answer would change the decision or help someone organize the activity.

How should a shared message thread handle duplicate requests?

Check whether the same outcome is already recorded before adding another entry. Add useful details to the existing request and keep its current status clear. If similar suggestions need different decisions, keep them separate and explain the distinction so members know which request to follow.

Can Askarr keep a history of movie and show requests?

Askarr’s plans include a request history with live status. ^[1] A message back from Radarr and Sonarr lets the site show when a title was added and downloaded. ^[1] People request a movie or show on Askarr, and their own Radarr and Sonarr add it. ^[1]

How does Askarr work with existing Radarr and Sonarr?

Askarr is a hosted website that works with existing Radarr and Sonarr. ^[1] You add Askarr to Radarr and Sonarr one time, and they then pick up your requests from it. ^[1] Askarr never connects to your Radarr or Sonarr and never receives their API keys. ^[1]

The Free plan costs $0 and allows 10 requests a month. ^[1]

Try Askarr

Sources

Askarr's own description of itself (the product of this site's publisher)