Obriym CRMObriym CRMCustomer flow workspace
AIFeaturesGetting startedPricingRoadmapIntegrationsBlog
Sign inGet started
AIFeaturesGetting startedPricingRoadmapIntegrationsBlog
Buyer notifications · TurboSMS

The buyer with no email address still needs to know

BetaBeta: available to connect today; the channel’s capabilities are still being refined.

An order from a marketplace or a direct message arrives with a phone number and often no email. That customer never receives a single order email — a text reaches them.

Try it in a workspaceAll integrations

Who hears from you today

A shop tells its customers about their orders by email. Half those orders arrive through channels that carry no email address at all.

The customer from your site

Left an email at checkout and gets every update: received, paid, shipped, delivered.

The customer from a marketplace or messenger

Left a phone number. Without SMS they receive none of those messages — and call to ask what happened to the order.

What one message costs

SMS is the only channel in the product billed per message, so the bill should be clear before you switch anything on.

Latin text
160 characters — one message
Cyrillic text
70 characters — one message
Longer text
splits into parts, each billed separately
Obriym CRM's own texts
every one fits a single message in both languages

What the buyer actually reads

Each event is switched on separately. Nothing is sent by default.

  • Order receivedOrder 20260901-006 received. Thank you!
  • Payment receivedPayment for order 20260901-006 received. Thank you!
  • ConfirmedOrder 20260901-006 confirmed.
  • Being preparedOrder 20260901-006 is being prepared.
  • ShippedOrder 20260901-006 shipped. Tracking 20450612345678
  • DeliveredOrder 20260901-006 delivered. Thank you!
  • CancelledOrder 20260901-006 cancelled.
  • RefundedOrder 20260901-006 refunded.

What this channel does not do

Said plainly, so you do not pay for something you already get for free.

  • Nova Poshta already texts the recipient about the parcel at no charge. These messages are about the order, not the delivery.
  • The buyer cannot reply to an SMS: the channel is one-way and nothing from it lands in the Inbox.
  • No event is switched on by default — the workspace owner chooses.
  • Delivery to Ukrainian numbers.

What you need to start

  1. 1

    A token from the TurboSMS cabinet

    Under API. Stored encrypted and never returned to the browser.

  2. 2

    A sender name

    The name the buyer sees in the FROM field. You register it in the TurboSMS cabinet, and the operators moderate it over a few working days.

  3. 3

    Your choice of events

    Tick what is worth telling people about. The CRM shows the balance straight away, so you can see there is something to send with.

Frequently asked

Why SMS when the CRM already sends email?
An email needs an address. Orders from marketplaces and direct messages often arrive with a phone number only — that buyer receives no order email at all.
Does this duplicate Nova Poshta's texts?
No. The carrier writes about the parcel moving; the CRM writes about the order's state: payment received, confirmed, cancelled. You can leave the waybill event switched off entirely.
What does it cost?
You pay TurboSMS per message, and the price depends on how many parts it splits into. Every text Obriym CRM sends fits one part in both languages.
Who can switch sending on?
The workspace owner. A developer can save and test the token, but switching the messages on is the owner's call, because it is a spend and it reaches your customers.

Let every buyer hear about their order

Connect TurboSMS in a workspace and pick the events worth writing about.

Create a workspace
Obriym CRMObriym CRMCustomer flow workspace

Obriym CRM is a focused workspace for sales teams and e-commerce operations. Leads, deals, orders, and customer retention in one place.

Product by OBRIYM

  • crm@obriym.com
  • OBRIYM
  • Serhii Oberemchuk

Individual Entrepreneur Oberemchuk Serhii Oleksandrovych · State reg. 178752761226

Product

  • Commerce CRM
  • AI
  • Features
  • Getting started
  • Pricing
  • Compare
  • Blog
  • Roadmap
  • Integrations
  • API Reference

Company

  • About OBRIYM
  • Founder
  • Contact
  • Roadmap

Developers

  • For developers
  • OpenAPI spec
  • JS Widget
  • Lead intake API
  • Orders API

©2026Obriym CRM by OBRIYM. Built for production sales and e-commerce teams.

Terms of UseTerms of ServicePayment & RefundsPrivacy PolicySubprocessorsData ProcessingLegal detailsData DeletionPricingAPI Docs