Clear answers.
A simpler start.

WatsBridge brings WhatsApp customer communication closer to your daily work: newsletters, order updates and ongoing customer conversations. The aim is to reduce repetitive work and keep useful context available. The features you can use depend on the release, connected services and plan confirmed for your business.

The free Chat Button lets visitors open a WhatsApp conversation from your WordPress or WooCommerce website. It does not turn a website click into an automated marketing campaign. The CRM and connected platform cover broader customer communication workflows, subject to their available features and setup.

The initial focus is businesses and professional users working with WordPress and WooCommerce, including independent professionals, shops and small teams. Before choosing a plan, identify who will answer customers, which communication tasks you want to simplify and how many WhatsApp numbers you need.

The free Chat Button is a WordPress plugin. WooCommerce is the initial commerce platform presented for the CRM. Shopify, Odoo and Standalone adapters are labelled In development on the Plans page. Confirm compatibility with your actual website and intended use before subscribing.

Yes, you can prepare your communication process and help existing visitors contact you. A newsletter also needs an audience you have permission to reach. WatsBridge does not supply prospect lists or replace acquisition. If you have few contacts, growing a relevant audience is part of the work.

No. AI is an optional paid layer, separate from the communication product. The Plans page currently marks AI assistance capabilities In development. Do not choose a plan on the assumption that an announced AI feature is already operational.

List your intended uses, website platform, team members, WhatsApp numbers and approximate communication volumes. Check access to the business assets you own, the quality of your customer data and the permissions you hold to contact people. Confirm the supported setup with WatsBridge before changing an existing WhatsApp configuration.

It identifies a planned capability that is not yet available for production use. It is not a delivery-date commitment. Base a purchase decision on the features and terms confirmed for the version you will actually receive.

Prepare the customer's request, relevant order or contact details, what has already been checked and any promise made. Give the follow-up a clear owner. Confirm the supported handover and the current availability of the optional AI Agent during onboarding; a planned capability should not be assumed to be ready.

Plan the handover to a person.

Agree which details the next person needs and where they will find them. WatsBridge's current commercial scope focuses on WhatsApp. Confirm any other channel or connection before planning around it. The wider communication process still needs someone to own the next step.

Read the multichannel communication guide.

Start with the number of people who need access and the WhatsApp numbers to connect. The homepage questionnaire suggests a starting plan from those needs. Message volumes, required features and the final commercial terms still need confirmation; a recommendation is not a quotation.

The current Plans page lists Starter with one number and up to three users; Growth with up to two numbers and unlimited users; Pro with up to five numbers and unlimited users; and Business with up to ten numbers and unlimited users. Confirm the applicable offer before ordering.

The current Plans page invites you to contact WatsBridge rather than displaying a final subscription price. Ask for the offer that applies to your business, including currency, taxes, billing period, available features and any separate usage charges. No price is established by the time-saving calculator.

They are separate from the WatsBridge subscription. Build your budget using the message categories, destination markets and provider terms that apply to your activity. Estimate the complete campaign cost before sending; do not treat a subscription price as an unlimited messaging allowance.

The Plans page states that WhatsApp Business numbers and telephony services are provided separately by third-party providers. Confirm number ownership, recurring costs, verification options and eligibility before choosing a provider. A number being available for purchase does not by itself establish WhatsApp compatibility.

No. A currency used to explain a scenario is a presentation choice. The accepted offer determines the billing currency and commercial terms. Check taxes, exchange costs and separately billed provider charges. A calculation in one currency cannot be transferred unchanged to every market.

Ask WatsBridge to confirm the process and terms applicable to your subscription. A plan change depends on the available configuration and your accepted order. Check notice periods, renewal, cancellation and any launch-offer conditions before subscribing; the FAQ does not create additional contractual rights.

Only an offer explicitly published or provided to you applies. Check its eligibility, duration, renewal price, taxes and cancellation terms. The free Chat Button is a separate product and should not be confused with a free trial of the paid platform.

The published preferred launch pricing applies for six commercial months, subject to the confirmed programme terms. Review the applicable start date, included plan and price after that period in the offer before accepting it. Beta participation is a separate programme.

Review the launch programmes and terms.

