About

Your identity, your team and your billing live in CosmoOps Connect, the platform this application is part of — so there is no second password, and the invoice comes from one place however many CosmoOps products you use. Messaging itself holds your senders, templates, contacts and message log.

Delivery is through a DLT-registered Indian aggregator. We do not own a carrier licence and do not claim to; what we own is the registration workflow, the compliance checks and the record of what happened.

• We refuse rather than attempt. A message whose template is not approved, whose sender is not registered, or whose category does not match its header would be dropped silently by the carrier and still charged. So we refuse it at submission, with the reason, instead of taking the money.
• A skip is not a failure. A promotional campaign passes over DND contacts, and they are counted and labelled separately. Folding them into a failure count is how a customer concludes a campaign broke when it was obeying TRAI.
• We bill on carrier acceptance, and say so. An accepted message that is later undelivered is still charged, because that is how our own carrier bills us. Putting it in the terms rather than discovering it on an invoice is the difference.

No delivery webhooks yet — you poll the status endpoint. No international routes. No voice, WhatsApp or email. No API for creating templates, because registering one needs a human decision about what text to put in front of an operator.

Publishing that list is deliberate. An SMS provider’s feature page that implies everything is available costs you an integration you have to unpick.

COSMOOPS OPC PRIVATE LIMITED, Aziz Nagar ,2nd cross ,Reddiyarpalayam.

hello@cosmoops.com · cosmoops.com