SMS Messaging and Shared Number Privacy

Overview

OneSuite SMS provides business text messaging from numbers available to the user. In shared-number environments, conversation ownership and privacy are critical: a conversation initiated or assigned for one user should not become visible to unrelated users simply because the underlying business number is shared. Current production work also supports administrator management of which operating number a user can use as additional numbers are added. This guide explains the user workflow, shared-number expectations, and verification practices that protect customer conversation context.

Business Value and Typical Use Cases

Send and receive customer text messages from an authorized OneSuite number.
Operate from a shared business number while preserving user conversation separation.
Assign operating numbers to users as the organization adds more messaging numbers.
Follow up with a CRM customer using the appropriate text conversation.

Before You Begin

Confirm the user has SMS access.
Confirm the correct operating number is available/assigned.
Search for the customer and existing conversation before creating a new thread.
Review privacy expectations before using a shared number.

Prerequisites and Permissions

SMS-enabled OneSuite environment.
Authorized user.
Available or assigned business messaging number.
Customer mobile number.

Concepts

A phone number can be an organization resource while the conversation context is still user-specific. Number sharing should not be interpreted as permission for every user to read every conversation.

Administrators determine which numbers users are allowed to operate from where current controls are available.

Customer identity and assigned contact information should be accurate so users can distinguish the correct text conversation from a similarly named or shared-number interaction.

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 SMS/Text Messaging from OneSuite Communications.
Confirm the operating number shown for the user is the one intended for the message.
Search existing conversations by customer identity or number before starting a new thread.
Open the correct conversation and review recent messages.
Compose and send the text. Confirm the outbound message appears in the conversation.
When a reply arrives, verify it appears in the same user/customer thread and is not exposed in another unrelated user’s panel.
If the organization uses multiple business numbers, have an administrator review number assignment so each user operates only from the numbers intended for that role.

Expected Results

Messages should remain associated with the correct customer conversation, the user should operate from an authorized number, and shared-number usage should preserve the intended user-level conversation visibility.

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.

Business Workflow

Verify user/number assignment → locate customer → open existing conversation → send/receive SMS → verify thread ownership/privacy → record or follow up in CRM as required.

Real-World Business Scenarios

No additional role-specific guidance is required for this topic.

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.

Screenshots

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

Best Practices

Search before starting another thread.
Use the same approved operating number for the customer relationship unless the business process requires a change.
Have administrators review assignments whenever new numbers or users are added.
Keep receipts, internal notices, or other system messages separated according to the current production visibility rules.

Common Mistakes

Assuming every user of a shared number should see every conversation.
Sending from the wrong operating number.
Creating duplicate customer conversations.
Using SMS for internal staff discussion that belongs in Team Chat.

Troubleshooting

Symptom: another user can see a conversation they should not see. Cause: assignment/ownership or visibility logic may be incorrect. Solution: stop sharing sensitive content, document the affected users and number, and have an administrator review number assignment and the current SMS privacy behavior. Verification: retest with separate users and confirm each sees only the intended conversations.
Symptom: the expected number is unavailable. Cause: the user may not be assigned that operating number. Solution: have an administrator review the user-number assignment. Verification: sign back in or reload the SMS view and confirm the number is available.
Symptom: replies appear in an unexpected thread. Cause: duplicate records or inconsistent customer/number context may exist. Solution: search the customer and phone number, identify duplicates, and use the authoritative thread.

Frequently Asked Questions

Can multiple users operate from one business SMS number?: Shared-number operation is supported in the current workflow, but conversation visibility should still respect user ownership/privacy rules.
Can an administrator assign which number I use?: Current development includes administrator assignment of operating numbers as multiple numbers are added.
Is SMS the same as Team Chat?: No. SMS is customer-facing business texting; Team Chat is internal staff messaging.

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