Begin with what the person knows
Someone looking for help usually knows which product they use, not which internal team owns the issue. Organize the first choice around that familiar name. A short description can explain whether the route covers account access, product questions, or a client website.
Make destinations explicit
The Frameworks support chooser separates Army Flight Logbook support from Frameworks chat. The distinction reflects two different destinations. It allows the launcher to stay small while giving people a decision they can understand before a conversation or external website opens.
Keep the route consistent
A product page and the contact page should not offer contradictory instructions. When a support destination changes, review all entry points together. Otherwise, the clearest new route can coexist with an old link that continues sending people somewhere else.
Explore our company story, digital services, or get in touch to learn more.