Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.revdesk.com/llms.txt

Use this file to discover all available pages before exploring further.

​
What is Branded Calling?

Branded Calling is a carrier-driven feature that lets your outbound calls arrive on recipient phones with your business name, logo, and a short call reason instead of a raw number. It dramatically improves answer rates for legitimate business calls and crowds out spam spoofing. The underlying primitive is the Display Identity Record (DIR) — one per enterprise registration. Your DIR bundles the display name, logo asset, and call reason the carrier pushes to carrier-side display engines (Hiya, etc.).

​
Current status

The Branded Calling endpoint is rolling out incrementally with our carrier. RevDesk has built the full customer-facing flow — you can save DIR drafts, upload logos, and mark them ready for submission today. A nightly worker (cron/submit-pending-dirs) watches for a readiness flag and batch-pushes all PENDING_SUBMIT DIRs once the endpoint goes live. This means you can set up your brand today and it’ll go live automatically when Branded Calling launches.

​
The DIR lifecycle

DRAFT ──► PENDING_SUBMIT ──► SUBMITTED ──► APPROVED
                                       │
                                       └─► REJECTED ──► (re-edit → DRAFT again)
  • DRAFT — you’ve saved some fields but haven’t clicked Submit. Safe to edit freely.
  • PENDING_SUBMIT — you clicked Submit. RevDesk has queued the DIR for submission; awaits the carrier’s Branded Calling endpoint going live.
  • SUBMITTED — we’ve pushed the DIR to the carrier. Awaiting vetting.
  • APPROVED — live. Your brand renders on outbound calls.
  • REJECTED — carrier reviewer pushed back. See rejection_reasons on the DIR object. Editing any field moves status back to DRAFT so a resubmit is a clean slate.

​
Required fields

FieldConstraint
display_name≤ 64 chars. Usually the same as DBA.
call_reason≤ 120 chars. Short, specific (e.g. “Annual roof inspection follow-up”).
logoPNG/JPEG/WebP, square, ≥ 200×200px. Upload via POST /v1/caller-trust/brand/logo.
The matching enterprise registration must be APPROVED before a DIR is eligible for submission — DIRs inherit the enterprise’s legal attestation.

​
Typical integration flow

# 1. Save a draft
curl -X PUT https://api.revdesk.com/v1/caller-trust/brand \
  -H "Authorization: Bearer $KEY" \
  -H "Content-Type: application/json" \
  -d '{"display_name":"Acme Roofing","call_reason":"Scheduled inspection follow-up"}'

# 2. Upload a logo
curl -X POST https://api.revdesk.com/v1/caller-trust/brand/logo \
  -H "Authorization: Bearer $KEY" \
  -F "file=@logo.png"

# 3. Submit when ready
curl -X POST https://api.revdesk.com/v1/caller-trust/brand/submit \
  -H "Authorization: Bearer $KEY"

# 4. Poll status (or listen for webhooks)
curl https://api.revdesk.com/v1/caller-trust/brand \
  -H "Authorization: Bearer $KEY"

​
Relationship to Number Reputation

Both features ride on the same enterprise registration, but they’re independent lifecycles. Your Number Reputation enrollment and DIR submission can be in different states (common: reputation APPROVED while DIR still DRAFT).