Sendbird provides the social layer for an application: in-app chat, plus voice and video calling, as a service rather than something a team builds from scratch. The argument for using it rests on scope discipline. Whatever the product is, engineering effort belongs in the core of that product, not in reimplementing a second one alongside it.
A booking and customer-management tool for dental practices illustrates the point. The hard part is making something that fits how dentists actually work and getting the UX right; messaging may matter a great deal, but the team is building dentist software, not chat software. Chat is also more demanding than it looks — it is not simply relaying a message from one user to another and rendering it. Modern expectations include reactions, replies and notifications, resilience on poor networks and in offline conditions, and moderation and social controls such as blocking and reporting. Sendbird covers that surface, and its UIKit handles the interface construction. On scale, the company's position is straightforward: build on Sendbird and it will scale.

Communication as a product requirement
Consider a typical practice: it texts, emails, calls and posts on social media to reach patients, yet the only channel available in the other direction is a phone call. The alternative — a quick digital chat to book an appointment, ideally with a browser button for a voice call or a video consult — changes the buying decision. Users of modern apps expect these features to be present.
Compliance and trust
Software sold into regulated fields has to satisfy many standards, and any dependency inherits that obligation. Sendbird states it is compliant with HIPAA/HITECH, SOC 2 and GDPR, among others, and describes itself as heavily security-focused. The vendor is established rather than new, with Reddit, Virgin UAE, Yahoo and Meetup among its customers.
Sendbird's client base gave us confidence that they would be able to handle our traffic and projected growth.
Ben Celibicic, CTO



