Standard Tier ($50)
<div class="post-category"><span class="cat-badge cat-tiers">Tiers</span></div>
<p class="lead"><strong>The Standard tier at $50 adds multi-channel messaging and a higher DZIT allowance to the Basic feature set. It remains fully API-hosted — no local install.</strong></p>
<h2>Overview</h2>
<p>Standard targets small businesses that need email plus Telegram coverage and slightly richer analytics. It still runs entirely from the main node.</p>
<h2>Key components</h2>
<ul><li>Email + Telegram surfaces</li><li>Expanded lead and ticket views</li><li>Higher DZIT monthly allowance</li><li>Optional light affiliate tracking</li><li>No local software required</li></ul>
<h2>Related</h2>
<ul><li>[Basic Tier ($20)](/post.php?slug=tier-basic)</li><li>[Pro Tier ($100)](/post.php?slug=tier-pro)</li><li>[Commercial Tiers](/post.php?slug=credit-tiers)</li></ul>
Powered by BizNode™
Related Posts
Add a Command to Your Bot in 10 Lines of YAML
Adding a new bot feature used to mean editing Python, wiring a `CommandHandler`, and redeploying. With the Feature Manifest Framework it is four steps and about ten lines of YAML — and you get a slash command and a paid network handle from
How 1BZ Bots Define Features via Manifest
1BZ bots used to hand-wire every capability as a Python `CommandHandler`. That put even a trivial command one code change and a redeploy away from production. The Feature Manifest Framework replaces that with a declarative YAML file at `bot
Slash Command vs Handle — what each is for
Slash commands and handles are related but not identical. A slash command is the owner-facing UI inside a single bot; a handle is a network-facing service endpoint that any other bot, workflow, or API on the 1BZ network can call. The same u