A useful assistant needs reliable business information. Start with the questions customers actually ask, publish the answers clearly and give the assistant that content. Adding a chat icon alone will not fix missing delivery terms or an unfinished product description.
1. Put the answers on your website
List five common questions: choosing a product or service, availability, delivery areas, returns and how to contact you. Make sure the answers appear on published pages or catalogue-visible product pages. Link to the policy rather than scattering different versions across your site.
TradeGear synchronizes the public pages and products you enable. Drafts, private or password-protected pages, hidden products and WooCommerce cart, checkout and account pages stay out of the assistant’s knowledge base. You can exclude particular published pages too. Keep unfinished or internal material private.
2. Connect WordPress and enable the assistant
- Install the TradeGear WordPress plugin. Create or sign in to your TradeGear account, verify your email and add your website.
- Use your website’s connection code in WordPress setup. The plugin retrieves site-specific credentials; you do not paste a chat key or a synchronization key.
- Start on Free with 20 completed assistant replies per website every 30 days. Growth includes 20,000 translation words and 100 completed assistant replies a month for US$19/month per website. Both plans include translation and your own AI assistant.
- Enable the assistant and knowledge synchronization for that website. Choose public pages and, if you use WooCommerce, the public catalogue. Wait for a successful synchronization status before testing knowledge.
- Check that the chat launcher appears on your website and opens the conversation. Test on a phone as well as a desktop.
Translation languages and conversation language are related, but separate: a visitor should be able to explore the site and ask a question in their language. Test both experiences. The WooCommerce translation guide covers publishing a translated storefront.
3. Try questions with known answers
Choose one product or service and ask a specific question whose answer is on its published page. Try it in your source language and a second language. Follow any source link and compare the answer with the page.
- “Which size is suitable for outdoor use?” — only if your published description answers it.
- “Do you deliver to my country?” — compare the reply with your delivery policy.
- “How do I return this?” — check the time limit and conditions.
- “Can you offer a discount that is not listed?” — it should not invent an offer.
- Ask about something you do not sell — it should acknowledge the gap instead of making up a product.
The assistant uses the knowledge your website supplies. Synchronizing a product catalogue does not connect private order history. For a personal purchase enquiry, do not treat an email address or order number alone as proof of identity, and do not promise access to order status unless that access is actually configured.
If the model has been idle, the first answer may take longer. Check that a pending answer completes rather than submitting the same question repeatedly. A correct, sourced answer matters more than a confident sentence.
4. Keep the answers current
Published content changes are queued for synchronization, and a weekly full check rechecks the public knowledge. WordPress cron must be running. After changing an important price or policy, check synchronization status and repeat the relevant question.
A completed reply counts once; a conversation can contain several replies. Watch reply usage for each website. When information is missing, improve the source page and check the next synchronization before assuming the assistant has learned the change.
Keep a clear contact route available for customers whose questions need a person. AI answers can be inaccurate, so review important business claims and avoid promising unattended resolution of every request.