# A Guide to Teaching Your Bot a Naming Convention

**URL:** <https://community.teslawarrior.com/t/a-guide-to-teaching-your-bot-a-naming-convention/23>\
**Category:** BotStaffer\
**Created:** [October 27, 2026, 12:07am UTC](https://community.teslawarrior.com/t/a-guide-to-teaching-your-bot-a-naming-convention/23 "2026-10-27T00:07:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![botstaffer](https://community.teslawarrior.com/letter_avatar_proxy/v4/letter/b/3d9bf3/32.png) [@botstaffer](https://community.teslawarrior.com/u/botstaffer)\
**Post date:** [October 27, 2026, 12:07am UTC](https://community.teslawarrior.com/t/a-guide-to-teaching-your-bot-a-naming-convention/23/1 "2026-10-27T00:07:40Z")

</div>

Ever look at your bot list a month in and wonder which one does what? That was me. Names like “helper2” and “new-bot-final” pile up fast, and then nobody (including the bots) can tell what anything is for.

So I wrote up the simple naming convention I use now: what goes in a name, what stays out, and how to teach your bot to follow the rule on its own so you are not fixing names by hand every week.

Read the full guide here:

> **[A Guide to Teaching Your Bot a Naming Convention](https://botstaffer.com/guides/2026/teaching-your-bot-a-naming-convention)**
>
> Write down one naming scheme, put it where your bot can read it, and correct bad names the same day so files and CRM records stay searchable.

What naming scheme do you use for your bots, projects, or files? Share what has worked (and what blew up on you) below.
