> For the complete documentation index, see [llms.txt](https://help.bots.business/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bots.business/import-and-integrations/store.md).

# Start from a Store bot or example

Install and inspect a Store bot, then adapt welcome messages, help replies and keyboard examples to your own bot.

The **Store** contains complete bot examples; **Libs** contains reusable code modules. Install a bot when you want a starting project. Install a library when you need one feature in an existing bot.

## Install and inspect

1. Open **Store** in the mobile app and choose a bot.
2. Read its description, developer information and available actions.
3. Tap **Install**. [Sign in](/start-here/sign-in.md) if prompted, then return to the selected Store bot to install it.
4. In the **Installed** dialog, tap **GO TO BOT**, or open the installed bot later from **My bots**.
5. Inspect its commands, libraries, Admin Panel and connection settings before starting it for users. Configure your own Telegram connection where required.

The images below use a fictional Store listing to show the controls. Choose a bot currently available in your catalogue.

<figure><img src="https://3310729168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVh0yg9olT-QWqi3AYt%2Fuploads%2Fgit-blob-c2ca966ede180021e50cd5a1bebb3ab684cc299d%2Fmobile-store-install.png?alt=media" alt="A demonstration Store bot card with Try now and Install"><figcaption><p>A demonstration Store bot card with Try now and Install</p></figcaption></figure>

<figure><img src="https://3310729168-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LVh0yg9olT-QWqi3AYt%2Fuploads%2Fgit-blob-fc2dee206ff625cd870148dbe9ac2b042eaf6d01%2Fmobile-store-installed.png?alt=media" alt="The Installed dialog with GO TO BOT for a demonstration installation"><figcaption><p>The Installed dialog with GO TO BOT for a demonstration installation</p></figcaption></figure>

For a bot with configuration fields, open its [Admin panel](/use-the-mobile-app/admin-panel.md), save the required settings, and test the result.

Store availability and each example's setup can change. An old Telegram demo link does not prove that the corresponding Store entry is currently installable. For exportable source, review a [Git export](/import-and-integrations/git.md); protected bots have different access limits.

## Welcome bot: greet a new member

The useful part of the older Welcome bot is reacting to Telegram's `message.new_chat_members` service message. In the current dispatcher, an update without command text reaches the `*` command. Create that exact command with empty **Answer** and **Keyboard** and **Wait for answer** off; a command named `/welcome` does not receive membership events automatically.

Follow the complete [Telegram updates receiver](/build-bot-behavior/telegram-updates.md) for the guarded welcome branch, required command setup and a group test. It handles missing usernames and preserves separate handling for contact, location and media updates. If you already have `*`, integrate its branches instead of replacing them.

Daily greetings are a separate [scheduled-command](/bjs-reference/background.md) task: polling every 50 minutes is not a guarantee of exactly one message per day.

## Help bot: answer a known phrase

For a small keyword reply in your master command `*`:

{% code title="Help bot: answer a known phrase · Example 1" overflow="wrap" %}

```javascript
if (typeof message !== "string") { return; }
const text = message.trim().toLowerCase();
if (text === "help" || text === "/help") {
  Api.sendMessage({ text: "Open the help center:\nhttps://help.bots.business/" });
}
```

{% endcode %}

Expand this into deliberate rules; a substring match can accidentally answer unrelated conversation. For Telegram's inline-search interaction, use the separate [inline bot guide](/bjs-reference/inline.md).

## Keyboard examples: contact and location

Use [Receive contacts, locations, photos and group events](/build-bot-behavior/telegram-updates.md) for a complete `/share` keyboard and `*` receiver. It includes the user's sharing choice, private-chat restriction, contact ownership check, location validation, saved contact/location properties and expected test results. Its media branches pass file IDs directly to the sender commands linked in the guide.

This keeps the useful scenario from SRB Demo Keyboard Tools together with the code that receives the resulting updates. A request button alone does not save a contact or location; a receiving command must handle those fields.

## BB Point Bot and other external example services

The historical BB Point Bot instructions described an external bot service with secret transfer URLs. That service's current account setup and contract are not established by the general Bots.Business code. Do not copy the old unrestricted transfer command or promise current exchange rates/extra iterations from that example.

If you already depend on it, check its current operator instructions and your account's secret/callback settings, then verify a non-production transfer path before using it. The general integration mechanism is [authenticated webhooks](/libraries-and-examples/webhooks.md); a webhook alone does not prove an incoming payment or grant permission to transfer points.

For a complete numeric-input example, use the [quantity dialog](/build-bot-behavior/quantity-dialog.md). For ordinary mobile command editing, see [Commands](/build-bot-behavior/commands.md).