Where to Ask Product Questions¶
Use this page to route BFDev docs chatbot follow-up questions to the product channel that owns the persistent product problem domain. Prefer the domain channel first. Use a sub-domain or topic-specific channel when the question clearly fits that narrower ownership, such as telematics within Operations & Dispatch.
Keep the visible text human-readable: use Slack channel labels. When the channel URL is known, make the label a link to the channel archive, such as [#product-example](https://betterfleet.slack.com/archives/C0123456789). Do not link to message threads or invite URLs.
Runtime config is a machine representation of this mapping. It can copy the label and channel URL from this page, then add the Slack channel id needed for posting.
Domain Channels¶
Use these channels when the ontology domain is the right level of ownership.
| Domain | Slack Channel |
|---|---|
| Smart Charging | #product-energy-charge-management |
| Energy & Cost Management | #product-energy-charge-management |
| Operations & Dispatch | #product-operations-dispatch |
| Roaming & Shared Charging | #product-roaming-shared-charging |
| Incidents & Notifications | #product-incident-management |
| Reporting & Insights | #product-management |
| Resilience & Security | #product-resilience-security |
| Accessibility & Usability | #product-management |
Sub-Domain and Topic Channels¶
Use these channels when the question clearly belongs to a narrower product area than the domain-level route.
| Domain | Sub-domain or topic | Slack Channel |
|---|---|---|
| Operations & Dispatch | Telematics, geo-tracking, live vehicle location, vehicle data feeds | #product-telematics |
Product Fallback Channels¶
Use these channels when the product context is clearer than the ontology domain, or when the domain route is uncertain.
| Product context | Slack Channel |
|---|---|
| BF Plan | #product-bf-plan |
| BF Manage | #product-bf-manage |
| Cross-product or unclear product ownership | #product-management |