FAQ

Robeeta Cloud Ms4 is a unified web platform that allows you to send and manage SMS and WhatsApp messages for your business communication needs.

The platform supports both SMS (Transactional & Promotional) and WhatsApp messaging using approved templates.

To send messages through the platform, follow these steps:

• For SMS: You must complete DLT registration, including:
  • Register your Entity
  • Register Sender ID (Header)
  • Get your SMS Templates approved
  After approval, link these details to the Msg4 platform to start sending SMS.
• For WhatsApp: You need a verified Meta Business Account and an approved sender number (WABA onboarding). Then connect it to the Msg4 platform.

Once setup is complete, go to the “Send SMS” or “Send WhatsApp” tabs, choose a template, select contacts, and either schedule the message or send it immediately.

Yes, you can create groups, import contacts using excel files, and manage them directly from the Contact Management section.

WhatsApp templates are pre-approved message formats used for initiating messages to users. You can configure and request new templates in the Template Management section.

Yes, you can schedule both SMS and WhatsApp messages for future delivery by selecting a date and time before sending.

Yes, detailed delivery reports with status, time, and response are available under the “Reports” and “Message List" section.

Yes, two-way communication is supported. Replies will appear in your inbox or conversation thread if the customer responds within the 24-hour WhatsApp window.

Yes, Robeeta Cloud Messaging is fully responsive and can be accessed from desktops, tablets, and mobile browsers.

If you need assistance, our support team is here to help:

DLT (Distributed Ledger Technology) is a blockchain-based registration system introduced by TRAI (India) to regulate SMS communications and prevent spam. All entities sending SMS must register on a DLT platform.

This is the unique registration ID provided after your business is registered on a DLT platform (e.g., Jio, Airtel, Vodafone).

A Sender ID (or Header) is a 6-character alphanumeric identifier that appears as the sender name in the SMS. For example: “VM-ROBEET”. It must be registered and approved in the DLT portal.

• Transactional SMS: For critical alerts (e.g., OTP, order status). Delivered 24/7.
• Promotional SMS: For marketing/promotions. Sent only between 10 AM – 9 PM.
• Service Implicit: Informational updates to customers (e.g., balance update).
• Service Explicit: Informational with user consent (e.g., offers after opt-in).

Yes. All SMS templates (content) must be approved on the DLT portal. Only approved templates can be sent using your Sender ID.

SMS template length depends on encoding:

• GSM-7 (English): 160 characters per SMS
• Unicode (Emojis/Non-English): 70 characters per SMS
• Concatenated messages:
  • GSM-7: Up to 7 parts (153 chars each) ? Max: 1,071 characters
  • Unicode: Up to 7 parts (67 chars each) ? Max: 469 characters

Yes, emojis are supported via Unicode encoding. However, the SMS length reduces to 70 characters per message. Template approval is subject to DLT rules regarding Unicode content.

While DLT does not specify a hard limit, the best practice is to keep each variable under 30–40 characters to stay within total message size constraints after dynamic data is inserted.

You can use up to 10 variables per SMS template. However, using fewer (3–6) ensures easier readability and approval.

A Principal Entity can register multiple Sender IDs (6-character headers) depending on services or departments. Each Sender ID must be approved by the DLT platform.

There is no official limit. A Principal Entity can register hundreds of templates across multiple categories, services, and languages, provided each one is DLT-approved.

Promotional SMS can only be sent between 10 AM and 9 PM, and only to non-DND numbers.
Service (implicit/explicit) and transactional SMS can be sent 24x7, even to DND numbers.

Only Transactional and Service (Implicit/Explicit) messages are allowed to DND numbers. Promotional SMS will be blocked for DND subscribers.

No. Each template must be individually mapped to a specific Sender ID on the DLT platform.

DLT approval usually takes 1–3 working days. However, this may vary depending on the DLT operator and accuracy of your submission.

Yes. As per DLT guidelines, dynamic links must follow a specific format:

