Cloud PBX User Provisioning in Houston, TX 77055

A user, an extension and a device are three different things

Every hosted platform sells seats, and a seat is an accounting unit, not a plan. Three lists have to exist before anything is created in a portal, and in a Spring Branch business they are never the same length.

A user is a person: a name, a login, a mailbox, a PIN, permissions. An extension is a number dialable inside your system, and plenty of extensions belong to nobody. A device is a thing that registers: a desk phone, a cordless base, a softphone, a mobile app, an analog adapter feeding a fax or a gate box.

One owner can be a single user with three registrations. A loading area can be an extension with no user at all. We have walked shops here with twelve staff that needed seven licensed users, nine extensions and fourteen endpoints.

The counter phone that three people answer, built so messages do not vanish

The classic failure in a walk-in business is quiet and expensive. Somebody builds the counter phone as one employee’s personal extension. Messages land in his private mailbox, and on the two days a week he is not in, nobody can open them. The business finds out when a customer asks why nobody called back about a job quoted three weeks ago.

The fix is deciding, deliberately, what the counter is:

• A ring group rings several phones at once – fine for two or three positions.
• A call queue holds the caller and distributes to whoever is logged in. Worth it once more than one call at a time is normal.
• A shared mailbox behind either, with voicemail-to-email going to an address more than one person can open. This is the single change that stops lost messages.

Pickup and park, not hold

Two features shop floors need and nobody asks for by name. Call pickup lets someone in the back answer a phone ringing at the counter by dialling a short code instead of walking. Call park puts a caller in a numbered slot retrievable from any phone in the building, where ordinary hold traps the call on one handset. When the person the caller wants is under a vehicle, that is the difference between a transfer and a lost call.

The paging horn

Overhead paging is still the right answer in a noisy building. A paging adapter turns the horn into a dialable zone, and at provisioning you decide who may page and whether announcements also cut into the desk phone speakers. Zones matter: a shop that pages the whole building for every call stops listening to the horn within a week.

Every decision that has to be made before a seat is created

Creating a user takes about ninety seconds. Deciding what goes in it is the actual work, and doing it once at a table beats fixing it one complaint at a time over the following month. For each person we settle:

• Internal display name, and the outbound caller ID they present to the outside world – which is frequently not their own number.
• Extension, and whether the role justifies a direct outside number.
• Voicemail PIN policy, greeting, and where voicemail-to-email lands.
• Mobile app, desk phone or both, and whether the mobile rings with the desk or after it.
• After-hours behaviour: voicemail, a mobile, or the on-call person.
• Calling permissions – local, long distance, international, premium-rate – per person, not for everyone at once.
• Call recording on or off, membership in queues, pickup groups and page zones.
• The emergency registered address for that seat.

Dial-by-name is the first thing to break on a street like this one

A dial-by-name directory searches one field, usually the surname. Spring Branch businesses are staffed by people with two surnames, hyphenated surnames, and names transliterated into English more than one way. A caller spelling a paternal and maternal surname on a keypad gets no match, hears an error and hangs up. That is a provisioning problem, not a caller problem.

What we set when we build the seats:

• The searchable surname field holds the name customers actually use, not the full legal name on the payroll record.
• Where aliases are supported, the second surname goes in as one, so either spelling finds the person.
• The name prompt is recorded in the person’s own voice. Text-to-speech mangles exactly the names most likely to be searched.
• For the four or five people customers ask for by name, the greeting states the extension outright. A short list beats a directory.

Two languages without a long menu

Bilingual businesses get sold a language menu at the front door, which adds a step for every caller. The lighter seat-level approach is a per-user voicemail greeting recorded in both languages, plus a per-user prompt language so the system speaks to each employee in the one they prefer. The menu stays short and the bilingual handling happens where the call lands.

Not everyone on the payroll needs the same seat

The expensive tier buys call recording for everybody, analytics, CRM integration and larger meeting rooms. A parts runner needs dial tone, a mailbox and a mobile app. Provisioning well means the smallest seat that does the job, re-checked after ninety days.

Three things worth checking on your bill:

• Common-area or device-only seats. Most platforms have a cheap seat type meant for a break room, a warehouse cordless or a lobby phone. Using a full user licence there is the most common overspend we find in a ten to thirty person business.
• Direct numbers billed separately. On several platforms the outside number is a line item apart from the seat, so handing one to everybody adds a monthly charge for numbers nobody publishes.
• Seats belonging to people who have gone. Licences never release themselves.

We do not sell the platform and take nothing from your monthly bill, so we have no reason to specify a bigger seat than the job needs.

What EVOTECH does on a 77055 provisioning visit, in order

1. Walk the building and count endpoints, not people: every live jack, cordless base, fax, analog adapter, paging amplifier and dock phone.
2. Build the map with you on one sheet – person, seat type, extension, direct number, groups, permissions – agreed before any account is created.
3. Confirm cabling and switch capacity, and flag any run or powered port to add before cutover.
4. Create users, extensions, ring groups, queues, pickup groups and page zones in your provider’s portal.
5. Bind each handset to its user by MAC address through the manufacturer’s redirect service, so the phone pulls its own configuration on boot instead of being typed in at the desk.
6. Program keys by role: line keys, presence keys only where somebody watches another phone, park slots, page, intercom.
7. Set and verify the emergency registered address on every seat, including ones with no person attached.
8. Sit with each person for a few minutes on transfer, park, pickup, voicemail and mobile app login, then leave the written map and PIN process with the office.

We are a licensed and insured low-voltage contractor, twenty years into this work in the Houston area. We work alongside whichever hosted platform you chose; the seat design, wiring, handsets and training are our side of it.

What moves the estimate, and the mistakes that bring us back

Provisioning is priced on the work in front of us and quoted itemised after we have seen the building. What moves it:

• Endpoint count rather than headcount.
• New cable runs or powered switch ports for phones with no jack today.
• How many analog devices need gateway ports.
• Whether we build the call flows and greetings too, or only the users.
• Whether handsets are new or re-used, and training as one group session or desk by desk.

We never quote a figure over the phone before seeing the site. The on-site estimate is free.

Five mistakes that generate a second visit

• A seat per employee, then finding the shop runs on two shared positions and a queue.
• Personal direct numbers on outbound caller ID, so customers ring one man’s phone and the business misses calls whenever he is out.
• International dialling left enabled by default on every seat.
• The extension belonging to nobody – fax, alarm dialler, gate – forgotten until the day it matters.
• Emergency addresses never updated after a desk reshuffle.

Related services

Frequently asked questions