Add approved knowledge
Bring together the website pages, policies, guides, FAQs, services and product information that should represent the business.
FROM APPROVED KNOWLEDGE TO CUSTOMER CONVERSATIONS
See what Helper knows before customers rely on it.
Add the knowledge that should represent your business, test real questions privately, review the evidence and go live when the answers are ready.
No credit card needed. Test important questions privately before going live.
Your HelperPrivate workspace
1. Approved knowledgeAdded
2. Tone and guidanceSet
3. Test questions24 reviewed
4. Evidence gaps3 to improve
5. Customer accessNot live
YOU DECIDE WHEN TO PUBLISHTesting need not appear on the live website; confirm storage and retention settings for your account.
01 Your approved sources
02 Your test questions
03 Your decision to publish
A CONTROLLED PATH TO GO-LIVE
Five steps from source material to useful conversations.
The workflow is designed to make the important questions visible before Helper becomes customer-facing.
Shape the assistant
Set the tone, greeting, questions to ask, topics to avoid and situations where a person should step in.
Test privately
Use realistic sales and support conversations, including awkward, incomplete and ambiguous examples.
Review answers and evidence
Inspect the response and supporting source material. Improve knowledge that is missing, unclear or conflicting.
Go live and learn
Publish when ready, review real questions and turn useful gaps into better approved knowledge.
Keep human judgement
Define the boundary between a useful automated answer and a question your team should continue.
1. ADD APPROVED KNOWLEDGE
Start with the information you already trust.
Use the website, business and product sources your plan supports. Keep the source material clear, current and aligned with the answers your team would give.
Website pagesServicesPoliciesFAQsGuidesProduct feedsSpecifications
Approved knowledgeReady to test
Services12 pages
Policies6 pages
Product records2,184 rows
Support guides23 pages
ONLY PUBLISH VERIFIED SOURCE TYPESConfirm the exact inputs supported by your chosen plan during setup.
2–4. SHAPE, TEST AND REVIEW
Use the questions customers actually ask.
Clean demo questions are not enough. Test vague descriptions, combined requirements, policy edge cases and missing information.
- Does the answer use the right source?Review the basis, not only the wording.
- Does it recognise uncertainty?Look for a clarification or safe handoff when evidence is incomplete.
- Does it feel like the business?Adjust tone, detail and the next step.
PRIVATE TEST QUESTION
“Will this replacement work with the older AX-420 unit in our plant?”
Expected behaviour: request the attributes needed to verify compatibility
More detail needed
I cannot confirm that from the model number alone.
Please share the voltage, connection size, operating temperature and available length. The flange pattern may also need specialist confirmation.
REVIEWER CHECKNo unsupported compatibility claim · useful next question · source gap visible
5. GO LIVE AND LEARN
Publish deliberately. Improve from real conversations.
Review what customers ask, where the answer succeeds and where clearer knowledge or a better handoff would help.
Keep proven guidance available whenever customers need it.
Improve missing or conflicting source material, then test again.
Keep the question and context when judgement belongs with the team.
A FEW GOOD QUESTIONS
Let’s clear things up.
Still deciding? Start free and test the questions that matter to your business.
Do I need to put Helper live straight away?
No. Use the private test environment to add knowledge, try real questions and review the evidence before adding it to the customer journey.
What knowledge can I add?
Supported sources depend on the product and plan. Typical categories include website pages, services, policies, FAQs, guides and product catalogue information.
How do we know an answer is ready?
Check the answer against the expected content, inspect the supporting source, verify the boundary and test the important variations customers may ask.
What should we test first?
Start with high-value sales questions, repeated support enquiries, ambiguous wording and questions where a wrong answer would create the most risk.
YOUR CUSTOMERS ALREADY HAVE QUESTIONS
Start privately. Go live when the answers are ready.
Bring your approved knowledge and a handful of difficult questions. The first goal is not an account — it is an answer you would be happy for a customer to receive.