Frequently Asked Questions

No. The WhatsApp Business app is Meta's mobile application for manually managing business conversations. WebWMS2u provides browser-based campaigns, automation, APIs, webhooks, contact management and message reporting.

With an eligible Coexistence connection, the same business number can be used in the WhatsApp Business app and connected to WebWMS2u through Meta's official platform.

Yes. A trial account can connect one eligible Meta Cloud API or WhatsApp Coexistence number and use the available trial credits to test supported messaging and automation features.

You must connect a number that you are authorised to manage and complete Meta's official onboarding process. Meta determines number eligibility, business verification requirements and message-template approval.

Meta WhatsApp Business Platform charges, if applicable, are billed separately from WebWMS2u trial credits.

A Meta Business Portfolio and WhatsApp Business Account are required for Meta Cloud API and Coexistence onboarding. The person completing Embedded Signup must have suitable access to that portfolio.

A Meta Business Portfolio is not required for a Personal Device Connection.

Often, yes, but the available method depends on the number's current registration.

• A number already used in the WhatsApp Business app may be eligible for Coexistence.
• A new or unused number can normally be registered as a standard Cloud API number.
• A personal WhatsApp number may be used through Personal Device Connection, subject to WebWMS2u requirements.

Do not remove or re-register an important number until you have confirmed the correct migration process.

Choose standard Meta Cloud API when you want an official API-only number. Choose Coexistence when you want the benefits of Meta Cloud API while continuing to use an eligible number in the WhatsApp Business app.

Personal Device Connection may suit simpler workflows or businesses that are not ready for Meta onboarding, but it is not the same as Meta's official WhatsApp Business Platform.

Personal Device Connection links a WhatsApp account to WebWMS2u using WhatsApp's linked-device functionality. It can be useful for simpler workflows or when Meta Cloud API onboarding is not suitable.

It is not the same as Meta's official WhatsApp Business Platform, and continued operation depends on the connected device session remaining available.

No. Personal Device Connection does not use Meta Cloud API onboarding and therefore does not require Meta Business Verification. You still need a working WhatsApp account and must comply with WhatsApp's terms and messaging policies.

Messages cannot be sent through that connection while its linked-device session is disconnected. Reconnect or scan the QR code again from your WebWMS2u account before resuming messages.

Normal self-service registration does not automatically include a setup fee. A separate fee may apply if you request assisted onboarding, custom integration, workflow development, data preparation, AI configuration or other professional services.

Any additional fee will be confirmed in advance or stated in your quotation.

Local customers can pay in Malaysian Ringgit by bank transfer. PayPal is available for supported payments and is recommended for international customers. Enterprise and special arrangements may be handled through a quotation.

WebWMS2u's standard published subscription plans are billed yearly. If you need an Enterprise or specially quoted arrangement, please contact us.

Messaging and automation that require platform credits may stop when your available balance is exhausted. Top up or upgrade as appropriate. Module subscriptions do not provide unlimited messages; monitor the shared account balance before accepting live orders or bookings.

When WebWMS2u records an outbound message as failed under its supported refund rules, the deducted platform credit can be returned and recorded in the credit transaction history.

A failed or refunded WebWMS2u credit does not automatically reverse a separate charge already imposed by Meta.

Published plan credits are allocated per annual subscription term, not renewed each month. You can use the available credits during the term and purchase additional credits. Your plan terms determine validity; this is separate from Meta's monthly Service-message allowance.

Yes. The modules are activated separately. Use distinct entry keywords, such as ORDER and BOOK, and test routing on your configured channel before going live. Platform messaging uses the same account credit balance.

Contact us to arrange a demonstration or module trial. The 14-day platform trial does not automatically activate either module. Any module trial period, outlet allowance and additional trial credits must be confirmed separately.

Standard module subscriptions are billed annually. A monthly equivalent shown on a page is a comparison figure, not monthly billing. Confirm your annual package and any additional services before activation.

Check that the relevant module has been activated for your account and that its entitlement is valid. If access is missing, contact support with your account name and module requested.

