South African number-porting software and CRDB integration
For a service provider, managing number portability involves more than submitting a request. Our geographic number-portability platform connects to South Africa’s Central Reference Database (CRDB) through the NPC interface. It brings requests, approvals, scheduled steps and confirmations into a shared workspace, helping provider teams spend less time chasing updates and more time handling the decisions that matter. From API integration to your own approval submission, the platform guides your team through each step with a full digital record and supporting evidence.
Your CRDB API integration, guided from start to submission
Step-by-step integration guidance and digital evidence help make your CRDB API approval process smoother. Approval remains subject to NPC review. Take [PROVIDER] through the full CRDB API integration process in one guided workspace. Work through each step, record its completion and retain the digital evidence needed to support your provider’s own API integration approval submission.
Follow each integration step
A step-by-step journey helps your team complete the CRDB API integration process and see what comes next.
Build a full digital record
Keep completion records, requests, responses, outcomes and supporting evidence together as your team progresses.
Prepare your approval submission
Use the recorded evidence to support [PROVIDER]’s own API integration approval submission. NPC assesses and grants each provider’s approval.
Automation that keeps people in control
Routine port-request steps can progress automatically once the required checks and approvals are in place. The platform watches for incoming confirmations, matches them to the right request and advances supported CRDB workflows. Managers approve or decline incoming requests, review initial submissions and can keep activation manual. Exceptions stop for attention, so a delayed or uncertain response is visible to the team.
Port numbers into [PROVIDER]
When [PROVIDER] is receiving a number, create a request with the number, donor account details, client reference and requested date and time. Review it before submission. After donor approval, the workflow sends the port notification and waits for confirmation. Activation can run at the selected time or follow an explicit manual action. The case completes only when both activation and donor deactivation are confirmed. A follow-up alert flags donor deactivation still outstanding after 24 hours.
Port numbers out of [PROVIDER]
When a number is moving away from [PROVIDER], incoming requests are checked against the supported request details and brought to a manager for a decision. The manager can approve or decline with a supported reason. After approval, the workflow follows the matching notification and activation messages before sending the donor deactivation response. Decisions and message history remain available for review.
Six processes, one place to follow them
Port requests
move a geographic number between providers, with donor and recipient workflows.
Cancellations
request cancellation of a port and retain the resulting confirmation.
Returns
manage the return of a ported number and track the related messages.
Reversals
request reversal of an eligible port, with the response and outcome recorded.
Installation changes
submit and follow changes to the recorded installation address.
Emergency notifications and restoration
record a notification and its restoration, with the associated confirmations.
The platform covers these six processes with recorded requests, responses and outcomes. Manager decisions and reviewed follow-up actions remain part of the workflows where required.
A workspace built around the whole case
Prepare and review
guided request builders, editable drafts and message validation before submission.
See what happened
incoming messages matched to requests, submission results and searchable submitted-request history.
Keep the context
client references, operator notes, recorded outcomes and printable case evidence.
Retain the record
an imported manual porting sheet, historical register and supporting documents alongside the electronic request history.
Handle exceptions
approval gates, supported rejection reasons, duplicate-send safeguards and review stops for mismatches, missed schedules or uncertain submissions.
Manage access
separate administrator and operator roles, invitations, password controls, authenticator verification and recovery codes. Optional trusted browsers can be remembered for 30 days and revoked.
PortaBilling integration for customer and number management
Alongside CRDB, we’ve built tools that connect customer records, number management and migration into the Vlocity operations portal.
Customer profiles
select a MoneyWorks customer, review mapped company and contact details, then create or update the matching PortaBilling customer. Shared account codes require an explicit branch choice where supported.
Number visibility
search complete or partial numbers and view numbers associated with a customer, including inventory entries and clearly identified account or alias records.
Controlled removal and restoration
review number removals, verify the PortaBilling result and clean up the matching VoIPswitch records. Supported restoration returns a previously removed alias to its original customer and main account.
Reviewed migration
move supported VoIPswitch PBX number groups to PortaBilling, reuse an existing main account and add further aliases. The workflow checks ownership, assignments and routes, verifies the selected numbers and changes the selected source routes together.
Service-account setup
review and create a main service account with company and available source contact details when needed for migration.
Recovery visibility
durable operation records identify completed steps and stop uncertain writes for review before another attempt.
Reporting
scheduled monthly PDF call reports, Excel call-detail records and analysis PDFs, with recipient management and a Send now option.
What this means for your operations team
Give your operations team a clearer way to manage number portability: less repeated administration, defined approval responsibilities and a traceable record of progress. Our PortaBilling integration work supports the related customer and number-management tasks. Talk to Vlocity about the workflows and integration scope your provider operation needs.
Built around your provider’s integration journey
Bring your porting workflow, approval responsibilities and customer-management requirements to Vlocity. We’ll discuss the CRDB API integration steps and PortaBilling scope that fit your operation, with a clear record of progress and evidence for your own approval submission.
Number porting and integration FAQs
How does the platform help a provider obtain its own CRDB API integration approval?
It guides [PROVIDER] through the integration process step by step, records completion digitally and retains supporting evidence for the provider’s own approval submission. Each provider needs its own approval from NPC; the platform supports that process without guaranteeing the approval decision.
What is number portability?
Number portability lets a customer retain a telephone number when changing service provider. The CRDB work described here covers geographic numbers in South Africa.
What does Vlocity’s CRDB database integration do?
It exchanges validated porting requests and responses through the NPC interface, associates incoming confirmations with the relevant request and records the progress and evidence of each case. This is an interface integration; it does not provide direct access to the underlying CRDB database.
Is number porting fully autonomous?
Routine steps in supported port-request workflows have been automated and tested. Managers still review initial submissions, approve or decline donor requests and handle exceptions. Other supported processes use reviewed requests and follow-up actions.
Does a completed CRDB port automatically provision PortaBilling?
CRDB porting and service provisioning are separate steps. The PortaBilling tools support reviewed customer profiles, number lookup, removal, limited restoration and supported migrations. Service provisioning after a CRDB port is handled manually; the platform does not automatically provision PortaBilling when a port completes.
Which number-porting processes are covered?
Port Request, Cancellation, Return, Reversal, Change of Installation and Emergency Notification with restoration. Each process keeps its requests, responses and outcomes available for review.