No. The private beta has a symbolic contribution of CHF 10 per month and its own capacity of 100 business accounts. Eligible beta participants can be offered commercial continuation on the programme terms without consuming one of the 100 public Founding places. Continuation requires an explicit offer and acceptance; beta participation does not create an automatic paid commercial subscription.

Compare beta participation and commercial launch access.

A new application does not reserve a place. The published process requires email verification, business review, acceptance of the programme offer and written confirmation. Keep the application reference and the confirmation you receive. The programme portal and confirmed status determine whether a place has been reserved.

Read how reservations work.

You can choose the optional waiting-list request on the application form. Joining that list does not reserve a place or guarantee an invitation. The beta and public commercial programmes have separate capacities and participation terms.

View the application process.

A newsletter can share useful news, product information or relevant offers with an audience you have permission to contact. Plan the content, approved message structure where required, frequency and next step. The value comes from relevance and follow-up, rather than simply sending to a large list.

The two channels can serve different needs. Email may suit longer content and broad communication; WhatsApp can support concise, targeted exchanges and replies. Compare your actual costs, audience expectations and results. The most suitable mix depends on the business, rather than a universal ranking of channels.

No. Sales depend on acquisition, your offer, audience, message, call to action, landing page and commercial follow-up. WatsBridge can support communication and measurement. Read rates and clicks are stages in a customer journey, not a guarantee of orders or revenue.

They are reported observations from one real re-engagement case involving 360 customers in several batches, including people last contacted more than three years earlier. They are not a platform-wide benchmark, a controlled comparison with email or a forecast for your business.

The case reports 83.5% gross delivery, a 75–85% read-rate range, up to 32% clicks and nine unsubscribes. Around 80% is a rounded description of the read range, not a calculated overall average. The precise denominators and unique-click basis remain to be documented.

A click proves an interaction with the linked content. It does not establish why the person clicked or whether they intended to buy. Measure the next action separately, such as a completed order, a qualified enquiry or a confirmed appointment.

Check that the landing page matches the message and that the offer, price, delivery conditions and next step are clear. Test the mobile journey and purchase or booking process. Also check attribution: an external booking or later purchase may not appear automatically in your campaign reporting.

Compare the contribution from attributable additional orders with the full campaign cost, including messaging, subscription share and preparation. Use contribution margin after relevant variable costs. Revenue alone does not establish profit, and orders that would have happened anyway do not prove an incremental gain.

There is no universal threshold. A useful estimate needs campaign costs, delivery, unique clicks, conversion and contribution margin per additional order. State the assumptions and test different outcomes. If additional orders have not been demonstrated, a universal profitable margin cannot be inferred.

It compares your current workload with the time you expect to spend after setup, using working hours per day and days per week. Daily and monthly durations are converted to a common weekly basis. The result is your projection, not a measured saving or a guaranteed productivity gain.

Typical needs include order confirmation, preparation and dispatch information. Identify the WooCommerce events, message content and exceptions you need, then confirm the workflows supported by your release. An order notification does not replace fulfilment, customer service or the accuracy of your store data.

Keep the purpose of each communication clear. Adding promotional content can affect the applicable message category and recipient expectations. Check the relevant Meta requirements and permissions before combining marketing with an order update; do not use a transactional label to avoid marketing requirements.

A contact is a record about a person or organisation. A subscriber has an applicable permission and subscription state for the communication concerned. Having a phone number, an order or a WordPress user account does not automatically make that person eligible for every marketing message.

A dynamic segment describes selection rules whose matching contacts may change as data changes. A fixed audience records a chosen membership. In either case, membership does not by itself establish permission to send; current consent, exclusions and other eligibility checks still matter.

The intended segmentation model uses business criteria, including AND/OR combinations where supported. Check the operators and field types offered in your installed version. Preview the selection and test both matching and non-matching contacts before relying on a filter for a real campaign.

Selection and send eligibility are different steps. A contact may be selected but lack an applicable permission, have opted out, have an invalid number or be subject to a frequency or provider restriction. Investigate the known reason rather than assuming every selected member should receive a message.

Confirm the import format and limits supported by your release. Prepare consistent column names, international phone numbers, languages and values. Review a small sample first, check duplicates and preserve the source of permissions. Importing data is not proof that the people agreed to marketing.

Investigate whether the records belong to the same person, a shared number or different people. Do not merge records solely because a number matches. Correct the source data and confirm the duplicate-handling behaviour in your version before sending or importing again.