No. Processed inbound messages and outbound replies or alerts consume platform credits. Meta API delivery fees may also apply. Subscriptions, included annual credits and top-ups are separate cost components.

Choose a compatible plan for your channel and expected usage. Starter supports Personal WhatsApp; using your own Meta number requires a plan with own-number support, such as Growth. Provider shared Meta numbers are not an Ordering channel. Confirm channel eligibility for your quotation.

Yes. Allocate your available account credits across Ordering, Booking, campaigns and other automation. Do not count the same included credits twice when preparing budgets. Included plan credits are an annual allocation, not a fresh monthly allocation.

The customer sends your configured entry keyword, such as ORDER. The guided flow presents your shop and available outlets, then collects the selections and details needed to submit the order.

Yes. Configure categories, pictures, descriptions, prices and optional extras. Customers can use the visual web menu with pictures and Add buttons, or continue the existing paginated text menu in WhatsApp.

Yes. Customers can choose products and quantities and use configured modifier options. Configure required choices and selection limits carefully before testing your menu.

The menu presents up to ten products per page. Customers can use NEXT, PREVIOUS and BACK, and select a category or view all categories.

Yes, according to the outlet settings. Delivery requires an address and your own fulfilment arrangements. Check the address and delivery suitability before accepting the order; WebWMS2U does not provide riders or dispatch services.

Yes. Use a connected Personal WhatsApp device or your own supported Meta number. Meta sends remain subject to its customer service window, approved templates and separate delivery charges.

One outlet is included in the standard Ordering add-on. Extra outlets require an additional allowance and subscription. An account has one shop profile and can use shared or different outlet menus.

Yes. Share a catalogue or duplicate a menu for independent editing. Duplicated menus can reuse existing image references rather than creating additional image-file copies.

Published launch pricing is RM468 per year for one outlet, plus RM228 per year for each extra outlet, subject to quotation. The base plan, additional platform credits, applicable Meta fees, optional capacity and other quoted services are separate. See Ordering pricing.

Using the published figures, Starter RM588 plus Ordering RM468 totals RM1,056 per year before additional usage or other quoted costs. Starter includes 1,000 annual platform credits shared with other account activity. Use a supported Personal WhatsApp connection; own-number Meta use requires a suitable plan.

The quoted Ordering subscription does not add a percentage commission on order value. Subscription, message usage, delivery arrangements and any external payment-provider costs remain separate.

Pay on pickup is available for pickup orders, or you can use your business static DuitNow QR. For QR orders, payment is requested after merchant acceptance. The merchant remains responsible for checking funds received.

No. Customers can submit payment evidence through their private order link. Staff must check actual receipt of funds and mark payment verified; a screenshot alone is not automatic bank verification.

Configure email alerts, WhatsApp alerts or both. Staff can review and act through the dashboard, a private mobile management link or supported commands from the authorised merchant number. Keep private management links within your team.

Yes. Record a reason and send the customer the supported order update. The merchant must handle any refund separately and should provide an outlet contact for enquiries.

Use roughly 25–35 credits as an initial planning range for a simple one- or two-product order, not a fixed charge or limit. Actual usage depends on browsing, modifiers, corrections, notifications and status updates. Each handled inbound message and each outbound WhatsApp message counts separately.

Email alerts and browser actions themselves do not use Ordering platform credits. Any resulting WhatsApp notification does use credits. An authorised merchant WhatsApp command and its acknowledgement also generate message usage.

Yes. Search records by customer, phone, order reference and status. Use supported order printing or browser Save as PDF, and export available CSV reports. Keep order status and payment status under review.

Automatic stock reservation and standard POS integration are outside the current module. Check availability before accepting orders. POS mapping or other custom integration must be assessed and quoted separately.

See the Ordering overview, customer journey, pricing and Ordering FAQs, or contact us for activation.

The visual web menu is optional. Customers can follow its link or continue using the existing chat ordering flow.

Yes. Both channels can offer the same responsive menu. Notifications remain associated with the number/device that started the conversation.

