Outbound communications for startups: doing it properly

Sending a message costs almost nothing, which is precisely why so many startups send too many of the wrong ones. The goal of outbound communication is not to maximise sends; it is to reach the right person with the right content at the moment it actually matters to them. Volume is easy. Relevance is the hard part, and it is the only part that builds a lasting relationship with your audience.

What outbound communication means in practice

Outbound communication is any message your product or team initiates without waiting for the customer to ask first. It includes onboarding emails, SMS alerts, re-engagement nudges, product announcements, and transactional confirmations. The category is broad, but the common thread is that you are requesting attention you were not directly given.

That distinction carries weight. When someone fills in a form or sends a support request, they have already chosen to engage. When you reach out first, you are making a claim on their time, and the implicit question every recipient asks is whether the message was worth it. A well-timed, relevant message builds trust incrementally. An irrelevant one erodes it, and several irrelevant ones in a row teach people to ignore everything you send, including the messages that matter.

A smaller list of people who genuinely want to hear from you will always outperform a large list of people who merely tolerate you.

Choosing the right channel

Each channel carries a different social contract with the recipient, and the best choice depends on the urgency, the nature of the content, and the level of interruption the message warrants.

• Email suits longer content, documents, invoices, onboarding guides, and anything that benefits from being archived or read at the recipient's own pace. It is asynchronous by design, and recipients expect to manage it on their own schedule.
• SMS is appropriate for time-sensitive, genuinely short messages: a one-time PIN, a delivery confirmation, a critical account notice. Because SMS is intrusive and carries a direct cost, every word must justify its place.
• Messaging platforms such as WhatsApp feel personal and conversational, which means an irrelevant message damages trust faster than the same message would by email. Reserve this channel for high-signal interactions where the conversational format adds real value.
• In-app notifications reach users only while they are already engaging with your product, which makes them the least intrusive option and often the most contextually relevant for product-related prompts.

A practical rule: choose the least intrusive channel that will still reach the person in time, and move to a more direct channel only when the message genuinely warrants the interruption. Using multiple channels without a clear rationale for each one trains users to tune out all of them.

Permission, consent, and POPIA

South Africa's Protection of Personal Information Act governs direct marketing, and its obligations are not complicated in principle, even if their application to a specific product requires careful thought.

You need a lawful basis for processing personal information. For direct marketing to existing customers, that basis may be legitimate interest, subject to conditions the Act sets out. For unsolicited electronic marketing to people who are not yet your customers, the Act requires prior consent. When you collect that consent, record what was agreed to, through which channel, and when. A vague "I agree to communications" buried in a terms acceptance is not the same as a clear, specific opt-in for marketing messages.

Every outbound marketing message must include a clear, functional way for the recipient to opt out. When someone unsubscribes, honour it promptly and do not contact them for marketing purposes again. Keep your suppression list clean and synchronised across every tool you use. An unsubscribe that gets lost in a system migration is a compliance failure, not merely a poor user experience. The Information Regulator of South Africa enforces these obligations, so before you launch any direct marketing programme, confirm your specific requirements with a qualified legal professional.

Beyond compliance, asking for permission properly is simply better product practice. People who opted in deliberately are more likely to engage, less likely to mark you as spam, and more likely to trust you when it matters.

Email deliverability: reputation before content

You can write the most useful email your audience will ever receive and it will still end up in a spam folder if the infrastructure behind your sending domain has not been set up correctly. Deliverability is an infrastructure problem before it is a content problem, and it is one your technical team or email service provider needs to solve before your first real campaign goes out.

The foundation of deliverability is domain authentication. Without it, mailbox providers have no reliable way to verify that a message claiming to come from your domain was actually sent by you. The three authentication standards that form this baseline are Sender Policy Framework, DomainKeys Identified Mail, and Domain-based Message Authentication Reporting and Conformance. Together, they tell receiving mail servers which senders are authorised to use your domain, allow recipients to verify that a message was not tampered with in transit, and instruct mailbox providers on what to do when a message fails those checks.

