One phone system. Two businesses. Different rules.
Tyler Heshka · https://heshka.com/work/casebook/shared-business-telephony
- Case Study
- Business rules · Telephony
- 1 min read
I configured separate incoming-number mappings, hours and menu logic within one shared phone system.
Projects in this story
My part
Business-rule translation, PBX configuration and endpoint integration.
Shared telephony environment
- Incoming number · Business A
- Business A time rules
- Business A menu / groups
- Responsible people / endpoints
- Incoming number · Business B
- Business B time rules
- Business B menu / groups
- Responsible people / endpoints
01
The number matters
Two businesses used the same overall telephony environment. I configured the incoming numbers, time conditions and menus around the business being called.
Calls to each business could enter through different numbers, follow that business’s hours and menu logic, and reach the appropriate people or endpoints.
02
Configure the rules and the endpoints
I configured separate interactive voice-response menus and extension/ring groups where appropriate, along with inbound and outbound routes, SIP trunks and main numbers. The endpoint work included IP phones and analogue/SIP adapters.
I also configured voicemail, conference calling, call parking, music on hold and paging/PA integration.