Asked, and answered without the hedge.
Several of these answers are “no”, “not yet” or “we do not know”. That is what it means to publish a page about a product in build, and the alternative — a page of confident present-tense sentences about something nobody can buy — is how a company spends credibility it has not earned.
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.
So what does "in build" actually mean here?
It means less than it means for Comsky Mail or Comsky Orbit, and the difference is worth being clear about. Those two are built and running on our own infrastructure, with our own people using them daily; what they lack is a way for you to sign up. Telephony is earlier than that: the product is being built, and the part of it that is not software — a licensed carrier, provisioned number series, your DLT registrations — has not been contracted. We would rather you knew which kind of "in build" you are reading about.
When will it launch?
There is no date, and there is not going to be one on this page until the carrier terms are signed, because that is the item we do not control. When there is a date it goes here and in the mail to everybody on the waitlist, in that order.
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 — the call, the recording, the transcript and the follow-up task are on the deal because they were never anywhere else.
Will it work with the CRM we already have?
Through the API and webhooks, yes. Every call event will be published — ringing, answered, transferred, ended, recording ready, transcript ready — 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. The API is described here.
Can I keep my existing phone numbers?
Where the carrier permits porting, yes, and we will tell you before you commit whether your specific series can move. Where it cannot, the usual answer is to forward the old number into the platform, which works but means you keep paying for both. Numbers and porting, in full.
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 no vendor can do it on your behalf, whatever they tell you. 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. What DLT asks of you.
Where are recordings and transcripts stored?
In Indian data centres, on Comsky Cloud. Retention is a setting you control, and deletion means deleted — including from the transcript index. The security page says who in your team will be able to play a recording, and what is logged when they do.
Can we pause the recording while a card number is read out?
Yes — pause and resume from the agent’s own screen, mid-call. It is on the first-release list rather than a later one, because a platform that records everything and leaves card data to you has moved the problem without telling you.
Is the audio end-to-end encrypted?
No, and it cannot be on a product that records: a recording is made by decrypting the audio. Audio will be encrypted in transit between the legs and at rest once written. Any telephony product offering you recording and end-to-end encryption in the same sentence is wrong about one of them.
Does the agent need a good internet connection to take a call?
Not necessarily. The dialer bridges two carrier legs, so the call can land on an ordinary mobile or desk handset and the audio path does not depend on your office broadband. A browser softphone is planned as well, for teams that want one.
Will there be a predictive dialer?
Deliberately not. A predictive dialer works by dialling more numbers than you have agents and dropping the ones that answer into silence, and the abandoned-call rate is the product. Preview and progressive dialling are on the list; the thing that hangs up on people is not.
Can supervisors listen to live calls?
Yes — silent monitor to hear without being heard, whisper to coach the agent while the customer hears nothing, and barge to join. All three are planned for the first release, and each will be recorded as having happened, because a monitoring tool with no trail is a different product from a monitoring tool.
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 — in rupees, with GST stated, and no quote-only line items hiding in the invoice.
Are you saying Exotel and MyOperator are bad?
No, and the product page says so. They carry calls perfectly well and they do it today, which is two advantages we do not have. The difference we are building for is what happens to the call after it ends, and who owns the join between the phone system and the sales record — and if that join is not a problem you have, they are a reasonable answer.
What happens to our data if we leave?
Call records come out over the API, and recordings over authenticated links, in formats that are not ours. There is no minimum term on any Comsky product. The refund policy is the binding text on what money comes back, and the honest summary of it is: usage you have had is not refundable, and a duplicate or incorrect charge is refunded in full.
Which carrier will carry the calls?
A DoT-licensed one, and we are not naming it until a contract is signed. Naming a carrier we have not contracted would be announcing a partnership that does not exist, and it is also the item most likely to move the launch date.
How is this different from Comsky Chat?
Chat is for conversations with your customers over WhatsApp, WhatsApp groups and website chat, in a shared inbox, and it is live and sold today. Telephony is the phone. The two meet in the same customer thread — the after-call WhatsApp message lands beside the call — but they are different products at very different stages. Comsky Chat is here.
If none of that put you off.
Tell us how many people answer the phone, what you are on today and which numbers you would need to keep. That is what decides who gets asked first when there is something to test — and, more usefully to us, the order the remaining work gets done in.
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.