No. The homepage estimate compares the time entered for the work described; it does not multiply that saving by the number of people in your team. Enter durations without double counting. Team size is used to help assess access needs for the suggested plan.

Cart recovery is a follow-up to an unfinished purchase. A useful reminder helps an eligible customer return to the relevant checkout or ask a question. The message needs a supported store event, appropriate permission and a destination that still works. Confirm the workflow available for your store during onboarding.

Explore the cart recovery workflow.

Start with customers whose contact details and permission cover the intended communication. Check the appropriate WhatsApp sending setup and template requirements. Adding an item to a cart does not by itself give a business permission to send marketing messages.

Review the preparation checklist.

Exclude a checkout once its purchase is completed. Stop follow-up when the customer opts out or the contact no longer meets the campaign conditions. Check the current order and contact state before each reminder, including delayed payments and duplicate records. Review these cases when confirming the store workflow.

Keep message interactions, orders attributed to a reminder and additional sales separate. Review completed orders, payment status, cancellations and the attribution period. A click or a read receipt does not establish that the message caused a sale. A suitable comparison or holdout can provide stronger evidence of an additional effect.

Read the measurement guide.

Meta controls the WhatsApp platform rules and provider-side restrictions. WatsBridge cannot grant an exemption or guarantee a capacity increase. Check the current account and template state, together with any explanation actually supplied by Meta, before deciding what to send next.

No. Connection establishes a technical relationship, not unlimited sending rights. Account eligibility, business verification, message quality, template state, recipient restrictions and other provider controls are distinct considerations. Confirm the limits applying to the particular account and use case.

No. A quality indicator is one signal at a particular time. It does not prove that every recipient is reachable, that all other limits are satisfied or that a future message will be delivered. Use the actual delivery evidence and current provider state.

They concern different things: control of a number, verification of business information and acceptance of a particular message template. Completing one does not establish that the others are complete or that all sending restrictions have been removed.

Under the current WhatsApp Business Messaging Policy, business-initiated conversations require an approved template. Replies without a template are permitted within the 24-hour customer service window following a user message; outside that window an approved template is required. Other applicable permissions and rules still apply.

The approved template defines its fixed wording, language, category, components and permitted placeholders. Local personalisation supplies values at those authorised positions. It does not change the approved structure or bypass approval. Changes to fixed wording or components require the applicable review and approval.

Use the approved language and components, and confirm that your WatsBridge release supports that structure. Approval of one text template does not validate every media type or button configuration. Test the actual message and required data before a campaign.

Check the status and explanation in the relevant Meta tools, then review the content and intended use. Do not silently substitute another category or repeatedly resubmit an unresolved request. If the available information is unclear, contact support with the status, time and non-sensitive diagnostic details.

Do not assume that it does. Separate batches may still be evaluated against the same account, time window or recipient restrictions. Batching can organise work, but it is not a way to bypass Meta limits or permission requirements. Confirm the actual restriction before resuming.

Accepted means the provider accepted a request; it does not prove receipt. Delivered indicates a delivery event. Read indicates a reported read event, where available. A click is a separate interaction. Keep these stages distinct when reviewing campaign totals and calculating rates.

Deferred means processing is postponed; excluded means a recipient was not eligible for the attempted operation; failed indicates a reported failure. Unknown means the available evidence does not establish the outcome. The exact labels and available details depend on the installed version; do not interpret unknown as definitely unsent.

Provider events and local processing are not necessarily simultaneous. Review the timestamp and freshness of the evidence, and allow for later updates when comparing reports. Avoid combining totals captured at different times or from different campaign scopes as though they were one fixed dataset.

Do not immediately resend. The original attempt may already have been accepted, even if confirmation is missing. Preserve the reference and ask for reconciliation before another attempt. Treating an unknown outcome as a confirmed failure creates a risk of duplicate messages.

No. An increase depends on Meta and cannot be promised. A provider may also omit a precise reason. Distinguish confirmed facts, reported error codes and hypotheses. WatsBridge should not invent a cause or promise that a retry will fix an unexplained restriction.

No. A number in your database is not sufficient permission for all communications. Check the purpose and scope of the permission you hold and applicable requirements. WhatsApp requires recipients to have provided their number or username and opted in to subsequent communications from the business.

