Lynxbe
עברית
All guides
Build an appointment reminder from Lynxbe’s examples. Check each component, understand Meta’s rules and see what to do while waiting and after a decision.
Submission and approval states use isolated demonstration data.
A 6:00 video without narration. On-screen guidance, captions and selectable chapters.
A template combines a consistent message with the right name, date and details for each customer.
The video is temporarily unavailable. Continue with the written steps and walkthrough below.
One template. Personal details. A template combines a consistent message with the right name, date and details for each customer. Real Lynxbe screens · Demonstration data
When do you need a template? Outside the 24-hour service window, use an approved template. Within the window, you can reply freely. Real Lynxbe screens · Demonstration data
Start with customer consent Meta approval does not replace customer consent. Contact people who opted in and honor opt-out requests. Real Lynxbe screens · Demonstration data
Open Message Templates In the menu, open Communications, WhatsApp, then Templates. Select your business WhatsApp account. Real Lynxbe screens · Demonstration data
Two different approvals The system-message card requests your business copy approval. Meta approval appears in the template status. Real Lynxbe screens · Demonstration data
Start from an example Choose Create, then the appointment reminder in the quick-start examples. It is a starting point you can edit. Real Lynxbe screens · Demonstration data
Utility: an existing appointment A reminder for an appointment already booked fits Utility when it contains no promotion. Real Lynxbe screens · Demonstration data
Marketing: engagement and offers Offers, promotions and re-engagement are Marketing. Meta can change the category based on the message. Real Lynxbe screens · Demonstration data
Authentication: a one-time code For identity verification, choose Authentication and use its dedicated flow. Meta defines the message wording. Real Lynxbe screens · Demonstration data
Give the template a clear name Use lowercase Latin letters, numbers and underscores. The nickname is a friendly label inside Lynxbe. Real Lynxbe screens · Demonstration data
Choose the message language Select Hebrew or your customers’ language. Check that the example body and buttons use the same language. Real Lynxbe screens · Demonstration data
Add a header, if needed You can omit the header or choose text, an image, a video or a document. Here, add “Appointment reminder.” Real Lynxbe screens · Demonstration data
Keep the body clear and focused Keep the appointment reminder in the body. A standard template requires a body of up to 1,024 characters. Real Lynxbe screens · Demonstration data
Put changing details in variables Use {{1}}, {{2}} and {{3}} for the name, date and time. Keep numbering sequential and fixed text around them. Real Lynxbe screens · Demonstration data
Keep the footer short and fixed The footer is fixed text, up to 60 characters. Our example includes a short opt-out instruction. Real Lynxbe screens · Demonstration data
Give customers a way to respond Check the two reply buttons: confirm the appointment or request a change. They are part of the same template. Real Lynxbe screens · Demonstration data
Check the button action too A link button needs a valid URL; a call button needs a number. A dynamic URL variable goes at the end. Real Lynxbe screens · Demonstration data
Fill in sample values Add Dana, 18.10.2026 and 10:30. Samples help Meta understand the complete message during review. Real Lynxbe screens · Demonstration data
See the complete message In Review, check the WhatsApp preview: header, personal details, footer and buttons. Real Lynxbe screens · Demonstration data
Check before submitting Check the category, complete samples and allowed content. Fix field errors before continuing. Real Lynxbe screens · Demonstration data
Submit for Meta review The create action submits the template for review. It does not approve it or send the reminder to a customer. Demo data · No live submission or approval
Wait for approval Pending means the template is under review. It is not ready for sending yet. Demo data · No live submission or approval
How long does review take? Meta says a decision can take up to 24 hours. The estimate on screen is not an approval or timing guarantee. Demo data · No live submission or approval
Sync and check the status Return to the list and choose Sync from Meta. Check the same template on the same account. Demo data · No live submission or approval
Approved is ready to use Once the same template shows Approved, use it under the rules. Quality pending is different from review pending. Demo data · No live submission or approval
If the template is rejected Check the reason in the desktop preview or Meta WhatsApp Manager. A rejected template cannot be sent. Demo data · No live submission or approval
Fix and submit again Correct the text or samples, check the preview and submit for another review. Approval must be checked again. Demo data · No live submission or approval
Add the real details before sending Choose an approved template and fill the real name, date and time. Check customer consent before sending. Demo data · No live submission or approval
Keep checking after approval A template can become Paused or Disabled. Continue checking status, quality and opt-outs after approval. Demo data · No live submission or approval
Example. Review. Approval. Start from an example, complete all eight steps, submit and wait. Use it only after a real approval. Demo data · No live submission or approval
Screens are captured from actual Lynxbe components using isolated demonstration data. No Meta submission, live approval or customer message was performed. Review waits and outcomes are shortened for the walkthrough.
Before you start: a connected WhatsApp account, template management permission, a clear purpose and customers who opted in to communication from your business.
A template is a message structure reviewed by Meta. Here it is a reminder for an existing appointment. The wording stays fixed; the name, date and time change for each appointment. Choosing a Lynxbe example creates a starting draft, not an approval.
A customer message opens or renews the 24-hour service window. Outside it, an approved template is required to contact them. Sending a template alone does not open a free-form message window. Qualifying WhatsApp calls can also open or renew the window under Meta rules.
Before using a template, confirm that the customer provided contact details and opted in to communication from the business. Make the business identity and purpose clear. Keep the content relevant, honor opt-outs and avoid sensitive information. Template approval is not permission to contact any number.
Open Communications → WhatsApp → Templates. In Message Templates, choose the WhatsApp account that will own the template. Creation and syncing require template management permission. If no account is connected, complete the WhatsApp connection guide first.
The system-message card lets you approve the wording Lynxbe uses for the business. This is a separate business approval: that action does not submit a template to Meta or approve it for sending. In this tutorial, create a regular template using Create.
Create opens an eight-step creation page. Choose Appointment Reminder under Quick-start templates. It fills the category, body, footer and buttons. These are Lynxbe examples; they are different from Meta’s approved template library.
Choose Utility for a reminder tied to the customer’s actual appointment. This category also covers specific order, account or service-request updates under Meta’s definitions. Adding a discount or purchase offer can make the template Marketing.
This is a separate marketing example. Choose Marketing for an offer, promotion or re-engagement. A message mixing a service update with commercial promotion is also Marketing. Meta may change Utility to Marketing during review or after approval. Return to our reminder to continue.
Authentication is for one-time identity verification codes. Lynxbe opens a Copy Code, One-Tap or Zero-Tap flow instead of a free-form body. App options require Android details; Zero-Tap requires acceptance of its terms. Do not add promotions, media or URLs to the authentication content.
Our example is appointment_reminder_2026. Lynxbe requires a leading letter and at least three characters; Meta accepts lowercase Latin letters, numbers and underscores, up to 512 characters. The name must be unique within that account and language. You can add a nickname such as Appointment reminder, an internal Lynxbe label. Existing template name and language are immutable; create a new version to change them.
The Hebrew example uses Hebrew; the English version uses English (US). Lynxbe updates the quick-start example text when its language changes. Check the result yourself. Meta does not translate your message; submit another language version for its own review.
In Header, choose no header or one of the supported formats. Our example uses the text Appointment reminder. A text header supports up to 60 characters and one variable. Media requires a sample for review; use a format and size supported by the screen and Meta rules.
The example addresses the customer, reminds them of the appointment and asks for confirmation or rescheduling. Keep one clear purpose. A standard body supports up to 1,024 characters. Do not add sales content to a Utility message or request sensitive identifiers. Meta reviews the content, not just the category selection.
In our reminder, {{1}} is the customer name, {{2}} the date and {{3}} the time. Numbered variables must be sequential without gaps. Do not begin or end the body with a variable, or make the body mostly variables. Sample values are not automatically sent to customers.
In Footer, check the example’s opt-out wording. A standard footer is optional, supports up to 60 characters and has no variables. The wording alone does not implement opt-out processing; ensure your workflow records and honors the request before any further message.
Our example includes Yes, confirm and No, reschedule. These are quick replies. Other screen options include a URL or phone call, depending on the template type. A standard button label supports up to 25 characters. Creating a button does not automatically confirm or reschedule an appointment; connect responses to the appropriate workflow.
For a URL button, supply a valid address and a sample if it is dynamic. Meta permits one variable at the end of a dynamic URL. A call button needs a valid number. Labels do not contain variables or newlines. Counts and combinations depend on the format and implementation; follow the screen’s validation rather than assuming every combination is supported.
In Examples, fill every variable: {{1}} = Dana; {{2}} = 18.10.2026; {{3}} = 10:30. These are demonstration values, without private customer information. Add samples for header or URL variables too. If you chose a media header, provide an appropriate media sample.
Read the message in the WhatsApp preview on Review. Check that samples are in the right positions and the meaning is clear. Also verify the name, account, language and category. This preview is a pre-submission check; it does not prove delivery or approval.
Screen validation catches missing fields and some structural errors. Review the wording again: permitted purpose, appropriate category, valid variables and a sample for each variable. Avoid duplicates, prohibited content and sensitive information. Passing local validation does not guarantee Meta approval.
After Review, choose the creation action. In the real system, Lynxbe submits the template to the selected Meta account. This tutorial demonstrates the action offline without a real submission. No customer message is sent here, and submission does not guarantee approval.
After submission, the template appears in the list with Pending status. It is not usable yet. Keep the submission details and check its status later. This screen uses demonstration data; no template was submitted to Meta.
Meta documentation checked on 10 October 2026 says a review decision can take up to 24 hours. The current Lynxbe interface shows a 24–48 hour estimate. This is not a guarantee, and the outcome may be rejection. While the status is Pending, wait; do not edit a template still under review.
Lynxbe can receive status updates by webhook and also offers Sync from Meta. Return to the account where the template was created, sync and check appointment_reminder_2026. Syncing fetches Meta’s status; it does not approve a template. The film shows a demonstration scenario only.
After a real approval, the status is Approved and the template is usable. Quality pending concerns the quality rating of an already approved template; it is different from Pending template review. This demonstration screenshot is not a live Meta approval. Approval is also not proof of customer delivery.
This is an alternative outcome for the same template. If it is Rejected, on desktop select it and read the reason in the side preview. The current mobile view does not show the reason; check desktop or Meta WhatsApp Manager. Possible causes include malformed variables, missing samples, duplicate content or policy violations. The desktop screen illustrates a reason; Meta determines the actual decision and reason.
You can edit a rejected template and resubmit it, or appeal with relevant evidence through Meta tools. An edit returns the template to review; earlier approval does not automatically cover the new text. Create a new version to change the name or language. Do not edit a Pending template.
On the standalone templates screen, Use shows that the template is ready and offers a separate shortcut to conversations. It does not send a message itself. In the appropriate sending screen, fill the actual values for every variable and check the customer, account and consent. The Dana, date and time sample values are not automatic sending data. This demonstration sends no message.
Meta continues monitoring customer feedback and quality. A Paused or Disabled template cannot be sent. Check status before using it, particularly in an automated workflow. Approval does not remove consent, opt-out or relevance requirements. The tutorial screens demonstrate the process only.
The path is complete: account, example, name and category, language, header, body and variables, footer, buttons, samples and review. Next comes submission and waiting for Approved status. This tutorial performed no Meta submission, live approval or customer message. Continue in your own Message Templates screen.
Ready to use only when its real status is Approved. Check consent, status and variable values before every send.
If rejected, read the reason, correct the wording or samples and resubmit. Do not send a template that is still under review.
Official Meta and WhatsApp sources checked on 10 October 2026. Meta may update its rules and review screens.
A read-only walkthrough. Pick a station or use Next. It does not change an account or send any template or message.
A template is a message structure reviewed by Meta. Here it is a reminder for an existing appointment. The wording stays fixed; the name, date and time change for each appointment. Choosing a Lynxbe example creates a starting draft, not an approval.
A customer message opens or renews the 24-hour service window. Outside it, an approved template is required to contact them. Sending a template alone does not open a free-form message window. Qualifying WhatsApp calls can also open or renew the window under Meta rules.
Before using a template, confirm that the customer provided contact details and opted in to communication from the business. Make the business identity and purpose clear. Keep the content relevant, honor opt-outs and avoid sensitive information. Template approval is not permission to contact any number.
Open Communications → WhatsApp → Templates. In Message Templates, choose the WhatsApp account that will own the template. Creation and syncing require template management permission. If no account is connected, complete the WhatsApp connection guide first.
The system-message card lets you approve the wording Lynxbe uses for the business. This is a separate business approval: that action does not submit a template to Meta or approve it for sending. In this tutorial, create a regular template using Create.
Create opens an eight-step creation page. Choose Appointment Reminder under Quick-start templates. It fills the category, body, footer and buttons. These are Lynxbe examples; they are different from Meta’s approved template library.
Choose Utility for a reminder tied to the customer’s actual appointment. This category also covers specific order, account or service-request updates under Meta’s definitions. Adding a discount or purchase offer can make the template Marketing.
This is a separate marketing example. Choose Marketing for an offer, promotion or re-engagement. A message mixing a service update with commercial promotion is also Marketing. Meta may change Utility to Marketing during review or after approval. Return to our reminder to continue.
Authentication is for one-time identity verification codes. Lynxbe opens a Copy Code, One-Tap or Zero-Tap flow instead of a free-form body. App options require Android details; Zero-Tap requires acceptance of its terms. Do not add promotions, media or URLs to the authentication content.
Our example is appointment_reminder_2026. Lynxbe requires a leading letter and at least three characters; Meta accepts lowercase Latin letters, numbers and underscores, up to 512 characters. The name must be unique within that account and language. You can add a nickname such as Appointment reminder, an internal Lynxbe label. Existing template name and language are immutable; create a new version to change them.
The Hebrew example uses Hebrew; the English version uses English (US). Lynxbe updates the quick-start example text when its language changes. Check the result yourself. Meta does not translate your message; submit another language version for its own review.
In Header, choose no header or one of the supported formats. Our example uses the text Appointment reminder. A text header supports up to 60 characters and one variable. Media requires a sample for review; use a format and size supported by the screen and Meta rules.
The example addresses the customer, reminds them of the appointment and asks for confirmation or rescheduling. Keep one clear purpose. A standard body supports up to 1,024 characters. Do not add sales content to a Utility message or request sensitive identifiers. Meta reviews the content, not just the category selection.
In our reminder, {{1}} is the customer name, {{2}} the date and {{3}} the time. Numbered variables must be sequential without gaps. Do not begin or end the body with a variable, or make the body mostly variables. Sample values are not automatically sent to customers.
In Footer, check the example’s opt-out wording. A standard footer is optional, supports up to 60 characters and has no variables. The wording alone does not implement opt-out processing; ensure your workflow records and honors the request before any further message.
Our example includes Yes, confirm and No, reschedule. These are quick replies. Other screen options include a URL or phone call, depending on the template type. A standard button label supports up to 25 characters. Creating a button does not automatically confirm or reschedule an appointment; connect responses to the appropriate workflow.
For a URL button, supply a valid address and a sample if it is dynamic. Meta permits one variable at the end of a dynamic URL. A call button needs a valid number. Labels do not contain variables or newlines. Counts and combinations depend on the format and implementation; follow the screen’s validation rather than assuming every combination is supported.
In Examples, fill every variable: {{1}} = Dana; {{2}} = 18.10.2026; {{3}} = 10:30. These are demonstration values, without private customer information. Add samples for header or URL variables too. If you chose a media header, provide an appropriate media sample.
Read the message in the WhatsApp preview on Review. Check that samples are in the right positions and the meaning is clear. Also verify the name, account, language and category. This preview is a pre-submission check; it does not prove delivery or approval.
Screen validation catches missing fields and some structural errors. Review the wording again: permitted purpose, appropriate category, valid variables and a sample for each variable. Avoid duplicates, prohibited content and sensitive information. Passing local validation does not guarantee Meta approval.
After Review, choose the creation action. In the real system, Lynxbe submits the template to the selected Meta account. This tutorial demonstrates the action offline without a real submission. No customer message is sent here, and submission does not guarantee approval.
After submission, the template appears in the list with Pending status. It is not usable yet. Keep the submission details and check its status later. This screen uses demonstration data; no template was submitted to Meta.
Meta documentation checked on 10 October 2026 says a review decision can take up to 24 hours. The current Lynxbe interface shows a 24–48 hour estimate. This is not a guarantee, and the outcome may be rejection. While the status is Pending, wait; do not edit a template still under review.
Lynxbe can receive status updates by webhook and also offers Sync from Meta. Return to the account where the template was created, sync and check appointment_reminder_2026. Syncing fetches Meta’s status; it does not approve a template. The film shows a demonstration scenario only.
After a real approval, the status is Approved and the template is usable. Quality pending concerns the quality rating of an already approved template; it is different from Pending template review. This demonstration screenshot is not a live Meta approval. Approval is also not proof of customer delivery.
This is an alternative outcome for the same template. If it is Rejected, on desktop select it and read the reason in the side preview. The current mobile view does not show the reason; check desktop or Meta WhatsApp Manager. Possible causes include malformed variables, missing samples, duplicate content or policy violations. The desktop screen illustrates a reason; Meta determines the actual decision and reason.
You can edit a rejected template and resubmit it, or appeal with relevant evidence through Meta tools. An edit returns the template to review; earlier approval does not automatically cover the new text. Create a new version to change the name or language. Do not edit a Pending template.
On the standalone templates screen, Use shows that the template is ready and offers a separate shortcut to conversations. It does not send a message itself. In the appropriate sending screen, fill the actual values for every variable and check the customer, account and consent. The Dana, date and time sample values are not automatic sending data. This demonstration sends no message.
Meta continues monitoring customer feedback and quality. A Paused or Disabled template cannot be sent. Check status before using it, particularly in an automated workflow. Approval does not remove consent, opt-out or relevance requirements. The tutorial screens demonstrate the process only.
The path is complete: account, example, name and category, language, header, body and variables, footer, buttons, samples and review. Next comes submission and waiting for Approved status. This tutorial performed no Meta submission, live approval or customer message. Continue in your own Message Templates screen.