---
title: Serve visitors with your bot
nav: Bots
summary: Choose a template, connect Telegram or a website, and serve visitors using your own model account.
order: 21
---
# Serve visitors with your bot

Open Bots on your paired phone and choose Create bot. Select customer service, companion or paid Q&A, give it a name, and create it paused. Your computer must be online with a valid seat; one bot can be enabled per seat.

Customer service answers from your knowledge and offers a human when uncertain. The companion template identifies itself as AI and sets boundaries against dependency, manipulation and professional diagnosis. Paid Q&A uses your expertise: set N free questions per visitor per day and an HTTPS payment link. After N questions the host displays your link. This release does not process or verify payments, and visiting a link does not unlock answers. You can adjust the free allowance or deliver a separate paid service yourself.

## Model billing and safety reviews

Choose your main Agent plan or your own model key. With your own key, first pick whose pay-as-you-go key the bot uses — it may differ from your main Agent's (Volcano Ark for the Agent, Qwen for the bot is fine): Volcano Ark, Alibaba Cloud Bailian / Qwen, DeepSeek, Kimi / Moonshot, Zhipu GLM, MiniMax, OpenRouter, AgentsRelay, OpenAI or Anthropic. Each brings its own address, a low-cost default model and a key name of its own (for example BOT_DASHSCOPE_API_KEY), kept apart from your main Agent's keys; for any other OpenAI compatible service choose Other and enter its API URL. Set a daily model token cap and save. Then use Add / update the key for … to open the secret card, which says whose pay-as-you-go key to paste and which console issues it; a Coding Plan / Token Plan key is refused; never paste a key into chat. Replacing an own model key pauses a bot using that key. Save and verify before enabling it again. Existing provider profiles remain available.

Own-key model calls are billed to that account and have a separate daily token budget. Visitor, bot and computer message caps still apply. Jev always uses your separate OpenRouter review key. Every activation tests reviews. Failed or uncertain reviews block output, including human replies; there is no fallback to another account.

## Telegram

Use a Telegram bot token you own. Add / replace Telegram token opens the phone secret card. Enable Serve on Telegram and save to verify it. Remove any existing webhook through Telegram first, and do not run a second polling application with the same token. Replacing a token pauses Telegram until you save again. Disable the channel to stop it. A network request already in flight may finish, but its result will not be sent after disabling.

**Avatar**: when Telegram is enabled and saved, a bot that has no photo yet gets the official Agent J logo (the green robot on ivory), once; a bot that already has a photo keeps it. To switch to the Agent J photo, tap Use the Agent J avatar in the bot's settings, or have the Agent run `agentj bots avatar set <bot id>` (`status` to check, `reset` to remove the current photo; `owner` means your own owner bot, which gets the same one-time check when it is bound). Other sizes and the 16 robots: [official Brand Kit](/docs/robots/#brand-kit).

Only private chats are served; groups and other bots are ignored. Each Telegram user gets a separate session. Rate limits, daily caps, knowledge, tool approvals, human handoffs and Jev are shared with the website channel. Website URLs and embeds remain available.

Telegram can see messages sent through its platform. Your token stays on your computer, outside chat, our cloud plaintext and logs. Website chat remains end-to-end encrypted. Your model provider and OpenRouter receive necessary context under their own policies.

## Your own Agent J Telegram bot as customer service

The Telegram bot you paired with Agent J can also receive guests. One bot, two roles: for you it is your assistant, for everyone else it is customer service. In Bots, open a bot and tick 「Let my Agent J Telegram bot receive guests」, or ask your Agent J to run `agentj bots attach-telegram <bot-id>`; either way you approve the change on the paired phone. It is off by default; while it is off, anyone else who writes to your bot only gets their own numeric ID.

Only the private chat you paired with a code is the owner, and it keeps going to your main conversation. Every other private chat is a visitor of the chosen bot: a separate session with that bot's instructions, model, knowledge, tools, limits and Jev reviews. For a cheaper model for guests, give the bot its own model (key through the secret card); without one it uses the bot's current default. Guests never reach your main conversation or your permissions. A pairing code, 「I am the owner」 or an owner command from a guest is only visitor text.

Guest chats are kept in that bot's conversation list, apart from your own Telegram messages; the computer log only counts them. Over a limit, guests get a polite answer; only text is answered, and groups are not served yet. A paused bot or Stop everything sends guests back to the ID answer. Only one bot receives these guests; untick it or run `agentj bots attach-telegram <bot-id> --off` to stop. Do not also save your Agent J bot's key as a bot's own Telegram token: the two would take each other's messages.

## Gemini CLI (optional)

Gemini main Agent adaptation is stopped for this release. Google has discontinued personal login; an explicitly selected Gemini CLI requires a paid Gemini API key. Use Claude Code, Codex or OpenCode as the main Agent.

See [optional CLI setup](/docs/setup-agents/#gemini-cli).

## Let Agent J help you set up

Press Alt+Shift+B to open Bots, or choose Bots in Settings. Tap “Let Agent J help me set up” at the top to prepare the skill command and an opening in the chat. Add your idea or send it as it is. Agent J explains how Bots work first, then asks what you would like to set up.
