DeeJay Beta Assistant

DeeJay Beta Assistant

DeeJay is the DeepGrooves collection assistant. It helps you ask plain-language questions about your own library, spot records worth revisiting, and understand cleanup priorities without digging through every page by hand.

DeeJay is currently a beta assistant. Treat it as a helpful guide, not as the final authority on your collection, record values, insurance readiness, or buying decisions.

DeeJay launcher button in the DeepGrooves app chrome

Opening DeeJay

You can open DeeJay from the app header or launcher when the assistant is available for your account.

  1. Sign in to DeepGrooves.
  2. Look for the DeeJay or headphones-style action in the app chrome.
  3. Open the panel.
  4. Type a short question and send it.
  5. Close the panel when you are done.

The panel should open without moving you away from your current page. Closing DeeJay should not change the album, collection view, or form you were working on.

During the current app session, closing and reopening DeeJay should keep the same local conversation visible. Refreshing the browser, signing out, or leaving the authenticated app shell resets that local chat. DeepGrooves does not use the Sprint 01 shell to save a permanent DeeJay chat history.

DeeJay panel open with title, beta assistant framing, help button, and prompt field

What DeeJay Is Good For Today

Use DeeJay for exploratory questions and a small set of confirmed collection actions. Good prompts are specific enough that the assistant has something concrete to work with.

Examples:

  • "What are some records I have not played recently?"
  • "Which albums should I clean up before I make an insurance report?"
  • "What jazz records from the 1970s are in my collection?"
  • "What wishlist items look highest priority?"
  • "Why does Collection Health say I am missing value data?"
  • "What should I listen to if I want something mellow?"

DeeJay can be useful when you want a starting point. It can help you notice a pattern, but you should still open the related records or workflow before making a final change.

DeeJay answer to a simple non-mutating collection question

Asking About Your Collection

DeeJay can answer many factual questions from your signed-in DeepGrooves collection. These answers use your own saved records, not a general web search.

Try questions like:

  • "How many records do I have?"
  • "How many jazz records are favorites?"
  • "Show my genre breakdown."
  • "What is my condition breakdown?"
  • "Which records are missing condition?"
  • "Which high-value records are missing storage?"
  • "Find I'll Eat It Here."

When counts can be confusing, DeeJay should call out the difference between copies and grouped albums/releases. For example, owning three different pressings of the same album may count as three copies, while grouped album views may show one album/release row.

For record lists, DeeJay should keep the answer short and include links to the matching album detail pages. If there are more matches than fit comfortably, ask a narrower follow-up such as "only favorites," "only jazz," or "only missing storage."

Private notes are not searched or summarized by DeeJay yet. That is intentional while the privacy boundary is being kept conservative.

Confirmed Actions DeeJay Can Do

DeeJay can make a few low-risk changes when it can identify exactly one owned record and you confirm the preview.

Supported confirmed actions:

  • Mark one record as a favorite, or remove one record from favorites.
  • Set or clear one record rating.
  • Record one spin for one record.

For these actions, DeeJay should first show the record it found and the action it plans to take. Nothing should change until you confirm. If the match is unclear, DeeJay should ask for a better title or artist instead of guessing.

Examples:

  • "Add The Turn Of A Friendly Card to my favorites."
  • "Rate Highway To Hell 5 stars."
  • "Log a spin for Toys In The Attic."

Cancel the preview if the record or action is not exactly right.

What DeeJay Should Not Do Yet

For the current web release, DeeJay should not be treated as a full action agent.

That means:

  • It should not delete records.
  • It should not edit album details, condition, value, tags, folders, or Vault locations by itself.
  • It should not move records between Collection and Wishlist by itself.
  • It should not send share emails, alert emails, or marketplace messages by itself.
  • It should not replace your own review of value, condition, pressing identity, or insurance readiness.

If you ask DeeJay for an unsupported write change, it should refuse or explain that the action is not supported yet. Make those edits in the normal DeepGrooves screens.

Clear unsupported commands such as "delete duplicates," "move this to a folder," "add these tags," or "create a Smart Collection" are blocked by the current DeeJay shell. Questions about how to use a workflow, such as "How do I delete a record?" or "Where do I change a rating?", may still be answered as help questions.

