End-user guide

Using CommuniQore to handle customer conversations

CommuniQore helps you create a chatbot based on your own business knowledge, install it on a website, share it as a public chat page, or connect it to WhatsApp, Telegram, and Messenger.

This documentation is written for business owners, operations admins, customer service teams, and marketing teams. It focuses on daily chatbot usage, not SaaS platform, server, or tenant administration.

Where to Start

1. Create a Bot

Define the bot name, primary language, answering style, welcome message, and answer rules.

2. Add Sources

Add FAQs, website URLs, sitemaps, or documents so the bot has material to answer from.

3. Sync

Run sync so CommuniQore reads the sources and builds the knowledge index.

4. Publish

Install the widget, share the public chat page, or connect the bot to external channels.

Frequently Used Menus

Menu Used for When to open it
Chatbot > Manage Bots Create and manage bot identity, language, answer rules, appearance, social links, and widget installation. When creating a new bot or changing bot behavior.
Chatbot > Sources Add manual FAQs, website pages, sitemaps, and knowledge documents. When the bot needs to learn new information or update its answers.
Chatbot > Channels Connect a bot to Telegram, WhatsApp, or Messenger through webhooks. When the bot should be used outside the website.
Chatbot > Credit Balances View the remaining available credits. When you need to make sure the bot can continue processing chats.
Chatbot > Top Up Credits Buy or add credits. When the credit balance is running low.
Chatbot > Credit Transactions View credit top-up and usage history. When checking usage or doing internal reconciliation.

Creating Your First Bot

1

Open Manage Bots

Go to Chatbot > Manage Bots, then create a new bot record. The bot name appears in the widget and public chat page, so use a name customers can recognize, such as Store Assistant or CommuniQore CS.

2

Choose status and language

Use Draft while preparing the bot. Once the knowledge sources are complete and test results look good, change it to Active. Choose Default Language for the initial chat language, then set Knowledge Languages to the languages that actually exist in your sources.

3

Set answer scope

Answer Scope controls how freely the bot may answer questions.

  • Strict Sources: the bot answers from available sources. This is the safest choice for product, service, pricing, policy, or procedure information.
  • Contextual Relevance: the bot still prioritizes sources but can answer more flexibly when the context is clear.
  • Broad Assistant: the bot can help more generally. Use it only if you are comfortable with answers that may not always come from your business documents.
4

Write messages and instructions

Welcome Message appears when the chat starts. Fallback Message appears when the bot cannot find an answer. System Instruction defines tone and boundaries, for example: answer politely and briefly, do not invent prices, and direct customers to an admin if data is unavailable.

5

Complete appearance and contact links

If needed, upload a Background Image for the public page and fill in WhatsApp, Instagram, Facebook, TikTok, or LinkedIn links. These links help customers continue contact after the chat session.

Tip: enable Show References and Require Reference for Knowledge Facts if your team needs to see the source of answers. This helps evaluate knowledge quality.

Adding Knowledge Sources

Sources are what the bot reads. Answer quality depends heavily on the sources you provide. Open a bot from Manage Bots, then use the Sources tab or section, or open Chatbot > Sources directly.

Manual FAQ

Use this for frequent questions, such as ordering steps, operating hours, payment methods, warranty, shipping, or admin contact.

Fill each item with Question and Answer. Write final answers that are ready for customers to read.

Single Page

Use this to take information from one website page, such as an FAQ page, product page, or policy page.

Fill Entry URL with the full URL of the page the bot should read.

Website URL

Use this when knowledge is spread across multiple pages. Choose Single URL for one address, or Import Sitemap to read a list of pages from a sitemap.

When using a sitemap, enter a URL such as https://example.com/sitemap.xml.

Document Upload

Use this for internal documents or service material. Supported formats during sync: PDF, TXT, MD, HTML, and HTM.

Make sure the document contains clear text, not only scanned images.

Source Sync

After a source is created or updated, run Sync Source on that source. If a bot has many sources, use Sync All from the bot detail.

Watch Latest Sync Status, Data Created, Data Total, and Last Synced At. If the data total is still empty, the bot probably does not have enough material to answer.

Testing Bot Answers

Basic test questions

  • Ask about information that exists in the sources.
  • Ask wording variations for the same question.
  • Ask something that is not in the sources to check the fallback message.
  • Check whether references appear if Show References is enabled.

If answers are not right yet

  • Improve the source content, not only the bot instruction.
  • Create manual FAQs for answers that must be precise.
  • Sync sources again after changes.
  • Use a stricter Answer Scope to reduce answers outside your data.

Publishing the Bot

Open Manage Bots, choose the bot, then click Install Widget. CommuniQore shows Script Embed, Iframe Embed, Public Chat Page, readiness checklist, runtime stats, allowed domains, and preview.

  1. Make sure the bot status is Active.
  2. Fill Allowed Domains with the website domains where the widget will be installed, such as example.com or app.example.com.
  3. Choose the widget position: bottom right, bottom left, top right, or top left.
  4. Enable movable if visitors may drag the chat icon.
  5. Copy the embed script and install it on your website.

Use the Public Chat Page if you do not have a website yet or want to share the chatbot directly as a link. This page displays the bot name, host, chat mode, primary language, social links, and chat area.

Open Chatbot > Channels, create a new channel, choose a bot, then choose the channel: Telegram, WhatsApp, or Messenger.

