Customer Portal

Your customers’ portal, with your brand.

An isolated, white-label self-service space where the operator’s end customers manage messages, campaigns, reports and technical access themselves. Routing, rates and permissions remain under the operator’s control.

The portal in pictures

Four views of the customer area.

Operator console

Real screenshots of the white-label customer area, with identifiers, numbers, message content and amounts masked. The displayed data is illustrative.

01 · Customer Portal · Overview

Customer area overview

The customer’s first view: message trends and the account’s financial position, with frequently used actions within reach.

Sent, delivered, delivery rate and failed
Traffic over the last 30 days
Account balance, credit limit and currency
Quick actions and recent messages

Illustrative sample data, with identifying information masked. The screenshot shows the console in its original language and direction.

02 · Customer Portal · Chats

Conversations by number

Conversations are grouped by phone number, with sent and received messages in the same view. No conversation is selected in this screenshot.

Conversations listed by number
Search by number or text
Filters by date and received reply
Sent and received message view

Illustrative sample data, with identifying information masked. The screenshot shows the console in its original language and direction.

03 · Customer Portal · Messages

Customer message log

A log of the customer’s own messages, with the status of each send. It shows what was delivered and how much was charged.

Filters by status and date
Recipient and sender
Delivery status
Message parts and price

Illustrative sample data, with identifying information masked. The screenshot shows the console in its original language and direction.

04 · Customer Portal · Reports

Traffic and spending reports

Statistics for the selected period, grouped by day and filtered by country, MCC and operator, with a daily chart and detail table.

Period and daily grouping
Filters by country, MCC and operator
Sent, delivered, failed and expired
Converted text, saved parts and total spending
Daily chart and detail table

Illustrative sample data, with identifying information masked. The screenshot shows the console in its original language and direction.

What the customer finds

Four areas, one sign-in.

Full list in the catalogue

Dashboard

Balance, invoices, payments and a traffic summary, available immediately after sign-in.

Sending and campaigns

Individual messages, campaigns, templates and contact lists.

Conversations and reports

Message history, conversations, inbound messages and reports by day, country and network.

Technical access

Sender ID requests, price list, SMPP credentials and API keys.

The customer checks balance, invoices and recorded payments alongside their traffic.

Campaigns

From list to message, without needing support.

The customer prepares, schedules and monitors their SMS campaigns in the portal.

Module details

RecipientsMultiple contact lists in one campaign, with exclusion lists.
SendingImmediate or scheduled; pause, resume and stop at any time.
PersonalizationName, birthday, gender and up to ten custom fields.
ImportLists of up to 200,000 rows with automatic column mapping.
BalanceAutomatic suspension and customer notification when the balance runs out.

Why it matters

Two sides of the same space.

For the operator

Customers handle tasks that otherwise need support: credentials, reports and sender ID requests.
Routing, rates and permissions remain with the operator: the portal displays, it does not decide.
The portal carries the operator’s name and logo, without further branding work.
Each customer sees only their own data: isolation is enforced by the server.

For the enterprise customer

Balance, invoices and recorded payments in one place, alongside traffic.
Campaigns and individual messages with history and reports; conversations are available for up to 180 days.
SMPP credentials and API keys available without submitting a request.
API keys stored only as hashes and revocable at any time.

White-label and isolation

Their space, your brand.

White-label

Your application name and logo on the customer portal and operator panel.

Isolated data

Isolation is enforced by the server: each customer sees only their own data.

Keys under control

API keys are stored only as hashes and can be revoked at any time.

Reports and conversations

What customers can check themselves.

Reports

Views by day, country and network.

Conversations

Conversation view for up to 180 days, including inbound messages.

Message history

Every sent message, available for the customer to inspect.

See what powers the portal.

The operator console manages routing, rates and permissions that the portal exposes to customers.

Operator console Portal modules