Voice and SMS API for SaaS vendors
Your customers expect to call, text or get notified from inside your software. TELQIO provides the numbers, voice and SMS layer, which you drive through an API, with usage you can tie back to each of your accounts.
The problem
A vendor who adds a “Call” or “Send SMS” button soon finds out what sits behind it: choosing numbers by country, tracking supporting documents, relaying statuses, working out who used what. Each piece takes months that do not move your product forward.
The second trap is internal billing. If you cannot isolate one end customer’s usage, you can neither re-bill it nor explain a rise. The split by project has to exist from the first number order, not be bolted on later.
How it flows
Example journey
SaaS vendors
One project per end customer
A vendor of scheduling software creates a “Project A” for each customer of its product. Permissions, numbers and usage stay separate from day one.
Number assigned at sign-up
When an account is activated, the back end searches for a compatible number and places an order tied to the project. An idempotency key prevents a duplicate order if the request is replayed.
Reminders sent by the software
The product sends appointment-reminder SMS from the project’s number and receives delivery statuses through a signed webhook.
Calling from a record
A user clicks a contact. The API connects their phone to the contact and sends call events back to your application.
Usage read per project
At month end, the vendor’s team queries usage grouped by project and by service, to reconcile it with its own invoicing.
Products involved
Virtual numbers
Search, order and attach phone numbers to a project.
Custom quoteSMS API
Send SMS, count segments, follow statuses.
Custom quoteVoice API
Place, receive and control calls from your code.
Custom quoteCall flows
Build a call journey visually or in text.
Custom quoteWhite label
One organization, sub-accounts, projects: each customer isolated.
Custom quoteLimits to know
- Countries, number types and SMS or voice capabilities depend on the chosen provider and your contract. Check them before promising a feature to your own customers.
- Re-billing usage to your end customers is part of your own commercial relationship. TELQIO supplies the data, not your price list.
- No ready-made integration is delivered today.
Frequently asked questions
Can I isolate each end customer?
Yes, that is what projects are for. Permissions, numbers and usage attach to a project, and API keys can be limited to it.
Will my customers see the TELQIO brand?
Under your contract, a console in your own colours is planned for white label use. The details are agreed with you.
Tell us about your product
Describe the communication features you want to add, your customers’ countries and your estimated volumes. We will prepare a custom quote.