
Owner control
You should not open a ticket to see your own balance, rotate a credential, or find out why a payment is still pending. This is the owner's desk. Crypto in. Credit after the provider or the chain confirms it. Keys you issue and revoke yourself. Enough API that the CRM can be the only screen a closer looks at.
- See the balance, the spend and the tape without opening a ticket.
- Crypto in. The portal shows pending until the provider or the chain confirms.
- You issue the keys. You kill them the day someone walks.
- When your endpoint dies, the dispositions wait in the queue instead of vanishing.

Own
If you have to ask us for last Tuesday's spend, the portal failed. Money, traffic, inventory, who holds which password: that is your desk.
Money
Balance, spend, rates by destination, invoices, payment history. A monthly PDF that arrives after you already overdialled is decoration.
Traffic
Pull the call, the outcome, the cost and the recording. Filter by line, number, campaign, team. Do it yourself.
Inventory
The account should look like the floor sitting there today: labelled devices, mapped DIDs, limits, who is registered.
Identity
You reveal SIP credentials per device when you decide to. They do not live in a Slack thread from March.
Fund
Funding a voice account should take minutes and involve nobody's opinion about your industry.
Top up in crypto
Fund the balance directly. Credit lands after the provider or the chain confirms the payment. The portal shows the transfer moving through each state instead of vanishing until someone reconciles it.
Pending means pending
Before confirmation it is a pending payment and the portal says so. Lying about a credit is how a floor overdials and then screams.
Spend against balance
Calls draw down what you funded, at the rates in the portal. Prepaid means the surprise arrives before the traffic.
Connect
Click the lead. Be in a conversation. Read presence so you do not dump a hot lead on a seat that is already in wrap.

Automate
Most webhook setups are fine until the receiving side has a bad afternoon, and then they quietly lose a day of events. These are built for the outage.
- Signed deliveries
- Every delivery is signed. Your endpoint can check it came from us before it acts.
- Retries and a queue that persists
- Failed deliveries retry from a persistent queue. Your outage costs you latency, not a missing day of dispositions.
- Circuit breaker
- When an endpoint is clearly down, the breaker opens instead of hammering it, and closes when it comes back.
- Alerts where you already are
- Operational alerts can land in Telegram so the person who has to act sees them without logging into anything.
Activation
For an eligible standard setup on destinations we already serve, this is the usual sequence. It is a typical path. It is not a promise about every configuration.
1 — Register
Create the account. No KYC to open the account. Opening the account is not the rest of the job. Activation, local-number orders, regulated destinations and abuse-prevention checks can still require information or documents where the law, the carrier, or the destination country demands it.
2 — Fund
Top up in crypto. The portal shows the payment's state until the provider or the chain confirms it.
3 — Provision
Lines and devices get credentials and labels. Numbers attach where the destination allows immediate issue.
4 — Dial
Install the softphone or register your own PBX. Place a test call. Check the record and the recording landed. Then open the campaign.
Questions
- Which coins can I fund with?
- The live list of assets and networks is confirmed at setup, because it moves with the payment providers, not with a marketing page. Ask before you send anything. Send only to an address the portal generated for your account.
- How long does a crypto top-up take to credit?
- Credit happens after confirmation: the provider's or the chain's, depending on the asset. Congested networks take longer. The portal shows pending rather than pretending the money has landed.
- Is there API documentation?
- Yes, and it comes with the account rather than as a public teaser. It covers click-to-call, presence, rates, calls, cost, recordings and the webhook event schema, including how to verify the signature.
- Can I run this next to 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.

Your account
Next
Next
Next
Next