Yes. Product cards, cart and checkout adapt to phones and larger desktop screens. No additional customer app installation is required.

Web browsing and form submission do not use WhatsApp inbound processing credits. Real WhatsApp replies and notifications still use platform credits; applicable Meta charges are separate.

Yes. The web preview can complete a simulated checkout with a TEST reference, without creating a live order, sending notifications or deducting credits.

No online payment gateway is added. Existing pay-on-pickup and configured DuitNow QR workflows still apply. QR payment instructions follow merchant acceptance; staff verify actual funds.

No. Staff must verify payment in the bank account. Uploading a receipt is evidence for review, not automatic payment verification.

Live POS delivery is not included in this release. Saved provider preferences and neutral order JSON are a foundation; each provider still needs an authorised, tested adapter.

The current flow uses a private, time-limited link generated from WhatsApp or merchant preview. The bare subdomain is not a public shop directory or a permanent storefront link.

Repeated submissions through the same invitation return the same order. A newly generated invitation can be used for another order.

The customer sends your configured keyword, such as BOOK. The conversation collects the service, date, available time and full name. A reliable sender phone can be captured automatically, with an option to change it.

Yes. The currently published Booking service supports a connected Personal WhatsApp device and your own Meta number. Meta API conversations and notifications remain subject to window, template and billing requirements.

Yes. Create services with displayed prices and durations. Availability is checked against the full appointment length rather than just the starting time.

A shared calendar prevents services from overlapping when they use the same resource. Independent service calendars allow different services to run at the same time. Choose the arrangement that reflects your real capacity.

The current module has one account-wide booking setup. Named-staff assignment, multi-staff capacity and allocation across multiple locations are outside its present scope. Discuss those requirements before selecting a package.

Yes. Configure immediate confirmation or merchant approval. Pending approval requests hold the selected slot until they are confirmed or cancelled, so staff should review pending requests promptly.

Yes. Configure appointment periods and date exceptions. Booking intake hours can be controlled separately, and new requests can be paused until a chosen time.

Optional reminders are available and start disabled until configured. Set the reminder arrangements before use. WhatsApp reminders consume platform credits, and Meta reminders outside the customer service window require an approved template.

Yes. Staff can correct customer details, reschedule, cancel and complete appointments through supported management actions. Changes retain an audit history. Check the resulting customer and merchant notification settings.

Yes. Completed or cancelled appointments can be archived and restored. Archived appointments remain in reports; archiving hides records rather than deleting them or reclaiming storage.

No. The current Booking module does not collect appointment payments or deposits, verify payments or process refunds. Continue your normal payment arrangements and discuss any payment integration as a separate requirement.

The published indicative add-on is RM348 per year, billed annually, for one account-wide setup. A compatible base subscription, message usage, applicable Meta fees and separately quoted services are additional. Your quotation confirms activation and terms. See Booking pricing.

There is no fixed credit fee per appointment. An illustrative flow with the customer conversation, merchant WhatsApp alert, one reminder and completion updates uses 17 credits. Approval, browsing, corrections and rescheduling can change the total. Budget actual inbound and outbound messages.

Yes. Review 7-day, calendar-month and calendar-year activity and statuses. Use available CSV export and browser Print or Save as PDF for reports. Archived appointments remain part of reporting history.

See the Booking overview, customer journey, pricing and Booking FAQs, or contact us for activation.

No. Web and chat bookings share the existing scheduling engine and appointment records. They use the same availability, duration and capacity rules.

Yes. The web option is an additional route. Customers can continue the guided WhatsApp conversation if they prefer.

Yes. The invitation retains its original channel and recipient so configured updates and reminders follow that route.

Availability is rechecked under the same merchant lock used by chat/admin booking. Only one can reserve an overlapping slot where the configured capacity forbids a clash.

Yes. Simulated checkout shows a TEST reference but creates no live appointment, consumes no capacity, sends no notifications and deducts no credits.

No. This release displays the service price but does not collect booking payments or deposits. Continue using your usual payment arrangements.

