Features › Use cases › Answer every call without a receptionist

Use case · interactive walkthrough

Answer every call without a receptionist

One main number gets calls for Sales, Support and individual staff. Nobody has time to answer and transfer each call, and after hours the phone just rings out.

👤 Customer👤 Sales, support or any staff member👤 Office manager who sets it upretailserviceshealthcareeducationhospitality

Tip: change the switches above the diagram and press ▶ Play. The address bar keeps your exact scenario, so you can copy the link and send it to a customer. Presenter mode ↗

What if…

  • Busy season? Add "press 3 to track an order" that plays a recorded status update and returns to the menu.
  • Sinhala, Tamil and English callers? Start with a short language menu, then a separate welcome menu per language.
  • Several branches? Give each branch its own number and greeting, all sharing one staff directory.
  • Urgent problems after hours? Add "press 1 for the on-call engineer" to the after-hours greeting, forwarding to a mobile.
  • No time to record greetings? Type them in and let text to speech read them out.

Questions to ask next

For the presenter: map this flow to the customer's own business.

  1. Which teams or people do callers ask for most often?
  2. What are your opening hours, and which public holidays and Poya days do you close?
  3. How long should a phone ring before the call moves to voicemail or another team?
  4. Who should receive messages left after hours, and how quickly must they reply?
  5. Do callers need the menu in more than one language?

Features that make it work

Each of these appears as a tag on the steps above. Open one to see every use case that relies on it.

Check your understanding

Two tracks at mid level: Business for owners and team leads, Technical for IT staff. Every question is a scenario, so you apply the flow rather than recall terms.