Skip to main content
Recipients see an alphanumeric sender ID when the upstream carrier accepts one.

​
Ready now

Every workspace can send as Robase (the default) or RAlerts without a request. Pick the default on Dashboard → Sender IDs. Each platform name is registered per country, and the page says where; a message to a country the name is not registered for goes out under the platform name that is.

​
Request your own name

Requests are open to funded accounts. The purchased-credit threshold is sender_id_min_funded_credits on GET /v1/pricing, the same admin gate Configure sets, so the docs stay in sync when it changes. Credits you have already used still count. Signup and purchase bonuses and refunds do not. The Sender IDs page shows how far you are and takes you to billing with the difference filled in. From Dashboard → Sender IDs → Request a Sender ID:
  1. Name. Pick the country the name is for (Nigeria today; the list grows as we open more), choose the sender name and say what it carries: one-time passcodes, transactional alerts, or both. Add a sample message, and up to two more if you have them. The dashboard checks the name against the carrier rules as you type.
  2. Company. Upload your company registration certificate (the CAC certificate in Nigeria). We read the company details from it; you confirm them. Add the physical address and PO box (if you have one), upload the tax registration certificate as a PDF, and give the details of the authorised representative: full legal name, email, mobile number, office telephone (optional) and passport or ID number.
  3. Authorize. Sign once, drawn or typed, and add your company stamp if you have one. We prepare and file the carrier letters on your behalf.
You then see the request move through Submitted → In review → Filed with carriers → Approved, on the request page and by email. If something needs fixing, the request comes back as Needs changes with the reason, and you edit and resubmit. Carrier registration usually takes 1 to 4 weeks after filing. The networks set the pace, we do not promise a number of days. Each status change reaches you by email, with the reason when a request needs changes or is rejected.

​
Rules

  • 3 to 11 characters: letters, numbers, space, hyphen and dot.
  • The name must relate to your business, product or service. No personal names, no brands you do not own.
  • The company on the registration certificate must own the name.
  • One custom sender ID per workspace for now, registered for the country you pick in the request.
  • An approved name is used for messages to its country. Messages to other countries keep the platform sender.

​
Not in the API

There is no public sender-ID endpoint. You cannot register, list, or pick a sender ID with the customer API. POST /v1/sms/send and POST /v1/otp/send send as the workspace default. Transactional OTP traffic is routed on transactional paths so Nigeria’s NCC DND registry is not treated as a promo filter for one-time passcodes. See DND compliance.