Web actions do not use WhatsApp inbound processing credits. Real WhatsApp replies, notifications and reminders still follow platform credit rules and applicable Meta charges.

No. Opening or submitting the web page is not a new inbound WhatsApp message. The existing delivery rules still determine whether an approved template is required.

The current Booking setup is account-wide, using shared or independent service calendars. Named staff allocation, multi-location routing and multi-capacity services need separate scope confirmation.

No. Customers use a private invitation from the business conversation. Merchant previews use separate TEST invitations.

No. WebWMS2U platform credits pay for platform messaging and processing. They do not pay your Meta bill or purchase Meta's free allowance.

WebWMS2U platform credits are separate from Meta charges: 1 platform credit per outbound message and 1 per inbound message processed by an automation; unmatched inbound messages are free. An inbound message processed with one AI reply normally uses 2 platform credits. Platform credits still apply when Meta message delivery is free.

From 1 October 2026, each business phone number receives 1,000 free delivered service messages per month. Meta charges from the 1,001st delivered service message at the applicable Service rate for the recipient market. The allowance resets monthly; unused messages do not roll over or transfer to another number. This counts individual messages, not customers, orders or conversations.

For example, processing one incoming customer message and sending one reply normally uses 2 platform credits. The reply may additionally incur a Meta Service charge if that number's monthly allowance is exhausted and no other exemption applies. Meta does not charge a message-delivery fee for the incoming customer message.

Messages sent through the API under Coexistence use the WhatsApp Business Platform and are subject to Meta's applicable messaging limits, template rules, quality requirements and policies.

Coexistence does not provide a separate or higher API messaging limit. Check WhatsApp Manager for the messaging limit currently assigned to your business.

Meta's messaging limit controls how many unique customers your business can contact outside the customer service window during a rolling 24-hour period. It is separate from message pricing and from the total number of individual messages.

Check WhatsApp Manager for your current limit and the account or portfolio scope applied by Meta. The displayed limit is authoritative and can change with eligibility, quality and sending history.

The 1,000 free Service messages per number per month are a billing allowance, not a daily sending limit or an allowance for starting conversations.

No. Meta WhatsApp Business Platform charges are billed separately from WebWMS2U subscription fees and platform credits unless expressly included in your quotation. Meta may charge for delivered service messages as well as templates.

From 1 October 2026, each business phone number receives 1,000 free delivered service messages per month. Meta charges from the 1,001st delivered service message at the applicable Service rate for the recipient market. The allowance resets monthly; unused messages do not roll over or transfer to another number. This counts individual messages, not customers, orders or conversations.

See Meta pricing and current rate cards for rates applicable to your recipient market and billing currency.

An unverified business can have restricted messaging capacity or features. Check the current limit and verification requirements in WhatsApp Manager. These limits are separate from the monthly allowance of 1,000 free Service messages per business phone number.

Verification does not guarantee unlimited messaging. Meta determines capacity using account eligibility, quality and usage. Check WhatsApp Manager for the current limit applied to your business.

Meta may automatically increase a business's messaging limit when it uses a significant portion of its current limit, maintains good message quality and follows WhatsApp policies.

Business verification, valid customer consent, approved templates and low blocking or reporting rates can help establish eligibility. WebWMS2U cannot manually override a messaging limit imposed by Meta.

The 24-hour customer service window opens when a customer messages your business and resets with each new customer message. While it is open, you may send free-form replies without an approved template. After it closes, an approved template is required to contact that customer through the API. A business reply does not restart the window.

From 1 October 2026, each business phone number receives 1,000 free delivered service messages per month. Meta charges from the 1,001st delivered service message at the applicable Service rate for the recipient market. The allowance resets monthly; unused messages do not roll over or transfer to another number. This counts individual messages, not customers, orders or conversations.

The 24-hour window controls when free-form messages are allowed; it no longer guarantees unlimited free Meta delivery.

Utility templates are charged per delivered message both inside and outside the 24-hour customer service window from 1 October 2026. They do not use the 1,000 free service-message allowance. Marketing and Authentication templates are also normally charged when delivered.

