Bell2go product datasheet
What it is, who it is for, differentiators, outcomes, subscription process, architecture, and security boundaries.
Download datasheet ↓See the system.
Plan the pilot.
Use these materials to align school leadership, operations, dismissal staff, families, and IT around one measurable pickup plan.
00:42 product overview
Featured overview
Watch the coordinated pickup journey.
See parent arrival, sibling readiness across buildings, capacity-aware campus flow, and safe loading in under one minute.
Download the videoResource library
Material for every conversation.
Parent App account flows
Review self-registration, delegate enrollment, phone recovery, legal notice, and pending school approval.
Open mobile preview →One trip for siblings
Understand how Demo Student A and Demo Student B can be prepared independently across two buildings and verified together.
See the workflow →Identity is not authorization
Review public SSO, local accounts, mandatory MFA, school relationships, trip context, and human verification.
Review security →Frequently asked questions
Questions teams ask before a pilot.
Does Bell2go change the school’s traffic route?+
No. The approved entrance, one-way circulation, lanes, loading zones, pedestrian paths, and exit are hard operating constraints. The system can rebalance capacity only inside that plan.
How does the system handle siblings?+
One family trip contains multiple student readiness records. Each building prepares its student independently, and the vehicle advances only when the shared handoff rule is satisfied.
Is AI releasing students?+
No. AI can forecast congestion and recommend timing, routing within approved choices, or staffing. Authorized staff verify and release every student.
Can parents use personal email accounts?+
Yes. Google, Microsoft, Sign in with Apple, and local accounts are supported. Apple private relay addresses are accepted. MFA is mandatory, and pickup authorization is resolved separately from the identity or email.
What happens if GPS, a camera, or the network fails?+
Every dependency has a staffed fallback: manual queue entry, QR/NFC or staff verification, fixed routing, cached active-trip context, and explicit degraded-mode indicators.