Use the dedicated messaging view
Read the conversation list, search a customer and open the thread in the iMessage workspace. The familiar layout makes everyday replies easy to follow.
Give customers a familiar way to stay in touch. Handle iMessage conversations in a dedicated messaging view or open the same thread in your shared Inbox, with your team and customer context nearby.
iMessage is a separate product. Line activation, allowances and messaging policies apply.A customer looking at a desk today might ask about a showroom visit tomorrow. Their next message should continue the discussion, wherever the team is working.
Read the conversation list, search a customer and open the thread in the iMessage workspace. The familiar layout makes everyday replies easy to follow.
Open the same conversation in Inbox when you need the wider customer record. The dedicated view reuses the conversation data instead of creating a separate copy of the support request.
The business’s messaging line belongs in a team workflow. Handle assignment and customer context through the Inbox so support does not depend on one person’s personal device.
Use eligible linked history to understand what happened before the customer reached out again. Keep private information behind the appropriate checks.
Related conversations can show what a teammate promised and whether an issue remains open. Confirm the link between records rather than assuming similar contact details identify the same person.
Supported connected sources can help your team understand products and orders. Customer-facing disclosure still needs the identity checks required for the information being requested.
Supported iMessage task-agent answers can use the configured business knowledge and guidance. Test the agent on common questions and handoff cases before activation.
Make it easy to keep the conversation going without turning support into a collection of personal phone threads.
Find a customer by name, number or message preview in the dedicated view. Search makes returning to an earlier discussion straightforward.
The sending line and its status matter. Select the configured line for a new conversation and keep an eye on the available allowance.
Open the thread in your shared workspace to reach assignment, customer history and the rest of your support workflow.
Line connection and policy checks can prevent a message from sending. Review the surfaced error rather than assuming an accepted action means the customer received it.
Use supported AI behavior with published knowledge and site scope. Keep factual product answers separate from private customer lookups.
New conversations and ongoing replies can have different allowances and restrictions. Use the line’s current policy and availability rather than treating it as an unlimited broadcast channel.
Use the iMessage setup in your workspace and review the current price, activation process and allowance. A purchased line may still need activation before use.
Send an authorized test message and reply from the receiving device. Confirm the thread appears in the iMessage view and the shared Inbox.
Decide who owns incoming requests and whether a task agent should answer. Review customer-history linking and handoff before using the channel broadly.
iMessage is a separate product. Line activation, allowances and messaging policies apply.