Who operates the platform? You do.
The platform is built to be run by your own commercial, operations and engineering teams. Below is what your team can do directly, what the platform automates, and the short list of work that genuinely involves BIND.
Who runs the platform after go-live?
Your team. Every recurring operational action lives in the management UI: onboarding clients and suppliers, connection settings, routing, filtering rules, pricing, credit control, invoicing, testing, alerting and reporting. After implementation and training, no BIND involvement is required to run the business day to day.
Do we need BIND to onboard a new client or supplier?
No. Supported connections are configured by your team: SMPP binds, HTTP credentials, IP allowlisting, session and throughput limits, delivery-report mapping. There is no per-connection platform charge, so onboarding is an operational decision, not a commercial one. Where an interface is not yet self-service, BIND performs the initial setup at no charge.
Can we change routing ourselves, in production?
Yes. Route creation and changes, priorities and weights, least-cost selection, MNP and HLR conditions, sender and content rules, retry and fallback behaviour, throughput limits, and enabling or disabling a route or source are all operational actions in the UI. Changes are recorded in the audit log with the user who made them.
Who maintains pricing and rate plans?
Your commercial team. Supplier price lists are imported in supported formats, including automatic imports, with price history and change alerts. Customer pricing runs across multiple rate plans with scheduled future pricing, percentage-margin pricing and negative-margin indicators. Nothing here goes through BIND.
Are billing and invoicing self-service too?
Yes. Prepaid and postpaid customers, multiple balances and currencies, manual adjustments, credit limits with automatic suspension, low-balance alerts, invoicing, taxes, payment terms, payment matching, reminders, netting, disputes and billing corrections are all handled in the platform by users with the right permissions.
A supplier degrades at 03:00. What happens?
Autopilot acts on the conditions you configured. It monitors delivery rates, route health, error patterns, latency, queue sizes and supplier connectivity, then reduces throughput, disables the route or source and activates the backup, then re-enables it on recovery. Alerts tell your team what happened; nobody has to be awake for traffic to keep moving.
Do we configure the automation ourselves?
Yes. Monitoring conditions, thresholds, test schedules and the resulting actions are yours to define per route, source or supplier. The platform automates decisions within your rules; it does not take decisions you have not authorised.
Does automation reduce visibility?
No. Every automated action is visible with the condition that triggered it, and alerting covers traffic start and resumption, delivery failures, error and status patterns, latency and credit thresholds. Dashboards and detailed records stay available for review afterwards.
Can we test routes without leaving the platform?
Yes. Send test traffic directly from the UI with configurable SMPP parameters, or build test cases and run them on a schedule. Results show delivery, measured latency, returned status and sender ID, and can drive Autopilot actions automatically.
How do we detect grey routes or faked delivery receipts?
Through testing against real handsets. BIND does not run its own test-node estate. The platform integrates established testing vendors and adds its own testing engine, so sender ID, content integrity and end-to-end latency come back into the platform and feed routing decisions. The testing provider itself remains your commercial relationship.
Do we need the full Number Intelligence Platform?
Only if you want number intelligence to be a product rather than an input. Messaging already includes the MNP and HLR resolution its routing needs, with your own suppliers and pricing. The full platform adds product creation, caching and cost optimisation, portability-driven workflows and external clients with their own connections and billing.
Can we add lookup suppliers ourselves?
Standard HTTP and ENUM suppliers are onboarded through the connection builder in the management UI, including pricing, imports and gateway configuration. SMPP sources are supported with assisted setup where required, at no additional platform charge. A supplier needing a non-standard adapter is integration work.
Who builds the products we sell?
You do. Products and the fields they return, protocol mappings, client-specific variants, cache retention per client or product, cleansing rules, routing conditions and client pricing are all configured in the UI, which is what makes launching a new number-intelligence product an operational task rather than a project.
What exactly is shared between the two platforms?
The operational and administrative layer, so the same client, supplier and finance records serve both platforms rather than being maintained twice:
- Clients & Suppliers
- Accounts & Access Control
- Commercial Management
- Finance & Billing
- Analytics & Monitoring
- Audit & Operational Control
- Roles & Multi-company Structure
- White-labelled Management UI
Country, network, MCC/MNC and prefix master data is shared as well. Either platform can still run entirely on its own.
Can different teams have different access?
Yes. Users, roles and permissions are managed by your administrators, with role-guarded dashboards, multi-company structures for group entities, IP-based access controls and audit logs across clients, suppliers, pricing, routing and platform configuration.
Can the platform carry our brand for our own customers?
Yes. The management UI supports your brand, colours and logo, your own domain and branded email notifications, so client-facing services run under your name rather than BIND's.
How much training does a team need?
An initial training allowance is included with the first production deployment, and training delivered during a POC counts toward it. Beyond that, courses are available on demand for commercial and operations teams and for engineering and NOC teams; optional, not a prerequisite.
Where can the platform run?
In a BIND-managed environment, in your own cloud, or on your own infrastructure where business or regulatory requirements demand it. BIND provides the infrastructure specifications and performs the deployment; customer-hosted deployments are subject to technical assessment.
Is the POC a demo environment or the real thing?
The real thing. The POC runs as a dedicated environment with setup, onboarding assistance, training and BIND network master data. On successful completion it can be promoted to production with its configuration, integrations, master data and endpoints intact.
Can we migrate our own data?
Yes. Self-service import of clients, suppliers, products and pricing using BIND templates is the standard path and carries no migration fee. Larger estates, custom routing logic, historical records or parallel running are assessed first and scoped as a migration project.
So what does actually require BIND?
A short and predictable list: platform deployment and upgrades, software defects, security and product updates, protocol or adapter development where a standard interface does not exist, parsers for unsupported price-list formats, direct MNP database integrations, custom integrations with your billing or ticketing systems, and assessed migrations.
Operational work you can perform yourself is charged only if you ask BIND to do it. It is never a dependency.
What if we would rather not operate it at all?
Then managed services cover it, at the level you choose: specialist support and escalation, co-managed operations alongside your team, managed day-to-day operations within your approved commercial policies, or a fully outsourced operational function. Commercial decisions stay with you unless explicitly agreed otherwise.
Is support available outside business hours?
Standard support runs during business hours, with software defects and platform maintenance included in the subscription. Extended support with contractual out-of-hours response targets and an availability commitment is available separately for production environments that need it.
Still a question we have not answered?
Bring it to the call with your own setup: routing, suppliers, volumes and the parts of the operation you want to keep in your own hands.