Your carriers, your providers, your CRM
The number stays with your carrier, SMS and Viber with your provider, the data goes where your team works. Connected by key, billed directly to you.
In the system today
- 01
Telecom carriers
Zadarma, DIDWW, Telnyx, Twilio — by API key: the trunk and numbers are configured automatically. Or any SIP carrier or your own PBX.
- 02
SMS and Viber
TurboSMS, SMS Club, eSputnik, Infobip — from your company’s sender name; Twilio and Vonage for Europe and the world.
- 03
Email and Telegram
Any SMTP (Gmail, Mailgun, Brevo, Amazon SES) and your company bot in Telegram.
- 04
REST API and webhooks
Leads, facts with evidence, calls, transcripts, recordings. Per-action permissions, signed webhooks.
- 05
S3 recording storage
AWS S3, Cloudflare R2, Backblaze or MinIO. The keys and access are yours.
- 06
Customer base import
CSV or Excel: preview before writing, duplicates enriched, consent with evidence.
CRM via the API, not a one-click connector
There are no ready-made connectors yet, and we do not pretend otherwise. A typical two-way sync is a handful of requests, and the permission set is already prepared.
A ready permission set for syncing
Permissions are never implied: “write” does not include “read”.
leads:readleads:writefacts:readclients:readcalls:readTell us where
the lead should go.
We will look at your CRM and say plainly how much work it is.