Skip to content
TablaDevelopers

Tabla · طبلة

One API for every notification your users get

Push, SMS, e-mail, WhatsApp and an in-app inbox behind one server-to-server API. Your backend says who gets which template with which data; Tabla picks the channel, renders it in your user's language, sends it, retries, falls back and tells you what happened.

Five channels, one call

Each template carries its text per channel and per language. Name the channels, or let Tabla choose over the ones your template has.

  • Push

    Firebase Cloud Messaging for Android and iOS, with your own Firebase project and your own data keys.

  • SMS

    Your registered sender name, only to the countries you allow, with delivery receipts.

  • E-mail

    From your own domain, once its DKIM and SPF records are published.

  • WhatsApp

    Your Meta-approved templates through the WhatsApp Cloud API.

  • In-app inbox

    A per-user inbox your apps read through your backend, with unread counts and read state.

Three lanes, so a campaign never delays a sign-in code

Every message goes on a lane by its template's category. The lanes never wait for each other.

  1. OTP

    Sign-in codes go first, ignore quiet hours, and never go to push or the inbox.

  2. Transactional

    What answers something your user did: a booking, a payment, a reply.

  3. Bulk

    Marketing and low-priority sends, throttled per second so they never crowd out the others.

Fallback chains and retries

Ask for PUSH then SMS: when every device of the user is gone, Tabla marks them dead and sends the SMS. A provider outage is retried after 30 seconds, 5 minutes and 30 minutes before the chain moves on, and each attempt is in the delivery log and in your status webhooks.

Built in Egypt, for Egypt first

  • Arabic first

    Templates in Egyptian Arabic and English. Each user gets their own language, and the other one when theirs is missing.

  • Arabic-Indic digits

    Numbers in Arabic text render as ٠١٢٣٤٥٦٧٨٩; codes stay in Western digits, so phones can fill them in.

  • Cairo time, DST included

    Days, usage and quiet hours follow Africa/Cairo, summer time and all.

  • Quiet hours

    Marketing waits until the user's quiet hours end; transactional push goes silent; sign-in codes always go.

From sign-up to your first message

  1. Create an account

    With your work e-mail: a one-time code signs you in, no password.

  2. Apply for a tenant

    Tell us about your company, your channels and your volume. We review every application.

  3. Build

    Create API clients, templates and your webhook in the console, then send.

Tabla is named after the Mesaharaty's drum, which has woken Egypt for suhoor for centuries.