Setting these up correctly involves publishing specific records in your domain's DNS configuration, generating cryptographic keys through your sending service, and gradually tightening your policy as you confirm that all your legitimate sending sources are passing authentication. Your email service provider will have documentation for their specific setup, and a developer familiar with DNS can complete the work in a few hours. The important point is that it must be done before you build a reputation, not after you discover your messages are not reaching inboxes.

Beyond authentication, sender reputation accumulates over time through your behaviour. Remove hard-bounced addresses from your lists immediately, because a high bounce rate signals to mailbox providers that your list is poorly maintained. Never purchase or scrape email lists; they are full of invalid addresses and traps that poison your reputation quickly. Send at a consistent cadence rather than in large infrequent bursts, which look suspicious to spam filters. Monitor your complaint rate as well, because a spike in recipients marking your mail as spam is an early warning that something is wrong with your targeting, your content, or the permissions you relied on.

Lifecycle messaging over broadcast campaigns

Sending the same message to your entire list at once is the default approach because it is easy, not because it is effective. The alternative is lifecycle messaging: communications triggered by what a specific person has or has not done in your product.

Consider the difference in relevance. A new user who signed up yesterday and has not yet completed a key setup step needs onboarding guidance. A user who completed that step and has used your core feature several times does not need the same onboarding guide; they need to be introduced to the next meaningful capability. A user who has not logged in for thirty days needs a re-engagement message that acknowledges their absence and makes a case for returning, not a feature announcement written for active users.

Effective lifecycle sequences are built around a small number of meaningful events: account created, first action completed, a key milestone reached, an inactivity threshold crossed, a subscription approaching its renewal date. For each event, decide whether a message is genuinely useful to the person at that moment, then automate it to fire based on behaviour rather than a calendar. This takes more effort to build than a newsletter blast, but it produces results that compound over time because the messages stay relevant as your user base grows and diversifies. Even simple segmentation based on plan tier or feature usage amplifies this further, letting you write messages that feel specific to the recipient's situation rather than generic to everyone on the list.

For a broader view of how messaging fits into the full customer journey, see customer engagement for startups.

Measuring what matters

Delivery rate tells you whether your messages are reaching inboxes at all. Click rate tells you whether recipients found the content relevant enough to act on it. Conversion rate, meaning whether the person did the thing the message was designed to prompt, is the figure that connects outbound effort to real business outcomes. These are the numbers worth tracking carefully.

Email open rates deserve a specific caution. Apple's Mail Privacy Protection and similar features in other mail clients now pre-fetch message content automatically, which means an open can be recorded even when the recipient never actually looked at the message. Open rates are no longer a reliable signal of genuine engagement, and optimising aggressively for them in isolation produces misleading conclusions. Use them as a rough directional indicator at most.

Reply rate matters more than most teams appreciate, particularly for transactional and onboarding sequences. A reply is a strong signal of genuine engagement and often surfaces product feedback you would not otherwise receive. Make sure your reply-to address is monitored and that someone is responsible for responding. Track unsubscribes and spam complaints per campaign too; a spike in either is an early signal that something is wrong, whether with the content, the targeting, the sending frequency, or the basis on which you obtained permission in the first place.

Where Formgang fits in

Good outbound communication starts with good capture: knowing who your users are, what they care about, and what they have already told you. Formgang is Lambdaserve's customer-engagement product, built around forms and flows that turn visitors into customers. It is designed to capture intent at the moment it exists and to collect the permission and context that makes outbound communication relevant rather than intrusive. For more on how the capture stage connects to your communication strategy, see lead capture with forms and flows.

Getting your data foundations right also matters for compliance. The POPIA and security foundations post covers what responsible data handling looks like across your technical stack.

Written by the Lambdaserve team as general, informational guidance for founders and engineers. It is not legal, financial or tax advice. Third-party product names, programmes and logos belong to their respective owners and are referenced for identification only.