Calling Belgium with +32 Numbers: Why Renting a Number Isn’t Enough

The dialer shows another attempt. The agent moves to the next player. By the end of the shift, the report looks busy, but actual conversations are thin on the ground. Before blaming the database, follow a few calls all the way to the receiving phone. In Belgium, a rented local number can be perfectly genuine and still be used on a route that gets the call blocked.

What the September BIPT figures tell us

On 15 September 2026, Belgian regulator BIPT released figures from five major telecom operators. In the first half of the year, 103 million fraudulent calls were blocked or had their caller ID suppressed. More than 74 million calls involving number spoofing were blocked.

There is no iGaming breakdown in those figures. They show how much traffic is being filtered before it reaches a recipient; they do not tell us how many casino calls were rejected.

The rules behind that filtering are already established: measures for geographic numbers have applied since 1 September 2024, and for mobile numbers since 1 December 2024. September’s announcement was a report on their results, not the introduction of a new restriction.

The problem with “we’ve bought a Belgian number”

Picture a routine support callback. A Belgian player has asked for help, an agent abroad opens the ticket, and the cloud phone system places the call using +32. The player is expecting it. The company has rented the number. Yet the call enters Belgium through an international interface while presenting Belgian caller ID.

That combination is generally subject to blocking unless the conditions of an exception are met. The rental agreement alone does not settle the question.

This is the detail to clarify before signing with a casino VoIP provider: how will your overseas team’s calls be admitted with that Belgian number? A +32 number in a provider’s catalogue does not explain the outbound route.

Who qualifies for the cloud customer support exception?

Belgium allows an exception for cloud-based customer support and telephone direct marketing, subject to conditions. It covers geographic numbers assigned to a company established in Belgium.

The company must be able to document the assignment in a written agreement and have full control of the numbers. They cannot be shared with other companies. The numbers must be registered with the operators and included in the written agreement between the operators handling the relevant route.

Operators must also retain control of the call through to the first operator receiving the international call and be able to identify the caller when BIPT requests it.

A provider should be able to explain how your arrangement meets those conditions. “We have +32 numbers available” leaves the most important part unanswered. For an iGaming contact centre, both the assigned number and the delivery route matter.

Switching to a Belgian mobile number is not an automatic fix. The cloud support exception concerns geographic numbers. Mobile numbering has separate provisions, including genuine roaming.

What to check before calling Belgium

Make a few agreed test calls to controlled numbers across Belgian networks. Check the connection, the caller ID on the receiving handset, and the return call to support. Look at what happens on the phone, not just the dialer status.

Keep the timestamps with their time zones and both phone numbers. If a call fails, send the provider a specific example and ask where it stopped. If you buy through a reseller, establish who can investigate with the operator carrying the traffic.

For player support, an attempted callback should not be enough to close a ticket. The agent may have dialed while the player received nothing. Your reporting needs to distinguish an attempt from an actual conversation.

Marketing permission is a separate question too. A compliant telecom route does not, by itself, authorize a promotional call.

Investigate the route before renting more +32 numbers

Before paying for another batch of Belgian numbers, find out what happened to the ones you already use. A missed conversation is worth investigating. Another +32 on the invoice will not explain it.