Official WhatsApp Service Terms

ERPMantra is a product and service operated by SKK Developers Global IT Services.

Availability notice: The Official WhatsApp add-on is offered on request and is subject to ERPMantra onboarding readiness, written activation, Meta review and Meta/WhatsApp availability. Publication of this page does not mean the add-on is active for every customer.

1. Service model

The Official WhatsApp service connects authorised ERPMantra workflows to the WhatsApp Business Platform. It is a standalone paid add-on, disabled by default and not included automatically in any ERPMantra subscription plan. Activation starts only after the applicable ERPMantra platform fee is paid and onboarding conditions are satisfied.

2. Ownership and business assets

The customer must normally own or lawfully control its Meta Business Portfolio, WhatsApp Business Account, business phone number, display name, business profile and message templates. ERPMantra receives only the partner, app, system-user or technical permissions reasonably required to provide the requested service. The customer remains responsible for its business identity, recipients, content and authorised users.

3. Charges

The customer pays ERPMantra the platform, onboarding and support fees stated in the applicable order form. Meta/WhatsApp messaging, conversation, template or other third-party charges are paid directly by the customer to Meta or its selected provider unless the order form expressly states otherwise. Meta may change pricing, categories or billing rules independently.

4. Activation prerequisites

• an active ERPMantra customer account and accepted applicable terms;
• payment of the applicable ERPMantra add-on/platform fee;
• an eligible Meta Business Portfolio and customer-owned WhatsApp Business Account;
• a business phone number eligible for onboarding and access needed to verify it;
• accurate legal-business, website, privacy and contact information;
• approved templates and documented messaging use cases; and
• consent, opt-out, recipient and administrator details requested for safe activation.

5. Customer messaging obligations

The customer must comply with applicable law and all current Meta/WhatsApp business, commerce, messaging and acceptable-use policies. In particular, the customer must:

• message only recipients for whom it has a lawful basis and any required opt-in;
• keep reliable evidence showing when, how and for what purpose consent was obtained;
• identify the sender and purpose accurately and use approved templates where required;
• honour STOP, unsubscribe and other opt-out requests promptly;
• avoid spam, purchased lists, misleading content and prohibited goods or services; and
• keep student, parent, staff and other personal data accurate and limited to the intended purpose.

6. ERPMantra operational role

When authorised, ERPMantra may assist with technical onboarding, templates, message dispatch, delivery webhooks, error handling, consent/suppression controls and operational reporting. ERPMantra does not determine the customer's recipients or underlying communication purpose. We may block a workflow, recipient or integration if needed to protect consent, security, system stability or policy compliance.

7. Meta-controlled dependencies

Meta/WhatsApp controls business verification, display-name approval, template approval, phone-number status, messaging limits, quality ratings, policy enforcement, pricing and platform availability. Approval or continued availability is not guaranteed. Rejection, restriction, delay, outage or account action by Meta is outside ERPMantra's direct control, although we may provide reasonable technical assistance under the applicable order.

8. Data, security and confidentiality

WhatsApp identifiers, message instructions, message content, statuses and webhooks may pass through ERPMantra and Meta/WhatsApp to operate the service. Each party must limit access to authorised personnel and protect credentials and business assets. The customer must never share OTPs, passwords or unrestricted administrator credentials over ordinary email or support chat. Data practices and retention are described in the Privacy Policy.

9. Templates, records and auditability

The customer is responsible for template wording and classification. ERPMantra may retain template versions, dispatch records, delivery/failure statuses, consent evidence, suppression records and operator audit events as needed for support, compliance and dispute handling. Delivery status does not prove that the intended person read or acted on a message.

10. Suspension and disconnection

We may suspend sending for non-payment, suspected compromise, missing consent, excessive failures, opt-out violations, prohibited content, Meta policy action or material breach. On termination, the customer should revoke ERPMantra access in Meta Business settings. Data deletion and retention follow the applicable order form, Data Deletion page and law.

11. Service levels and support

Any onboarding date, support response, availability target or service credit applies only as stated in the applicable order form. Meta/WhatsApp outages, reviews, restrictions and policy decisions are excluded unless that order form expressly provides otherwise.

12. No affiliation or endorsement

WhatsApp and Meta are trademarks of their respective owners. ERPMantra's compatibility with the WhatsApp Business Platform does not imply sponsorship, endorsement or ownership by Meta or WhatsApp.

13. Contact