> For the complete documentation index, see [llms.txt](https://university.obvious.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.obvious.in/working-with-features/building-help-and-support/how-to-design-discovery-for-support.md).
# How to design discovery for support
## đ Introduction
Getting this right will reinforce the userâs trust in your product. If Support is hard to access in a moment of frustration for the user, you risk losing the user.
***
## 1ď¸âŁ App level
### Make it easy to find
This doesnât have to be an area to innovate.
1. **Mobile:** Place it in your Profile settings.
2. **Web:** Make it a floating action button, place it in a sidebar, or in the top right handâany place visible to the user regardless of what screen theyâre on.
### **Use recognisable icons**
Use icons that correspond to the type of Support youâre offering.
***
## 2ď¸âŁ Feature level
### Identify features where a user is likely to require Support
1. Time-sensitive actions (Eg: UPI payment)
2. Actions that trigger background operations (Eg: Food delivery)
**More examples:** shopping online, making payments to peers/merchants, scheduling accommodation, making travel bookings, and hailing rides.
Use the context you already have about this feature to narrow down the issue more quickly.
***
