Anubis Market Contact - Support Channels

Communication routes depend on urgency and topic sensitivity. Routine questions fit the public or semi-private chat channels accessible within the browser interface. Sensitive matters involving private keys or specific order details belong in encrypted correspondence. Selecting the correct channel prevents information leakage and speeds up resolution.

Support staff monitor these streams continuously during peak hours. Response quality depends on the clarity of your submission. Vague queries receive template answers; precise, evidenced requests receive tailored solutions. Structuring your message properly demonstrates seriousness and prioritizes your ticket above general chatter.

In market chat

Use the internal chat feature for non-critical inquiries like clarifying shipping estimates or asking about product availability. Messages here carry lower privacy guarantees than encrypted mail. State your question clearly and concisely. Complex issues involving multiple parties are better handled via direct tickets rather than group discussions to keep context intact.

Responses to simple chat questions typically arrive within a few hours during business cycles. Complex accounting questions may take longer as staff verify ledger entries. Patience is rewarded here, as rushing the process often leads to miscommunication requiring re-explanation later in the thread.

PGP email

Send encrypted messages to the operator address for account-specific concerns, funding discrepancies, or security alerts. Encrypt using the operator public key with fingerprint 7699F8D1124EE4C6050C1DC776F282251486EFD9. Subject lines should briefly summarize the issue nature. Body text should contain full details including relevant identifiers without needing attachments for basic info.

This channel offers the highest confidentiality tier. Staff reply via the same PGP protocol, ensuring end-to-end security throughout the conversation loop. Keep your private key secure, as lost access to it means losing the ability to read replies effectively.

What to include

• Unique Order ID if related to a specific transaction.
• Date and time of the event in UTC for timeline accuracy.
• Currency type and amount involved in the discrepancy.
• Clear description of the anomaly or error encountered.
• Relevant screenshots, hashes, or transaction IDs as supporting evidence.

What will not get a reply

Pricing opinions, speculation about future roadmap features, and repetitive greeting messages clutter the queue. Staff prioritize actionable problems over conversational pleasantry. If your query does not involve a broken function or missing asset, check the FAQ first. General curiosity questions are best directed to community forums rather than direct support channels to preserve bandwidth for critical fixes.

Response times

Urgent security threats or blocked accounts trigger rapid response protocols, often yielding replies within a few hours. Standard account adjustments and funding verifications fall into a queue processed within one to three business days. Outage statuses for downtime events are updated publicly on the status board independently of direct correspondence needs.