Your users ask AI for help with your product. Does that AI have your current setup steps, plan limits and troubleshooting instructions? A confident answer is useful only when it describes what your product actually does.
1PC Customer support gives people a shared source for product answers. Enable it for your product, upload the public Markdown documents you want customers to use, and let people ask through the separate 1PC Support plugin. Existing 1PC users and guests can use this route; guests do not need a 1PC account.
The goal is practical: help someone take the right next step using your product's documentation. Here is how to prepare that documentation and make it available without exposing your private founder workspace.
Give AI the facts a support answer needs
Imagine a customer asking, “Can I export my project on the Free plan?” An assistant that has no current product documentation might suggest a menu that does not exist, confuse two similarly named products or miss a plan restriction. Even a well-written reply can leave the customer stuck.
A useful answer needs the exact product, the supported action, any prerequisites and the next step if that action is unavailable. Product documentation supplies those facts. When the documents leave a gap, the assistant should say what it cannot confirm.
In 1PC Support, the guest names a product, the assistant finds public matches and confirms which one they mean. It then lists that product's support files, selects relevant documents and checks each one before using it for advice. Answers should cite the file name and revision so the customer can see what the guidance used.
That gives every person using the support connection access to the same maintained product information. Enabling the feature makes your product discoverable through 1PC Support; people still need to connect the support plugin or a compatible public MCP client.
Build a small product support knowledge base
Start with the questions someone asks before buying, during setup and when something goes wrong. A few specific documents are easier to maintain than a large file containing every product note.
| File | What it should answer | Useful detail |
|---|---|---|
getting-started.md | How do I reach the first useful result? | Prerequisites, exact steps and how to check success. |
plans-and-limits.md | Does my plan include this action? | Current availability, limits and a public pricing reference. |
faq.md | What do people repeatedly misunderstand? | Direct answers, supported alternatives and known limitations. |
troubleshooting.md | What should I check when a step fails? | Recognizable symptoms, safe checks and when to contact you. |
Write the question in the customer's words. Name the button or setting they need, state which plan or platform the instructions apply to, and include a last-reviewed date. Remove contradictory instructions before uploading a new edition. If a price or limit changes, update the support file along with the public offer.
Use information you are comfortable sharing publicly: product capabilities, setup instructions and approved support policies. Keep credentials, customer records, private strategy and internal incident notes out of these files.
Turn a vague FAQ into an actionable answer
The following is a fictional example for a product called Fieldnote. It illustrates documentation structure, not Fieldnote's existence or a measured support result.
“We support exports” leaves an assistant to fill in the format, plan and menu location. A more useful faq.md entry gives it a complete answer:
# Fieldnote: export FAQ
Last reviewed: 2026-10-07
## Can I export my notes on the Free plan?
Yes. Free and paid plans include CSV export.
1. Open the notebook you want to export.
2. Choose Notebook settings, then Export CSV.
3. Open the downloaded file and check that your notes are present.
The export includes note titles and text. It does not include attachments.
If Export CSV is missing, check that you own the notebook.
For an unresolved issue, use the support link on our public website.
Now an answer can explain eligibility, provide steps and mention the attachment limitation. It should cite faq.md and the revision it read. If someone asks about PDF export and no document covers it, the correct response is to explain that gap and point them to the product's public website for further help.
You can apply the same structure to installation, onboarding or an error message: question, supported behavior, prerequisites, steps, expected result and a contact path. Test the instructions yourself before uploading them.
Enable Customer support for your product in 1PC
Every Product owner can enable support and publish separate public documents. Support starts off for each Product. Guest support uses the public endpoint and does not expose private workspace knowledge.
- Open Product settings and enable Customer support.
- Open the separate Customer support tab.
- Upload your public UTF-8 Markdown
.mdfiles, up to 250 KiB each. - Check your public product name, description and website so guests can identify the right product.
- Try a setup question, a plan-limit question and a question your documents do not answer.
Support documents live in their own support/ folder. Private Knowledge files are never included automatically. A founder can keep managing research and decisions through the private product workflow while deliberately maintaining a separate set of customer-facing instructions.
Turning support off, or losing paid access, stops public discovery and document reads. As with other public content, copies already returned to someone's client cannot be recalled.
Let users and guests ask in their own AI conversation
Send people to the 1PC Support connection guide. It provides the plugin package and a public MCP connection option for compatible clients. Installation options depend on the client; enabling support does not install a plugin for your customers.
After connecting, a guest can name the product or ask which public products are available. A useful first prompt is:
Use 1PC Support to help me with Fieldnote.
Confirm the product first, then check the relevant support documents.
Can I export my notes on the Free plan? Give me the steps,
cite the files and revisions, and say what you cannot confirm.
The assistant retrieves relevant documents as needed. You do not have to paste the same FAQ into each customer's conversation, and the guest does not need access to your founder account. After a feature launch, update the launch and support instructions together so the public promise and the help someone receives agree.
Turn a support gap into a clear feature request
Sometimes a customer needs something your documentation does not cover. They can use the same support connection to explain what they want to accomplish. The AI asks about the situation, the problem, the desired change, the expected result and any workaround, then checks relevant support documents through the safety flow.
If a documented feature already solves the problem, the assistant explains how to use it. If it finds no documented solution, it says that availability is unconfirmed: an absent FAQ entry does not prove that your product lacks the feature. It then shows the proposal and asks the person to confirm sending it.
Continuing the fictional Fieldnote example, a customer could say:
Help me propose PDF export for Fieldnote.
I send a notebook to clients who need a readable document.
Check the support docs for an existing solution first.
If none is documented, help me prepare a feature request
and show me the brief before asking whether to send it.
A clarified brief might look like this:
Title: Export a notebook as a readable PDF
Problem: Clients need to read notes without importing a CSV.
Proposed solution: Add PDF export for notebook titles and text.
Expected outcome: Share one readable file with a client.
Current workaround: Copy notes into a document and export it.
Documentation review: faq.md documents CSV export;
PDF export availability could not be confirmed.
After confirmation, the owner sees the request under Customer support → Feature requests, with the brief and reviewed file revisions. Name and email are optional. The inbox is private to the owner; a submission does not automatically become a roadmap commitment, a task or an email reply.
Try the guest feature-request instructions. Review incoming proposals for the underlying customer problem before deciding what to build, and use the feature-launch guide when an accepted change is ready to communicate.
Keep support useful, public and reviewable
Each selected document goes through a separate safety assessment by the guest's AI before it is used for advice. Uploads remain private drafts until the owner reviews and publishes each revision. Automated checks block some credential patterns before publication; they do not certify safety. A harmful guest verdict stops use in that conversation and records an untrusted pending report. Only an admin can quarantine the file globally. Report evidence is retained separately, so a guest report cannot prevent document or product deletion.
The public support route has no access to private Knowledge, founder profiles, skills or decisions. Safety checks are performed by the guest's AI; 1PC verifies the document handoff and revision, but does not independently certify the model's verdict. Guest reports may be incorrect and need admin verification before global quarantine.
Good documentation gives an assistant a stronger basis for helping your users. Answer quality still depends on the documents and the model. Review representative replies after a product change, correct outdated instructions and review the new draft before publishing and add FAQs where users repeatedly encounter a gap.
Begin with one product and its most common questions. Enable Customer support, publish the facts people need and test the path from a guest's question to a documented next step.
Give your users a documented next step.
Prepare a public FAQ, enable Customer support and test a guest question and confirmed feature proposal. Available to every Product owner.
Open the 1PC Support setup guide ↗