Connect your AI

Download the 1PC Support plugin

Import this package in a client that supports plugin packages. Alternatively, add a remote Streamable HTTP MCP connection with no authentication:

https://use1pc.com/support/mcp

After connecting, ask “Which products can I ask 1PC Support about?” or name the product. Your AI lists public matches and confirms your selection before looking at its files.

Client installation options vary. The source package does not mean that 1PC Support has been published in a plugin directory.

How document checks work

  1. Select and confirm a public product.
  2. The AI lists its available Markdown files and chooses relevant documents.
  3. It requests each document strictly for a separate safety assessment.
  4. It submits the verdict in another request. Safe content can then support advice; harmful content is excluded from that conversation and reported for admin review. Only an admin can quarantine it globally.

Checks look for prompt injection, exposure of confidential data and harmful instructions. The guest's AI performs the check. 1PC verifies the request sequence and document revision, but does not independently certify the AI's verdict or control its inference calls.

Answers cite file names and revisions. When the documents do not support an answer, the AI should explain the gap rather than invent product facts.

For product owners

Preparing your first files? Read the guide to AI customer support from product documentation for a Markdown FAQ example and a starter document checklist.

Open Product settings and enable Customer support. Use the Customer support tab to upload UTF-8 Markdown drafts (.md), up to 250 KiB per file. Review the full content, remove sensitive information and explicitly publish the revision before guest access. Automated checks detect some secret patterns, but do not certify safety. Internal Knowledge documents are never included automatically.

Turning support off or losing paid access stops guest access. Guest reports stay pending and do not lock documents. An admin can confirm a violation or dismiss a false report; evidence is retained separately from the file. Confirmed files are hidden until corrected and reviewed by the owner. Historical safety locks need explicit admin review before editing or deletion.

Suggest a feature

Ask your AI to help propose a feature for the selected product. It clarifies the problem and desired result, checks relevant documents through the safety flow, and explains an existing feature if it finds one.

If the proposal is not documented, the AI shows you a structured brief and asks you to confirm sending it. A missing mention does not prove that the feature is unavailable. With your confirmation, it saves a feature request for the owner to review in Customer support. Name and email are optional and unverified; no account or contact details are required.

Help me propose [feature] for [product].
Clarify the problem and check the support docs for a solution.
Show me the brief and ask whether to send it.

The brief includes a title, problem, proposed solution, expected outcome, documentation review and any workaround. See a worked feature-request example.

Requests are private to the product owner. Submission does not promise acceptance, delivery or an email reply. Turning support off or losing paid access stops new submissions; existing requests remain available to the owner.

Public support instructions · Support tool schema · Privacy