Quick documentation

A practical, lightweight version. More visuals, video, and deeper guidance can be added later.

Quick onboarding

  1. Create the customer account.
  2. Enter the business details (hours, prices, services, address, policies).
  3. Connect the channels you want (Telegram / WhatsApp / Webchat …).
  4. Upload knowledge files or connect data sources to build RAG.
  5. Test the replies and the human-handoff scenario.
  6. Go live.

Service principle

  • We reply to inbound customer messages only—we do not run broadcast campaigns or mass marketing.
  • Replies are grounded in your company knowledge (RAG) to reduce mistakes and hallucinations.
  • If the answer is unclear, the assistant asks a clarifying question or escalates to a human.

Telegram setup

  1. Open Telegram and search for @BotFather.
  2. Send /newbot and follow the steps to create the bot.
  3. Copy the Bot Token.
  4. In OwlRespond, enter the token and attach it to the correct tenant/business.
  5. If you want to manage a channel, add the bot as an admin in that channel.
  6. To obtain a Channel ID, forward a message from the channel to the bot and read forward_from_chat.id from the updates.

Advanced channel/group/topic guidance can be added later.

WhatsApp setup (recommended option: Cloud API)

The official and safer route for business use is WhatsApp Cloud API through Meta.

  1. Prepare Meta Business Manager and complete business verification if required.
  2. Create an app on Meta Developers and add the WhatsApp product.
  3. Connect the business number inside your WhatsApp Business account (WABA).
  4. Collect the values you need for OwlRespond:
    • Phone Number ID
    • WABA ID
    • Access Token (preferably a managed system-user token)
  5. Configure the webhook so incoming messages and delivery events reach OwlRespond.

Important: following WhatsApp policies—opt-in, the 24-hour window, and anti-spam rules—is essential to reduce the risk of number restrictions.

QR-code fallback (only when Cloud API is not viable)

  • A fallback option can connect through a QR-based session tied to a device/app.
  • This path remains the customer’s responsibility and may carry restriction risk if platform rules are violated or spam is suspected.

Ready to start?

Begin with your business details and channel connections—and we can help you shape the knowledge base and reply behavior.

Go to the signup page