Add Messaging Features to Your App With Dittofeed Embedded Components

Everyday, somewhere in the world, a SaaS product team reimplements the same set of messaging features

A handful of the most common:

📝 Code and low-code template editors for email and SMS
🛤️ Journeys for event-triggered messaging workflows
🔊 Broadcasts for one-off sends
⏱️ Real-time user segmentation engine

This is particularly true for vertical SaaS

Consider the example of an app for healthcare providers: the providers may want to automate SMS to patients when a prescription refill is available. Or maybe there's an app for property managers that needs to let managers email tenants when a lease is up for renewal. It’s a non-trivial lift to build this suite of tools. Engineering teams regularly take 6-12 months to implement them, not to mention the ongoing maintenance requirements.

Let's stop doing this

Engineers' time is valuable, and a company's development speed is often it's greatest asset.

If messaging software isn't your core business, building it is going to slow you down and take you off-course. So why not embed messaging in your app? Dittofeed’s Embedded Components wrap up features from its existing open-source messaging automation, allowing them to be embedded within your own application.

‍

Embedded Components can be consumed using styled iframes, unstyled react components, or by using Dittofeed as a headless API to rebuild your own components from scratch.

There's no need to keep building this stuff. It's hard and boring.

‍