Channels and delivery

SaleSprint can reach people five ways: in-app (the bell), push (a phone alert), email, SMS and WhatsApp. They do not all work equally well.

What you have to set up

Almost nothing. Email, text messages and push all go through SaleSprint’s own messaging service. There is no SMTP server to configure, no API key to paste and no sender domain to verify.

The flip side is that you cannot change any of it either:

Messages go out under SaleSprint’s name, not yours

The “from” address on emails and the sender name on text messages belong to the platform. There is no setting anywhere that makes a notification come from your shop’s own address or sender name.

There is a per-branch sender-id box in settings. It is read and then discarded — messages always go out under the platform sender regardless of what you put in it.

Push notifications

Push works automatically, with no setup by the business.

1. Sign in on a phone.
2. The phone asks whether to allow notifications. Tap Allow.
3. That is all — the phone registers itself and starts receiving.

If you tap “Don’t allow”, push is off for good and nothing tells you

There is no warning anywhere in SaleSprint, no indicator, and no way to ask again from inside the app. You have to turn notifications back on for SaleSprint in your phone’s own settings.

This matters more than it sounds: push is the only thing that refreshes the bell, so a phone with push denied will show a stale notification count all day.

On Windows and Linux desktops there is no push at all, silently. On the web version it depends on how the app was built. Use the inbox and pull to refresh instead.

Uninstalling the app stops push automatically.

WhatsApp

WhatsApp notifications never arrive

The WhatsApp channel for notifications is not built. Every attempt fails immediately.

If you see WhatsApp offered as a channel in your preferences or on a policy, do not choose it — nothing will be sent, and nothing will tell you so.

This is only about notifications. WhatsApp broadcasts are a completely separate feature and do work.

Do notifications use up message credits?

Mostly no, and that is a trap in both directions.

What is sent	Uses credits?
Notifications — approvals, alerts, reminders, statements	No
Marketing broadcasts	Yes
A sale receipt texted or emailed to a customer	Yes

So running out of SMS credit does not stop your business notifications going out. It also does not stop receipts.

Running out of credit does not block anything — it goes negative

Credit is deducted after a message has already been sent, and when there is nothing left the balance simply goes below zero rather than the send being refused.

You will discover you are out of credit by finding a negative balance, not by anything failing. Check Broadcasts → Resource credit ledgers rather than waiting to be told.

When a message fails

There are no retries, and nobody is told

A failed email or text message is recorded once and abandoned. There is no retry, no queue that drains later, and no alert to anybody.

A momentary problem at the messaging service means that message is simply lost.

And there is a subtler problem in the other direction:

“Sent” does not always mean sent

A message with no address to send to, or sent while the messaging service is not configured, is recorded as sent without ever being attempted.

“Sent” also never becomes “delivered”. SaleSprint learns only that the messaging service accepted the request — never whether it reached the phone or the inbox.

Can you check whether a message went out?

For notifications, no — nowhere in the app.

The record exists internally, with the channel, the address, whether it succeeded and any error. Nothing displays it. There is no screen, no export and no permission that reveals it.

Two menu entries look as though they should:

Message Templates and Delivery Log are managed by SaleSprint, not by you

Both sit under Notifications. Neither is a screen you fill in — each now explains itself when opened.

Message Templates says “Notification message templates are maintained by the platform. Use Notification Preferences to choose which alerts you receive.” You cannot change the wording of an alert; you choose which ones reach you, on preferences.

Delivery Log says “Notification delivery is handled by the platform. See your Notification Inbox for the messages you’ve received.” There is no per-message delivery report for alerts — the inbox is the record of what arrived.

For marketing broadcasts the picture is much better — those have a per-recipient report showing who was sent to, who failed and why. See Broadcasts.

Sale receipts sent to a customer fall between the two: they cost credits but leave no delivery record at all.

What is recorded internally

For completeness, since it affects how long things last: every notification sent to a signed-in person is recorded, along with one row per channel it was tried on, including ones deliberately held back by your preferences.

Messages sent to a customer who has no login leave no record whatever. So there is no trace that a customer statement or an order confirmation was emailed.

Related

• The bell and your inbox
• Your notification preferences
• Broadcasts