# Onboarding New Members Effectively

Your onboarding process determines whether new members stay active or quietly disappear after their first week. A smooth, welcoming, and technically successful first experience converts curious newcomers into committed network participants.

## The Onboarding Journey

1. **Discovery** - They learn the network exists
2. **Acquisition** - They obtain hardware
3. **Configuration** - They get the node on the network
4. **First contact** - They exchange messages with another member
5. **Deeper engagement** - They explore features, attend events, consider contributing infrastructure

## Hardware Recommendations

Standardize on 1-2 recommended hardware options. Prices below are approximate single-unit retail as of mid-2026 and vary by retailer and region. Current recommended starter kit:

- **Budget option:** Heltec WiFi LoRa 32 V3 (~$32 single-unit; sub-$20 only in bulk/multipacks) - USB-C, built-in OLED, no GPS. Good for indoor/desktop use.
- **All-in-one option:** LILYGO T-Beam (roughly $30-45 depending on retailer/region) - GPS built in, battery connector, excellent for portable use
- **Premium:** RAK WisBlock Starter Kit (~$60-80, depending on bundled modules) - Modular, excellent build quality, best for fixed outdoor installations

## Pre-Configured Firmware Distribution

- Create a saved configuration file with your community channel key, frequency preset, and node naming convention pre-filled
- Host it on your community wiki or website
- Flash firmware at [flasher.meshtastic.org](https://flasher.meshtastic.org), then share your channel settings separately via a Meshtastic channel QR code or URL (meshtastic.org/e/#...). The web flasher loads firmware onto the device; it does not bake your channel config into the firmware link - that is a separate step.
- Document: "Flash this firmware, scan this channel QR code, done." - Two steps maximum.

## First-Week Checklist for New Members

- Node powered on and flashed with community firmware
- Channel key loaded (via QR code scan or manual entry)
- Node name set to community naming convention
- Sent a test message received by at least one other member
- Joined community Discord/Signal channel
- Node visible on your community map (note: a node only appears on meshmap.net if MQTT uplink is enabled, which private community channels usually keep off - so absence from meshmap.net is not a failure)

Assign a "buddy" - an experienced member who agrees to be on-call for a new member's first week. A quick DM check-in on day 3 dramatically improves retention.

## Managing Stale and Orphaned Nodes

Every network accumulates abandoned nodes - nodes still visible on the map but owned by someone who has moved on. Management strategies:

- **Annual "node census"** - Message all known node operators, ask for a check-in. Non-responders after 30 days are marked as inactive.
- **Last-heard tracking** - Meshtastic shows a "last heard" timestamp per node in the app. Some community map tools then style nodes not heard in 30+ days differently; that styling is a property of the map software, not the Meshtastic firmware itself.
- **Node decommission policy** - Backbone/shared infrastructure nodes require formal handoff if an operator leaves. Document the process.