Start your EVOTECH request in under a minute.
Setting Up an Auto Attendant in Fulshear, TX
In little more than a decade Fulshear grew from a small crossroads town into a city of master-planned neighborhoods, so many of its businesses are putting a phone menu together for the first time. Below is how we build one from a blank account, in the order we do it, and how we track down the fault when an existing menu starts misbehaving.
Phone menus in a town that is still being built
Much of Fulshear’s commerce is brand new: medical and dental offices, fitness studios, restaurants and professional suites in centers along FM 1093 and FM 359, close to neighborhoods like Cross Creek Ranch, Fulbrook on Fulshear Creek and Jordan Ranch. A newly opened office typically has a phone number and nothing behind it.
We see three situations over and over:
- A new tenant in a freshly finished suite. Desk phones need cable and power before any menu matters, and the landlord’s buildout may or may not have included data drops at each workstation.
- A home-based business in one of the master-planned communities. One owner and a cell phone, where the attendant’s job is to make the business sound established and send each caller to the right person, even if that person is the same owner in a different role.
- Ranch, equine and farm operations beyond the edge of town, west toward Simonton or south toward the Brazos. Internet there may be fixed wireless or cellular, and that shapes what a hosted phone platform can carry.
EVOTECH works out of Katy, so Fulshear is part of our regular service area rather than a special trip.
First check: can your internet connection carry the calls?
A hosted auto attendant lives in the provider’s data center, so the menu keeps answering even when your office is offline. The phones on your desks are another matter, and they depend entirely on your connection.
- Bandwidth. A standard uncompressed call (the G.711 codec) uses roughly 90 to 100 kbps in each direction once packet overhead is counted. Ten simultaneous calls need about a megabit each way. Upload speed is usually the limit on cable and wireless service.
- Jitter and packet loss. These break calls long before raw speed runs out. A fixed-wireless link that tests fast at noon can turn choppy in heavy rain or in the evening, so we measure over a period of time instead of trusting one speed test.
- Router settings. We give voice traffic priority, and we turn off the SIP ALG feature that many small-business routers enable by default. It rewrites call signaling and is a frequent cause of one-way audio and phones that lose registration.
- Power. A battery backup on the modem, router and PoE switch carries the phones through the short flickers that come with summer storms.
For a total outage, we set a failover destination on the provider’s side, such as the owner’s cell phone, so the menu has somewhere to send callers while the office is dark.
Building the attendant from a blank account, step by step
- List every reason people call. We sit with whoever answers the phone, or review a few weeks of call history, and group the calls into three to five reasons. Rare requests fold into a single “for anything else” option.
- Decide on numbers. Keep the main number or port it in, choose whether key staff get direct numbers, and decide whether a toll-free line should reach the same menu.
- Create destinations before the menu. Ring groups, queues and mailboxes are built first, so every key points to something real. An option aimed at an empty or deleted group is a classic silent failure.
- Set the calendar. Central time, weekday hours, any lunch closure, and the full year’s holidays.
- Write the script. See the sample in the next section.
- Record the prompts. A human voice for the main greeting, exported in the format the platform asks for (often 8 kHz, 16-bit mono WAV) and level-matched so the volume doesn’t jump from one prompt to the next.
- Handle the edges. What happens on silence, on a wrong key, on 0 for the operator and on star to repeat, plus a limit on how many times the menu can replay.
- Verify emergency calling. Kari’s Law and the RAY BAUM’S Act require multi-line systems to let anyone dial 911 without a prefix and to send a location responders can use. For internet phones, that means the registered emergency address for each phone, suite number included, must be right.
- Test from outside the building. We call from a cell phone and a separate line, try every key, stay silent, press a wrong key, and temporarily shift the schedule to hear the after-hours and holiday paths.
- Hand it over. We show the owner how to change a greeting, add a holiday and flip the closed-now switch, and leave a one-page diagram of the call flow.
A sample main greeting, and why it is written that way
“Thank you for calling [Business Name]. If you know your party’s extension, you may dial it at any time. To schedule or change an appointment, press 1. For billing and insurance, press 2. For our hours and address, press 3. For anything else, press 0 or stay on the line.”
- The need comes before the key. Callers listen for their reason and then catch the number that follows. “Press 1 for scheduling” makes them hold a digit in memory before they know whether it applies.
- No “please listen carefully, our options have changed.” It costs every caller several seconds and is almost never true.
- The whole top level runs under about 20 seconds. Longer than that, and callers start pressing 0 to escape.
- “Stay on the line” catches everyone else, including callers on older phones or in a car who can’t easily press keys.
- No advertising before the options. Promotions belong in the hold music, after the caller has chosen where to go.
When a menu misbehaves: symptoms and causes
If your attendant already exists and something is off, this is the path we work through:
| What callers report | Most likely cause | Where we look |
|---|---|---|
| They press 1 and nothing happens | Touch-tone method mismatch between carrier, platform and phones, or a compressed codec distorting the tones | DTMF settings on the trunk and platform; whether the keypress shows up in the call log |
| One press counts as two | Tones sent both in the audio and as separate events | Set a single DTMF method end to end |
| The closed greeting plays at 10 a.m. | Wrong account time zone, a holiday left switched on, or a daylight-saving rule | Account time zone, schedule rules and the holiday list |
| Silence after choosing an option, then a disconnect | One-way audio from SIP ALG, NAT or a firewall closing the voice ports | Router SIP ALG, firewall timeouts, phone keep-alive settings |
| An option rings forever or drops the call | The key points to a deleted or empty ring group | Trace every key to its final destination |
| Forwarded calls land in an employee’s personal voicemail | The cell phone’s own voicemail picks up before the forward times out | Shorten the forward ring time, or require a keypress to accept |
| The name directory finds no one | Directory disabled for users, or names never recorded | Directory settings and each user’s recorded name |
| Volume jumps between prompts | Prompts recorded at different levels | Normalize the audio files and upload them again |
Leaving room for the next hire and the next location
Fulshear businesses often double their staff within a year or open a second site in Katy or Richmond. A few choices made now prevent a rebuild later:
- Point menu options at ring groups, not individuals, so hiring or losing a person never requires editing the menu.
- Reserve extension blocks, such as the 100s for the front office and the 200s for providers or field staff.
- If a second location is likely, pick a platform that manages several sites in one account, each with its own hours.
- When cabling a new suite, leave a spare Cat6 at each desk and buy a PoE switch with open ports.
What you can safely change yourself
Once the attendant is built, day-to-day edits belong to you: recording a seasonal greeting, adding a closure date, flipping the closed-now switch for a storm day, or moving an employee between ring groups. We show you each of those at handover.
Call us when the problem is below the menu: keypresses that don’t register, calls that drop or go silent, a port that stalls, a second location to bring in, or new phones that need cable and network work. Those take tools and access that a web portal doesn’t give you.
Factors that set the scope of a Fulshear phone project
- Whether the suite needs cabling, a PoE switch or battery backup before phones can go in
- Internet readiness work, such as router replacement, voice priority settings or a backup connection
- How many menus, sites and numbers are involved, and any porting
- Recorded versus synthesized prompts, and a second language
- An after-hours cutover and staff training
We list each of these on its own line so you can see where the effort goes. A call to (832) 359-2425 books the on-site estimate.
Request an auto attendant quote in Fulshear
Related services
Frequently asked questions
How long should our main greeting be?
Our office west of town is on fixed-wireless internet. Can we still use a hosted auto attendant?
What happens when someone presses a key that isn’t on the menu?
Can we change the holiday schedule ourselves?
Does a one-person home business need an auto attendant?
Build your first Fulshear phone menu the right way
We will check the connection, build the menu in order, test every path from outside the building and show you how to run it. Ring (832) 359-2425 and we will schedule an on-site estimate, followed by an itemized quote.
Book a Consultation
Ready for EVOTECH to help?
Before you leave, send the quick version. We will review the page you came from and reply with the clean next step.
