Feature scope - proposed scope
White Label Messaging App Features: Chat, Calls and Console
This page describes proposed scope for a build in this category, agreed in writing per project. Nothing here is a finished product, a fixed bundle or a fixed price.
Scope areas for this kind of build
Who Uses What: The Feature Set by Role
Six people touch the platform. Each gets a complete toolset, all of it served by one Node.js API.
The Member
- Joins with a phone number and a one-time code, or with email, Apple, Google or Facebook. The phone book is matched against your user base, contacts can be renamed privately, and strangers can be found by name or number. In a thread: ticks that move from delivered to read, a typing signal, online status, last seen and in-conversation search.
The Group Admin
- Creates a named group with a photo, invites people, promotes co-admins and removes anyone who should not be there. Groups can be opened to the public so newcomers find them. Inside a busy thread there are replies, emoji reactions, forwarding and polls whose tallies move as people vote.
The Caller
- Rings one person or a whole group by voice or video and gets a full incoming-call screen with a ringtone, even with the app closed. Each call lands in a history as missed, answered or declined, with its length, and the list can be narrowed by type.
The Desk User
- The browser client carries the full product rather than a trimmed view: the same threads, calls, stories and settings. One account holds several live connections, so a message lands on phone and laptop together and opening it in one place clears the badge in the other.
The Moderator
- Works two queues, one for reported people and one for reported groups. Every entry names the reporter, the target, the reason chosen and the conversation involved. An account or an entire group can be blocked, and reviewed items are flagged so colleagues skip them.
The Operator
- Reads fifteen live figures, sees who is online now and within the last half hour, checks the phone-versus-browser split and learns which sign-in route members pick, which tells you whether SMS codes deserve their cost. The same person edits branding, languages and integration keys through forms.
One Member's Path, From First Code to a Blocked Account
Seven moments, every one a working part of the platform and none a mock-up.
A code opens the door
- Sign-in runs on a one-time code sent to a phone or an email, or on a social account. No member password exists to leak. Which routes are offered is a console choice, not a development decision.
Friends appear
- The app matches numbers from the address book against your user base and shows who is already inside. A member can attach a private label to any contact, and can still search for people who are not saved.
Words travel over a live socket
- Messages ride a persistent connection instead of being polled for, so ticks, typing and presence are events that fire as they happen. Content is end-to-end encrypted: it crosses the network and rests in your database as ciphertext.
Media rides the same road
- Photos and clips come from camera or gallery, voice notes are recorded inside the app, and documents, GIFs, location pins and contact cards join them. Video is shrunk and given a thumbnail on the handset first, which keeps uploads moving on a poor signal.
Two people become a group
- A private chat and a group are one kind of object distinguished by a flag. Delivery, permissions, moderation and clean-up therefore follow identical rules, and there is no second code path to drift out of step.
A call rings through
- Audio and video travel straight between the two handsets using WebRTC. A relay steps in only where a strict network blocks the direct path. The ring itself is signaled over the connection that already carries chat.
A report leads to action
- The report arrives in the correct queue with a reason picked from your own list, the reporter and the conversation attached. The moderator blocks the account or the whole group, and the reviewed flag tells the next person to move on.
- A scheduled job runs every hour and deletes stories older than a day and pins past their expiry, so temporary content is actually removed and not merely hidden.
Why Each Design Choice Is in the Base Build
Every row is here because a messenger misbehaves without it, whatever the feature lists of other products say.
Sixteen interface languages arrive translated, right-to-left layouts included, and the console can add more. Wording is data read from the server, so a change needs no store resubmission.
The Technology Under the Feature List
Ordinary on purpose, so a capable Node and Flutter team can maintain it without needing us.
One Node.js application owns the rules, and the four clients only present them. Because there is one deploy and one schema, the surfaces cannot slowly disagree about what a message is.
Boundaries we state in writing for your build
White label here has edges. These are the boundaries, set down before purchase.
Not a hosted chat SDK or a tenancy
- End-to-end encrypted chat is part of delivery. The layer around the keys is separate scoped work: encrypted backup and restore across a new phone, and a recovery route for someone who loses theirs.
No payment processing or billing
- Neither is in an initial scope, and the right provider depends on your market. Paid tiers, in-app purchases or transfers between members are an integration against your own merchant accounts, quoted separately.
The hardening pass is still owed
- Before the public arrives you still need TLS termination, global rate limiting, upload size and type limits, secret vaulting, security headers, a locked-down console and a backup restore someone has actually tested. We complete it with you as scoped work.
Grow-into items and enterprise sign-on
- Corporate single sign-on with directory sync, a real-time adapter spanning several servers, media on object storage with a CDN, append-only audit logs forwarded to a SIEM, and outbound webhooks for bots. Each is quoted against your plan.
Your community stays your responsibility
- No members, contacts or phone numbers are supplied. Data retention, lawful-access duties, age and consent rules, moderation decisions, SMS sender registration and the privacy and telecoms law of each market you serve rest with you.
- Documentation is written for your engineers: requirements, the data model, an API reference, a developer and security handbook and a VAPT compliance reference. It is not a certificate, and nothing here claims to be one.
Weigh Omnistu against rentals, scripts and agencies
- Nine questions to put to any seller, the delivery steps, the warning signs and a modelled scenario are gathered on the Provider page.
Four surfaces. One API. Every setting in your hands.
iPhone, Android, browser and an operator console over a single Node.js application, with branding, languages, limits and rules held as configuration that your own team controls.
Omnistu is an independent software development project. We are not affiliated with, connected to, sponsored by, or endorsed by WhatsApp , or any other messaging, chat or calling service.
Discuss this scope by message
Tell us your market and audience, and we will respond with a practical read on scope.
team@omnistu.com