Documentation

Elite Call Center User & Administrator Manual

Current-build documentation for setup, routing, queues, agents, browser calling and administration.

About This Manual

This manual describes the current Elite Call Center implementation in the supplied September 28, 2026 source package. It is written for both administrators and agents. The same core Call Center can be used inside Elite Office Suite; standalone packaging may present the same functions under a different entry point.

Two access levels Inside Elite, calls.use exposes day-to-day phone/call tools. calls.manage exposes administration such as Departments & Queues, Phone Menus, Announcements and Extensions.

Quick Start

Use this order for a clean first-time configuration.

  1. Configure the Twilio connection and save settings.
  2. Set the Twilio phone number's inbound voice webhook to the Inbound Voice Webhook URL shown by Elite.
  3. Select Test Twilio Connection and confirm the status becomes connected.
  4. Create Departments that reflect the business structure.
  5. Add Call Agents from active staff members.
  6. Create Queues, choose a ring strategy and max wait time, then assign agents to each queue.
  7. Create Announcements for spoken greetings or prompts.
  8. Create Extensions for staff and choose Browser Phone, External Phone or Browser + External behavior.
  9. Create a Phone Menu, choose its greeting and make it default if it should answer the main number.
  10. Add menu options that route digits to queues, extensions, announcements, another menu, voicemail, repeat menu or hang up.
  11. Have agents open Agent Console, set Availability to Available and verify their queue assignments.
  12. Have browser-phone users open Phone and select Enable Phone before taking or placing calls.

1. Access and Permission Model

Call Center functions are scoped to the active organization and are separated between normal call use and call administration.

AbilityCurrent navigation
calls.usePhone; Calls & Voicemail; Call Directory
calls.manageDepartments & Queues; Phone Menus; Announcements; Extensions

A Call Center entitlement must also be active for the organization. The current Call Center landing page reports the organization name and that the entitlement is active.

2. Twilio Connection Settings

Call Center Settings stores the organization's Twilio connection and basic call behavior.

FieldCurrent validation / purpose
Account SIDTwilio Account SID; format AC followed by 32 hexadecimal characters.
Auth TokenSecret token. If a token is already stored, leaving the field blank keeps the existing secret.
API Key SIDOptional key SID; format SK followed by 32 hexadecimal characters.
API Key SecretOptional secret. Blank keeps an existing stored secret.
TwiML Application SIDOptional application SID; format AP followed by 32 hexadecimal characters.
Twilio Phone NumberE.164-style number beginning with + and country code.
Enable call recordingTurns call recording behavior on/off for the organization.
Enable voicemailTurns voicemail behavior on/off; new settings default voicemail on in the UI.
After-hours destinationOptional text destination used by call behavior logic.
Inbound Voice WebhookElite displays the exact organization-specific webhook URL to configure on the Twilio phone number.

Configure and test

  1. Open Call Center Settings.
  2. Enter Account SID, Auth Token and Twilio Phone Number. These three fields are what the current controller uses to determine whether the configuration is complete.
  3. Add API Key SID / Secret and TwiML Application SID if your deployment uses them.
  4. Choose recording and voicemail behavior and enter an after-hours destination if required.
  5. Select Save Call Center Settings.
  6. Copy the displayed Inbound Voice Webhook into the Twilio phone number's incoming voice webhook configuration.
  7. Return to Elite and select Test Twilio Connection.
  8. Confirm the connection status reports connected. If the test fails, recheck credentials and try again.
Secrets The settings form is designed so blank Auth Token or API Key Secret fields keep the stored secret rather than clearing it.

3. Departments

Departments group queues by business function.

Create a department

  1. Open Departments & Queues.
  2. Under Departments, enter Department name.
  3. Optionally enter Description.
  4. Select Add Department.

Department names are limited to 100 characters; descriptions to 1,000 characters in the current controller.

4. Call Agents

A Call Agent is an active staff member who can be assigned to one or more queues and receive queued calls.

Add a call agent

  1. Open Departments & Queues.
  2. Under Call Agents, select an eligible staff member.
  3. Select Add Call Agent.
  4. Confirm the agent appears in the list. Newly added agents are created active and allowed to receive calls in the current implementation.
Agent readiness Being a Call Agent is not enough to pick up queued calls. For browser queue pickup, the current code also requires an active browser-phone extension, an Available presence status, and assignment to the target queue.

5. Queues

Queues hold callers until an eligible agent receives the call.

