Team Chat and Direct Messaging

Overview

Team Chat gives OneSuite users an internal business messaging experience for group conversations and person-to-person communication. Current production work includes Messenger-style conversation presentation, group management, direct messaging controls, files and picture sharing, emoji and attachment tools, popup chat behavior, and user-avatar support where profile imagery is available. The purpose of Team Chat is to keep operational conversation close to the work employees perform in OneSuite without turning customer SMS or email into an internal staff channel.

Business Value and Typical Use Cases

Coordinate a sales or service team without leaving OneSuite.
Send a direct internal message to another permitted user.
Share an image or file needed for internal work.
Maintain persistent group conversations for departments or projects.

Before You Begin

Confirm Team Chat is available to the user.
Confirm the intended recipient or group is permitted.
Do not use Team Chat to expose customer or payment information beyond what is appropriate for the internal audience.

Prerequisites and Permissions

Active OneSuite user account.
Team Chat access.
A permitted user or group conversation.

Concepts

Team Chat is internal staff communication and should be distinguished from customer SMS, email, and phone conversations.

Group access and direct-user interaction can be subject to administrator controls. Users should not assume that every staff member can see or join every conversation.

Main chat and popup chat are designed to provide equivalent core messaging tools so users can continue a conversation while working elsewhere in OneSuite.

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 Team Chat from the OneSuite area available to your role.
Select an existing group or direct conversation, or create/manage a group if your permissions allow it.
Review the conversation history before responding so you understand the current context.
Enter the message in the composer. Use emoji, file, or picture tools when the conversation requires supporting material.
Send the message and confirm it appears in the conversation. If popup chat is enabled, verify the same conversation remains synchronized between the main chat area and the popup experience.
For group administration, add or remove permitted users, choose the available group controls, and save. Reopen the group to verify the membership change persisted.

Expected Results

The message should appear in the intended internal conversation, available participants should see it according to their access, and supported attachments or images should remain associated with that chat.

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

Open Team Chat → choose group/person → review context → compose → attach files/images if needed → send → verify delivery in the conversation → follow up or archive/manage the group as permitted.

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

Use descriptive group names.
Keep customer-facing communication in the appropriate customer channel.
Use direct messages for private internal coordination and groups for work that should remain visible to the team.
Review group membership when staff roles change.

Common Mistakes

Confusing Team Chat with customer SMS.
Creating duplicate groups for the same team.
Sharing sensitive information with a broader group than necessary.
Assuming group membership saved without reopening and verifying it.

Troubleshooting

Symptom: a user is not available for direct messaging. Cause: administrator interaction controls or user access may prevent it. Solution: ask an administrator to review Team Chat permissions. Verification: reopen the composer and confirm the user can be selected.
Symptom: a picture/file tool is not visible. Cause: the interface may not be fully loaded or the user may be in a different composer. Solution: reopen the conversation and confirm the current main/popup chat tools. Verification: attach an approved test file and confirm it appears.
Symptom: group changes do not appear. Cause: the group may not have been saved or the view may be stale. Solution: save the group, close it, reopen it, and verify membership.

Frequently Asked Questions

Is Team Chat the same as SMS?: No. Team Chat is internal OneSuite staff communication; SMS is a customer/business phone-number channel.
Can I send pictures?: Current Team Chat work includes picture and file sharing in the supported chat interface.
Can administrators control who can message whom?: Current administration includes controls intended to allow or block direct interactions.

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