AUDIENCE-AWARE COMMUNICATION
Keep the customer case together and its audiences distinct.
Use internal notes for the team and the supported external lane for customer communication, with recipients and permissions checked before sending.
One case, two different audiences
Internal preparation and external communication keep distinct lanes.
The same customer context does not mean the same audience
A colleague’s pricing question and a customer-facing answer may concern the same quote, but they should not be the same message. Tsumira’s supported record communication distinguishes internal discussion from external communication. The case can remain together while the team still chooses the appropriate audience, channel and recipient for each action. This is a useful boundary to review, not permission to skip checking a message before sending it.
Write team context as internal communication
Internal messages can explain preparation, questions and decisions to people authorized for the record. They are distinct from an external delivery obligation. Use this lane for the discussion needed to prepare a response, and keep sensitive context within its actual audience. A coworker reading the case can then understand the background without assuming that every visible internal comment was also sent to the customer.
- Internal record messages
- Audience separated from external delivery
- Team preparation context
Prepare the external message deliberately
Where the module supports external communication, compose the actual recipient information and customer-facing text through that channel. Supported email fields can distinguish To and Cc, while channel-specific delivery behavior remains part of the configured workflow. Review the recipient and the content together: the right customer record does not make an outdated address or wrong attachment correct. A draft is an opportunity to make that decision before external delivery.
- Supported external communication lane
- Recipient and content review
- Separate draft and send decision
Review who receives the words
Internal discussion is not a delivery obligation to a customer.
Team-only preparation
Read replies and delivery in their proper meaning
Incoming customer communication can return to the relevant supported conversation through configured intake routes. Delivery information distinguishes queued or sent work from later provider outcomes where available. Internal note access, external messaging permission and inbound channel setup are not interchangeable. The record brings the story together, but each operation still depends on its own authority and configuration. Check those facts when a reply or delivery has not appeared as expected.
- Supported inbound conversation context
- Delivery state beside the message
- Operation-specific permission and setup
A concrete workflow
Read the customer case
Inspect the relevant record and existing internal or external context.
Prepare with the team
Use an internal note for questions that should not be customer-facing.
Review the external answer
Check recipient, wording, attachments and channel in the supported compose flow.
Follow the actual outcome
Read delivery information and relevant incoming replies instead of treating an internal comment as a sent answer.
An illustrative working example
Illustrative workflow: clarify a proposal before replying
A colleague asks internally whether a customer’s requested revision changes the scope. The team discusses that question on the record. The account owner then prepares a separate customer-facing message with the intended recipient and reviewed wording. The internal discussion remains team context, while the external message has its own delivery outcome and any supported customer reply can continue the case.
Questions about this topic
Is an internal note a customer email?
No. Internal record discussion and external communication are different audience and delivery actions.
Can every record send external mail?
External communication depends on the module and configured channel. Do not infer that every internal conversation has a customer-mail lane.
Should I still check the recipient?
Yes. Record context does not replace checking the actual destination, wording and attachments before external communication.
Are incoming replies automatic without channel setup?
No. Supported reply intake depends on the configured route and authority. Review that setup when diagnosing a missing response.
Explore connections around this workflow.
Ideas for intended connections. Check the actual availability, permissions and supported data for each app before using a scenario.
