API & Number Ban Responsibility Policy

1. Purpose & Scope

This policy explains, in plain terms, who is responsible when a client's WhatsApp Business number is restricted, flagged, quality-downgraded, or permanently banned by Meta — Automyra Ai Agency (the delivery platform) or the client (the business using it). It applies to every client onboarded onto the Automyra dashboard for WhatsApp, Instagram, or Messenger messaging via Meta's Cloud API.

Automyra operates strictly as a technology enabler. We connect a client's own WhatsApp Business Account (WABA) to our dashboard, provide inbox, broadcast, template, and automation tooling, and manage the technical uptime of that connection. We do not control, approve, or monitor the content a client's team sends, the audiences they message, or the opt-in practices used to acquire those audiences — those decisions belong entirely to the client.

In short: Automyra is responsible for the pipes. The client is responsible for what flows through them — the content, the audience, and the honesty of what a message claims to be.

2. How Meta Actually Enforces Its Policy

The responsibility split in Section 3 is not an opinion — it follows directly from how Meta's WhatsApp Business Platform is documented to operate.

2.1 — Opt-in is the business's obligation, not the platform's

Meta's WhatsApp Business Messaging Policy requires that a business obtain clear, explicit opt-in from a customer before sending them any message. This obligation is placed on the business — the entity that owns the WABA and the customer relationship — not on the technology provider that supplies the sending interface.

2.2 — Quality rating is driven by recipient reaction to content, not delivery infrastructure

A number's quality rating is calculated from how recipients respond to what they receive — blocks, reports, and negative feedback signals — combined with the content and relevance of the messages themselves. It is not affected by which dashboard, BSP, or CRM was used to send the message. A drop in quality rating is Meta measuring the client's message content and targeting, not Automyra's platform performance.

2.3 — Enforcement is warning-first and escalating

Meta's policy enforcement framework is not a single-strike system. Violations typically trigger a warning, then escalating restrictions (limited messaging, template pausing) on repeat or uncorrected violations, before a full account ban is applied. A ban is therefore evidence of a pattern the client was already notified about and did not correct — not a sudden, unexplained platform failure.

2.4 — Template miscategorization is itself a documented violation

Submitting marketing content under a Utility or Authentication template category — a common tactic to reduce per-conversation cost — is explicitly treated by Meta as a policy violation in its own right, independent of any other issue with the message. Template category selection is made by the client (or filled in on the client's instruction) at the point of template submission.

3. Responsibility Split

The table below is the operative part of this policy. It is incorporated by reference into every Automyra Client Service Agreement.

AUTOMYRA IS RESPONSIBLE FOR

Technical integration and uptime of the dashboard-to-WhatsApp Cloud API connection
Correct configuration of webhooks, message routing, and inbox/broadcast delivery mechanics
Timely submission of templates exactly as instructed and approved by the client
Data security of information stored within the Automyra dashboard
Advising the client — in writing — when we observe activity that risks a Meta violation
Platform-side bugs, outages, or misconfiguration that we caused

THE CLIENT IS RESPONSIBLE FOR

Obtaining verifiable, documented opt-in from every contact before messaging (Section 2.1)
All message content, creative, links, and claims sent from their number
Accuracy of the template category declared for each template (Marketing vs. Utility vs. Authentication)
The source, quality, and consent status of every contact list or audience uploaded
Responding to and correcting any warning issued by Meta or flagged by Automyra
Compliance with the WhatsApp Business Messaging Policy, Commerce Policy, and Business Terms as the account owner

4. Worked Scenarios

Scenario A — Number restricted after multiple recipient reports

Client uploads a purchased or scraped contact list and sends bulk promotional messages without prior opt-in. Recipients mark the number as spam; Meta lowers the quality rating and restricts sending.

CLIENT RESPONSIBILITY — no verifiable opt-in, per Section 2.1

Scenario B — Template rejected/account flagged for category mismatch

Client asks Automyra to submit a promotional discount template under the 'Utility' category to reduce conversation cost. Meta detects the mismatch and flags the account.

CLIENT RESPONSIBILITY — category instruction and content originated from the client, per Section 2.4

Scenario C — Messages fail to send due to a dashboard/webhook fault

Automyra's webhook misconfiguration causes duplicate sends or failed delivery, independent of message content or targeting.

AUTOMYRA RESPONSIBILITY — technical delivery fault, per Section 3 (left column)

Scenario D — Client ignores a documented warning and continues the same practice

Automyra flags a rising block rate and advises the client in writing to change targeting. Client continues the same campaign; Meta escalates to a temporary restriction, then a ban.

CLIENT RESPONSIBILITY — warning was issued and not acted on, per Section 2.3

Scenario E — Mixed cause

Client's content is compliant, but an agency configuration error also independently triggers a warning (e.g., malformed template variables causing recipient confusion and reports).

SHARED — reviewed case-by-case against the evidence available at the time

5. What Automyra Does to Help Prevent Bans

Although the compliance obligation sits with the client, Automyra takes proactive steps because a banned number is bad for everyone involved:

Important: These are supportive measures, not a guarantee. Automyra does not have the ability to inspect a client's real-world consent records, verify the true source of an uploaded contact list, or override a client's content decisions. Providing a warning does not shift responsibility back to Automyra if the client proceeds regardless.

Dashboard prompts requiring confirmation of opt-in source before a broadcast list can be sent
Template category review before submission, with a written recommendation to the client where a category looks mismatched to the content
Quality-rating and block-rate monitoring, with proactive written alerts to the client when metrics trend downward
Onboarding guidance covering Meta's opt-in and content rules before a client's first campaign

6. Process if a Number Is Restricted or Banned

1Automyra collects the available facts from the dashboard logs and Meta's Business Manager/notification (timestamp, cited reason, message history where accessible).
2The case is assessed against Section 3 and the scenarios in Section 4.
3The client is issued a written summary of the finding, referencing the specific clause and Meta source relied upon.
4Where the cause is client-side, Automyra will still assist with Meta's appeal process on a best-effort basis, but does not guarantee reinstatement — that decision rests solely with Meta.
5Where the cause is agency-side, Automyra will remediate the fault and this will be documented against our own service-credit policy in the Client Service Agreement.

7. Relationship to the Client Service Agreement

This policy is referenced by, and forms part of, the Automyra Client Service Agreement executed with each client. In the event of any conflict between this policy and the Service Agreement, the Service Agreement's liability and indemnity clauses govern.

8. Policy Review

Meta updates its WhatsApp Business Platform policies from time to time. Automyra reviews this document against Meta's published policy pages periodically and will notify clients of material changes. Clients remain bound, at all times, by Meta's current policy directly — this document is Automyra's interpretation and operational summary of it, not a replacement for it.

PRIMARY SOURCES REFERENCED

Hafiz Saad Khalil

Founder & CEO, Automyra Ai Agency

Client Representative — Name & Signature