These API pricing rules also apply to API messages sent using Coexistence. Ordinary manual messages in the WhatsApp Business app are not subject to these API message-delivery charges.

Yes. An approved template is generally required for an API-initiated message sent outside the 24-hour customer service window.

Coexistence does not remove Meta's template requirements. Templates must be submitted to Meta and approved before they can be used. Meta determines whether a template is classified as Marketing, Utility or Authentication.

Not without limit. The 24-hour customer service window permits free-form replies, but no longer guarantees unlimited free Meta message delivery.

From 1 October 2026, each business phone number receives 1,000 free delivered service messages per month. Meta charges from the 1,001st delivered service message at the applicable Service rate for the recipient market. The allowance resets monthly; unused messages do not roll over or transfer to another number. This counts individual messages, not customers, orders or conversations.

Utility templates are charged per delivered message both inside and outside the 24-hour customer service window from 1 October 2026. They do not use the 1,000 free service-message allowance. Marketing and Authentication templates are also normally charged when delivered.

Eligible messages in Meta's 72-hour free entry point window can still be free of Meta message-delivery charges. This applies to qualifying Click-to-WhatsApp ad or Facebook Page action-button entry points when the business responds within 24 hours, subject to Meta's eligibility rules. It does not extend permission to send free-form messages beyond an open customer service window.

WebWMS2U platform credits are separate from Meta charges: 1 platform credit per outbound message and 1 per inbound message processed by an automation; unmatched inbound messages are free. An inbound message processed with one AI reply normally uses 2 platform credits. Platform credits still apply when Meta message delivery is free.

Meta uses per-delivered-message pricing. The fee depends on the recipient market, message category and applicable rate card. A message being submitted or accepted by the API is not the same as being delivered.

From 1 October 2026, each business phone number receives 1,000 free delivered service messages per month. Meta charges from the 1,001st delivered service message at the applicable Service rate for the recipient market. The allowance resets monthly; unused messages do not roll over or transfer to another number. This counts individual messages, not customers, orders or conversations.

Utility templates are charged per delivered message both inside and outside the 24-hour customer service window from 1 October 2026. They do not use the 1,000 free service-message allowance. Marketing and Authentication templates are also normally charged when delivered.

Eligible messages in Meta's 72-hour free entry point window can still be free of Meta message-delivery charges. This applies to qualifying Click-to-WhatsApp ad or Facebook Page action-button entry points when the business responds within 24 hours, subject to Meta's eligibility rules. It does not extend permission to send free-form messages beyond an open customer service window.

Incoming customer messages do not themselves incur a Meta message-delivery fee.

WebWMS2U platform credits are separate from Meta charges: 1 platform credit per outbound message and 1 per inbound message processed by an automation; unmatched inbound messages are free. An inbound message processed with one AI reply normally uses 2 platform credits. Platform credits still apply when Meta message delivery is free.

See Meta pricing and current rate cards for rates applicable to your recipient market and billing currency.

No. Coexistence is an official Meta connection method, but the number must still comply with WhatsApp's Business Messaging Policy, Commerce Policy and customer consent requirements.

High block or report rates, unsolicited messages, misleading content or other policy violations can reduce message quality, restrict messaging or cause the account to be disabled.

Yes. Businesses should obtain clear consent before sending business-initiated WhatsApp messages, particularly marketing messages.

The consent process should explain that the customer agrees to receive WhatsApp messages and should identify the business or type of communication. Customers should also be provided with a reasonable way to opt out.

Blocks and reports can negatively affect the quality rating of your telephone number and message templates.

If message quality becomes poor, Meta may pause templates, reduce messaging capacity, restrict the number or disable the WhatsApp Business Account. Businesses should only contact customers who have provided consent and should promptly respect opt-out requests.

Meta's applicable message charges are normally billed through the payment arrangement attached to your WhatsApp Business Account. Check Meta Billing Hub or WhatsApp Manager for your payment method, billing currency and invoices.

