AD SPACE AVAILABLE · BRAND PARTNERS WELCOME

How Customer Support Teams Configure Botsonic for Website and Document Knowledge Bases

365Finds Editorial
Indexed 11,430 Wiki articles

Put 365 Wiki to work with your AI

Copy the prompt below, paste it into the AI you already use, then ask your question.

Download full Skill

Try it with the prompt first. If you use 365 Wiki often, install the full 365Wiki Skill so you do not have to paste it again. No regular AI? Gemini or Microsoft Copilot on the web will work.

365Wiki Skill

Customer support teams facing seasonal spikes or expanding ticket volumes often encounter a difficult operational dilemma: generic rule-based chatbots frustrate users with rigid decision trees, while building proprietary Retrieval-Augmented Generation (RAG) pipelines demands engineering talent and infrastructure maintenance. Botsonic, developed by Writesonic, bridges this divide by providing a no-code conversational AI platform where support managers can turn existing product manuals, help centers, and live website URLs into an interactive support representative in under an hour.

Configuring Botsonic effectively requires more than dumping URLs into an upload field. To achieve high first-contact resolution (FCR) rates without generating inaccurate answers, support teams must structure their data sources systematically, define strict behavioral guardrails using Botsonic's Guidelines engine, and wire fail-safe escalation paths to human agents via Zendesk or Freshdesk.


1. Preparing and Ingesting Knowledge Base Sources

Botsonic indexes content from static files, public websites, and cloud documents to form its retrieval corpus. The accuracy of the AI model depends directly on how cleanly this information is structured before training.

Document Uploads (PDF, DOCX, TXT)

Support operations usually maintain standard operating procedures (SOPs), warranty policies, and technical troubleshooting manuals in document form. In the Botsonic dashboard under Sources > Files, administrators can drag and drop multiple documents simultaneously.

To optimize these files for retrieval accuracy:

Web Crawling and Sitemaps

For e-commerce stores and SaaS products with public help centers, manual document uploads quickly become stale. Under Sources > Links, teams can ingest:

Cloud Documents and Synchronization

Support teams collaborating across Google Workspace can share Google Docs or Google Sheets with Writesonic's service account (botsonic-training@writesonic.iam.gserviceaccount.com) and paste the sharing link directly into the platform.

On the Advanced and Enterprise tiers, Botsonic includes AutoSync, allowing teams to set automated crawl frequencies (every 1, 2, or 4 weeks). When policy pages or shipping terms change on your live site, the AI automatically ingests updated revisions without requiring manual retraining. Administrators can also click Sync Now to trigger an instantaneous re-index after releasing product updates.


2. Setting Guardrails and Behavioral Boundaries

An untrained AI tends to answer off-topic queries or formulate plausible-sounding speculations when information is missing. Customer support workflows demand predictable, compliant interactions. Botsonic provides several layers of control across Settings and Guidelines.

Core Engine and Response Controls

Within Settings > General and Settings > Messages:

Custom Guidelines for Tone and Operational Compliance

The Guidelines tab serves as the operational rulebook for the assistant. Support managers can create targeted rule blocks without writing system prompts:

Guideline CategoryConfiguration GoalConcrete Example in Botsonic
Tone & PersonaMaintain brand-aligned empathy and professionalism"Maintain an empathetic, supportive tone; never use aggressive or overly sales-oriented language."
Forbidden PhrasingPrevent robotic or dismissive AI clichés"Never reply with 'I do not have this in context'; say instead 'I could not find that detail in our knowledge base, let me connect you with our team.'"
StandardizationEnforce currency, time zones, and terminology"Always state prices in USD unless the customer explicitly requests EUR or GBP."
Verification LogicRequire order identifiers before giving account data"Before checking return status, always ask the customer for their Order ID and billing zip code."

For transactional capabilities, guidelines can bind to Actions using @action tags, triggering pre-built REST API calls to query Shopify order status, issue return labels, or update internal records.


3. Configuring Human Escalation and Ticketing

Even the most comprehensive knowledge base cannot resolve edge cases like chargeback disputes, defective item claims, or frustrated customers demanding immediate human intervention. Botsonic supports both automated live agent handoffs and asynchronous ticket creation.

+-----------------------------------------------------------+
|                     Customer Inquiry                      |
+-----------------------------------------------------------+
                              |
                              v
             +---------------------------------+
             |   Botsonic Knowledge Base RAG   |
             +---------------------------------+
               /                             \
     [Answer Found]                   [Escalation Needed]
            /                                   \
+-----------------------+           +-----------------------+
| Instant Resolution    |           | Trigger Live Handoff  |
| + Post-Chat CSAT Form |           | or Support Ticket     |
+-----------------------+           +-----------------------+
                                                |
                              +-----------------+-----------------+
                              |                                   |
                              v                                   v
                 +--------------------------+       +--------------------------+
                 | Zendesk Live Handoff     |       | Freshdesk Ticket         |
                 | - Real-time agent chat   |       | - Asynchronous ticket    |
                 | - Bi-directional sync    |       | - Fallback email routing |
                 +--------------------------+       +--------------------------+

Zendesk Live Agent Handoff

Under Integrations > Apps > Zendesk Live Agent Handoff:

  1. Install the integration and provide your Organization Subdomain, Zendesk admin Email, and a generated Zendesk API Token (created under Zendesk Admin Center > Apps and Integrations > Zendesk API).
  2. Once verified, when a user types "I want to talk to an agent" or when the bot fails consecutive queries, the chat interface displays a Start live chat with human button.
  3. The widget collects the visitor's name and email, generates a priority ticket in Zendesk, and routes incoming messages directly to live support agents. Agent replies sent from the Zendesk console appear in real time inside the customer's web chat window.

Freshdesk Ticketing Integration

For teams utilizing Freshdesk, navigate to Integrations > Apps > Freshdesk, enter your Freshdesk domain and API key (retrieved from Profile Settings > View API Key), and activate the module. When an issue requires investigation, the bot prompts the customer for issue details and logs a structured support ticket directly into Freshdesk queues.

Native Email Fallbacks and Conversation Transcripts

If your team does not operate a full-scale helpdesk suite:


4. Chatbot Styling and Website Deployment

Once knowledge sources and workflows are verified in Botsonic's built-in Test bot simulator, support leads can tailor the widget's visual identity under Appearance:

To publish on e-commerce platforms (Shopify, WooCommerce, BigCommerce) or web properties (Webflow, WordPress):

  1. Navigate to Integrations > Embed on your website.
  2. Select Javascript and copy the generated snippet.
  3. Paste the code into your site layout just before the closing </body> tag, or deploy via Google Tag Manager without engineering sprint cycles.
  4. If working with private portals, add your authorized production domains under the hostname whitelist settings to prevent unauthorized third-party embeds.

5. Subscription Tiers and Operational Trade-Offs

Deploying Botsonic effectively requires matching your operational requirements with the appropriate pricing tier:

By methodically preparing your documentation, enforcing behavioral guardrails through Guidelines, and connecting reliable human escalation channels, your support team can automate routine tier-1 inquiries, maintain brand trust, and preserve human agent bandwidth for high-value customer interactions.


References