Native workforce conversation

Keep the shift conversation inside LiftedPOS.

Team Chat gives authenticated employees Direct, Group, public Channel, and Announce conversations with searchable history, unread context, mentions, reactions, editing, pinning, archive and restore, typing, membership controls, and qualified presence.

Run the shift handoff checklist Inspect the seeded demo

Current product proof

Read the audience and record before sending.

Conversation history is tenant-scoped and membership-scoped. Team Chat coordinates work; it does not replace the schedule, time entry, transaction, inventory, customer, or approval record.

LiftedPOS Team Chat with conversation list, messages, members, and composer — Current Team Chat with safe seeded demo data.

DIRECTOne-to-one

A focused conversation between two tenant employees.

GROUPNamed members

A multi-person conversation with explicit membership.

CHANNELPublic tenant subject

A shared subject available according to current membership and access.

ANNOUNCEMember-scoped notice

A recognizable announcement conversation for its configured members.

The shift wire

Carry context through an observable sequence.

Use the right audience, call the responsible person into context, preserve unread state, acknowledge carefully, and keep a durable instruction findable.

DIRECT OR ANNOUNCEChoose the current audience.
Use existing conversation membership that matches the shift responsibility.
MENTIONPoint to the responsible employee.
Use an explicit mention when narrower attention is appropriate.
UNREADPreserve newer activity.
The returning member can distinguish newer work from earlier history.
REACTAcknowledge without overstating it.
A reaction is context, not formal acceptance or task completion.
PIN + FINDKeep durable instruction retrievable.
Pin the reference and use membership-scoped search to return later.

OPERATING WORKFLOW · VERIFIED AGAINST PRODUCT BEHAVIOR

Message tools

Keep useful context observable.

The current interface supports @member, @channel, and @here mentions, reactions, editing, tombstone deletion, archive and restore with actor and time, pinning, cross-channel search, history pagination, member changes, typing, and unread counts.

Mentions and unread

Use a direct message or explicit mention when a person needs narrower attention. Opening a conversation advances that employee's read watermark; the interface does not present a per-recipient delivery certificate.

Reactions and edits

Reactions can acknowledge context without becoming formal acceptance. Editing retains the working conversation; deleted content uses a tombstone treatment.

Pin, archive, restore

Pin durable instructions, archive supported content out of active work, and restore through the product path when authorized.

Search and history

Search and pagination remain bounded by conversation membership. Current history loads the latest working set and can retrieve earlier messages.

Accepted attachments

The server accepts JPEG, PNG, WEBP, GIF, and PDF files up to 10 MB after file validation. Merchant policy still controls what belongs in chat.

Presence and typing

Presence means a live LiftedPOS notification connection, not that someone is clocked in, on premises, reading Team Chat, or available. Typing is only current composition context.

Delivery boundary

Fast internal coordination without an invented guarantee.

Live message delivery uses the LiftedPOS application connection and reconnect behavior, with a 30-second fallback refresh for the conversation list. Direct messages and explicit mentions can create narrower per-user notification records. Normal channel activity should not be treated as a guaranteed alert, SMS, email, mobile push, or proof that a person read and understood the instruction.

Reading requires the messaging module and view_messaging. Conversation membership governs accessible history. Moderation capability does not mean an employee can read every conversation in the tenant.

Shift handoff

Write the exception packet, then return to the source record.

Name the employee, shift or date, observed state, expected state, safe evidence, decision owner, next action, and next check. Announce conversations are member-scoped, and Team Chat is tenant-wide rather than automatically segmented by location, so verify membership during rollout.

Messaging does not change a schedule, clock event, timesheet, approval, transaction, inventory quantity, or customer record.

Use the manager handoff tool

LiftedPOS Team Chat member roster with owner and member controls — Current Team Chat membership view with safe seeded demo data.

Membership and moderation

Make the current audience observable.

Member controls show who belongs to the conversation and which employee owns it. Add and remove operations change future access according to the supported path; archive and restore preserve who acted and when.

Team Chat is tenant-wide and does not automatically create location-specific audiences. Build membership from the merchant's real roster and operating responsibilities.

Team Chat questions

Answers grounded in the current surface.

Which conversation types are available in Team Chat?

The current interface provides Direct, Group, public Channel, and Announce conversations inside the authenticated LiftedPOS tenant.

How does Team Chat call attention to a message?

Team Chat supports unread counts and @member, @channel, and @here mentions. Direct messages and explicit mentions have narrower notification behavior than ordinary channel activity.

Which files can Team Chat accept?

The server accepts JPEG, PNG, WEBP, GIF, and PDF files up to 10 MB after validating the file type.

Does presence mean an employee is working?

No. Presence reflects a live LiftedPOS notification connection; it does not establish that an employee is clocked in, on premises, reading Team Chat, or available.

Does a Team Chat message update a schedule or timesheet?

No. Messaging preserves coordination context while the schedule, clock event, timesheet, and approval remain in their owning LiftedPOS workflows.

How does message history access work?

Reading requires the messaging module and view_messaging. Search, pagination, and history remain bounded by the conversations an employee belongs to.