Lynxbe
עברית
All guides
Build a voice menu callers can follow and your team can answer.
Call routes are tested in a simulation. The demonstration does not place a call.
A 6-minute 30-second video in 26 chapters. Jump directly to the step you need.
Build a greeting that welcomes callers and leads them to sales or service.
The video is currently unavailable. You can continue with the written steps and demonstration below.
Every call. Its destination. Build a greeting that welcomes callers and leads them to sales or service. Real Lynxbe screens · Demo data
Open your call flows Open IVR / Flows. Start a new flow or open an existing one here. Real Lynxbe screens · Demo data
Start with a template Choose Basic Receptionist: a greeting, two keys and two destinations. Then make it yours. Real Lynxbe screens · Demo data
Give the flow a clear name Our name is Example business — sales and service. We use the same flow throughout. Real Lynxbe screens · Demo data
Write the welcome Enter the greeting: Welcome to our example business. We will help you shortly. Demo data · No live routing changes
Two keys. Two choices. Name each choice: 1 for sales, 2 for service. The menu prompt says exactly the same. Real Lynxbe screens · Demo data
Connect every key Connect 1 to sales and 2 to service. Also define what happens when no choice is received. Real Lynxbe screens · Demo data
Choose the timezone Add Business Hours before the greeting, choose Asia/Jerusalem and keep Skip hours check off. Real Lynxbe screens · Demo data
Set when the business is open Set the days and hours. Our example opens Sun–Thu, 09:00–17:00; Friday and Saturday are closed. Real Lynxbe screens · Demo data
Include a closure day Add a date and name for a schedule exception, then connect Holiday to the appropriate greeting. Real Lynxbe screens · Demo data
Explain what happens when closed The closed greeting invites callers to leave a message and leads to voicemail. It needs a destination too. Real Lynxbe screens · Demo data
Sales reaches an extension For key 1, choose extension 1001 and set the ring time. Busy and No answer continue to voicemail. Real Lynxbe screens · Demo data
Service reaches a queue For key 2, choose Example customer service. Check that the queue has agents who can take calls. Real Lynxbe screens · Demo data
Give waiting a clear end Review the ring strategy, wait limits and no-answer destination. A time limit still needs a fallback connection. Demo data · No live routing changes
When the destination is another number Transfer uses a phone number instead of an extension or queue. This is an alternative, outside our chosen route. Demo data · Alternative without a call
Give every caller a next step Read the warnings and review missing connections, destinations and voicemail. Fix them before activation. Real Lynxbe screens · Demo data
Review the whole flow Trace the entry through to every destination. A valid graph is still not a real call test. Real Lynxbe screens · Demo data
Try the sales branch Open Simulate flow, choose Open and press 1 at the menu. Check that the destination is extension 1001. Demo data · Manual simulator
Try service too Restart, choose Open and press 2. Check that the route reaches your chosen service queue. Demo data · Manual simulator
Check the closed branch In the simulator, choose Closed. Check the route to the closed greeting and then voicemail. Demo data · Manual simulator
Check the closure exception Choose Holiday and check the exception route. The listed date still needs review. Demo data · Manual simulator
Try receiving no selection Return to the menu and try Timeout and No-match. Check that both reach the fallback. Demo data · Manual simulator
Save before linking a number Save the flow and check that the draft was saved. Saving and publishing are separate steps. Demo data · No live routing changes
Choose the business number Open Route numbers from Flow settings. Review the existing assignment before enabling your selection. Demo data · No live routing changes
Check where the number leads The example number is assigned to the flow. Linking can activate routing immediately, even for a draft. Demo data · No live routing changes
Publish after reviewing Check the number, audio and warnings before Publish. After real activation, test incoming calls too. Demo data · No live routing changes
Original Lynxbe screens use isolated demonstration data. The simulator manually selects branches. There are no live calls, number purchases, audio generation, publication or routing changes.
Before starting: page access and required permissions, destination names, extensions and a queue with agents, opening hours and greeting text. Before activation, also prepare a business-owned number, reviewed audio and a chosen no-answer response.
Open IVR / Flows and create a flow from Basic Receptionist. It starts with a greeting and two queues that need adapting. Enter a clear name and save a draft. Our example is Example business — sales and service.
Write the greeting: Welcome to our example business. We will help you shortly. Configure 1 for sales and 2 for service in the menu, with a prompt that says exactly those choices. Our example waits 5 seconds with 3 tries. Connect each key to its destination, and connect Timeout and Default to voicemail too.
Add Business Hours before the greeting. Choose Asia/Jerusalem and set days and hours: our example opens Sun–Thu, 09:00–17:00. Keep Skip hours check off. Connect Open to the menu, and Closed and Holiday to a closed greeting and voicemail. The example closed greeting is: We are currently closed. Please leave a message and we will get back to you. The exception is 21 October 2026, Example closure day.
Sales reaches extension 1001; service reaches Example customer service with example agents 1002 and 1003. Review ring times, queue strategy and wait limits. Connect Busy and No answer to voicemail. Queue settings apply to every flow using that queue. Transfer to an external number is an alternative needing a reviewed number and fallback destinations; it is outside our final example route.
Read the canvas warnings and fix missing destinations. In Simulate flow, choose Open and press 1, then restart and test 2. Also try Closed, Holiday, Timeout and No-match. These are manual simulator choices: they do not place calls, evaluate the real clock, record messages or prove agent availability. Review the schedule and audio separately.
Save and check the draft name. Recheck the flow before linking a number: assignment can activate routing immediately, even for a draft. From Flow settings, open Route numbers and inspect the inventory and existing assignment. Publication is blocked without a linked number; with no numbers, Go to Phone Numbers offers purchase or porting. In real publication, review warnings, audio and the compile/load result. After real activation, call and test every route. This demonstration performs no live actions.
Check that each choice reaches its destination and unanswered callers have a next step. Save and review the draft before linking a number, because linking can change routing immediately.
Saving, number assignment and publication are different actions. A simulator check is not a test call; after real activation, also test incoming calls.
Checked against Lynxbe screens and source behavior on 14 October 2026. The shown result uses isolated data; it does not prove phone-system activation or a live phone call.
A read-only walkthrough. Choose a step or use Next. It does not call, publish or change an active phone number.
An interactive voice response flow, or IVR, offers callers choices and routes their call. We will build one business flow: 1 for sales, 2 for service, and a different greeting outside opening hours. The shown data and actions are isolated. No calls or customer routing are changed.
Open IVR / Flows. If a flow already serves your phone number, review it before creating another. In this example we create a new flow. Your permissions determine which editing and publishing actions are available.
When creating a flow, choose Basic Receptionist. It starts with a greeting, menu and two queues. It does not itself connect agents or an active phone number. Business Hours Router is another template; here we add hours to our selected flow. Check every destination and connection, including those supplied by the template.
Enter a recognizable name that will also make sense on the phone-number page. Our example is Example business — sales and service. The name identifies the flow in Lynxbe; it is not the greeting heard by callers. Save the draft before continuing to actions that need a saved flow.
Select the greeting node and enter the text shown in this example: Welcome to our example business. We will help you shortly. We put the key choices in the next menu. Choose a suitable language and voice, or use the available file and recording options. Generate & Listen can contact an audio provider; this example generates no live audio. Listen to the greeting and menu before real activation.
In the menu node, name key 1 Sales and key 2 Service. Set the menu prompt to: For sales, press 1. For service, press 2. Use my services can help when your service names belong in the menu. This example needs just two choices. Above five choices, the page suggests a sub-menu; that is guidance, not a hard limit.
Connect output 1 to the sales destination and output 2 to service. Our example waits 5 seconds and allows 3 tries. Connect timeout and default to a fallback instead of leaving a branch without a destination. Check that the spoken options, menu keys and canvas connections agree.
Add a Business Hours node and connect the flow entry to it. Select Asia/Jerusalem so the example schedule uses the business timezone. Keep Skip hours check off: enabling it sends every call down Open instead of using your configured hours and exceptions. Next, set the days and hours.
Review the day rows and set Sunday–Thursday to 09:00–17:00 in this example. Leave Friday and Saturday closed. Check each day’s opening and closing time, including when you use a schedule preset. Connect Open to the greeting and menu, and Closed to the closed greeting. An open day should reach your regular greeting; a closed day should reach your chosen closure response.
Our example adds 21 October 2026 as Example closure day. This is a demonstration date, not a claim that it is a holiday. Exceptions identify days needing a separate path. Connect Holiday to the closed greeting or another chosen response. If you use the offered holiday list, review its dates and adapt them to your business.
Write the closed greeting shown in this example: We are currently closed. Please leave a message and we will get back to you. Connect the greeting to Voicemail. Check the maximum message length and what happens after recording. Promising a callback also needs a team workflow; the greeting alone does not create a return call.
An extension suits a choice that should reach a specific internal destination. Our sales key reaches extension 1001 with a 20-second ring time. Select an existing extension and check its owner. Connect Busy and No answer to voicemail or another destination. An unconnected output can end the call without a fallback.
A queue suits requests that several agents can handle. In the queue picker, choose Example customer service, with example extensions 1002 and 1003. Check the queue’s agents. You can create a queue from this page, but naming it alone does not add agents. Queue settings are shared by every flow using that queue.
Our example rings all agents together, with a 15-second agent ring time. The caller waits at most 60 seconds, or 15 seconds when no agent is available. Save the queue settings and connect No answer to voicemail. Check that the queue has agents. Changing its times or agents also affects other flows using the same queue.
Transfer suits a destination reached through an external phone number. Enter the number, check Will dial and set a ring time. Connect Busy and No answer to a fallback. The example screen uses 0500000002 as a demonstration number; it is not added to the final sales-and-service route and makes no call. Before real use, review the number, permissions and account telephony costs.
The canvas review bar highlights items needing attention. Select a warning to reach its node. Check menu timeout, extension Busy and No answer, and queue No answer. Connect them to your chosen destination. A warning is not necessarily a blocking error; even if you can continue, understand what happens to the caller.
Check that there is an entry point, needed nodes are connected, and the extension and queue are selected. Flow validation can block publication when there is an error. Connection and node warnings still need review even when not blocking. Next we use the simulator to check each choice. A saved or checked graph does not prove that an active number reaches it.
Open Simulate flow. Manually choose Open in the simulator, continue through the greeting and menu, and press 1. Check the highlighted node and trace through to extension 1001. Inspect Busy and No answer connections on the canvas; this simulator does not offer an extension-status test here. It does not call the extension or prove an agent answers.
Restart the simulation. Choose Open and press 2 at the menu. Check that the trace reaches your chosen service queue. The simulator may show demo-service; this is the same Example customer service queue. Review No answer to voicemail and the wait limits in settings and on the canvas; this simulator does not offer a queue-status test here. It does not test agent availability, real waiting times or actual recording.
Restart and manually choose Closed at the hours node. Check that the route avoids the open menu and reaches the closed greeting and voicemail. This tests the branch you selected. The simulator does not evaluate the current clock as a real schedule test; separately review your days, hours and timezone.
Restart and manually choose Holiday. Check that the exception reaches the chosen closed greeting. Return to the hours settings and verify the Example closure day date. Choosing Holiday in the simulator tests that branch connection; it does not prove that the active phone system recognized the date.
Restart, choose Open and reach the menu. Select Timeout and check the voicemail connection. Restart again and choose No-match to check Default too. This does not wait on a real call or receive keys from a phone; it manually tests the branches you connected.
Choose Save and confirm the correct flow name. Without a routed phone number, the draft is not itself an incoming-call route. Saving stores the settings; it does not confirm that the active phone system uses them. Complete the checks and greeting before number assignment, because assignment itself can affect incoming calls.
Open Flow settings, then Route numbers to this IVR. Choose a number owned by this business and intended for this flow. If it belongs to another flow, enabling it reassigns the route here. With no numbers, Go to Phone Numbers opens purchase or porting options. Purchase, porting and routing changes are real actions; this guide uses isolated demo inventory only.
After assignment, check that the number appears under the correct flow. Assignment itself can compile and activate routing, even while the flow is a draft; do not link an active number before reviewing. If a routing-preparation warning appears, review it instead of relying only on the number selection. This shows isolated assignment, without changing live routing.
Return to the flow builder and review Publish. Without a linked number, publication is blocked. Fix errors and read warnings before confirmation. Publication can generate audio and perform activation effects; also check the compile/load result. If compilation fails, read the failure message and check the flow status before retrying. After real activation, call and test every branch. This example stays at readiness with isolated data; it shows no successful live publication or call.