Do not treat a purchased or collected list as permission to send. You need a valid basis and the applicable recipient permissions for your own business and communication purpose. WatsBridge does not provide prospect lists. Review the Acceptable Use Policy before preparing any imported audience.

Keep enough evidence to show who agreed, when and how, which business and purposes were covered, and the wording presented. Retain withdrawal information as well. Confirm how your installed tools store and expose that evidence rather than assuming a checkbox or import is sufficient.

Respect the request and stop the communications concerned, including requests received outside WhatsApp. Check that the exclusion is reflected in the tools you use before preparing another campaign. Do not import the person again to bypass the withdrawal.

No. A new subscription action must be assessed against the relevant permission and any existing exclusions or restrictions. Do not assume that one form submission removes a suppression, account restriction or unresolved delivery condition. Confirm the applicable re-subscription process with support.

It depends on the features and services you activate. Review the Data Processing Agreement, Privacy Policy and Subprocessor Register for the applicable roles and providers. Your WordPress hosting and selected plugins also matter. Do not infer that all processing stays in one country merely because one infrastructure provider is Swiss.

It can. Optional AI features may require information to be processed by an additional provider. Review the relevant feature, configuration and current legal documents before enabling it. The provider list does not mean that every provider receives data from every customer.

This FAQ makes no certification or uptime guarantee. A certification claim needs a current certificate and defined scope. Any service level must be expressly included in the applicable agreement; the public Service Availability Policy does not create automatic service credits.

WooCommerce is the initial commerce platform listed as supported. The Plans page marks Shopify, Odoo and Standalone adapters In development. Confirm the exact function and versions needed for your use case. A partner logo or a website link does not demonstrate a working integration.

Coexistence is a possible setup, subject to eligibility and the supported onboarding route. Confirm it for your number and account before making changes. Do not disconnect an existing configuration on the assumption that every number or provider follows the same process.

No. A virtual number needs to meet the relevant verification and provider requirements. Confirm ownership, ability to receive the required verification, country coverage and ongoing access. WatsBridge does not promise compatibility merely because a provider offers an API or sells numbers.

For WordPress, a profile-field plugin can store additional business information. Confirm where it stores values and whether your CRM release can discover and use them. Start with a simple field and a saved value, then test the selection behaviour before using it in a campaign.

ACF Free is a candidate for simple fields in WordPress administrative user profiles. This is a scoped recommendation, not end-to-end certification with every WatsBridge release. Confirm the exact plugin and CRM versions and test saved values, discovery and filtering before relying on it.

Do not assume that they will. Administrative profiles, public registration and the WooCommerce My Account area are separate forms and workflows. A field visible to an administrator does not prove that customers can view or edit it. Confirm the frontend implementation and permissions separately.

Discovery depends on the supported source and how the field is stored or declared. A field definition without a saved value may not be enough. Test a real non-sensitive value on an authorised profile, refresh the supported discovery process and check whether the source is actually covered.

They need separate verification. A value may be exposed as text rather than as a number or date; arrays, groups and repeaters can use a different storage structure. Do not assume that a visible label or successful text-field test validates complex values and all filter operators.

Identify segments, audiences and workflows that depend on the field. Check data preservation, storage keys and type changes, then test before applying the change to live communication. Removing a plugin does not prove either that its values are deleted or that they remain usable by the CRM.

Provide your plugin versions, the affected function, a short description, relevant time and timezone, and non-sensitive error or campaign references. Explain what you expected and what happened. Do not send passwords, access tokens, payment-card data or a full customer database through the public contact form.

First check configuration, selection rules, permissions and previewed content without sending. If a real delivery test is necessary, use a specifically authorised recipient and account for provider charges and message history. A preview is not delivery evidence; a successful single-recipient test does not prove bulk capacity.

Ask for the documentation and release notes matching your installed version. Confirm supported WordPress, PHP, WooCommerce and third-party plugin versions before updating. Do not infer support for a version combination or an upgrade path solely because another combination passed a test.

WatsBridge focuses on communication and customer relationships. Acquisition, content and the sales journey still need attention. Agency or software partnerships must be confirmed with a defined scope; this FAQ does not announce an existing partner network or promise rankings or visibility in AI answers.