Powerlily’s conversation system keeps internal discussion, customer communication, workflow updates, and project history connected. Teams can work in internal, customer, workflow, direct, and group threads without scattering important context across unrelated inboxes.
Choose the right conversation
Before sending a message, confirm who should see it and which record should retain it.
- Customer conversations are for communication the customer is meant to receive or see.
- Internal conversations keep staff discussion private from the customer.
- Workflow or project conversations keep operational context attached to the work.
- Direct conversations are for one-to-one staff communication.
- Group conversations coordinate a defined set of participants.
Do not place private pricing, HR, legal, or internal assessment notes in a customer-visible thread.
Start or continue a thread
Open the relevant client, lead, quote, project, workflow, or conversation workspace. Continue an existing thread when the subject belongs to the same work. Start a new conversation when the audience or purpose is materially different.
Use a clear subject or opening message so someone joining later can understand the issue without reconstructing it from scattered comments.
Mention teammates
Use mentions to draw a teammate’s attention to a specific message. Mention only the people who need to respond or act; broad mentions create notification noise and make genuinely urgent requests easier to miss.
A mention does not replace assignment. Create a task or event when the work needs an owner, due date, reminder, or completion state.
Reply and keep context together
Reply in the relevant thread instead of starting a disconnected message. Replies preserve the decision trail and make it easier to understand what a file, question, or approval refers to.
Forward a message when another conversation needs the information, but add enough context to explain why it matters to the new audience.
Use reactions, pins, and saved messages
Use reactions for quick acknowledgement when a written reply adds no value. Pin important instructions, decisions, or reference messages that the whole conversation may need again. Save messages privately when you want to return to them without changing what other participants see.
Work with drafts and scheduled messages
Powerlily can preserve message drafts so unfinished work is not lost. Review the audience and attached record before sending a resumed draft.
Schedule a message when it should arrive at a deliberate time. Check the company time zone, recipient, content, and project state before scheduling. Cancel or revise scheduled communication if the situation changes.
Send customer SMS
Supported customer actions can be delivered by SMS, including proposal links, signature requests, secure invoice links, appointment confirmations, reminders, reschedules, cancellations, and crew-on-the-way updates.
Keep text messages concise and use the secure Powerlily link for private project actions or documents. Confirm the customer’s phone number and communication consent before relying on SMS.
Keep the communication history on the record
Use the conversation attached to the relevant customer or project whenever possible. This gives sales, office, field, and service teams one history instead of private inbox fragments.
When a lead becomes a quote or project, preserve the acquisition and communication history so later teams understand what was promised and why decisions were made.
Control participants and visibility
Add participants who need ongoing access and remove people who should no longer be part of a group thread. Visibility still follows company roles, branches, record scope, and module permissions.
Before sharing sensitive information, verify both the conversation audience and the underlying record access. A convenient thread is not permission to expose information outside the participant’s role.
Use notifications intentionally
Conversation activity can generate in-app, browser, mobile, or other supported notifications. Use presence and read context to decide whether a normal message is sufficient or whether the issue needs a task, phone call, or operational escalation.
Communication practices that scale
- Keep one topic in one thread when practical.
- State the decision or requested action clearly.
- Mention the responsible person, not the entire company.
- Use tasks for accountable work and conversations for discussion.
- Attach files to the customer or project that owns them.
- Use customer-visible threads only for appropriate external communication.
- Correct outdated information instead of allowing conflicting instructions to remain unexplained.
Final review checklist
- The conversation is attached to the correct record.
- The participant list matches the intended audience.
- Internal information is not in a customer-visible thread.
- The message clearly states the decision, question, or requested action.
- Mentions are limited to relevant teammates.
- Tasks or events exist when accountability or timing is required.
- Customer contact details and SMS consent are current.
- Scheduled messages still make sense before they send.
- Secure links are used for private customer actions and documents.
