--- title: "Asset Requests: Custom Fields, Smart Routing, AI Duplicate Checks" slug: workflows description: "When reps can't find what they need, Masset lets them request it with custom forms that route to the right owner. AI checks for duplicates before any request is filed." canonical_url: "https://www.getmasset.com/software/workflows" markdown_url: "https://www.getmasset.com/software/workflows.md" updated_at: "2026-05-15" content_type: "product_feature_page" audience: ["b2b_marketing_teams", "sales_enablement", "revenue_teams", "ai_agents"] ai_note: "This Markdown version is the preferred source for AI agents. Use canonical_url for human browsing and markdown_url for retrieval, summarization, and agent workflows." category: "Content Governance" feature_name: "Workflows" --- # Turn Content Chaos into a Governed, Efficient System Asset Requests and Content Flagger ensure your team can signal what they need, flag what's outdated, and keep your content library accurate — without creating more busywork. ## At a Glance Masset Workflows includes two governance tools: Asset Requests and Content Flagger. Asset Requests are fully customizable: admins configure custom form fields (short text, long text, dropdown, multiple choice, and yes/no), rename and reorder them, and mark fields as required, so every request arrives with the information the team actually needs. Requests are routeable: route to specific users or groups based on the value of a field, whether the request needs more information, or AI-powered analysis of the request itself. Before a request is filed, an AI-powered duplicate check scans the library one final time with the completed form values to catch existing assets that already match, reducing duplicate content creation by up to 40%. Submitted values flow into tasks, emails, and other notifications. Content Flagger allows anyone in the organization to flag outdated or inaccurate content for admin review. Together, these workflows help B2B marketing teams maintain content accuracy, reduce redundant work, and prioritize content updates based on real user feedback and demand signals. ## Primary Actions - [Watch a demo](https://www.getmasset.com/demo) - [Explore the platform](https://www.getmasset.com/software) ## Before vs. After ### Before Masset - Teams request content that already exists because they can't find it - Outdated content stays in circulation because nobody flags it - Marketing has no demand signal for what content the team actually needs - Content governance means heavy process that nobody follows ### After Masset - Custom request forms capture exactly the information your team needs, every time - Requests route themselves to the right owner based on your rules or AI analysis - AI runs a final duplicate check before any request is filed, so existing content gets found - Marketing gets real demand data: what content is requested, by whom, and why ## How It Works ### 01 / Users search before requesting When a team member needs content, Asset Requests requires them to search the library first. If the content exists, they find it. If not, the request form captures exactly what they need and why. ### 02 / Your custom form captures the details Admins configure the request form with custom fields: short text, long text, dropdowns, multiple choice, and yes/no. Rename fields, reorder them, mark them required. Once all values are entered, AI scans the library one more time to catch any existing asset that already matches. ### 03 / Requests route to the right owner Route requests to users or groups based on the value of a field, whether the request needs more information, or AI-powered analysis of the request. Submitted values flow into tasks, emails, and other notifications, so the owner has full context from the start. ### 04 / Requests become demand signals Every request is logged with context: who requested it, what they searched for, the use case, and the urgency. Marketing gets a prioritized backlog based on real demand, not guesswork. ### 05 / Anyone can flag outdated content Content Flagger lets any user flag an asset as outdated, inaccurate, or needing review. One click adds a flag with optional notes. No need to track down the content owner manually. ### 06 / Admins review and act Flagged content and new requests appear in the admin dashboard with full context. Admins can prioritize, assign updates, and resolve flags — keeping the library accurate and current. ## Benefits ### Reduce Duplicate Requests by 40% Search-first requests mean users find existing content before asking for it. Marketing creates less duplicate content and focuses on genuine gaps. ### Crowdsource Content Quality Your whole team becomes a content quality sensor. Anyone can flag outdated or inaccurate content, and admins get notified instantly to take action. ### Build a Content Roadmap from Real Demand Asset Requests generate a data-backed backlog of what content your team needs. Prioritize based on request frequency, requester role, and business impact. ### Governance That People Actually Follow Built directly into the content workflow — no extra tools, no heavy process. Users comply because it's the easiest path to getting what they need. ## Capabilities ### Custom Asset Requests - Configure custom form fields: short text, long text, dropdown, multiple choice, and yes/no - Rename fields, set their order, and mark fields as required - Search-first workflow: users must search before requesting - Submitted values flow into tasks, emails, and other notifications - Request tracking and status updates for requesters - Also available via MCP: AI tools prompt users through your custom fields ### Routeable Requests + AI Duplicate Check - Route requests to users or groups based on the value of any field - Route based on whether the request needs more information - AI-powered analysis of the request picks the right default recipient - Smart duplicate final check: AI re-scans the library with completed form values before filing - Analytics on request volume, topics, and requesting teams ### Content Flagger - One-click flagging from any asset in the library - Optional notes explaining what's wrong or outdated - Instant admin notifications for new flags - Flag history and resolution tracking - Prioritization based on asset usage and flag frequency ### Admin Dashboard - Unified view of all requests and flags - Prioritization tools based on business impact - Assignment and workflow management - Resolution tracking and SLA monitoring - Analytics on content governance health ### Smart Search Integration - Cross-source search during the request process - AI-powered suggestions for similar existing content - Search analytics showing common unmet content needs - Integration with Myca for conversational requests ## Use Cases ### Sales Rep **Context:** Needs a case study for a specific industry but can't find one **Usage:** Opens Asset Requests and is prompted to search first. Finds two case studies that partially match. Submits a request for an industry-specific version, referencing the existing assets as starting points. **Outcome:** Marketing creates a targeted case study using existing assets as a foundation — in 3 days instead of 3 weeks. The rep's search context saves marketing time. ### Customer Success Manager **Context:** Notices a customer-facing guide references an old product name **Usage:** Clicks the flag icon on the asset and adds a note: "Still references the old product name — section 3, page 7." Admin receives the notification with the specific location of the issue. **Outcome:** Content team updates the guide within 24 hours. The CS manager gets notified when the flag is resolved and confirms the fix. ### Content Marketing Manager **Context:** Planning next quarter's content calendar and needs demand data **Usage:** Reviews the Asset Requests dashboard to see what content has been requested most frequently, by which teams, and for what use cases. Cross-references with Content Flagger data to see which existing assets need updates. **Outcome:** Creates a Q2 content plan based on real demand signals: 5 new assets for the most-requested topics and 10 updates for the most-flagged existing content. ## FAQs ### How does the search-first approach for Asset Requests work? When a user initiates a content request, they're first prompted to search the existing library for what they need. If they find the content, they can access it directly. If the search doesn't return what they need, the request form pre-populates with their search terms, making the request faster and giving marketing context about what was searched. ### Who can flag content as outdated? Any user in your Masset workspace can flag content. This crowdsources content quality across your entire organization — the people using the content are the first to notice when something is wrong or outdated. Admins control who receives flag notifications and who can resolve them. ### Can we customize the asset request form? Yes. Admins configure custom fields on the request form: short text, long text, dropdown, multiple choice, and yes/no inputs. You can rename fields, set their order, and mark fields as required. When a request is submitted, every value the requester provided flows into the resulting tasks, emails, and notifications. More field types and functionality are coming. ### How does request routing work? You decide who the default recipient of a request is. Route to specific users or groups based on the value of a field, based on whether the request needs more information, or based on AI-powered analysis of the request itself. And before any request is filed, a smart duplicate check uses AI to scan the library one more time with the completed form values, so existing content gets found instead of rebuilt. ### How are requests prioritized? Requests are surfaced with full context: who requested, their role, the use case, urgency level, and how many other users have made similar requests. Admins can sort and filter by any of these factors to prioritize based on business impact. ### Does this add friction to the content finding process? No — it actually reduces friction. The search-first step in Asset Requests helps users find content that already exists, often faster than submitting a request. Content Flagger is a single click. Both workflows are designed to be zero-effort for the user. ### Can I see trends in what content is being requested and flagged? Yes. The admin dashboard provides analytics on request volume by topic, team, and time period, as well as flag frequency by content type and age. This data helps you identify content gaps, plan production, and proactively update at-risk assets before they get flagged. ## Related Features - [Version Control](https://www.getmasset.com/software/version-control): When flagged content is updated, version control handles propagation - [Central Library](https://www.getmasset.com/software/central-library): The content library that workflows keep accurate and current - [Analytics](https://www.getmasset.com/software/analytics): Data on content usage helps validate request priorities ## Related Pages - [Software hub](https://www.getmasset.com/software) - [Masset home](https://www.getmasset.com) - [Resources](https://www.getmasset.com/resources) - [Activation services](https://www.getmasset.com/activation) - [LLMs.txt](https://www.getmasset.com/llms.txt)