From 1 October 2026, chargeable messages include service replies after the monthly 1,000 free service messages per business phone number, as well as chargeable templates. Keep a valid payment method in place so chargeable replies are not interrupted.

WebWMS2U bills subscription fees and platform credits separately.

If Meta cannot charge your account, delivery of chargeable messages may be restricted or stopped. This includes service replies after the monthly free allowance is exhausted, not only templates.

Check billing, outstanding balances and payment settings in Meta Billing Hub or WhatsApp Manager. Renewing WebWMS2U or adding platform credits does not fix a Meta payment problem.

Marketing: Promotional templates, offers and campaigns.

Utility: Non-promotional templates tied to a customer request or transaction, such as order updates and appointment reminders.

Authentication: Templates for identity verification, such as one-time passwords.

Service: Free-form API replies inside an open 24-hour customer service window, including replies sent by staff, keyword automation or third-party AI such as WebWMS2U AI.

Meta determines the category of each submitted template. A Utility template remains a Utility message when sent inside the service window; it does not become a Service message.

From 1 October 2026, each business phone number receives 1,000 free delivered service messages per month. Meta charges from the 1,001st delivered service message at the applicable Service rate for the recipient market. The allowance resets monthly; unused messages do not roll over or transfer to another number. This counts individual messages, not customers, orders or conversations.

Utility templates are charged per delivered message both inside and outside the 24-hour customer service window from 1 October 2026. They do not use the 1,000 free service-message allowance. Marketing and Authentication templates are also normally charged when delivered.

See Meta pricing and current rate cards for rates applicable to your recipient market and billing currency.

It is 1,000 delivered Service messages per business phone number per month from 1 October 2026. A conversation containing five service replies uses five messages. Meta charges from the 1,001st eligible Service message; unused allowance does not roll over.

No. A Utility template has its own category and applicable delivery fee, including when sent inside the 24-hour window. The Service allowance is for free-form service replies. Other qualifying Meta delivery exemptions may apply separately.

With the standard WhatsApp Cloud API arrangement, the telephone number is normally used through the API and cannot simultaneously remain active in the WhatsApp Business mobile app.

WhatsApp Coexistence allows an eligible WhatsApp Business app number to connect to the WhatsApp Business Platform while continuing to use the same number in the mobile app. Staff can continue using the WhatsApp Business app while WebWMS2U handles supported API messaging and automation.

Yes. This is the main purpose of WhatsApp Coexistence. An eligible telephone number can remain available in the WhatsApp Business app while also being connected to WebWMS2U through Meta's official WhatsApp Business Platform.

Eligibility is controlled by Meta, and some app or API features may behave differently after the connection is completed.

It may be possible, but it is not an instant switch intended to be changed repeatedly.

Changing the connection method may require disconnecting or deregistering the number, waiting for Meta's systems to update, registering the number in the WhatsApp Business app, and completing Embedded Signup again.

Please contact WebWMS2U support before attempting a change so that the correct procedure can be confirmed for your number.

Potentially, but an existing Cloud API-only number normally cannot be moved directly into Coexistence using a single setting.

The number may first need to be removed or deregistered from its current Cloud API registration, registered in the WhatsApp Business app, and then connected again using the Coexistence onboarding process. Eligibility and the exact migration process are determined by Meta.

Do not try to register the number in the WhatsApp Business app before completing the required Cloud API removal steps.

It may be possible to disconnect Coexistence and register the number as a standard Cloud API number. However, the change may affect WhatsApp Business app access, message history and existing WebWMS2U configuration.

Please contact WebWMS2U support before disconnecting the number or removing it from WhatsApp Manager.

Meta may provide supported history sharing or synchronization during Coexistence onboarding, but the amount of history made available to the API can be limited.

You should create a WhatsApp Business app backup before onboarding. WebWMS2U cannot guarantee that every historical chat, media file, label or app setting will be imported into the platform.

Supported app messages and message events may be shared with the connected platform under Coexistence. However, synchronization may not be identical to what is displayed in the WhatsApp Business app.

