Lynxbe
עברית
All guides
Prepare a clear broadcast, review every choice and know what happened to each message.
Template approval and results are demonstration data. The guide creates no job, sends no message and charges nothing.
A 6-minute video in 24 chapters. Jump directly to the step you need.
Prepare recipients, personalize a template and inspect each message result. Every result here is demonstration data.
The video is currently unavailable. Continue with the written guide and demonstration below.
The right audience. The right message. Prepare recipients, personalize a template and inspect each message result. Every result here is demonstration data. Original Lynxbe screens · Example approvals and results
A list and a job do different things In Template Broadcast, open Recipient Lists to prepare an audience. Broadcast Jobs tracks each send. Original Lynxbe screens · Demo data
Give the audience a clear name Choose New List. Our list is Example customers — updates. This example uses a file with customer names. Original Lynxbe screens · Demo data
Paste is for phone numbers Separate pasted numbers by lines, commas or semicolons. This is an alternative; our main example continues with a file. Demo data · Separate alternative, no send
Keep personal values in a column Map the phone and customer_name columns. Check valid, invalid and duplicate entries before using the list. Original Lynxbe screens · Demo data
Choose how to add recipients New Broadcast starts with Recipients. Paste and Manual accept numbers; Saved List can also provide personal columns. Demo data · Separate alternative, no send
Valid does not always mean eligible Select Example customers — updates. Check permission and opt-outs; importing a list does not create new consent. Original Lynxbe screens · Demo data
Choose the business account Continue to Template, keep WhatsApp selected and choose the account customers should receive the message from. Original Lynxbe screens · Demo data
Choose a template for the purpose Select Example customer update. This example is MARKETING; its tracking name is example_customer_update. Original Lynxbe screens · Example approvals and results
A static value is the same for everyone Static uses one value in every message, such as Example customers. Our main route uses each recipient’s name. Demo data · Separate alternative, no send
Each customer gets their own name Choose Per Recipient and map BODY — {{1}} to Customer name. The selector also shows the original customer_name header. Original Lynxbe screens · Demo data
Read the complete message Preview shows Hello Noa Example. It uses the first recipient; it does not validate the whole audience. Original Lynxbe screens · Demo data
Review before creating Check account, template, language, category and audience. Create Broadcast is not only a Save Draft action. Demo data · No live creation or send
Check what can be sent now Read remaining capacity, quality, batches and warnings. The example does not promise a limit for your account. Original Lynxbe screens · Demo data
Cost is an estimate before sending Review the cost estimate and currency. The shown amount is demonstration data, not a quote or charge. Original Lynxbe screens · Demo data
Now, later or over several days Send Now starts on creation. Schedule sets a future time. Custom Limit sets a daily amount when offered. Demo data · No live creation or send
Check the device clock too Schedule takes a date and time. For this Israeli business, set the device to Asia/Jerusalem before choosing. Demo data · Separate alternative, no send
Spread without promising delivery pace Custom Limit shows a daily amount and estimated plan. When the cap is reached, check the resume time. Demo data · Separate alternative, no send
After creation, check that it started Send Now attempts to launch the new job. Open example_customer_update and check status and progress. Demo data · No live creation or send
Pause and verify the status Pause requests a stop. Wait for Paused; Resume continues progress. These are alternative demonstration states. Demo data · Separate alternative, no send
Cancel stops the remaining work Cancel applies to recipients not sent yet. It cannot erase sent messages or reverse charges already incurred. Demo data · Separate alternative, no send
Completed does not mean everyone received it Our example has 8 sent, 7 delivered, 5 read and 2 replies. One failure and one skip explain the rest. Original Lynxbe screens · Example approvals and results
Open recipients and read the reason Filters show each recipient’s current status; Overview totals are cumulative. Read failure reasons before trying again. Original Lynxbe screens · Example approvals and results
Continue only with an eligible group Check who is eligible for a retry. A failed-recipient campaign is a new job; recheck template, permission and timing. Demo data · No live creation or send
Original Lynxbe screens show isolated demonstration data, including template approval and message outcomes. Scheduling, pause and cancellation are separate alternatives, not an executed sequence. No live job creation, send, consent change, charge or Meta approval occurs. Entry pages use their original routes; the full application menu is not shown scrolling.
Before starting: broadcast permissions, a connected WhatsApp account, a suitable approved template, an audience with recorded permission and complete personal values. Check opt-outs, frequency, capacity, cost and timezone before creating a job.
12 rows of demonstration data only. Replace the numbers and names with your own records and check recipient permission before use. Download the example file
In Recipient Lists, choose New List. Our audience is Example customers — updates. File import is useful when every row needs customer_name; Paste and Manual suit numbers alone. Our 12 rows produce 10 valid numbers, one invalid entry and one duplicate. Validation and import do not provide marketing permission. Check existing consent, preferences, opt-outs and frequency before continuing.
The wizard order is Recipients, Template and Review. Select Saved List and Example customers — updates. Ensure an additional audience was not selected accidentally. A list contains numbers and values; it does not start a broadcast. Preparation counts are estimates, and later checks can skip recipients.
In Template, keep WhatsApp selected and choose the appropriate account. Select Example customer update, technically example_customer_update, in MARKETING. Check language and status. The shown APPROVED state is demonstration data only. Monitoring uses the technical template name; the wizard has no additional campaign-name field.
Per Recipient maps BODY — {{1}} to Customer name, the saved label of the customer_name column. Select the name saved at import. Noa Example is the first preview recipient. The message reads: Hello Noa Example, this is Example business. On Tuesday we will introduce our new services. Reply for details. To opt out, reply STOP. Check every other row; the first-recipient preview does not approve every value. Static is an alternative using one value for everyone.
In Review, read remaining capacity, quality, batches and warnings. UNKNOWN is not a healthy quality confirmation. The cost estimate depends on available system data and is not an invoice or guaranteed rate. Send Now and Custom Limit attempt launch after creation. Schedule can send when due without further confirmation. The picker uses the device clock: for this Israeli business, check Asia/Jerusalem and the saved time. Spreading and resume times are a plan, not promised delivery.
Create Broadcast is not only Save Draft. Inspect monitoring; if created but not started, read the reason before making a duplicate. Pause requests a stop; wait for Paused. Resume continues progress. Cancel stops eligible remaining work; messages already sent cannot be recalled. Scheduling, pause and cancellation in the guide are separate alternatives without live actions.
Overview has 8 sent, 7 delivered, 5 read and 2 replies. One failure and one skip complete the 10 recipients, with nobody remaining. These stages are cumulative; do not add them. Recipient status filters show one current state per recipient: 1 Sent, 2 Delivered and 5 Read. Read failure reasons and replies before continuing. Resend-to-failed allows only defined reasons and creates a separate job awaiting launch. Follow-up groups open the ordinary wizard and do not preserve custom columns; recheck values and consent. The 72-hour reply attribution rule is not Meta’s service window.
Our demonstration result: 10 recipients after list checks; 8 sent, 7 delivered, 5 read and 2 replies. One failure, one skip and none remaining. This is isolated data, not proof of real sending.
Template approval does not provide recipient permission. Sent is not Delivered; Read is not a reply. Ordinary broadcast creation can send immediately; a scheduled job can start later without another click.
Checked against Lynxbe screens, source behavior and official Meta / WhatsApp sources on 14 October 2026. Demonstrated data and actions are isolated; this does not prove a live provider connection, approval or message delivery.
A read-only walkthrough. Select a step or use Next. It creates no job and sends no message.
We prepare one WhatsApp campaign: Example customer update. Start with recipients, use example_customer_update and finish with the results. A list keeps recipients for reuse; a broadcast job also specifies a template, account, timing and results. Opening a list sends nothing. Creating a broadcast in the wizard can start sending immediately. All shown records, approval states and outcomes are isolated demonstration data.
Open Template Broadcast and choose Recipient Lists. This is where you prepare reusable groups. Broadcast Jobs shows execution and outcomes for each campaign. This guide captures original product pages through their entry routes; it does not show a scroll through the full application menu. Viewing and management depend on your permissions and selected business.
Choose New List. You can start by pasting numbers, using a file or importing contacts. Our list is Example customers — updates. Use a file when the message needs an individual value for each customer. We use a phone number and the customer_name variable. A contact list does not itself record new recipient permission.
In Paste Numbers, enter the list name and numbers, preferably in international format. Use new lines, commas or semicolons. The system checks structure and removes duplicates after normalization. A valid number does not prove WhatsApp availability or marketing permission. This is the paste alternative, not the file containing names used for later personalization.
Return to our main file route. In the file preview, assign Phone Number to the phone column and Custom Variable to customer_name. Label it Customer name. A separate column can hold Contact Name; use Skip / Ignore for unneeded columns. Our file has 12 rows: 10 valid numbers, one invalid entry and one duplicate. Check numbers and values throughout the file. These are data checks, not consent checks.
Open New Broadcast. The wizard order is Recipients, Template and Review. Paste accepts several numbers; Manual adds individual numbers that you can remove from the selection. These suit a small audience. Saved List supports reuse and file-column variable mapping. The count shown while entering numbers is an estimate; normalization, duplicate and eligibility checks are separate.
Choose Saved List, then Example customers — updates. Meta requires permission for business messages and respect for opt-outs. Lynxbe also checks marketing permission and preferences before sending. Importing does not create consent. Opt-outs, disabled promotions, missing permission and frequency controls can cause skips. The valid count is not a count of everyone eligible to receive the campaign.
Continue to Template and choose WhatsApp. Select the sending business account and check that it is connected and suitable for this audience. Email and Both are other wizard choices; this example uses WhatsApp only. Splitting across numbers, where offered, creates several jobs and requires checking each account and its template. We use one account here.
Choose Example customer update, technically named example_customer_update. A new-service announcement is promotional, so our category is MARKETING. Use the right language and account. The wizard requests approved templates, but recheck the state before sending: pending, rejected or disabled is not approved. APPROVED here is a fixture, not a live approval. Monitoring pages identify this campaign using its technical template name.
In our template, {{1}} is the greeting name. Static inserts one value for every recipient. Example customers could be a collective greeting. This is an alternative only. Our main route uses Per Recipient to take each name from the list. Pasting numbers alone does not supply a personal name column. Sample values submitted for template review are not your recipient values.
Choose Per Recipient. For BODY — {{1}}, select Customer name, the label assigned to customer_name during import. The selector shows both the original file header and your saved label; the saved name is the mapping value. This mode appears when the selected list supplies columns. Check every variable and data row: a blank or wrongly mapped value can produce an incorrect message or failure. With several lists, ensure the same saved column name and suitable values throughout. Selecting a column from one list does not inspect all lists.
Read Preview (Recipient #1). Noa Example replaces {{1}}. The message reads: Hello Noa Example, this is Example business. On Tuesday we will introduce our new services. Reply for details. To opt out, reply STOP. This preview uses the body and first recipient’s data only. Separately review the other names and any header, media or buttons. A preview does not send a test message or prove delivery.
Continue to Review. Check your chosen account, template, language, MARKETING and recipient source. Confirm the audience and personal values. Keep the parallel-other-channel option off in this example. Read capacity, cost and timing before Create Broadcast: with Send Now or Custom Limit, the wizard attempts to launch after creating the job. Do not click merely to inspect the result screen.
Read remaining capacity, tier, quality and the batch plan. These depend on the account and information available to Lynxbe. UNKNOWN or a missing/stale-data warning is not a healthy quality confirmation. A capacity plan is an estimate, not a delivery promise. Meta also limits the marketing messages a recipient can receive. Review warnings before increasing audience or pace; do not bypass restrictions with more campaigns.
Read Cost Estimate and its note. Meta pricing varies by market and category; there is no fixed rate for every account or recipient. Lynxbe estimates use the data and pricing available to it, and a tracking cost is not necessarily a provider invoice. Check your terms and current rates before a real send. This demonstration incurs no charge. Starting, delivering and billing are different events; recipient count alone does not determine a charge.
Choose timing suitable for your audience. Send Now attempts to launch immediately after creation. Schedule sets a future time at which the scheduler can begin sending. Custom Limit, shown when spreading is needed, sets a daily amount and can also start immediately. This is an operational choice, not a safe draft-saving method. We show timing alternatives separately, then return to the immediate example route.
This is a scheduling alternative, not an action performed by the main example campaign. Choose Schedule and a future date and time. The wizard uses the device’s local timezone and converts the selection to UTC; there is no separate timezone picker. For our example business, set Asia/Jerusalem on the device first and check the saved time. A scheduled job can send when due without another click. Review or cancel before then, subject to its status.
Custom Limit is another choice when offered. Set a daily amount and review Estimated Send Plan. Creating the job can start sending today. At the daily cap, it may pause until an auto-resume time shown in its details. This is not a promised completion time or delivery outcome. Check the displayed resume time instead of assuming it matches your timezone. This alternative is separate from the immediate job used for our example results.
In a real workflow, choose Create Broadcast only after reviewing everything. Send Now creates and attempts to launch the job. Return to Broadcast Jobs and open example_customer_update. Check Sending and the remaining count. If it was created but did not start, read the reason before another attempt; an existing job is not a reason to create a duplicate. Sending does not confirm delivery of every message. This shown state is an offline fixture; no live job is created.
During Sending, Pause requests a stop. It is not instantaneous for every message, so already-started messages may still update. Verify that the job becomes Paused. Resume continues remaining recipients, subject to system checks. With an automatic daily-cap pause, inspect its resume time and the effect of a manual pause. This screen is an alternative state of our example; no live job controls are used.
Cancel is for a job you no longer want to continue. Review its state and summary before confirming. The system cancels eligible unsent recipient states; provider operations already in flight may finish. It does not recall messages from phones or reverse completed delivery or charges. Then verify Cancelled and inspect recipient outcomes. This is an alternative ending, not the path leading to the completed example next.
Return to the main route and its isolated result. The checked list supplies 10 valid recipients. At completion: 8 sent, of those 7 delivered and of those 5 read; 2 replied. There is one failure, one skip and zero remaining. Sent means accepted by WhatsApp, Delivered means reaching the recipient and Read records a read event. These are cumulative stages: do not add 8, 7 and 5. Replies are separate. Completed means processing ended, not that everyone received or read the message.
Open Recipients and choose a filter. Status filters show each recipient’s current status, so their counts differ from cumulative Overview totals: our example has 1 Sent, 2 Delivered and 5 Read. Overview has 8 Sent, of those 7 Delivered and of those 5 Read. Each recipient has one current status. Expand a row to inspect times, a failure reason or reply snippet. A transient failure differs from a number unable to receive WhatsApp, an incorrect template or an opt-out. Skipped is not delivered. No Read event does not prove the person did not see it or permit another message. Lynxbe’s reply attribution rule covers up to 72 hours after sending; it is separate from WhatsApp’s service window.
Review the resend-to-failed suggestion. Only defined failure reasons qualify; an unknown code or a failure needing correction is not automatically eligible. For 131049, Lynxbe requires at least 24 hours before eligibility; this does not promise Meta’s limit will reset. Creating this retry campaign makes a new job that waits for explicit launch. Read, no reply and Did not read instead prepare a new list and open the normal wizard, where creation can start immediately. Follow-up lists do not preserve custom variable columns, so recheck mapping. No group bypasses consent, opt-outs, template or capacity checks.