SettingCurrent choices / limits
Queue nameRequired; up to 100 characters. Queue names must be unique within the organization after slugging.
DepartmentOptional; must belong to the organization.
Ring strategyRound robin; Ring all available agents (simultaneous).
Max waitRequired; 30 to 3,600 seconds.
AgentsOne or more Call Agents can be assigned with Save Queue Agents.

Create and staff a queue

  1. Open Departments & Queues.
  2. Enter Queue name.
  3. Optionally choose Department.
  4. Choose Round robin or Ring all available agents.
  5. Enter Max wait seconds.
  6. Select Add Queue.
  7. In the queue card, select the agents who should receive that queue.
  8. Select Save Queue Agents.

6. Announcements

Announcements are reusable spoken prompts for phone menus and routing.

Create an announcement

  1. Open Announcements.
  2. Enter Name.
  3. Enter Spoken Text.
  4. Optionally set Voice and Language.
  5. Select Create Announcement.

The current controller allows up to 120 characters for the announcement name and 4,000 characters for spoken text. Voice and language are optional fields.

7. Phone Menus and IVR

Phone Menus define the greeting and keypad routing presented to callers.

Create a phone menu

  1. Open Phone Menus.
  2. Enter Menu Name.
  3. Choose a Greeting announcement or leave No greeting selected.
  4. Set Timeout Seconds (1-30).
  5. Set Max Attempts (1-10).
  6. Select Make this the default phone menu if this menu should be the organization's default menu.
  7. Select Create Phone Menu.

Add a menu option

  1. Choose the Phone Menu.
  2. Choose a Digit: 0-9, * or #.
  3. Enter a Label describing the choice.
  4. Choose Destination.
  5. If the destination requires a target, select the appropriate Queue, Extension, Announcement or another Phone Menu.
  6. Select Save Menu Option.
DestinationBehavior represented by current UI
QueueSend to a configured active queue.
ExtensionSend to an active internal extension.
AnnouncementPlay a configured announcement.
Another Phone MenuRoute to a different active menu; the current validation blocks a menu from routing to itself.
VoicemailRoute to voicemail behavior.
Repeat MenuReplay/re-enter the current menu flow.
Hang UpEnd the call.
Direct extension dialing In the current inbound controller, the default company menu also accepts a three-digit extension directly in addition to one-digit menu choices. Extensions use the 101-999 range.

8. Extensions

Extensions connect staff members to browser calling, external forwarding, voicemail and the directory.

FieldCurrent behavior
ExtensionRequired three-digit-style number from 101 through 999; unique for the organization.
Staff MemberRequired and must be an active organization member.
Directory NameRequired display name, up to 120 characters.
DepartmentOptional active department.
Ring ModeBrowser Phone; External Phone; Browser + External.
Forwarding NumberOptional external target, up to 32 characters in current validation.
Browser PhoneEnable browser endpoint for that extension.
VoicemailEnable voicemail for that extension.
DirectoryMake the extension visible in Call Directory.
ActiveEnable/disable the extension.

Create an extension

  1. Open Extensions.
  2. Enter an unused number between 101 and 999.
  3. Select an active Staff Member.
  4. Enter Directory Name.
  5. Optionally choose Department.
  6. Choose Ring Mode.
  7. If external ringing is used, enter Forwarding Number.
  8. Choose Browser Phone, Voicemail, Directory and Active flags as needed.
  9. Select Create Extension.

9. Browser Phone

Phone is the staff browser-phone interface.

  • If the account has no active browser-phone extension, the page reports No Browser Phone Assigned.
  • Select Enable Phone before receiving browser calls.
  • The phone interface provides Call, Answer, Reject, Hang Up and Mute controls.
  • Outbound external calls require a valid E.164 phone number and a configured organization caller ID / Twilio phone number.
  • Internal browser calls can target an active three-digit extension.
Queue pickup requirements The current queue-pickup controller verifies the signed-in browser-phone identity, active extension, active Call Agent record, Available presence state and assignment to the selected queue before allowing pickup.

10. Call Directory

Call Directory lists extensions that have Directory enabled and provides a Call action for internal staff dialing.

Directory entries can reflect Browser Phone, Voicemail and External Ring capabilities as configured on the extension.

11. Agent Console

Agent Console gives a Call Agent a focused view of presence, assigned queues and waiting callers.

Availability

