Quick answer: Georgia (+995) sits in the sender-ID whitelisting wave of markets: the national regulator, the Georgian National Communications Commission (ComCom), presides over a registry where approved alphanumeric sender IDs are whitelisted per operator, and unregistered alphanumeric marketing traffic is either overwritten with a generic numeric sender or filtered at the operator level. For marketing SMS into Georgia, the launch sequence is: confirm the GE row in the country-rules reference, clear the three exclusivity checks (the sender string must be yours to claim, distinctive enough to survive review, and not a generic dictionary word), file business registration and brand-authorization documents, register the sender, then hold production sends until the entry reads approved. Everything below is a tenant-owned control — you file, the platform carries the filing and reports review status back. Approval is granted by the Georgian operators under ComCom oversight, not by Devotel Orbit, and market coverage on your account is per tenant.
Why Georgia whitelists sender IDs
Sender-ID whitelisting is the middle regime between "registration recommended" markets (France, Germany, the UK — send now, register for stability) and the special regimes (India DLT, US 10DLC). In a whitelisting market, operators maintain a registry of approved alphanumeric sender strings, and the network checks each A2P message's sender field against it. Georgia joined this wave as part of the broader Caucasus/Mediterranean alignment with EU-adjacent registration practice; ComCom's registry is the one operators enforce at the interconnect.
The enforcement posture matters because it is not advisory. In recommended markets, skipping registration degrades delivery over time. In Georgian whitelisting practice, an unregistered alphanumeric sender on marketing traffic does not degrade — it arrives with the sender rewritten to a numeric identifier (the recipient sees a number, not your brand) or the message is dropped at the operator SMPP bind when the route is a registered-only route. For a marketing program, the rewritten sender is nearly as bad as the drop: brand-name display is the entire reason to use an alphanumeric sender, and two-way replies do not reach a rewritten numeric source.
Three consequences fall out of this for launch planning:
- Registration enters the critical path, not the post-launch backlog. File the sender before the first production send.
- The sender string is a review artifact. Operators review what you ask to display, and generic or misleading strings are refused.
- Transactional vs marketing mix matters less than in some regimes, but consent still matters. Georgia's content rules expect prior consent for marketing SMS and an opt-out path; the whitelist gets you a working sender, not a content pass.
The three exclusivity checks
Registries across the whitelisting wave apply the same family of sender-name rules. Georgia's review, run by the operators under ComCom oversight, rejects on three grounds more often than any other — clear all three before you file:
1. Exclusivity: the string must be yours to claim. You must be entitled to the brand you register — your own legal entity name, your registered trademark, or a brand you can document authorization for. "GEORGIA CARE" filed by a logistics company without a trademark claim is refused; so is any string another registrant already owns. The fix is paperwork: attach the business registration extract and, where the string is a trademark, the registration certificate or a letter of authorization from the rights holder.
2. Distinctiveness: the string must identify a sender, not describe a message. Review refuses strings that read as message content rather than identity. "SALE2026", "DISCOUNT", "FREESHIP" fail here. The string should be the brand as the recipient knows it — what appears on your storefront, invoices, and website header. If the brand and the promotional word collide, register the brand and put the promotion in the message body.
3. The generic-name trap: common dictionary words are unclaimable. Strings like "INFO", "SMS", "NOTICE", "ALERT", or a plain geographic name cannot be exclusively whitelisted, because no sender can own them. This is the trap that stalls first filings: the applicant asks for "BAKU-MART" style distinctiveness and files "MARKET" instead. Add the brand element — "MARKET" fails, the registered brand succeeds.
Length and charset hygiene still apply on top of the three checks: keep the string within the standard 11-character alphanum limit, avoid spaces and special characters (operators normalize or reject them inconsistently), and pick one casing — registries store the string case-insensitively, but display consistency across operators follows what you registered.
How to file: documents, submission, and tracking
The filing is a tenant-owned loop. You gather documents once, upload them to the document library, reference them in the sender-ID registration, and the platform carries the filing to the operator registry and reports the review status back on the sender registry page.
Documents Georgian filings typically require:
- Business registration certificate — the registry extract for the legal entity claiming the sender.
- Brand ownership or authorization — trademark certificate, or a letter of authorization from the rights holder if you operate under a partner's brand.
- Use-case description — a short statement of what you send (marketing promotions, order updates, OTP) and to whom. Marketing use cases should state the consent basis in one sentence.
Upload each document once into the tenant document library; it returns a doc_ ID you can reference from every subsequent filing. Accepted formats are JPEG, PNG, WebP, and PDF.
Submission and tracking. The sender-ID registration carries the sender string, the country, the use case, and the doc_ references. On the dashboard's sender registry page (Audience → Senders), the filing moves through pending → approved (or rejected with a review note). Operators typically answer within a few business days; plan a week of lead time into the launch. Until the entry reads approved, hold production sends to GE — the send-time behavior on an unregistered sender is the rewrite/filter described above, not a warning.
If a filing is rejected, the note almost always names one of the three exclusivity checks. Refile with the corrected string or the missing authorization document; rejections do not prejudice the corrected filing.
Where the country-rules lookup answers
This post is a playbook, not the data. The per-country row lives behind a read-only reference any authenticated user can call:
curl "https://api.orbit.devotel.io/api/v1/compliance/country-rules?channel=sms®ion=GE" \
-H "Authorization: Bearer $ORBIT_API_KEY"The GE row answers the launch questions before you file anything: registration (the whitelisting posture in force), sender_types (which sender classes the market accepts), content_restrictions and stop_requirement (consent and opt-out expectations), two_way and dlr_support (whether replies route and whether delivery receipts come back), and a default_tps ceiling. Rows carry a freshness stamp from the upstream regulatory feed, so the endpoint answer supersedes any page — this one included.
One guard to keep honest: a country in the reference is data, not enablement. Coverage is enabled per tenant; confirm Georgia is enabled on your account before the launch plan depends on it.
Frequently asked questions
Is registration actually mandatory for Georgia, or just recommended?
Treat it as mandatory for marketing SMS on alphanumeric senders. The whitelisting posture means an unregistered alphanumeric sender is rewritten to a numeric identifier or filtered at the operator level on marketing traffic — not merely degraded. Read the registration field on the GE country-rules row for the current enforcement level, and file before the first production send.
How long does Georgian sender-ID approval take?
Operators under ComCom oversight typically answer within a few business days. Plan a week of lead time, and longer if the filing needs trademark documentation pulled from a rights holder. The sender registry page (Audience → Senders) tracks the review state per filing.
Can I use the same documents for Georgia and other markets?
Yes. The document library is tenant-wide: upload a business registration certificate once and reference its doc_ ID from the Georgian filing, a UK filing, or any other market that accepts it. Per-market differences live in which fields the filing requires, not in the library.
What if my sender string is rejected as generic?
Refile with the brand element included. Generic dictionary strings ("INFO", "SALE", a plain geographic name) are unclaimable by any sender; adding the distinctive brand element is the fix, and rejections do not prejudice the corrected filing.
Does whitelisting my sender satisfy Georgia's content rules?
No. The whitelist answers "may this string display as a sender." Consent for marketing SMS and an opt-out path are separate obligations under the market's content rules — the whitelist gets you a working sender, not a content pass. Both live on the GE row's content_restrictions and stop_requirement fields.
Is this legal advice?
No — this is a tenant-owned onboarding playbook pointing at per-market reference data, not legal advice. The legal interpretation of Georgia's rules stays with you and your counsel; approval is granted by the Georgian operators under ComCom oversight, not by Orbit.
Published 21 September 2026.