Read-Only Capability Results

Some DeeJay responses may use structured read-only capability results. These are app-owned summaries, not free-form guesses. Depending on what is enabled, DeeJay may be able to summarize:

Area What DeeJay May Help Explain
Collection Health Missing condition, value, storage, artwork, runout, or duplicate-review cues
Wishlist Priority, target price, max price, desired condition, and watch state
Listening Records to revisit, unplayed records, or recent-history patterns
Value and insurance Records that may need manual value review or documentation cleanup
Help Which DeepGrooves workflow or manual topic may answer your question

Even when DeeJay uses structured data, it can still misunderstand your intent or explain something unclearly. Open the related page before acting on an important recommendation.

Privacy And Data Access

DeeJay is collection-aware, which means your question and relevant collection context may be sent to the assistant service so it can answer. It should use only the context needed for the request.

Good privacy habits:

  • Do not type payment details, passwords, or private notes that are not needed for the question.
  • Avoid entering sensitive personal information into prompts.
  • Remember that public share links are controlled by the Sharing workflow, not by DeeJay chat.
  • Use Settings and the Privacy Policy for account, telemetry, and data-use details.

Asking Better Questions

Short, concrete prompts work best.

Try:

  • "Show me records missing condition before insurance."
  • "What are five albums from my wishlist that need target prices?"
  • "What have I added recently?"
  • "Suggest something from my collection that I have not played."

Avoid:

  • "Fix my collection."
  • "Make everything ready for insurance."
  • "Delete duplicates."
  • "Buy this record for me."

If DeeJay gives a vague answer, ask a narrower follow-up:

  • "Limit that to vinyl."
  • "Only show records with missing value."
  • "Explain why those are cleanup priorities."

When DeeJay Gets It Wrong

DeeJay can be wrong, incomplete, or temporarily unavailable. If something feels off:

  1. Open the record, Collection Health, Wishlist, Stats, or Settings page related to the answer.
  2. Check the actual saved fields.
  3. Refresh the page if the assistant seems to be using stale state.
  4. Ask a narrower question.
  5. Use Settings support if the answer exposes a repeatable bug.

Do not make purchase, sale, grading, or insurance decisions from a DeeJay answer alone.

Service Or Configuration Errors

If DeeJay returns a service error, configuration error, or "hit a snag" message, it usually means the assistant service could not complete the request. Confirmed actions should report success only after the change saves. If DeeJay reports a failure, check the record before assuming anything changed.

If your browser is offline, DeeJay should show an offline message instead of trying to send the question. Reconnect and ask again when the app is online.

Try:

  • Sending the question again.
  • Rewording it more simply.
  • Checking whether the rest of the app is online.
  • Returning later if the assistant service is temporarily unavailable.

DeeJay Telemetry And Privacy

DeepGrooves may record basic DeeJay shell events so the team can see whether the assistant opens, closes, succeeds, fails, or hits unsupported actions. The shell telemetry is designed not to include prompt text, answer text, private notes, storage locations, price paid, runout text, or your email address.

Your prompt still has to be sent to the DeeJay assistant service for DeeJay to answer it. That service path is separate from analytics telemetry.

AI Access Limits

DeeJay uses AI service capacity, so accounts may have monthly AI access limits. These limits help keep the assistant available and predictable for everyone.

Your monthly allotment can be used whenever you want during the month. If you use it quickly during a big cleanup session, that is okay. Once the monthly allotment is used, DeeJay should tell you the limit has been reached instead of showing a generic service error. You can continue when the allotment resets.

DeepGrooves may add extra AI access purchases later. When that is available, the limit message should give you a clear way to buy more access.

Current limit messages may mention:

  • Monthly request allotment: the number of DeeJay questions or actions available in the month.
  • Monthly token allotment: the amount of AI input and output capacity used in the month.
  • Temporary daily safety limit: a protection against runaway requests, accidental loops, or abuse.

If DeeJay says a limit was reached but you think that is wrong, wait a few minutes and try again. If it still happens, contact support with the date, time, and the question you were trying to ask.

DeeJay service or configuration error state with retry-friendly wording

Related Help