Projects/Mittis
The registration and calling layer underneath everything else.
Business messaging in the United States runs through a carrier registration regime that most software teams meet the hard way, halfway through a launch. Mittis handles it as infrastructure: numbers, brand and campaign registration, programmable voice, and a softphone.
- Sector
- Telecom infrastructure
- Improvement area
- Messaging compliance and voice
- Ownership
- An Obsidian Labs company
- Status
- In active development, in production
The bottleneck
Sending business text messages in the US means registering a brand and each messaging campaign under the A2P 10DLC regime. The submission has to be right — the business details, the use case, the sample messages, the opt-in language — and a rejection sends you back to the start of a queue you do not control.
Most teams discover this near launch, get it wrong once or twice, and lose weeks. Renting the layer from someone else means renting your phone numbers, your delivery rates, and your ability to fix things at two in the morning.
What we built
- Number provisioningacross tenants, so each business has its own numbers under one operational roof.
- A2P 10DLC brand and campaign registrationwith the submission prepared properly rather than approximated, and the trail kept alongside each campaign.
- Programmable voice— routing, ring groups, transfers, recording and voicemail.
- A softphonethat puts calls on the right device and stops ringing when it should.
- Delivery and quality telemetryso a failure is diagnosable instead of theoretical.
Where it stands
Measured
- Two days faster on average through the A2P approval process. Owner-reported; the measurement period and sample size are not yet documented, and we have marked it as owner-reported until they are.
In useDelivered
- Number provisioning and management across tenants
- Brand and campaign registration with the submission trail retained
- Programmable voice, routing and a working softphone
- Delivery and quality telemetry
What the figure does not mean
Mittis prepares and submits registrations. It does not control carrier approval decisions, and no platform can. The two-day figure is an average reduction in how long the process took — not a promise that approval arrives in two days, and not a guarantee of approval at all.
We would rather state that plainly than let a good number imply something it does not support.
What could
run better?
Show us where work slows down, breaks, or gets stuck. We’ll help map the next move.
Thirty minutes, no deck required. We reply within two business days.