• The base domain (e.g., https://example.com) must be whitelisted.
• Your Sender ID (Header) must be included in the URL path after the base domain.
• You can use variables in the format {#var#} for personalization.

Example:
https://example.com/EXMPL/track_order?transaction_id={#transaction_id#}

In this example:

• https://example.com – Base domain
• EXMPL – Sender ID
• {#transaction_id#} – Dynamic variable

Important: Variable names are case-sensitive and must match the data sent via API. Incorrect or missing formatting will cause template rejection or SMS delivery failure.

DLT portals do not provide sandbox testing. However, once your template is approved, you can test SMS delivery using the Robeeta Cloud Msg4 web console. Use the Send Single SMS feature to test the message with a real mobile number before launching your bulk SMS campaign.

No. SMS supports only text content and does not support multimedia content like images or videos.

Login to your DLT portal, navigate to your template list, and choose to edit or delete. Updated templates must go through a new approval cycle.

SMS without approved DLT templates will be rejected by telecom operators and not delivered. It may also result in temporary suspension or blacklisting of your Sender ID or Entity by the DLT platform. Always ensure templates and Sender IDs are approved before sending.

Yes. Both are supported:

• Static URL: Fixed link like https://robeeta.link/track123
• Dynamic URL: Use variables (e.g., {{1}}) and send personalized links like https://robeeta.link/user123

Ensure all domains (e.g., robeeta.link) are whitelisted during DLT template approval.

Yes. You can include mobile numbers or any user-specific data as variables like {{1}}, {{2}}, etc.

Example template:
Hi {{1}}, your mobile {{2}} is verified.

CTA Whitelisting:
Any URLs, phone numbers, or email addresses used in your SMS—whether static or passed as variables—must be whitelisted on the DLT platform. This ensures only verified and safe content is delivered, helping prevent spam and fraud.

SMS gateways report various delivery failure statuses. Common ones include:

• REJECTED: SMS content or template not approved on DLT.
• FAILED: Delivery failed due to invalid mobile number or technical issue.
• UNDELIVERED: Message couldn't reach the recipient due to network issues or the device being unreachable.
  • Category has been blocked: Attempted to send a promotional SMS to a DND (Do Not Disturb) number.
  • Content not mapped with the template: Message content does not match the approved DLT template.
  • Header not active: Sender ID (Header) is not active or not approved on DLT.

Tip: Always ensure your templates, headers, and recipient numbers comply with DLT and telecom regulations to avoid delivery failures.

Here are common reasons and fixes:

• Unapproved Template: Ensure DLT template is approved and matched
• Sender ID mismatch: Template must be linked to specific Sender ID
• DND Restriction: Do not send promotional SMS to DND numbers
• Unwhitelisted Domain: Register your base URL on the DLT portal
• Overlong Variables: Keep each variable under 30–40 characters
• Wrong Time: Promotional SMS must be sent between 10 AM – 9 PM

Yes. This is called bulk personalized messaging. You can send the same template to many users by:

• Using an approved template with dynamic variables (e.g., {{1}}, {{2}})
• Populating each message with user-specific values (e.g., name, URL, mobile)
• Ensuring you follow type and time restrictions (promotional vs. service)

Meta (formerly Facebook) requires businesses to verify their Business Manager, link a phone number, and go through WABA (WhatsApp Business API) onboarding via providers like Tata, 360dialog, Gupshup, or Twilio.

This is your official business-registered number on WhatsApp used to send messages. It must be verified and approved by Meta during onboarding.

• Session Messages: Any message sent within 24 hours of the user's last reply.
• Template Messages: Pre-approved messages used to initiate conversations beyond the 24-hour window.

• Marketing: Offers, updates, re-engagement.
• Utility: Transactional updates (e.g., invoice, order info).
• Authentication: OTP and login verification.

You can use numbered variables like {{1}}, {{2}} etc. for dynamic content such as names, dates, and values. All variable data must match the content type during API submission.

• Image: JPEG, PNG (Max: 5MB)
• Document: PDF, DOC, XLS, etc. (Max: 100MB)
• Video: MP4, 3GP (Max: 16MB)
• Header: Can be text, image, or document depending on template type

WhatsApp applies messaging tier limits based on business phone quality and user engagement:

• Tier 1: 1K unique users per day
• Tier 2: 10K unique users/day
• Tier 3: 100K users/day
• Higher tiers require strong quality and engagement metrics.

Each part of a WhatsApp template has specific character limits:

• Header: Up to 60 characters (if it's a text header)
• Body: Up to 1024 characters
• Footer: Up to 60 characters

For media-based headers (image, video, document), no text is used in the header section.

Variable values can be up to 256 characters long. Avoid sending large JSON strings or encoded media.

Yes. WhatsApp fully supports emojis in template content, including headers, body, and footers.

You can include up to 30 variables in the body of a WhatsApp template.

Each sender (business number) can have hundreds of templates, depending on approval and usage. Meta doesn’t publicly enforce a strict cap but recommends template management based on relevance.

A business account can have multiple sender numbers. The limit depends on the number of phone numbers verified in Meta Business Manager (typically up to 20 by default, can be increased upon request).

Each WhatsApp template can include one media file (image, video, or document) in the header. Multiple attachments are not supported in a single message.

Most WhatsApp templates are approved within 24–48 hours by Meta, but it may take longer during peak times or if the content needs clarification or review.

Common reasons for template rejection include:

• Using promotional content in a utility or authentication template
• Inappropriate or vague language
• Unclear or misused variables
• Missing proper format or structure

You can revise and resubmit rejected templates.

Yes. WhatsApp supports several types of interactive elements in templates:

• Call-to-Action (CTA) Buttons: Up to 2 buttons for actions like "Call Now" or "Visit Website".
• Quick Reply Buttons: Up to 3 buttons for predefined replies like "Yes", "No", "More Info".
• List Messages: Allows a dropdown-style list with a header, body, and multiple options for users to choose from.

These components must be configured during template creation. You cannot change them dynamically while sending the message.

Yes, WhatsApp supports combining text content with interactive components using the API. You can send messages that include a text body along with buttons or list messages. This helps improve user engagement and makes your communication more actionable.

WhatsApp defines specific limits for interactive templates:

• Quick Reply Buttons: Up to 3 buttons per message
• Call-to-Action Buttons: Up to 2 buttons (e.g., Call or Visit Website)
• List Messages: Can contain up to 10 selectable options
• Character Limits:
  • Body Text: Max 1024 characters
  • Header Text: Max 60 characters
  • Footer Text: Max 60 characters
  • Button Text: Max 20 characters per button

Note: Buttons, lists, and other interactive elements must be part of the approved template and cannot be added dynamically during a session.

No. WhatsApp templates support only static media in the header section. You cannot personalize images or videos based on user data at the template level.