Availability depends on Meta's Coexistence features, permissions and the way the number was onboarded. Older chats, labels, status posts and app-only features may not appear in WebWMS2U.

Yes. Staff can continue handling conversations through the WhatsApp Business app while WebWMS2U is used for supported API messages, templates, campaigns, keyword replies and automation.

Businesses should establish an internal process to prevent two staff members or automations from replying to the same customer at the same time.

Customers continue communicating with the same WhatsApp business number. They generally do not need to know whether a particular message was sent manually through the WhatsApp Business app or through WebWMS2U.

The business profile and displayed telephone number remain associated with the same WhatsApp business account, subject to Meta's configuration.

No. Coexistence is intended for eligible numbers registered in the WhatsApp Business app.

A number used with the standard personal WhatsApp Messenger app would normally need to be moved to the WhatsApp Business app first. Back up important chats before changing applications.

No. Eligibility is controlled by Meta and may depend on the country, WhatsApp Business app version, account status, business portfolio, existing API registration and other Meta requirements.

If the Coexistence option is not offered during Embedded Signup, WebWMS2U cannot force Meta to enable it for that number.

Yes. The WhatsApp Business Account and telephone number are connected to a Meta Business Portfolio during Meta's Embedded Signup process.

The user completing the onboarding must have the necessary administrator access to the relevant Meta Business Portfolio.

Not every business must complete verification before beginning limited WhatsApp Business Platform use. However, an unverified business may have lower messaging limits or restricted access to certain features.

Meta may require business verification before allowing higher messaging limits, additional telephone numbers or other capabilities.

Yes, subject to your WebWMS2U plan limits and Meta's eligibility requirements. Each number must be properly registered under a WhatsApp Business Account and connected through the appropriate onboarding process.

The number of Meta Cloud or Coexistence numbers available in WebWMS2U depends on your subscription plan.

No. Business verification, telephone number eligibility, display-name approval, template classification and template approval are controlled by Meta.

WebWMS2U can provide technical guidance and help identify common configuration problems, but it cannot override or guarantee a decision made by Meta.

You normally need an eligible number already registered in the WhatsApp Business app, the latest suitable app version, administrator access to the correct Meta Business Portfolio, and permission to manage the relevant WhatsApp Business Account.

Back up important app data and confirm the number's current registration before beginning.

Coexistence is designed for the WhatsApp Business app rather than the standard personal WhatsApp Messenger app. A personal account would normally need to be moved to the WhatsApp Business app and meet Meta's eligibility requirements first.

Back up important chats before changing applications.

Because the number remains active in the WhatsApp Business app, supported WhatsApp Business app calling features may remain available under Coexistence.

Calling is an app feature and is not provided through the WebWMS2u messaging API. Availability can depend on Meta, the account and the customer's location.

WebWMS2u's Meta Cloud API messaging is intended for supported one-to-one business conversations. Do not assume that WhatsApp groups, group administration or group campaigns are available through the Cloud API.

Yes, provided the recipients have consented to receive the messages and the content follows WhatsApp policies.

Marketing messages sent through the WhatsApp Business Platform normally require an approved Marketing template. Customers should also be given a clear way to opt out.

Yes. Supported connection types can send selected media formats such as images and documents. Available formats, file-size limits and template requirements depend on the WhatsApp connection and message type.

WebWMS2u records supported message-status updates such as sent, delivered, read or failed when those events are supplied by the connected WhatsApp service.

A read status depends on an actual receipt being made available and cannot be guaranteed for every recipient or connection type.

The customer should retain ownership and administrator access to its Meta Business Portfolio, WhatsApp Business Account, telephone number and Meta billing method. WebWMS2u provides the platform connection and related assistance but should not replace the customer's ownership of these business assets.

Only upload information required for legitimate business communication. Restrict account access to authorised staff, use strong passwords, remove access when staff leave, and follow applicable privacy and data-protection requirements.

Do not send sensitive information through campaigns unless you have an appropriate lawful and secure process.