Because channel setup involves external providers, follow the Channel Setup section below in order. Do not activate the channel before token, webhook, and setup checklist are complete.

External Channel Setup

A channel connects your CommuniQore bot to an external chat app. The flow is always the same: create the channel in CommuniQore, fill the token from the provider, copy the webhook from Setup, install the webhook in the provider, then test by sending a message.

Recommended General Order

  1. Make sure the bot has knowledge sources, has been synced, and has status Active.
  2. Open Chatbot > Channels, then create a new channel.
  3. Choose the Bot to connect.
  4. Fill Channel Name with something easy to recognize, for example Main WhatsApp CS.
  5. Choose Channel: Telegram, WhatsApp, or Messenger. Provider follows the selected channel.
  6. Keep status Disabled while token and webhook are incomplete.
  7. Fill the provider token field, then save the channel.
  8. Click Setup on the channel row to see the Webhook URL, Verify Token, readiness checklist, and provider guide.
  9. Install the Webhook URL in the external provider.
  10. When the readiness checklist is green, change the channel status to Active and send a test message.

Telegram

Telegram is the simplest channel for testing because it only needs a Bot Token.

  1. Create a Telegram bot through BotFather.
  2. Copy the Bot Token from BotFather.
  3. In CommuniQore, choose the Telegram channel.
  4. Fill Access Token / Bot Token with the Telegram token.
  5. Save the channel, then click Setup.
  6. Open the Telegram setWebhook link once to register the webhook.
  7. Change channel status to Active.
  8. Send a message to the Telegram bot to test it.

WhatsApp Cloud API

WhatsApp requires configuration from Meta Developer and a WhatsApp Cloud API phone number.

  1. Prepare an app in Meta Developer and enable the WhatsApp product.
  2. Get the Access Token from Meta.
  3. Get the Phone Number ID from the WhatsApp API configuration.
  4. In CommuniQore, choose the WhatsApp channel.
  5. Fill Access Token and WhatsApp Phone Number ID.
  6. Fill Verify Token with your own secret text, such as an internal random code.
  7. Save the channel, then click Setup.
  8. In Meta Developer, enter the exact same Webhook URL and Verify Token.
  9. Subscribe to the required message events in Meta, then activate the channel in CommuniQore.

Messenger

Messenger connects the bot to a Facebook Page through the Meta Graph API.

  1. Prepare a Facebook Page and an app in Meta Developer.
  2. Enable the Messenger product in the Meta app.
  3. Get the Page Access Token.
  4. In CommuniQore, choose the Messenger channel.
  5. Fill Access Token with the Page Access Token.
  6. Fill Messenger Page ID if available.
  7. Fill Verify Token with your own secret text.
  8. Save the channel, then click Setup.
  9. In Meta Developer, enter the exact same Webhook URL and Verify Token, then subscribe to message events.
Field Telegram WhatsApp Messenger
Access Token / Bot Token Bot Token from BotFather. Access Token from Meta WhatsApp Cloud API. Page Access Token from Meta Messenger.
Verify Token Not required. Required. Must match the Verify Token in Meta Developer. Required. Must match the Verify Token in Meta Developer.
Phone Number ID Not used. Required. Taken from the WhatsApp API configuration. Not used.
Page ID Not used. Not used. Used for the Facebook Page/Messenger.
API Base URL Optional. Leave empty to use the Telegram default. Optional. Leave empty to use the Graph API default. Optional. Leave empty to use the Graph API default.

Reading the Readiness Checklist

The Setup modal shows a readiness checklist. If any item is yellow, the channel is not ready yet.

  • Bot is active: bot status must be Active.
  • Channel is active: channel status must be Active after configuration is complete.
  • Webhook secret generated: the unique webhook URL is available automatically.
  • Access token filled: the provider token has been filled.
  • Phone Number ID filled: for WhatsApp, Phone Number ID must be filled.
  • Verify token filled: for WhatsApp and Messenger, Verify Token must be filled and must match the value installed in Meta.

Daily Maintenance

Update knowledge

Whenever prices, schedules, procedures, promos, addresses, or policies change, update the source and run sync again.

Monitor credits

Check Credit Balances and Credit Transactions regularly so the chat service does not stop when traffic increases.

Review customer questions

Record questions the bot often fails to answer, then add manual FAQs or clearer documents.

Go-Live Checklist

Bot status is Active.
Welcome message and fallback message match your brand voice.
At least one active source has synced successfully.
Important test questions are answered correctly.
Allowed domains include the target website domain.
Credit balance is enough for initial usage.
If using an external channel, webhook URL and token have been installed in the provider.

Common Issues

Issue Likely cause What to do
The bot says it does not know Sources are incomplete, inactive, or not synced yet. Check Sources, add FAQs or documents, then run Sync Source.
The bot answers too freely Answer Scope is too loose or general knowledge is enabled. Use Strict Sources and require references for business facts.
The widget does not appear on the website The script is not installed correctly or the domain is missing from Allowed Domains. Copy the embed script again and check the allowed domain list.
External channel does not receive messages Webhook URL, token, channel status, or provider data is incomplete. Open Setup on the channel and follow the readiness checklist.
Chat stops or fails to process Credits are depleted or the bot configuration is not active. Check Credit Balances, Top Up Credits, and bot status.
Core principle: a good bot is not created once and then abandoned. Maintain its knowledge sources the same way you maintain FAQs, catalogs, and customer service SOPs.