The WhatsApp Business Platform is Meta’s solution for business messaging through approved templates, automated notifications, customer support, chatbots and integrations.

The app serves small-team conversations; the API enables integrations, shared inboxes, webhooks and scaled workflows through a compatible platform.

You may Contact our Pre Sales/Arihant Global Helpdesk team, provide business details, complete Meta Embedded Signup, connect an eligible phone number and configure services.

Meta may request legal registration, proof of business name/address and verification of business contact details. Accepted documents vary.

In Meta Business Settings, select the portfolio, open Security Center and start verification if offered. Supply the requested details and monitor status.

If pending, monitor requests without duplicate submissions. If rejected, review the reason, correct discrepancies and resubmit or appeal if available.

Possibly, through supported migration or coexistence arrangements. Eligibility depends on the existing number and configuration, during to migration 2FA should disabled.

A guided flow to connect a business portfolio, WhatsApp Business Account and eligible phone number to a provider.

Check the country code, SMS/voice access and retry guidance. Do not repeatedly request OTPs during a rate-limit period.

An additional PIN-based protection for the number. Follow authorized migration instructions and never disclose the PIN.

A 640 × 640 px square PNG or JPG is a practical recommendation. Center the artwork with space for circular cropping.

In WhatsApp Manager, select the WABA and phone number, open profile settings, upload the photo and save. Some configurations use the provider or app.

Supported fields can be updated in the manager or platform. Display-name changes may require Meta review.

Yes, subject to account eligibility, number limits and provider capabilities.

A structured message used to initiate business messaging outside the customer service window. Templates may include variables, media and buttons.

Marketing: promotions; Utility: service/order updates; Authentication: OTP and verification <as per the meta approved Terms>. Meta determines the category.

Many templates are reviewed within minutes or hours, but reviews may take longer. If pending after roughly 24 hours, check status with your provider.

Possible causes include policy violations, misleading wording, category mismatch, unsupported content or invalid variables.

Some edits are supported but can trigger re-review. Check status before sending.

Allowed combinations and button limits depend on template type and current Meta rules. Use distinct labels/actions; provider UI may impose additional constraints.

Yes. Variables such as {{1}} and {{2}} can be mapped to customer-specific values. Supply representative examples for review.

No. Obtain appropriate opt-in, comply with relevant laws and Meta policies, and honor opt-out requests.

Common Cloud API maximums: images 5 MB (JPEG/PNG), video 16 MB (MP4/3GP), documents 100 MB (supported formats), audio 16 MB. Provider limits may be stricter, you may cross check always before onboard.

Some platforms use hosted URLs instead of stored media IDs, or prior media references may expire. Confirm the workflow with the provider.

In the provider Media Library / Media Spot, select the uploaded file and copy the URL if the feature is available.

When supported, use an accessible HTTPS URL with the correct file type. Do not expose confidential documents via public links.

Yes, using supported document, image and catalog messaging features according to the chosen workflow.

Not by default. Some portfolios begin at 250 unique recipients per rolling 24-hour period for business-initiated messages outside the service window. Eligible tiers can progress to 2,000, 10,000, 100,000 and Unlimited, subject to Meta rules/quota.

Follow an eligible scaling path, maintain good quality, use opted-in recipients and satisfy Meta’s activity criteria. Upgrades are not guaranteed.

Messaging limit concerns unique recipients in a rolling window; throughput concerns processing speed (messages per second).

An account-quality signal influenced by recipient experience, including blocks and reports.

Recipient-level marketing controls, account status, content, eligibility and other delivery restrictions can apply.

Meta generally charges per delivered template message according to category and recipient country. Eligible service-window replies and utility templates can have different charging treatment. Provider fees may apply.

Not entirely. Messaging, software, support, chatbot or agent-seat fees may apply under your plan.

You may see in Arihant Global dashboard, once you login in panel you will get and choose as per the required services you chosen.

Available reports may include sent, delivered, read, failed and billed messages, depending on your platform.

Meta template fees are generally delivery-based; provider-specific fees may differ. Refer to the service agreement/SOWs.

Yes. Incoming messages can be handled through a shared inbox, bot, CRM or integrated application, cost parameters and setup need to discuss with our helpdesk team at: [email protected]

A customer message opens a 24-hour window for supported non-template replies. Outside it, an approved template is generally required.

Yes, for FAQs, lead qualification, order updates, appointments and other supported workflows.

Yes, when the selected platform supports human handoff, we have enterprise and control panel for setting up such provisions, feasibility need to check as per your further requirement.

Yes, through APIs, webhooks and compatible connectors, subject to scope.

Yes, using the appropriate templates, category and secure integrations.

Yes, through a compatible team inbox. Seat limits and fees depend on the package.

Meta withheld delivery to maintain healthy ecosystem engagement, commonly in marketing messaging. Improve consent, targeting and relevance.

Message undeliverable. Recipient eligibility, availability, blocking or other restrictions may be involved; the exact cause may not be exposed.

A recipient may be part of a Meta experiment restricting certain marketing messages. Providers cannot override it.

No. It indicates an HTTP-layer success, not final delivery. Check response payload, message ID and delivery webhooks.

Subsequent delivery can fail due to restrictions, template status, media problems or Meta controls.

Yes. Configure authenticated HTTPS webhook endpoints and process asynchronous delivery and incoming-message events.

Yes. Obtain appropriate consent, identify the sender and honor opt-outs; maintain records as applicable.

A purchased list alone does not demonstrate valid WhatsApp opt-in.

The platform has security controls, but businesses must protect tokens, webhooks, CRM data and access permissions.

Only authorized personnel with least-privilege permissions and strong account protection.

Avoid exposing credentials in URLs or browser-side code. Use server-side authentication and secure secret storage.

Rotate or revoke immediately, review logs and access, and investigate potential exposure.

Assistance with onboarding, templates, messaging campaigns, engagement, chatbots and integrations, according to the subscribed package.

No. Meta controls verification, template approvals and messaging-limit eligibility.

Email [email protected] ; call or WhatsApp +91 9799135786 or Call: 0141-29426222 <Ext 601, 602>; visit and submit contact us form https://arihantglobal.in.