Private status
Give each customer a browser-based view of their own journey without publishing the internal queue.
Guest communications
Keep the customer informed without exposing the operation.
Turnli separates the customer-facing journey from internal queue, floor, assignment, and management context. Guests get the update they need; staff keep the controls they need.
Customer layer
Private status. Clear operational updates.
The customer can follow their own journey while the business keeps internal order, notes, assignments, and capacity private.
GuestPrivate status
TeamInternal context
DeliveryExplicit state
ConnectedExact customer and workflow handoffs
TruthfulLive, stale and fallback states stay distinct
PrivateGuest and staff context stay separated
Plan-awareAvailability follows real entitlements
What this capability owns
Built around the operational job, not a feature checklist.
Turnli keeps the system responsible for the work as the authoritative place to act, while related screens carry the exact context into the handoff.
Operational messages
Send service updates such as check-in, readiness, reservation changes, or other transactional customer-care messages.
Delivery health
Keep delivered, failed, suppressed, and opted-out states distinguishable instead of silently treating every send as successful.
Consent boundaries
Keep SMS consent separate from general terms and preserve STOP/HELP and suppression behavior as provider integrations expand.
How the flow works
One customer journey. Clear steps.
The specific workflow changes by business type, but the operating principle stays the same: preserve intent, preserve context, and hand off deliberately.
Customer starts
Join, reserve, or staff check-in begins the journey.
Status stays private
The guest sees only information intended for that customer.
Team sends updates
Operational messages follow the business workflow.
Delivery stays visible
Failures and suppression can surface back to the team for review.
Product guardrails
Useful without pretending to know more than the system knows.
These boundaries are part of the product behavior, not just marketing language.
Transactional first
Turnli’s current SMS direction is customer care and service notification, not assumed marketing consent.
No internal exposure
Queue order, staff notes, table/station state, and other customers remain private.
Provider reality
Turnli should show when a message is failed or suppressed rather than implying successful delivery.
Buyer questions
What businesses usually need to know.
Availability and exact workflows can differ by plan and business type. The working demos are the fastest way to evaluate the current product behavior.
Do guests need to install an app?
No. Turnli is designed so basic guest status can work in the browser without requiring a dedicated guest app.
Does transactional SMS mean marketing permission?
No. Transactional service communication and marketing consent are different. Turnli’s current SMS direction keeps those boundaries explicit.
Can a business ignore STOP or suppression?
No. Suppression and opt-out behavior are safety and compliance boundaries, not optional convenience settings.
Keep evaluating
See how this capability connects to the rest of Turnli.
Turnli is designed as one operating system, so the highest-value proof is how the handoffs behave together.
Try Turnli
See the workflow before creating a workspace.
Open the browser-local demo, then start with the Free plan when you are ready to create a real workspace.