Most businesses do not start with a messaging strategy. They start with a single problem: users are not receiving verification codes, or a campaign needs to reach ten thousand people before the weekend. Over time those isolated needs turn into a stack of tools that do not talk to each other. This guide walks through the services available on UIPAPP, what each one is actually good for, and how they fit into a single account.
Bulk SMS: reach without an app install
Bulk SMS remains the simplest way to put a message directly in front of a customer who has not installed your app and may not open email. It is a good fit for appointment reminders, delivery updates, payment notices, service outage warnings and time-limited promotions.
On UIPAPP you can send bulk messages from the web panel or through the REST API. The panel suits marketing teams who work with uploaded contact lists; the API suits anything triggered by your own systems — an order status change, a subscription renewal, a support ticket update. For high-volume senders, an SMPP connection is available on request, which is typically the right choice when you are pushing sustained traffic and want a persistent binary session rather than HTTP calls.
Coverage spans more than 200 countries, including Turkey, Cyprus and European markets. Delivery rules, sender ID requirements and pricing vary by country and operator, so it is worth confirming the specifics for each market you plan to enter rather than assuming one setup works everywhere.
OTP SMS: a different traffic profile entirely
One-time passwords look like SMS, but they behave nothing like marketing traffic. A promotional message that arrives four minutes late is mildly annoying. A login code that arrives four minutes late is a failed signup, an abandoned checkout, or a support ticket.
UIPAPP handles OTP traffic on prioritised routing with a template system, so verification messages are not queued behind campaign volume. A few practices make a measurable difference regardless of provider:
- Keep the message short and put the code near the beginning, where it is visible in the notification preview.
- Use consistent templates so users learn to recognise your messages and operators can classify them correctly.
- Set a sensible expiry — long enough for slow networks, short enough to limit replay risk.
- Rate-limit resend requests on your side, both to control cost and to blunt abuse.
Real-time delivery reports and webhook callbacks let your application react to what actually happened. If a code fails to deliver, you can surface a fallback channel to the user instead of leaving them staring at an empty input field.
IVR voice calls: when a message must be heard
IVR voice calling is available on UIPAPP as an optional, permission-based service. It is disabled by default on new accounts — the support team enables the IVR permission and defines per-country call pricing before you can use it.
Once active, the workflow is straightforward. You write your message in the panel and it is converted to natural-sounding Turkish speech using AI voice synthesis, or you upload your own MP3 if you prefer a recorded human voice or a specific brand tone. Messages can run up to 20 seconds. You then upload your number list, which is automatically cleaned of invalid and duplicate entries, and launch the campaign. Afterwards you get reporting on who answered and how many seconds of the message they listened to — a useful signal that plain SMS delivery receipts cannot give you.
Voice tends to earn its place in scenarios where reading is unlikely or unreliable: overdue payment reminders, urgent operational notices, event-day changes, or reaching demographics that answer calls more readily than they read messages.
Reseller sub-accounts
Agencies, software vendors and integrators often need to serve several end customers from one platform without giving everyone access to the same balance and logs. The reseller model addresses this with sub-accounts, where you define per-customer limits, permissions and pricing.
Practically, that means each client gets an isolated workspace and its own reporting, while you keep control over what they can send, how much they can spend and what they pay. It removes the need to build a billing and permission layer yourself before you can start reselling.
White-label custom domains
The white-label option lets the panel run under your own domain, so customers log in to your brand rather than a third-party one. Combined with sub-accounts, this is the difference between reselling someone else's product and operating what looks like your own messaging platform. It matters most when messaging is part of a broader service you sell — a CRM, a booking system, a logistics tool — and brand consistency affects perceived value.
How the pieces fit together
A typical progression looks like this: OTP SMS secures signups and logins through the API; bulk SMS handles transactional and campaign traffic from the panel or via scheduled API jobs; IVR covers the small share of critical notifications that need to be heard rather than read; and sub-accounts plus white-label turn the whole setup into something you can offer to your own clients.
Everything runs on a prepaid credit model — no subscription, and you pay per message or per call. Credits can be topped up with Visa, Mastercard or USDT (Tether). Support and account questions are handled over WhatsApp, Telegram or info@uipapp.com.
If you are unsure which combination fits your traffic, the sensible first step is to test one channel with real volume in one market, look at the delivery reports, and expand from there.