What is a pattern menu?

How it differs from a regular menu

In a regular IVR menu, every key leads to a destination: 1 for sales, 2 for service. That works when there are five destinations. But what do you do when there are two hundred? A yeshiva with two hundred students, a company with eighty extensions, a call center with a hundred customer numbers — you can't build a menu with two hundred keys.

A pattern menu solves this: the caller presses a sequence of digits, and the PBX checks which pattern the sequence matches. A pattern can be an exact number ("204" — to extension 204) or a broad rule ("any three-digit number starting with 5" — to the dormitory).

In other words: a regular menu asks "What do you want?", while a pattern menu asks "Who are you looking for?"

How it works behind the scenes

1. The caller hears a message: "Enter the extension number" or "Enter the student's number followed by pound."
2. The PBX collects the digits until the caller presses pound, until the expected number of digits is reached, or until a few seconds pass with no keypress.
3. The sequence is checked against the list of patterns.
4. If a match is found — the call goes to the pattern's destination.
5. If there is no match — the caller hears a message and tries again, or goes to a default destination.

The choice between "enter and press pound" and "a fixed number of digits" is an important consideration. When all the numbers are the same length (for example three digits), the PBX can continue right after the third digit. When the lengths differ, a pound at the end prevents the system from "jumping ahead" after 20 when the caller meant 205.

Real-life examples

• Direct dial to an extension — "If you know the extension number, enter it now." Someone who knows the extension doesn't have to go through the menu.
• A yeshiva — a parent enters a student's number and reaches the student's personal voicemail box. Numbers starting with 5 go to the dormitory, and with 7 to the cheder.
• A service center — a customer enters a customer number, and is routed to the team that handles their area.
• An information line — you enter the code of a class or a message, and hear its recording.
• A nonprofit — a volunteer enters a personal code and reaches the box designated for them.

The yeshiva example shows the power of broad patterns. Instead of defining two hundred lines — "501 to student A's box, 502 to student B's box" — in many systems you can build the list so that each range of numbers leads to a different area, and each number within the range reaches the matching voicemail box. When a new student joins, you add him to the right range.

Advantages and Limitations

The big advantage is scale. One phone number and one message lead to hundreds of destinations. There is no need for a separate number for each student or each employee, and no need for a secretary to transfer calls. When a student is added, you add a line to the list.

The second advantage is speed for people who know the system. A regular customer who knows that his contact is at extension 214 dials the number in the middle of the greeting and gets through in seconds, without going through layers of menus.

The limitation: the caller has to know what to dial. Someone who doesn't know the number gains nothing from a pattern menu, so it always needs another route alongside it - a key to a regular menu, or to the front desk. Another limitation is maintenance: a list of hundreds of patterns has to be managed, and a list that isn't kept up to date sends callers to destinations that no longer exist.

Common mistakes

• Overlapping patterns - "any number starting with 2" and also "204". You need to know which one wins, and test it.
• No handling of a wrong entry - a caller who dials a number that doesn't exist hears silence, and hangs up.
• Unclear length - not telling the caller whether to press pound, so he waits and the system waits.
• An outdated list - students who have finished, employees who have left. It's worth updating at the start of every year or quarter.

Practical tips

Combine the pattern menu inside the regular menu: "For service press 1, for sales press 2, and if you know the extension number, dial it now." That way someone who knows the number gets through directly, and someone who doesn't uses the keys.

When there are many patterns, manage them in a spreadsheet. It's easier to go over a list of two hundred rows in Excel than on a screen, and it's easy to spot duplicates.

Don't use patterns that begin with a digit that has a meaning in the regular menu. If 1 is sales, a pattern starting with 1 will confuse both the system and the caller.

Full example 1: direct dialing to an extension in a company with eighty employees

An IT services company with eighty employees, extensions 200 through 279. Until now the receptionist transferred every call, and at busy times customers waited half a minute for her just to say "Put me through to Yossi." The solution: a pattern menu built into the main menu.

The script: "Hello, you've reached the company. If you know the extension number, dial it now. For support press 1, for sales 2, for the front desk 0." The invitation to dial an extension comes first, because a regular customer already dials in the middle of the sentence.

The patterns: all the extensions are three digits and begin with 2, so instead of eighty rows you define one pattern: "2 followed by two digits" - destination: the extension that was dialed. The keys 1, 2 and 0 stay in the regular menu, and there is no conflict because no extension begins with 1 or 0.

What actually happens: a customer dials 214. The PBX recognizes three digits, doesn't wait for a pound, and rings extension 214. If the employee doesn't answer within 25 seconds, the call goes to his personal voicemail box, and the message is sent to his email. A customer who presses 2 and stops - the PBX waits about three seconds, and if no more digits arrive it treats it as the key 2 (sales). This is exactly the place to check that the delay is neither too long nor too short.

What this saved: according to the call log, after a month about a quarter of the incoming calls reached an extension directly, without going through the front desk. The receptionist was left with the calls that really need her.

Full example 2: student numbers in a yeshiva with 240 students

A large yeshiva with three grade levels and a dormitory. Each student has a personal voicemail box, and parents call one number. Without a pattern menu, the office manager would get dozens of calls every evening saying, "Tell my son to call home."

Number structure: the yeshiva assigns each student a four-digit number: the first digit is the grade (1, 2 or 3), the second is the room, and the last two are a running number. So 2117 is a student in grade 2, room 1. The number is printed on the student's personal dialing card, and he gives it to his parents at the start of the year.

The script: "To leave a message for a student, dial the student number followed by pound. If you don't know the number, press 0 for the office." The pound is required here, because there are also short codes for staff (for example 51 for the mashgiach) and the lengths are not uniform.

The patterns: the range 1000-1999 for the boxes of grade 1, 2000-2999 for grade 2, 3000-3999 for grade 3. Three rows instead of 240. At the start of the year, the list of new students is imported from a file with each one's box number, and those who have graduated are deleted.

What the parent experiences: he dials 2117#, hears "Leave a message after the tone" with the student's name in the personal greeting, and leaves a message. The student hears the message during a break, from the dormitory phone, with his personal card. The whole call ends without anyone from the staff.

A number that doesn't exist: "The student number was not found. Try again, or press 0 for the office." After two failed attempts the PBX transfers to the office on its own, because the parent probably has an old number.

What happens when it goes wrong - symptom, cause, fix

A rule that saves most of the table: after every change to the list, dial three numbers - one from the start of the range, one from the end, and one that doesn't exist - and check that each one reaches the right place.

Pattern menu versus routing code and speed dial

Three tools look similar because in all of them you dial a sequence of digits, but they sit at different points in the call. A pattern menu works on an outside caller who is already inside the call. A routing code is an internal number that leads to a component of the PBX - you can dial it from an extension, and you can point to it from a menu. Speed dial is a shortcut that you dial from an extension to reach a long external number.

In practice they complement each other: a pattern menu saying "Dial the student number" can send each range to a routing code that represents the dormitory boxes, and you can change that code once without touching the patterns.