Phone System, Phone Numbers, and Call Routing

Overview

The OneSuite Phone System brings supported business calling controls into the Communications area. The current public interface includes phone-number management, phone-system setup, phone menus and greetings, browser-based calling tools, and voicemail. Administrators configure the service while staff use the calling experience provided for their role.

Business Value and Typical Use Cases

Assign or review business phone numbers.
Configure how inbound calls reach staff or voicemail.
Set up phone menus and greetings.
Place calls from the browser dialer or click-to-call controls where available.

Before You Begin

Confirm the organization has a configured communications provider.
Know which phone number and destination you are configuring.
Prepare the greeting or menu choices before changing inbound routing.

Prerequisites and Permissions

Communications module access.
Configured phone service and number.
Administrator permission for setup changes.

Concepts

A business phone number is the public entry point. Routing decides what happens to an inbound call. A phone menu or greeting can guide callers. Staff destinations and voicemail handle the call when appropriate.

How This Feature Fits Into OneSuite

Communications intersects with CRM, tasks, appointments, booking, and customer history. Use related records to avoid repeating conversations or contacting the wrong person.

Connected services such as Gmail, Microsoft/Outlook, Google Calendar, Google Meet, and Zoom should be treated as provider connections that enable specific OneSuite workflows; their presence does not automatically grant every user access.

Screen Orientation

Communications brings multiple channels into OneSuite, including supported email, SMS, browser calling/phone functions, voicemail, calendar connections, meetings, and booking. Each channel has its own connection and permission requirements, so validate setup before diagnosing a user workflow.

Always confirm the sender, mailbox, phone number, extension, calendar, or meeting provider context before sending or placing an action. Shared communication resources can serve multiple users, but ownership and visibility rules still matter.

Use customer context whenever available. Messages, calls, appointments, and related activity are more useful when staff can understand who the customer is and what happened previously.

Open the area described in this guide and pause before editing. Identify the page heading, primary action button, search/filter controls, record list or detail panel, status indicators, and any related-record or history areas. This quick orientation prevents users from applying instructions to the wrong record or module.
When the page contains both a list and a record/detail view, use the list for discovery and the detail view for action. Search or filter first, then open the exact record and verify identifying information before making changes.

Role-Specific Guidance

End users work within the channels assigned to them and should not change provider-level configuration unless their role explicitly requires it.
Managers establish communication practices such as response ownership, shared-number usage, appointment handling, and escalation.
Administrators configure supported accounts, numbers, extensions, provider connections, permissions, and organization-level communication settings.

Step-by-Step Instructions

Open Communications.
Use Phone Numbers to review the numbers available to the organization.
Open Phone System for the guided configuration area.
Use Phone Menu & Greetings when configuring caller prompts and menu behavior.
Confirm the intended staff, group, or voicemail destination.
Test the number from an outside phone after saving changes.
For outbound calling, use the browser dialer or click-to-call controls available to your role.

Expected Results

Inbound calls should follow the saved routing and greeting flow, and authorized users should have access to supported outbound calling controls.

Verification Checklist

Confirm the correct OneSuite user is signed in and the expected role/permissions are active.
Confirm the customer, company, invoice, product, message, appointment, employee, or other record shown on screen is the one intended for the task.
After saving or completing the action, refresh or return to the relevant list and verify the new status, history entry, balance, message, appointment, or record appears where expected.
Verify the phone number, user/extension, browser availability, routing mode, and intended destination before testing live call behavior.

Business Workflow

Caller dials business number → OneSuite phone routing answers → Greeting or menu plays → Call reaches staff or voicemail → Activity can continue in OneSuite.

Real-World Business Scenarios

Inbound customer call: identify the destination/user context, answer through the configured workflow, use transfer or routing features only as documented, and confirm the customer is connected before the originating user leaves the call.
Browser calling: verify browser registration/availability and the assigned operating number before placing a live outbound call.
Voicemail follow-up: review the message in the correct user or phone context, contact the customer, and record any required CRM or task follow-up.

Advanced Operational Guidance

For repeatable business work, standardize naming, ownership, tags/statuses, and staff responsibilities before increasing volume. Consistency makes OneSuite search, reporting, history, and handoffs substantially more useful.
When multiple modules participate in the workflow, verify each handoff. Do not assume that completing one screen automatically proves the customer, payment, communication, or reporting outcome is correct elsewhere.
Test phone changes with a controlled call path before relying on them for customers. Calling workflows involve multiple states—ringing, answering, transfer/routing, and hangup—and each should be verified.

Screenshots

Production screenshots appear here only after approved OneSuite captures are attached. Written instructions are complete without screenshots.

Best Practices

Test every menu option after changing a greeting or routing path.
Keep greetings short and clear.
Document the intended routing before making major changes.

Common Mistakes

Changing the greeting but not testing the menu destinations.
Routing a number to a user or destination that is unavailable.
Assuming browser calling is configured just because inbound calling works.

Troubleshooting

Calls do not reach the expected destination: review the number and saved routing.
Menu option behaves incorrectly: test each option and confirm its destination.
Browser dialer cannot call: verify calling setup and the user’s communications access.

Frequently Asked Questions

Can OneSuite use phone menus?: Yes, the current Communications area includes Phone Menu & Greetings.
Can staff call from the browser?: Browser calling controls are available where configured for the user.
Where are phone numbers managed?: Use the Phone Numbers area in Communications.

Next Steps

Continue with the Related Articles section to follow the workflow into the next OneSuite function instead of returning to the homepage after every task.

Last Updated: August 21, 2026
Version: 0.3.2-Phase2B-SHORTCODE-RENDER-RECOVERY
Verified Public Source Baseline: PASS35H66DN RC1 GOLD R63.97
Documentation Revision: Phase 2B Enterprise Detail Expansion