StatusMeaning in current UI
AvailableEligible for queued-call pickup when other requirements are met.
AwayNot presented as available for queue pickup.
OfflineNot available for queue pickup.
  1. Open Agent Console.
  2. Choose Available, Away or Offline.
  3. Select Update Status.
  4. Review My Queues to confirm assignments.
  5. Under Waiting Calls, review Queue, Caller and Waiting Since.
  6. Select Answer to open the Phone page for that queued call.

12. Calls & Voicemail

Calls & Voicemail is the operational call-history and follow-up screen.

  • Summary counts include Answered, Voicemails and Open items.
  • Recent call rows classify activity such as Live, Voicemail, Answered or Missed based on current call state.
  • Voicemail rows can expose the recorded voicemail when a recording SID is present.
  • Staff can Mark Reviewed, Complete or Reopen call follow-up items.
  • Refresh Live Calls reloads current call state.
  • The current transfer control offers Sales, Technical Support and Billing as transfer destinations.
Current transfer limitation The live-transfer UI is presently wired to three named department choices: Sales, Technical Support and Billing. If you configure a different department structure, confirm the transfer UI is updated before documenting other destinations for staff.

13. Recording, Voicemail and After-Hours Behavior

Organization-level settings control whether recording and voicemail are enabled. Extension-level settings also control voicemail availability for an extension.

  • Enable call recording is an organization setting.
  • Enable voicemail is an organization setting and voicemail can also be enabled per extension.
  • The settings page accepts an After-hours destination value.
  • Voicemail completion and recording-status webhooks exist in the current routing layer so recorded voicemail can be associated with call activity.

14. Current Routing Behavior

The Call Center combines organization settings, default menu selection, menu options, extensions, queues and agent state.

  1. An inbound call reaches the organization-specific Twilio inbound webhook.
  2. The current routing layer can render the default active phone menu.
  3. On the default menu, a caller may enter a single configured menu digit or a three-digit extension.
  4. Menu options can route to queues, extensions, announcements, another menu, voicemail, repeat or hang up.
  5. A queue holds the caller until an eligible agent can receive/pick up the call or queue handling reaches its configured wait behavior.
  6. Browser Phone can place internal extension calls and external PSTN calls when configured.

15. Troubleshooting

Use this table for the most likely current-build causes.

SymptomCheck
Connection status is not_configuredAccount SID, Auth Token and Twilio Phone Number must all be present.
Test Twilio Connection failsRecheck Twilio credentials; save first, then test again.
Inbound calls do not reach EliteConfirm Twilio phone number incoming voice webhook exactly matches the Inbound Voice Webhook shown in Call Center Settings.
Agent cannot see/answer queued callsConfirm agent record, queue assignment, Available status and active browser-phone extension.
No Browser Phone AssignedCreate/activate an extension for that user with Browser Phone enabled.
Internal extension unavailableConfirm extension is active and Browser Phone is enabled for internal browser dialing.
Queue creation rejectedUse a unique name, valid department, supported ring strategy and max wait from 30-3600 seconds.
Menu option rejectedConfirm the selected target is active and belongs to the same organization; another-menu routing cannot point to the same menu.
External call rejectedUse a valid +country-code E.164 destination and confirm the organization Twilio phone number is configured.
Transfer choices do not match configured departmentsCurrent Staff Calls transfer control is fixed to Sales, Technical Support and Billing in this source build.

Appendix A - Administrator Field Reference

AreaImportant current limits
DepartmentName 100 chars; description 1,000 chars
QueueName 100 chars; max wait 30-3,600 sec; round_robin or simultaneous
AnnouncementName 120 chars; spoken text 4,000 chars
Phone MenuTimeout 1-30 sec; attempts 1-10; digits 0-9, * or #
Extension101-999; directory name 120 chars; forwarding text 32 chars
Agent presenceavailable; away; offline
Twilio phoneE.164 format beginning with +

Appendix B - Deployment Checklist

  • Twilio credentials saved and connection tested.
  • Inbound voice webhook configured at Twilio.
  • Recording/voicemail policy choices set.
  • Departments created.
  • Agents added.
  • Queues created and agents assigned.
  • Announcements created.
  • Extensions assigned and tested.
  • Default phone menu created.
  • IVR options routed and tested.
  • Agents trained to set presence.
  • Browser Phone tested for internal and external calls.
  • Voicemail and call follow-up tested.
  • Transfer destinations verified against the current three-choice transfer UI.