Colombia's RNE/CRC Portal, Step by Step

DNC LATAM · Compliance guides

Companies can query Colombia’s official Do Not Call registry themselves, but it means registering on a Spanish-language government portal and picking the right consultation channel for your call volume — there’s no public API a foreign team can just plug into. This guide walks through what that self-managed path actually involves, step by step, so you can decide whether to run it or hand it off.

Step 1: Register on the CRC trámites portal

Colombia’s Registro de Números Excluidos (RNE) is administered by the Comisión de Regulación de Comunicaciones (CRC), and access starts with registering a company account on the CRC’s trámites portal. As covered in our Colombia Do Not Call guide, the portal and its technical manuals are in Spanish, and the credentials, tokens, and operating windows are built around local users. That’s the first fork in the road: a team without Spanish-speaking staff or a local contact who can navigate government-portal paperwork is already at a disadvantage before the first query runs.

Step 2: Pick a consultation channel that matches your volume

Once registered, the CRC gives companies a few ways to check numbers against the RNE: individual lookups for one-off queries, file uploads for batch checks, and a government web service for programmatic, high-volume access. Which one makes sense depends entirely on how you dial:

  • Individual lookups work for small, occasional campaigns — checking a handful of numbers by hand before a call.
  • File uploads fit a list-based workflow: export your calling list, upload it, get back which numbers are excluded.
  • The web service is the option for a dialer or CRM that needs to check numbers continuously rather than in batches — but integrating against it means building and maintaining that connection yourself, on top of the registration step.

For a small, occasional Colombia campaign, individual lookups or file uploads might be manageable in-house. For anything closer to continuous outbound volume, the web service is the only channel that scales — and it’s also the one with the highest integration cost.

Step 3: Query before every campaign, not once

Registering on the portal is not a one-time setup task. Ley 2300 of 2023 expanded the RNE’s reach beyond SMS into calls and other channels, and consumers can add numbers to the registry at any time. That means a file you queried last month doesn’t tell you anything reliable about a campaign running today. Every list, before it goes out, needs to be checked against a current pull from the registry — which turns the portal from a one-time registration hurdle into a recurring operational task, same as the Mexico and Argentina equivalents.

Step 4: Keep dated evidence of each check

The registry check itself isn’t the whole job — you also need to be able to show, after the fact, which registry pull a given campaign was checked against and when. That’s the same standard covered in what a screening record is and what auditors actually ask for: a dated record tied to the specific check, not a general claim that “we scrub our lists.” Without that record, a query you actually ran is indistinguishable, under review, from one you didn’t.

Where this gets harder for foreign teams

Colombia’s registry is more accessible on paper than Mexico’s zone-by-zone system or Argentina’s CUIT-gated registration — there’s no need to buy geographic zones separately, and the consultation channels are documented rather than requiring a special local-entity status. But “more accessible” is relative. The portal is still a Spanish-language government system built for locally registered companies, and the web service — the only channel that supports real dialing volume — is an integration project, not a checkbox. A US team running this path needs someone who can read the CRC’s technical manuals, register the company correctly, choose the right channel, and then keep that integration working through campaign after campaign.

That’s before accounting for what happens when the registry updates, the portal’s requirements shift, or the web service’s response format changes. None of that is unusual for a government system, but it’s overhead that has nothing to do with actually running outbound campaigns — it’s infrastructure work a US-based team has to maintain for one country, in a language most of the team doesn’t speak.

What this means operationally

If you’re weighing self-managed CRC access against a specialist, the checklist looks like this regardless of which path you take:

  1. Register the correct consultation channel for your volume — individual lookups and file uploads for occasional checks, the web service for anything close to continuous dialing.
  2. Re-check every list against a current registry pull before each campaign — a stale check is not a valid one under Ley 2300’s continuous-registration model.
  3. Keep a dated record of every check, tied to the specific campaign, not a general statement that scrubbing happens.
  4. Honor direct opt-outs immediately, independent of what the registry shows on a given day.

The practical takeaway

Running Colombia’s RNE/CRC access yourself is more approachable than Mexico’s or Argentina’s equivalents, but it still means Spanish-language registration, a channel decision tied to your call volume, and — for real dialing throughput — a web service integration you have to build and maintain. DNC LATAM runs that access on your behalf: send country: "co" through the same DNC scrubbing API used for Mexico and Argentina, and get back the RNE determination with a dated screening record attached. No CRC registration, no Spanish-language manuals, and no separate integration for a third country’s web service.