This guide was originally published on the Hailbell blog .
Short answer: If you get a few messages a week, a mailto link or a contact form is enough. For most apps, a hosted chat SDK (Intercom, Crisp, Zendesk, Hailbell) is the right call: an afternoon to install, and it handles the inbox, push for replies and storage for you. Build your own only if chat is the product itself. Whichever you pick, the work that decides whether it helps is the same: a button where people get stuck, a signed user identity, context with every message, push for replies, and deletion when the account goes.
I build Hailbell, an in-app support chat for mobile apps, and use it in my own apps. The steps apply whichever SDK you pick. Swift examples use Hailbell's real API where it's named, and plain iOS code elsewhere. One section near the end covers where Hailbell fits, with its gaps, and the other SDKs.
Building for Android too? The same decisions, in Kotlin, are in how to add support chat to an Android app .
1.…