Questions about an item
Good questions help buyers decide faster, help sellers avoid repeated messages, and keep proof requests attached to the item instead of scattered across support.
Public Item Questions
- Buyers ask about condition, fit, serials, accessories, pickup timing, packing, or compatibility from the item page.
- Answered questions can appear on the listing when they help every buyer understand the item.
- Repeated questions turn into listing repair prompts so the seller can improve the description.
Seller Response
- Seller answers stay tied to the item, seller profile, response time, offer state, and buyer confidence signals.
- Answers should include direct proof when a buyer asks about serials, certificates, measurements, battery health, or accessories.
- Late or incomplete answers can lower placement until the seller replies or updates the listing.
Proof Requests
- Requests can ask for a new corner photo, port closeup, box photo, certificate detail, size tag, or accessory count.
- Proof cards show what was requested, what was added, who added it, and whether the item page now reflects it.
- High-value items can route the request to hub intake or staff review before the answer appears publicly.
Safety Boundaries
- Questions should not ask for private addresses, off-platform payment, account credentials, harassment, or unrelated personal details.
- Unsafe questions can be hidden, moved to message safety review, or attached to a support case.
- Private details stay out of public item pages and seller storefronts.
Buyer Follow-Up
- After an answer, buyers can save the item, compare similar listings, make an offer, add to cart review, or set a price alert.
- Sold or expired items point buyers to similar listings instead of ending the path.
- Won-auction and purchased-item questions move into order status, report, or review flows.
Moderation Review
- Moderators need the item, seller, question text, answer text, proof files, report reason, and customer-visible outcome together.
- Restricted item hints, private-detail requests, counterfeit claims, and abusive wording create reviewable decisions.
- Every moderation action needs a reason, timestamp, owner, and appeal path.
Support Handoff
- Support can reuse item questions when a buyer later reports missing accessories, wrong condition, or shipment damage.
- Seller answers become part of the order evidence trail only when tied to the purchased item.
- Support requests ask for exact missing proof instead of sending buyers into a generic form.
Owner Approval
- Owners approve which questions are public, which stay private, which need staff review, and how unanswered questions affect seller quality.
- Launch review should cover response targets, privacy boundaries, moderation staffing, support reuse, seller appeals, and route QA.
- Rollback can hide new public questions while preserving item and order evidence already shown to staff.
Creator graphics card
Item condition, seller context, proof notes, cart review, and seller messaging.
Message thread
Question context, offer state, listing detail, safety cues, and handoff notes.
Message safety
Boundaries, attachment review, reports, blocks, privacy records, and owner approval.
Seller reputation
Response quality, buyer actions, recent questions, reviews, and placement impact.
Support operations
Evidence handoff, response targets, case ownership, customer notices, and review quality.
Moderation review
Listing reports, restricted content, message reports, seller appeals, and staff decisions.
Current demo state
Listing questions are represented as guided marketplace data.
The demo shows item questions, seller answers, proof requests, safety boundaries, moderation cues, support handoff, and buyer follow-up without collecting visitor messages.
Future platform state
Live listing questions need account-linked controls.
Launch needs signed-in buyers, seller permissions, public/private answer rules, attachment storage, moderation queues, notification delivery, support reuse, privacy controls, and owner approval.