Bosca / Communications

Bosca Communications

Talk in real time.
Reach them with care.

Two ways to reach people β€” real-time chat channels, and transactional email and push. Every notification renders from a template, respects the recipient's preferences, and reports back whether it actually arrived.

How it works

Converse, render, deliver.

01

Converse or notify

Open a real-time chat channel for people to talk in, or send a notification on email and push β€” both first-class parts of the platform.

02

Render per person

A transactional email pulls its event template and renders at send time with the event's data β€” personalized down to the unsubscribe link, no redeploy to change a word.

03

Deliver with respect

Every notification clears the recipient's preferences and the suppression list first β€” and afterward you can see whether it reached each person, or why it didn't.

What makes it powerful

Live conversation and reliable delivery

The immediacy of real-time chat and the reliability of preference-aware email and push that you know got delivered β€” under one roof.

Real-time channels

Direct, group, and public chat channels, delivered live over subscriptions, with membership and roles.

The real-time toolkit

Threaded replies, emoji reactions, typing indicators, and presence β€” the whole conversation, live.

Email and push

Transactional email through SendGrid and push to iOS and Android β€” often from a single message.

Event templates

An event key resolves to a rendered template at send time, so changing an email never needs a redeploy.

Delivery you can see

See whether each message was delivered, deferred, bounced, or dropped β€” so a silent failure never slips by.

Preferences that stick

Per-person, per-channel, per-type opt-outs β€” while transactional and security messages always get through.

Quiet hours

Push honors a timezone-aware do-not-disturb window; urgent and security notifications still break through.

Automatic suppression

A hard bounce suppresses the address on its own, and suppressed addresses are skipped before they reach the provider.

Delivered with care

Every send earns its delivery

Nothing goes out unchecked. Before a notification reaches the provider, it clears the recipient's channel and category preferences, a do-not-disturb window for push, and the suppression list β€” and only then does it go out.

  • One gate decides every send: allow, hold for quiet hours, or suppress β€” with the reason recorded on the delivery record.
  • Preferences are per person, per channel, per type β€” and the ones that matter, transactional and security, can't be turned off.
  • A hard bounce adds the address to the suppression list automatically; future sends to it are skipped, not attempted.
  • Afterward you can see the outcome for each recipient β€” delivered, or the reason it wasn't.
message Β· checkout-receipt
preference Β· transactionalallowed
suppression Β· not listedok
quiet hours Β· n/aβ€”
sent Β· delivered

Reach people the right way

Real-time channels for the conversation, reliable email and push for the moments that matter β€” each one rendered, gated by preferences, and delivered to the person it's for.