WhatsApp bot. From first message to the right teammate.
From a ready-made template to your own flow. Set up Sales, Service and a teammate, test locally and save without activation.
Original screens and isolated example data. The simulator is local; no live bot activation, message delivery or customer conversation assignment occurs.
A 5-minute video in 20 chapters. Jump directly to the step you need.
Every inquiry. A clear start.
Build a bot with Sales, Service and a teammate option. Collect what is needed, then test every path before activation.
The video is currently unavailable. Continue with the written guide and demonstration below.
View transcript
Every inquiry. A clear start. Build a bot with Sales, Service and a teammate option. Collect what is needed, then test every path before activation. Original Lynxbe screens · Demo dataEvery inquiry. A clear start. Build a bot with Sales, Service and a teammate option. Collect what is needed, then test every path before activation. Original Lynxbe screens · Demo data
Start with a ready-made example. In the empty list, choose Start from Template, then Welcome & Menu. It is an editable bot flow with a greeting and a menu. Original Lynxbe screens · Demo dataStart with a ready-made example. In the empty list, choose Start from Template, then Welcome & Menu. It is an editable bot flow with a greeting and a menu. Original Lynxbe screens · Demo data
Give the draft a name. Enter a clear name and save. Close the settings opened after the first save. Saving does not activate the bot. Original Lynxbe screens · Demo dataGive the draft a name. Enter a clear name and save. Close the settings opened after the first save. Saving does not activate the bot. Original Lynxbe screens · Demo data
Check where the flow begins. Follow Start to the greeting and then the menu. Edit the greeting to explain briefly what the customer can do. Original Lynxbe screens · Demo dataCheck where the flow begins. Follow Start to the greeting and then the menu. Edit the greeting to explain briefly what the customer can do. Original Lynxbe screens · Demo data
Three options. An easy choice. Choose Buttons and set Sales, Service and a teammate. Each option has a customer label and an ID for its path. Original Lynxbe screens · Demo dataThree options. An easy choice. Choose Buttons and set Sales, Service and a teammate. Each option has a customer label and an ID for its path. Original Lynxbe screens · Demo data
For Sales, start with a name. Add Collect Info to the Sales path. Its first field is name, type Text, with a short question for the customer. Original Lynxbe screens · Demo dataFor Sales, start with a name. On desktop: Add Collect Info to the Sales path. Its first field is name, type Text, with a short question for the customer. Desktop step · Original Lynxbe screen
Add email. And a helpful retry. Add an email field with type Email. Write a clear prompt and an error message that helps the customer try again. Original Lynxbe screens · Demo dataAdd email. And a helpful retry. Add an email field with type Email. Write a clear prompt and an error message that helps the customer try again. Original Lynxbe screens · Demo data
For Service, ask what happened. Add a separate Collect Info node for Service: issue, type Text. Ask for a short description to help the teammate. Original Lynxbe screens · Demo dataFor Service, ask what happened. On desktop: Add a separate Collect Info node for Service: issue, type Text. Ask for a short description to help the teammate. Desktop step · Original Lynxbe screen
Choose who receives the handover. In Agent Handover, explicitly select Noa Example. Write a general summary that works for all three paths. Original Lynxbe screens · Demo dataChoose who receives the handover. In Agent Handover, explicitly select Noa Example. Write a general summary that works for all three paths. Original Lynxbe screens · Demo data
Connect. Then check the whole flow. Sales and Service collect information before Noa. The teammate option goes straight to handover. Check completion and cancellation paths too. Original Lynxbe screens · Demo dataConnect. Then check the whole flow. On desktop: Sales and Service collect information before Noa. The teammate option goes straight to handover. Check completion and cancellation paths too. Desktop step · Original Lynxbe screen
Save the flow. Keep it a draft. Save and wait for completion. The editor also autosaves after five seconds without another change. Publish activates the bot. Original Lynxbe screens · Demo dataSave the flow. Keep it a draft. Save and wait for completion. The editor also autosaves after five seconds without another change. Publish activates the bot. Original Lynxbe screens · Demo data
Test before activation. Open Test Bot, from the three-dot menu on mobile. Check that the greeting and menu appear in the local simulation. Original Lynxbe screens · Demo dataTest before activation. Open Test Bot, from the three-dot menu on mobile. Check that the greeting and menu appear in the local simulation. Original Lynxbe screens · Demo data
Sales. One question at a time. Choose Sales and enter Maya Example. Check that the bot asks for email next, following the field order. Original Lynxbe screens · Demo dataSales. One question at a time. Choose Sales and enter Maya Example. Check that the bot asks for email next, following the field order. Original Lynxbe screens · Demo data
Test a reply that needs correction. Enter maya.example.com. Check the retry message and make sure the bot waits for email instead of proceeding to handover. Original Lynxbe screens · Demo dataTest a reply that needs correction. Enter maya.example.com. Check the retry message and make sure the bot waits for email instead of proceeding to handover. Original Lynxbe screens · Demo data
Correct it. The path continues. Enter maya@example.com. Check that collection completes and the simulator shows handover. This is a local result. Original Lynxbe screens · Demo dataCorrect it. The path continues. Enter maya@example.com. Check that collection completes and the simulator shows handover. This is a local result. Original Lynxbe screens · Demo data
Restart. Check another path. Choose Restart. Make sure the simulator returns to the greeting and menu before testing Service. Original Lynxbe screens · Demo dataRestart. Check another path. Choose Restart. Make sure the simulator returns to the greeting and menu before testing Service. Original Lynxbe screens · Demo data
Service. A short issue before handover. Choose Service and enter an example issue. Check that this path collects the description and reaches Agent Handover. Original Lynxbe screens · Demo dataService. A short issue before handover. Choose Service and enter an example issue. Check that this path collects the description and reaches Agent Handover. Original Lynxbe screens · Demo data
A direct path to a teammate too. Restart and choose the teammate option. Check that it reaches handover without the Sales and Service questions. Original Lynxbe screens · Demo dataA direct path to a teammate too. Restart and choose the teammate option. Check that it reaches handover without the Sales and Service questions. Original Lynxbe screens · Demo data
Return to the list. Check the state. Close the simulator and save. Return to the bot list and check that the example was saved and remains inactive. Original Lynxbe screens · Demo dataReturn to the list. Check the state. Close the simulator and save. Return to the bot list and check that the example was saved and remains inactive. Original Lynxbe screens · Demo data
Reopen. See what was saved. Reopen the draft and check its menu, fields, Noa and connections. Activation is a separate step after business checks. Original Lynxbe screens · Demo dataReopen. See what was saved. Reopen the draft and check its menu, fields, Noa and connections. Activation is a separate step after business checks. Original Lynxbe screens · Demo data
Original Lynxbe screens with isolated example data. Editor autosaves use isolated transport; this page’s walkthrough is read-only. The simulator checks local flow, not real delivery or conversation assignment. Adding and connecting nodes in this example is shown on desktop. No live bot activation, customer message or publication occurs.
The steps. At your pace.
Before starting: the correct business, authorized bot access and an existing teammate. Use a draft and example data. Prepare the example’s connections on desktop. Later activation requires a suitable WhatsApp account and messaging checks.
Define the task.
Build a first-response flow with Sales, Service and a teammate option. Sales collects name and email; Service collects an issue. All three paths reach the handover configured for Noa. Start and finish with an inactive draft and example data only.
Choose a starting template.
In the empty bot list, choose Start from Template, then Welcome & Menu. This is an editable bot-flow template, not a Meta-approved message template. Give it a clear name, save and close settings after the first save. On mobile, Save is in the three-dot menu.
Edit the greeting and menu.
Check the sequence from Start through the greeting to the menu. Write a short welcome and choose Buttons. Set Sales, Service and a teammate option with IDs sales, service and human. Label is the customer-facing text; ID is used to connect the path.
Add name and email collection on desktop.
Drag Collect Info onto the desktop canvas. In Collect Information, add name, type Text, with a name prompt. Choose Add Field and add email, type Email, with a clear prompt and error message. Keep name before email. The simulator’s email check is basic format only, not ownership or delivery verification.
Add a Service path on desktop.
Add a separate Collect Info node with issue, type Text, and a short issue prompt. This path does not need the Sales questions. Use desktop to add and connect nodes in this example; existing settings can also be reviewed and edited on mobile.
Select the teammate explicitly.
Open Agent Handover and choose Noa Example in Assign To. Write a general summary suitable for all three paths. Dashboard Alert is the example setting. The simulator neither assigns a real conversation nor sends Noa an alert.
Complete the connections on desktop.
Remove unused example reply nodes. Connect sales to name and email, service to issue collection, and human directly to handover. Connect both collection completion outputs to handover. Connect the menu default output and both cancellation outputs to End. Check that each connection starts from the correct option.
Separate saving from activation.
Choose Save and wait for completion. The editor also autosaves after five seconds without another change. Publish saves and activates a bot that meets the requirements, including a selected WhatsApp account. Do not activate it in this guide. Demonstration saves use isolated transport only.
Test Sales and an invalid email.
Open Test Bot, from the three-dot menu on mobile. Choose Sales and enter Maya Example. Enter maya.example.com and check that the error keeps the bot waiting for email. Correct it to maya@example.com and check completion and simulated handover. This local run sends no messages.
Test Service and a teammate separately.
Choose Restart, then Service. Enter an issue and check handover without the Sales questions. Restart again and choose the teammate option; check direct handover. A simulator message is not proof of real assignment or delivery.
Check the list and state.
Close the simulator, save and return to the bot list. Find the example by name and check that it remains inactive. A listed bot is not necessarily active. Do not use an activation toggle or Publish to finish the check.
Reopen what was saved.
Reopen the draft and review its three choices, fields, Noa and completion/cancellation connections. Before real activation, review the WhatsApp account, messaging requirements and the team’s process. Publication and activation remain a separate step outside this demonstration.
The result being checked: a saved inactive draft with three choices, name/email or issue collection, and handover configured for Noa. Test invalid email and correction, Service and a teammate locally, then reopen the draft.
No next step? Check the connection from the correct option. Invalid email advances? Check that the field type is Email. Save failed? Do not assume changes were stored. A simulator handover does not test real teammate handling.
The screens and behavior checked.
Content checked against Lynxbe screens and source behavior on 15 October 2026. The demonstration is isolated; validation and delivery status are recorded separately.
One flow. Three ways forward.
A read-only walkthrough. Select a step or use Next. This page does not save or activate a real bot.
Every inquiry. A clear start.
A bot helps when inquiries start with repeated questions. Our example offers Sales, Service or a human teammate. Sales collects a name and email; Service asks about the issue. Noa is the selected handover target. We finish with a saved inactive draft. All data and checks are isolated, with no message to a real customer.
Every inquiry. A clear start.
A bot helps when inquiries start with repeated questions. Our example offers Sales, Service or a human teammate. Sales collects a name and email; Service asks about the issue. Noa is the selected handover target. We finish with a saved inactive draft. All data and checks are isolated, with no message to a real customer.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Start with a ready-made example.
In the empty bot list, choose Start from Template, then Welcome & Menu. This is a starting bot flow with a greeting, menu and example actions. It is different from a Meta-approved message template. We will edit its content and connections for our task.
Start with a ready-made example.
In the empty bot list, choose Start from Template, then Welcome & Menu. This is a starting bot flow with a greeting, menu and example actions. It is different from a Meta-approved message template. We will edit its content and connections for our task.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Give the draft a name.
Rename the bot “Welcome enquiries. Example.” and choose Save. On mobile, Save is in the three-dot menu. The first save may open Bot Settings; close them to continue editing. The editor also autosaves after five seconds without another change. Publish is a separate action that activates the bot; we do not use it in this guide.
Give the draft a name.
Rename the bot “Welcome enquiries. Example.” and choose Save. On mobile, Save is in the three-dot menu. The first save may open Bot Settings; close them to continue editing. The editor also autosaves after five seconds without another change. Publish is a separate action that activates the bot; we do not use it in this guide.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Check where the flow begins.
The template already connects Start to a greeting and then to the menu. Check those connections, select the greeting and write a short welcome, such as: Hi, happy to help. What can we help with today? On mobile, tap a node to open its settings. Text on the canvas has not been sent to a customer.
Check where the flow begins.
The template already connects Start to a greeting and then to the menu. Check those connections, select the greeting and write a short welcome, such as: Hi, happy to help. What can we help with today? On mobile, tap a node to open its settings. Text on the canvas has not been sent to a customer.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Three options. An easy choice.
Select the menu and choose Buttons. Write a short question and replace the options with Sales, Service and a teammate. Label is the text the customer sees; ID identifies the path to connect. Our IDs are sales, service and human. Renaming a label alone does not connect a path. We check the connections next.
Three options. An easy choice.
Select the menu and choose Buttons. Write a short question and replace the options with Sales, Service and a teammate. Label is the text the customer sees; ID identifies the path to connect. Our IDs are sales, service and human. Renaming a label alone does not connect a path. We check the connections next.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
For Sales, start with a name.
On desktop, drag Collect Info from the node palette onto the canvas. In Collect Information, set the first field to variable name name, type Text, and a prompt such as What is your name? The bot waits for a reply before the next field. Use desktop for adding and connecting nodes in this example. Existing settings can also be reviewed and edited on mobile.
For Sales, start with a name.
On desktop, drag Collect Info from the node palette onto the canvas. In Collect Information, set the first field to variable name name, type Text, and a prompt such as What is your name? The bot waits for a reply before the next field. Use desktop for adding and connecting nodes in this example. Existing settings can also be reviewed and edited on mobile.
Original Lynxbe screens · Demo data
Desktop step · Original Lynxbe screen
Add email. And a helpful retry.
In the same node, choose Add Field. Use variable name email and type Email. Add a prompt such as What is your email address? and a retry message such as Enter an email with @ and a dot. Keep name first, then email. The simulator checks only basic format. It does not verify address ownership or whether messages can be delivered.
Add email. And a helpful retry.
In the same node, choose Add Field. Use variable name email and type Email. Add a prompt such as What is your email address? and a retry message such as Enter an email with @ and a dot. Keep name first, then email. The simulator checks only basic format. It does not verify address ownership or whether messages can be delivered.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
For Service, ask what happened.
On desktop, drag a second Collect Info node onto the canvas for Service. Set a field named issue, type Text, with a prompt such as What do you need help with? This path is separate from Sales and does not ask for the name and email fields configured there. Use an invented issue without real customer details.
For Service, ask what happened.
On desktop, drag a second Collect Info node onto the canvas for Service. Set a field named issue, type Text, with a prompt such as What do you need help with? This path is separate from Sales and does not ask for the name and email fields configured there. Use an invented issue without real customer details.
Original Lynxbe screens · Demo data
Desktop step · Original Lynxbe screen
Choose who receives the handover.
Select the existing Agent Handover node. In Assign To, choose Noa Example instead of leaving Any available agent. Write a general summary, such as New inquiry from the first-response menu. The same handover serves all three paths. Our example uses Dashboard Alert; the local simulation does not alert a real teammate or assign a customer conversation.
Choose who receives the handover.
Select the existing Agent Handover node. In Assign To, choose Noa Example instead of leaving Any available agent. Write a general summary, such as New inquiry from the first-response menu. The same handover serves all three paths. Our example uses Dashboard Alert; the local simulation does not alert a real teammate or assign a customer conversation.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Connect. Then check the whole flow.
On desktop, remove the unused example reply nodes. Connect Sales to name and email collection, and Service to issue collection. Connect both completion outputs to Noa’s handover. The teammate option goes directly there. Connect the menu’s default output and both cancellation outputs to End. Check for unfinished paths. A connection must use the matching option output, not simply pass near a node.
Connect. Then check the whole flow.
On desktop, remove the unused example reply nodes. Connect Sales to name and email collection, and Service to issue collection. Connect both completion outputs to Noa’s handover. The teammate option goes directly there. Connect the menu’s default output and both cancellation outputs to End. Check for unfinished paths. A connection must use the matching option output, not simply pass near a node.
Original Lynxbe screens · Demo data
Desktop step · Original Lynxbe screen
Save the flow. Keep it a draft.
Choose Save after editing. On mobile, open the three-dot menu. The editor schedules autosave after five seconds without another change; still check completion before leaving. Publish saves and activates a bot that meets the requirements, including a selected WhatsApp account. Leave this example inactive and test it locally.
Save the flow. Keep it a draft.
Choose Save after editing. On mobile, open the three-dot menu. The editor schedules autosave after five seconds without another change; still check completion before leaving. Publish saves and activates a bot that meets the requirements, including a selected WhatsApp account. Leave this example inactive and test it locally.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Test before activation.
Choose Test Bot to open the original simulator. On desktop it appears beside the canvas; on mobile it fills the workspace. Check that the greeting comes before the three clear options. This runs the flow locally, even before activation. Messages shown here are not sent to a customer’s WhatsApp.
Test before activation.
Choose Test Bot to open the original simulator. On desktop it appears beside the canvas; on mobile it fills the workspace. Check that the greeting comes before the three clear options. This runs the flow locally, even before activation. Messages shown here are not sent to a customer’s WhatsApp.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Sales. One question at a time.
Choose Sales in the simulator and answer Maya Example to the name prompt. The bot should continue to the email prompt you configured, without skipping the field. This checks the field order and the menu connection to the correct collection node. All names and addresses in the example are invented.
Sales. One question at a time.
Choose Sales in the simulator and answer Maya Example to the name prompt. The bot should continue to the email prompt you configured, without skipping the field. This checks the field order and the menu connection to the correct collection node. All names and addresses in the example are invented.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Test a reply that needs correction.
Enter maya.example.com, without @. The simulator should show your configured error message and keep waiting for the same field. This matters alongside the successful path: the customer needs a clear way to continue. No email provider is contacted to check the address.
Test a reply that needs correction.
Enter maya.example.com, without @. The simulator should show your configured error message and keep waiting for the same field. This matters alongside the successful path: the customer needs a clear way to continue. No email provider is contacted to check the address.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Correct it. The path continues.
Correct the address to maya@example.com. Once accepted, the flow follows the completion output to Agent Handover. Review the simulated handover and the collected values. A local handover message does not prove that Noa received a real conversation or that a customer message was delivered.
Correct it. The path continues.
Correct the address to maya@example.com. Once accepted, the flow follows the completion output to Agent Handover. Review the simulated handover and the collected values. A local handover message does not prove that Noa received a real conversation or that a customer message was delivered.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Restart. Check another path.
Choose Restart in the simulator. The local run returns to its starting point, so the next check does not continue with the previous choice and values. Check that the greeting and three options appear again. This does not restart a customer bot or publish the draft.
Restart. Check another path.
Choose Restart in the simulator. The local run returns to its starting point, so the next check does not continue with the previous choice and values. Check that the greeting and three options appear again. This does not restart a customer bot or publish the draft.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Service. A short issue before handover.
From the restarted menu, choose Service. Answer the issue prompt, for example Could I get an update about my order?. Check that the simulator stores the issue and continues to handover without the Sales name and email questions. This catches an incorrect connection even when the menu itself looks right.
Service. A short issue before handover.
From the restarted menu, choose Service. Answer the issue prompt, for example Could I get an update about my order?. Check that the simulator stores the issue and continues to handover without the Sales name and email questions. This catches an incorrect connection even when the menu itself looks right.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
A direct path to a teammate too.
Restart and choose the human teammate option. It should go directly to the handover configured for Noa. The simulator displays a local handover result; the check does not alert a teammate or change a real conversation’s assignment. This keeps a simple path for someone who does not want to answer the collection questions.
A direct path to a teammate too.
Restart and choose the human teammate option. It should go directly to the handover configured for Noa. The simulator displays a local handover result; the check does not alert a teammate or change a real conversation’s assignment. This keeps a simple path for someone who does not want to answer the collection questions.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Return to the list. Check the state.
Close the preview, save and wait for completion. Return to the bot list and find the example by name. Check its inactive state. Appearing in the list does not mean the bot was published or sent to a customer. Do not use an activation toggle to complete this guide.
Return to the list. Check the state.
Close the preview, save and wait for completion. Return to the bot list and find the example by name. Check its inactive state. Appearing in the list does not mean the bot was published or sent to a customer. Do not use an activation toggle to complete this guide.
Original Lynxbe screens · Demo data
Original Lynxbe screens · Demo data
Reopen. See what was saved.
Reopen the bot from the list. Review the freshly loaded flow: three choices, Sales and Service fields, Noa’s handover, completion and cancellation connections. This checks saved data rather than an editor left open. Before real activation, review the WhatsApp account, messaging requirements and the team’s working process. Publish activates the bot and remains outside this demonstration.
Reopen. See what was saved.
Reopen the bot from the list. Review the freshly loaded flow: three choices, Sales and Service fields, Noa’s handover, completion and cancellation connections. This checks saved data rather than an editor left open. Before real activation, review the WhatsApp account, messaging requirements and the team’s working process. Publish activates the bot and remains outside this demonstration.
