Sequences

Sequences sends messages for you. A sequence messages each person as they act: a welcome after a signup, a nudge after three quiet days. A broadcast sends one message to a whole audience at once.

Email, SMS, WhatsApp, or push, through your own provider.

Write a template

The message, personalized for each person.

Build a sequence

A trigger, a message, a wait. About 15 minutes.

Read results

How a sequence performs, and what happened to one message.

The parts of Sequences

In the sidebar	What it is
Sequences	Your automatic flows
Segments	Groups of contacts defined by rules, to target
Templates	Messages you write once and reuse
Broadcasts	One message to a whole audience
Message log	Every message sent, and what happened to it
Settings	Your channels, your sending hours, and what you track

Your contacts and their events live in Analytics. Sequences uses the same people.

You build sequences inside FounderHQ. FounderHQ still needs a way to put each message on the wire. That is what a connection does.

FounderHQ does not resell sending. You connect your own provider account, so messages leave from your domain, your number, or your WhatsApp sender. You keep your provider's pricing, your sending reputation, and your compliance paperwork.

Connecting a provider gives you three things:

Delivery. Sequence steps on that channel start sending.
Status back. Delivery receipts, opens, and clicks flow into FounderHQ, so a later step can branch on what happened. How much you get depends on the provider.
A choice per step. When a brand has more than one connection for a channel, a sequence step can name which one to send through.

To add one, open Sequences → Settings and press Connect channel.

Channels and providers

Channel	Providers
Email	Resend, Postmark, Amazon SES, any SMTP server
SMS	Twilio, and ready-made recipes for Telnyx, Plivo, Sinch, Exotel, and MSG91
WhatsApp	Meta Cloud API, Twilio, and ready-made recipes for 360dialog, Gupshup, icpaas, and Interakt
Push	Firebase Cloud Messaging, Apple Push Notification service (APNs), Expo, and web push for browsers
Anything else	A REST API connection you define yourself

Two kinds of connection

Built-in providers. Resend, Postmark, SES, SMTP, Twilio, Meta WhatsApp, Firebase, APNs, Expo, and web push. FounderHQ speaks each API directly. You paste credentials and a couple of settings.

REST API connections. Everything else. FounderHQ builds the HTTP request for each message from a template you control. A recipe fills that template in for a provider FounderHQ already knows: you type a few fields and the request, the response mapping, and the delivery callback are set up for you. A recipe connection runs on exactly the same machinery as one you build by hand, so you can always inspect what it sends.

What FounderHQ can report per channel

Channel	Sent	Delivered	Opened / read	Clicked
Email	Always	From the provider's feedback. Plain SMTP has none.	Yes. FounderHQ tracks opens itself	Yes. FounderHQ wraps links itself
SMS	Always	Where the provider reports delivery receipts	No	No
WhatsApp	Always	Where a status webhook is wired	Yes, with that same webhook	No
Push	Always	No	Yes, when your app has the FounderHQ SDK. Not on a REST API connection	No

Email tracking is per step. A Service message tracks neither opens nor clicks unless you turn them on, and you can turn either off on any step.

A branch on "delivered" only works when the connection can report it. The builder offers only the states your channel and connection can reach, and publishing stops with an error if a condition uses one they cannot.

Pick your channel

Send from your own server

A connection also sends messages your backend decides on, like a receipt or a password reset. One request sends one message to one contact. See Send a message from your server.

Your backend can also put a person into a sequence. See From your own server.

AI agent or LLM? Read this page as markdown

Start here

Connect a channel

Write a template

Build a sequence

Send a broadcast

Who receives messages