Every call, connected to the customer record it belongs to.
Virtual numbers, IVR, smart routing, recording and call analytics — running on Indian carriers, DLT-compliant, and writing straight back into Comsky CRM.
In build — not yet open for self-service · Indian carriers, DLT and TRAI compliance from day one · Recordings stored in India · Native to Comsky CRM, not connected to it
The phone system and the CRM will be the same product.
Everyone sells an integration. An integration is a webhook, a field mapping and a person who has to keep both alive. Comsky Telephony is being built inside the same database as Comsky CRM, so a call is not a record that has to be copied across — it is already on the deal.
Matched before it is answered
The caller’s number will be looked up against your contacts while the phone is still ringing. The rep sees who it is, which company, which open deal and when they last spoke — before saying hello.
Dial from the pipeline
Every phone number in Comsky CRM becomes a dial button. Click it on a contact, a company or a deal and the call places itself. No softphone window to find, no number to retype.
The recording sits on the deal
Recordings will attach to the activity they came from, playable in the timeline next to the emails and the notes. Not in a separate console, found later by timestamp.
Transcribed and searchable
Every recording will be run through speech-to-text so you can search what was actually said across a quarter of calls, rather than listening to twenty of them to find one sentence.
Calls become pipeline data
Call count, talk time and outcome will be fields on the deal like any other. That means your pipeline reports can use them — which stages get called, which do not, which reps let a deal go quiet.
One user list, one deactivation
A rep is added once and removed once. There is no second admin console where an ex-employee keeps an extension and a licence for four months.
Telephony is designed around Comsky CRM, which is live today. It will also run on its own, with a REST API and webhooks for a CRM you already use — you just lose the part that makes it worth buying from us.
What will happen between the ring and the write-up.
Four things, none of which anyone in your office has to remember to do.
Which number was dialled sets which menu plays. The IVR builder is a tree you drag together, not a script someone has to write for you.
The menu choice narrows it to a queue. Then the rules decide who in that queue gets the call, and who gets it if they do not pick up.
The matched contact, company and open deal appear on the rep’s screen as the call connects, with the last three conversations already visible.
At hang-up the duration, the outcome, the recording and the transcript are written to the deal. Nobody logs an activity afterwards, because there is nothing left to log.
That is the inbound path. The outbound one — campaign lists built from a CRM filter, the preview and progressive dialers, DND scrubbing before a number is dialled and the permitted calling hours — is on the features page, because it is a different shape and pretending otherwise makes both harder to follow.
The difference is not the dial tone.
Standalone cloud telephony in India is good. Exotel, Knowlarity and MyOperator all carry calls perfectly well, and we are not going to pretend otherwise. The difference is what happens to the call after it ends, and who owns the join between the phone system and the sales record.
| Standalone cloud telephony | Comsky Telephony | |
|---|---|---|
| Where the call ends up | A webhook into your CRM, which somebody on your side maintains | The same database as the deal. There is nothing to sync, so there is nothing to break. |
| Setting it up | Two vendors, two contracts, two support desks, one integration you own | One account. Telephony switches on inside Comsky CRM. |
| Placing a call | A browser extension or a separate softphone window | The number on the record is the dial button. |
| Finding a recording | In the telephony console, located by date and time | Attached to the activity on the deal, played in the timeline. |
| Reporting | Call reports in one tool, pipeline reports in the other | Talk time and call outcome are deal fields, so pipeline reports can use them. |
| When a rep leaves | Deactivate twice and hope the mapping survives | One user record, one deactivation. |
| Carrier, DLT and TRAI | Handled by the vendor | Handled by us as well — licensed carrier, registered headers and templates, DND scrubbing. |
| Cost of the integration | A connector tier, or an implementation partner | Included |
| Available today | Yes | Not yet — in build |
The three questions people ask next.
What will it actually do?
IVR, queues, routing, the dialer, the wallboard, recording and the API — by area, with what is in the first release and what is not.
See the features →
Can I keep my number?
Local, toll-free, missed-call and masked numbers, what DLT registration asks of you, and what porting a series really involves.
Numbers and compliance →
Where do the recordings live?
Indian data centres, retention you set, pause-and-resume while card details are read out, and who in your team can hear what.
Read about security →
What people ask before joining the waitlist.
Can I buy Comsky Telephony today?
No. It is in build. Carrier arrangements, number provisioning and DLT onboarding are the long poles, and we are not quoting a launch date we cannot hold. Join the waitlist and we will tell you when there is something to test, not when there is something to announce.
Do I have to use Comsky CRM as well?
No, but the whole argument for buying telephony from us is that the call lands on the CRM record without an integration in the middle. On its own it will be a competent Indian cloud telephony product with a REST API and webhooks. With Comsky CRM it is a different thing entirely.
Will it work with the CRM we already have?
Through the API and webhooks, yes — every call event will be published, and click-to-call can be triggered from an external system. What we will not have at launch is a maintained native connector for every CRM on the market. If you need one, tell us which, and we will be straight about whether it is on the list.
Who registers the DLT headers and templates?
You do, as the principal entity — the regime requires the sender to register in their own name and we cannot do it on your behalf. We will do the filing alongside you, and the platform will refuse to send on an unregistered header or template rather than letting it fail at the operator. How that works, in full.
How is this priced against Exotel or MyOperator?
We do not know yet, and any answer we gave you now would be invented. What we will commit to is the structure: a published per-user price, a published rental per number, a published per-minute rate and a published WhatsApp conversation rate — no quote-only line items hiding in the invoice. More answers →
Start with Comsky Telephony.
Grow into the ecosystem.
One Comsky account, being rolled out across the products — and one invoice covers them, however many you run.