Skip to content
Balkan Tecnologia
AccessibilityGet in touch
Balkan Tecnologia

Notifications and WhatsApp triggered by events in your system

We connect events in your system to email, SMS, push and WhatsApp messages, with templates, each person's preferences, opt-out and delivery reports.

A mint-green thread running underneath a blank white slab the size of a phone.

Who it's for

For companies that notify customers about orders, payments or appointments and still send some messages by hand.

What it solves

  • The customer has paid, but the confirmation only goes out when someone remembers to send it.
  • Each part of the system sends messages its own way, with different wording.
  • Someone asked to stop receiving messages, and they keep arriving.
  • Nobody knows whether a message was delivered or failed.

What we do

Event-driven sending
An order created, a payment confirmed or a deadline approaching triggers the message set up for that type of event.
Message templates
Texts with variables, versioned and reviewed; for WhatsApp, submitted to Meta for approval through your account.
WhatsApp Business Platform
Integration with Meta's API, directly or through a provider, using your company's account.
Preferences and opt-out
Each person chooses channels and topics; anyone who opts out is removed from every send of that type.
Consent record
When and how each person agreed to receive messages, stored with the LGPD in mind.
Delivery and failures
Delivery status per message, a retry on another channel where it makes sense, and sending limits.

What you get

  • A notification service in production, connected to your system's events
  • A versioned template library, with Meta approvals tracked
  • Preferences and opt-out available through an API for your app
  • A report of deliveries, failures and opt-outs per channel
  • Automated tests for the events that trigger messages

How we do it

  1. Inventory

    Which messages exist today, who sends them, on which channel and with what wording.

  2. Accounts and providers

    The WhatsApp Business account and the email and SMS providers, checked with you.

  3. Development

    Events, templates, preferences and reports, tested in the sandbox.

  4. Template approval

    WhatsApp templates submitted to Meta before go-live; rejected ones are rewritten.

  5. Follow-up

    Deliveries, failures and opt-outs checked during the first weeks.

Technology examples

  • WhatsApp Cloud API
  • Amazon SES
  • SendGrid
  • Firebase Cloud Messaging
  • RabbitMQ
  • PostgreSQL

In Brazil, we handle

WhatsApp Business Platform
Meta's platform for businesses to send and receive WhatsApp messages.
LGPD
Brazil's General Personal Data Protection Law (Law 13,709/2018).

Related services

FAQ

Can we use this for mass marketing blasts?

That is not what this service is for. It sends messages tied to events in your system to people who agreed to receive them. We do not send to bought lists.

Who pays for WhatsApp messages?

Your company, on its own account, directly with Meta or through the chosen provider. Pricing and template approval rules are Meta's; we take them into account in the design.

Do we need an intermediary provider?

Not necessarily. Whether to use Meta's API directly or through a provider depends on volume, the support you want and the other channels the provider already brings together.

How is the recipient's consent handled?

Every opt-in and opt-out is recorded with its date and source. The legal basis for each type of message is a decision for your legal team; the system applies whatever is set.

Write to Balkan

Talk to us about your project