Owner control
Own the account. Automate the rest.
Everything an owner needs to run the commercial side of a floor without opening a support ticket, and enough API surface that your CRM can be the only screen an agent ever looks at.
- Balance, spend, calls, recordings, rates and invoices in one portal
- Crypto top-ups, credited once the payment confirms
- API keys with rotation and revocation
- Signed webhooks with retries, a queue and a circuit breaker
Own
The owner's desk
Self-service that goes further than a password reset. If it is your account, it is your data, and it is visible without asking us for it.
Money
Balance, spend over time, rates by destination, invoices and payment history — the commercial picture, not a monthly PDF that arrives after the decision was needed.
Traffic
Calls with their outcomes, durations, costs and recordings, filterable by line, number, campaign and team.
Inventory
Lines, devices and numbers with their labels, mappings, limits and registration state, so the account reflects the floor as it is today.
Identity
Profile, password, device labels and deliberate SIP credential reveal per device. Credentials are shown to the owner, not scattered through an email thread.
Fund
Crypto in, balance up once it confirms, no thirty-day terms
Funding a voice account should take minutes and involve no one's opinion about your industry.
Top up in crypto
Fund the balance directly. Credit lands after the provider or the chain confirms the payment, and the portal shows it moving through each state rather than disappearing into a void until someone reconciles it.
Credited on confirmation
Balance credits automatically once the provider or the chain confirms the payment. Before that it is a pending payment and the portal says so.
Spend against balance
Calls draw down the balance you funded, at the rates shown in the portal. Prepaid means the surprise arrives before the traffic, not after it.
Top up your balance in crypto.
Balance is credited after the provider or the chain confirms the payment, and the portal shows the payment sitting in each state until it clears. No invoice chase, no thirty-day terms, no waiting on a bank that does not like your industry.
Connect
API keys, click-to-call and presence
The API exists so your CRM can be the front door. An agent should click a lead and be in a conversation, not alt-tab into a second application to type a number they already have.
Keys you control
Issue API keys, rotate them, and revoke them the day someone leaves. Key management is an owner function in the portal, not a support request.
Click-to-call and presence
Start a call from your own interface and read agent presence back, so your CRM knows who is available before it routes a lead at them.
Calls, cost and recordings
Pull call records, costs and recordings into your warehouse, your BI, or the CRM record the deal lives on.
Rates
Read current rates programmatically instead of maintaining a stale copy in a spreadsheet that decides your margin.
Automate
Webhooks that survive your bad afternoon
Most webhook integrations are fine until the receiving end has an outage, and then they quietly lose a day of events. Ours are built on the assumption that your endpoint will fail, because everyone's does.
Signed deliveries
Every delivery is signed, so your endpoint can verify the event came from us before it acts on it.
Retries and a persistent queue
Failed deliveries are retried from a persistent queue rather than dropped. Your outage costs you latency, not data.
Circuit breaker
When an endpoint is clearly down, the breaker opens instead of hammering it, and closes again when it recovers.
Alerts where you already are
Operational alerts can be delivered to Telegram, so the person who needs to act sees them without logging into anything.
Activation
What the first fifteen minutes actually look like
For an eligible standard setup on destinations we already serve, this is the normal sequence. It is a typical path, not a promise about every configuration.
1 — Register
Create the account. No KYC verification is required to register. That covers registration only - activation, number orders, regulated destinations and abuse-prevention checks may still require information or documents.
2 — Fund
Top up the balance in crypto. The portal shows the payment's state until the provider or the chain confirms it.
3 — Provision
Lines and devices are created with credentials and labels; numbers are attached where the destination allows immediate issue.
4 — Dial
Install the softphone or register your own PBX, place a test call, and check the record and recording landed. Then open the campaign.
1 — Register
Create the account. No KYC verification is required to register. That covers registration only - activation, number orders, regulated destinations and abuse-prevention checks may still require information or documents.
2 — Fund
Top up the balance in crypto. The portal shows the payment's state until the provider or the chain confirms it.
3 — Provision
Lines and devices are created with credentials and labels; numbers are attached where the destination allows immediate issue.
4 — Dial
Install the softphone or register your own PBX, place a test call, and check the record and recording landed. Then open the campaign.
Eligible standard setups can be live in about fifteen minutes.
That is the typical path for a standard build on destinations we already serve: account, balance, lines, softphone, a route out. It is not a guarantee for every configuration. Regulated destinations, specific local-number types, ported numbers, and unusual routing take as long as they take, and we will tell you which one you are before you start counting.
Questions
Straight answers
- Which cryptocurrencies can I fund with?
- The current list of accepted assets and networks is confirmed at setup, because it changes with our payment providers rather than with our marketing. Ask before you send anything, and send only to an address the portal generated for your account.
- How long does a crypto top-up take to credit?
- Crediting happens after confirmation — the provider's or the chain's, depending on the asset. Congested networks take longer, and the portal shows the payment as pending rather than pretending it has landed.
- Is there API documentation?
- Yes, and it is provided with the account rather than published as a public teaser. It covers click-to-call, presence, rates, calls, cost, recordings and the webhook event schema, including signature verification.
- Can I run this alongside my existing PBX?
- Yes. Plenty of floors register their own PBX or dialler against our edge, use the API for click-to-call and reporting, and never touch our dialler. The portal and the API do not require you to move your floor software.
Keep reading
Where to go next
- Get StartedWhat we need from you, what activation may require, and how the first build is scoped.
- Voice, Numbers & DialerThe lines, devices and numbers this portal provisions and this API drives.
- Call IntelligenceThe recordings and call records the API hands to your warehouse.
- Our NetworkWhich edge your devices register against, and why that is our decision to answer for.
Own the account
Fund it, wire it up, and stop asking permission
Bring the CRM you already use and the way you already pay. We will tell you which API endpoints cover your workflow and what the first top-up looks like end to end.