01
Describe the task
Explain whether you are setting up a channel, sending messages, connecting an integration, checking delivery, or troubleshooting an existing workflow.
Support
Support & Help Center
Get help with onboarding, troubleshooting, or account questions- guides, FAQs, and a real team that replies within 24 hours.
24-hour response · +91 96676 94088 · Noida, India
Trusted by 10,000+ businesses across India
Ways to Get Help
Choose whatever fits your question
Contact Our Team Directly
Reach us by phone at +91 96676 94088 or through the contact form- we reply within 24 hours on business days.
Browse Frequently Asked Questions
Answers to the most common onboarding, pricing, channel, and compliance questions in one place.
Read Guides on the Blog
In-depth guides on WhatsApp, RCS, Bulk SMS, and Voice/IVR- setup, best practices, and troubleshooting.
Enterprise Account Support
Enterprise clients get a dedicated account manager and negotiated SLA terms instead of a shared support queue.
Common Topics
Jump straight to what you need
Getting Started & Onboarding
Setting up your first WhatsApp, RCS, SMS, or Voice channel.
Pricing Questions
Understanding per-message, per-conversation, and per-minute pricing across channels.
DLT & Compliance
Principal Entity registration, Sender IDs, and template approval for SMS compliance.
Integrations
Connecting your CRM, helpdesk, or e-commerce platform to your messaging channels.
Support Workflow
Start with the right information
Good support starts with a clear description of what you are trying to do and what is not working. Sharing a few useful details helps the team understand the issue faster and point you toward the right guide, configuration, or next step.
02
Share the channel
Mention whether the issue relates to WhatsApp, RCS, Bulk SMS, Voice or IVR, email, or an integration with another business system.
03
Add the error or result
Include the message, error description, or unexpected result you are seeing. A precise example is often more useful than a general statement that something failed.
04
Tell us the urgency
Let the team know whether you are planning an implementation, testing a workflow, or dealing with an issue that is currently affecting customer communication.
A simple support request can be enough
You do not need to prepare a technical report before contacting the team. A short description of the business use case, the communication channel, the expected result, and the result you are seeing is a useful starting point. When more information is required, the team can ask focused follow-up questions.
Response Time & Contact
24-hour response, every business day
Our team typically replies within 24 hours on business days. For anything urgent, call us directly at +91 96676 94088.
Troubleshooting Guide
Common support situations
Many support questions fall into a few familiar categories. Knowing the type of problem can help you choose the right documentation or explain the issue clearly when contacting the support team.
Message delivery
When a message does not reach the intended customer, start by identifying the channel, message type, approximate send time, and the response or delivery status returned by the system.
Template or compliance questions
For SMS, WhatsApp, or RCS setup questions, provide the relevant template, sender information, or approval message so the team can understand which part of the process needs attention.
API and integration issues
If an API or integration is involved, include the endpoint or workflow area, the type of request, and the response or error you received. This helps narrow down where the connection may be failing.
Account and onboarding
New account questions may involve setup steps, account verification, channel configuration, sender details, or access requirements. Start with the service you are trying to activate.
Pricing and billing
For pricing questions, mention the service and an approximate usage level. The existing pricing guides can provide initial context before you contact the team for account-specific information.
Business workflow questions
Some questions are not errors at all. Teams may need help deciding which channel, automation, integration, or message flow best matches a customer communication use case.
Still stuck?
Send us a message with what you're trying to do- we'll point you to the right guide or get on a call.
One message could
change your business.
Big or small, we power communication for all- talk to us today.
Onboarding Support
From first setup to ongoing usage
Support is useful at different stages of a messaging project. New teams may need help understanding the setup process, while existing users may need guidance when changing workflows, adding channels, or connecting another system.
Starting a new channel
Ask about the steps needed to get a WhatsApp, RCS, SMS, or Voice workflow ready, including the information and configuration required for the service you choose.
Improving an existing workflow
When a workflow is already live, support questions can focus on delivery, automation, integrations, message content, or operational changes.
Adding an integration
CRM, helpdesk, and e-commerce integrations can introduce new technical steps. Share the system you are connecting and the part of the workflow you want to automate.
Scaling communication
As message volumes and customer journeys grow, teams may need help reviewing channel usage, operational processes, and the tools used to manage communication.
Frequently Asked Questions
Support FAQs
Call us directly at +91 96676 94088, or reach out through our contact form- our team typically replies within 24 hours on business days. Contact us.
Our team replies within 24 hours on business days. For urgent queries, calling directly is the fastest way to reach us.
Each topic has its own dedicated guide- pricing pages per channel, a DLT registration walkthrough, and integration guides for CRM and helpdesk platforms- all linked above under Common Topics.
Yes- you can call our team directly at +91 96676 94088 during business hours.
Yes. Enterprise accounts move to a dedicated account manager and negotiated SLA terms- uptime, delivery-latency, and support-response commitments- rather than a shared support queue. See enterprise solutions.