Shared Bot Group Requirements and Troubleshooting
Most Shared Bot Group problems come down to a handful of causes. This article covers what the shared bot needs in order to join your group, and what each error means.
The Two Requirements
A shared bot joins your group by itself, so your group must be genuinely free to join:
- Open enrollment. Anyone must be able to join without an invitation. The bot will never receive or accept an invite.
- No membership fee. A joining fee would be charged to the bot's own account, so the bot will not join.
🔹 You can switch your group to open enrollment with no fee, add it to LifeBots, then change it back. The bot only needs the group open at the moment it joins.
Error Messages and What They Mean
| What you see | What to do |
|---|---|
| This group is invite only, so the bot cannot join it | Set the group to open enrollment in your Viewer, then try again. Alternatively, ask a group officer to invite the bot and then mark the group as joined. |
| This group charges a L$ membership fee, so the bot cannot join it automatically | Set the group's join fee to L$0, then try again. |
| No Shared Bots Available | Every shared bot is offline or full right now. Try again shortly. |
| The selected bot is offline | Choose a different shared bot, or wait for that one to come back online. |
| The selected bot has reached its group limit | Second Life caps any avatar at 50 groups. Choose a different shared bot. |
| The selected bot is not connected to a channel right now | A temporary connection problem. Wait a few minutes and try again. |
| Insufficient Wallet Balance | Add funds to your LifeBots Wallet, or use Pay In-World. |
Moving Your Group to a Different Shared Bot
If your group is on a bot that is often busy or offline, the group can be moved to another shared bot. The new bot joins your group first, and the old one only leaves once that has succeeded, so your group is never left without a bot.
The move will be refused if the new bot is offline, already has 50 groups, or if your group is no longer open enrollment with no fee.
🔹 Contact support if you want a group moved and you cannot do it from your dashboard.
Services Are Not Working
If the bot is in your group but nothing is happening, check these in order:
- Is the group expired? Check the group on your dashboard. Expired groups have all services stopped until renewed.
- Is the service actually enabled? Open the group's services and confirm the one you expect is switched on. You are only charged for enabled services, and only enabled services run.
- Is the bot still a member? Look at your group's member list in world. If the bot is missing, it may have been ejected, or it left when the group expired.
- Does the bot have the right group role? Sending notices and inviting members need group powers. Give the bot's role permission to send notices and invite members.
🔹 Important: Group Notices and Group Greeter/Inviter both depend on group role powers that only a group officer can grant. If the bot is a member but cannot send notices, this is almost always the cause.
The Greeter Is Not Inviting Anyone
The Greeter service needs a Group Inviter Device rezzed on your land. The shared bot is not standing there, so without a device nothing detects your visitors. Work through these in order:
| Symptom | What to check |
|---|---|
| Nothing happens at all | Is a device rezzed and not in your inventory? It registers itself on rez. |
| Device menu says No groups available | Group Inviter is not enabled for the group on the website. Enable it there first, then touch the device and use Reload Config. |
| Device is rezzed but no group is chosen | Touch it, click Select Group, and pick your group. |
| Only some visitors get invited | Each action has a repeat limit. If it is set to once, returning visitors are skipped on purpose. |
| Visitors are missed | Raise the detection range. It defaults to 5 metres and can go to 100. |
| One person never gets invited | Check they are not on the ignore list, and that they have not already hit the repeat limit. |
| Invites arrive but the role is wrong | Check the group role selected for Group Invite on the website. |
| Nothing works and you want proof | Touch the device and click Test Invite. It sends you whatever you configured, which isolates the device from the settings. |
🔹 The bot still needs group role powers to send invites. A device that reports success while nobody joins usually means the bot's group role cannot invite members.
Still Stuck?
Open a support ticket from the LifeBots website and include your group name, which services you enabled, and the exact message you saw. That is usually enough for support to resolve it without further questions.