# See what the conversation accomplished. Connect Apple Messages activity to the customer’s task. Understand where conversations start, where customers need help and which journeys lead to a confirmed booking, purchase or resolved request. [Plan your measurement approach](/demo?product=apple-messages) [Read the analytics guide](/docs/guides/apple-messages/analytics) [Explore Apple Messages for Business](/products/apple-messages) Measure the completed task Business Fieldnotes Sent to Apple Gateway accepted Customer responses Observed separately Device read receipt Unavailable Studio visit completed Connect the conversation to the booking record. Origin City studio entry point Business event Attended appointment Repeated reports Deduplicated Illustrative metric relationships. Gateway acceptance, a customer response and a business conversion are different observations. ## Find the step that needs your attention. A studio page brings customers into Messages. They choose a product, share their preferences and select a time. Connect those stages to the recorded appointment so your team can see where the journey progresses and where customers need more help. Use message outcomes, conversation activity, entry-point context and business results together. Compare like-for-like service journeys and investigate the actual requests behind a pattern before changing the experience. ## Measure a conversation on its own terms. Use the observation that answers your question. Channel processing, customer responses and business completion describe different parts of the service, and they should stay recognizable in reporting. ### Keep the origin with the conversation Preserve the product, location, campaign or service entry point that started the request. Group conversations by a meaningful intent before comparing how customers move through the journey. ### Read message status accurately Follow message processing and the outcomes reported by the channel. Apple gateway acceptance is a sent result; it does not establish a device-delivery or read receipt. Keep unobserved stages distinct from confirmed outcomes. ### Connect the business result Join the confirmed order, booking or resolved service request using the relevant references. Take payment amounts and currencies from the financial record, and distinguish a submitted preference from a completed appointment. ### Turn the finding into an improvement Inspect the step that is losing customers: an unclear entry point, an unnecessary field, unavailable times or a handoff without context. Change that part of the experience and compare the relevant cohort again. ## A view that helps different teams act. ### Give service teams useful context Review conversation queues, handoffs and unresolved requests alongside the customer’s original task. A service manager needs to understand the request, its owner and the outcome alongside channel activity. ### Keep comparisons meaningful Use consistent time windows, intent definitions and completion rules. Explain missing observations and keep brands, locations and teams distinguishable when they operate different services or have different availability. ## Analytics questions ### Does sent mean delivered to the customer’s device? Sent records acceptance by Apple’s messaging gateway. Device delivery and reading are separate observations and are not established by that status. ### Can an entry-point report tell us which journey created traffic? Use the supported conversation-origin dimensions and their defined scope. Keep them separate from later message-level metadata. ### Is an invitation sent count an acceptance count? No. Invitation submission and the customer’s response are separate observations. Missing response data does not imply acceptance or decline. ### How should we measure conversion? Join the conversation to the completed business event using the agreed attribution and deduplication rules. A message or conversation count alone is not a sale. ## Build the connected journey - [Analytics guide](/docs/guides/apple-messages/analytics): Follow the practical setup and operational steps. - [Entry points](/products/apple-messages/entry-points): Connect Apple Messages entry points from your website, app and discovery surfaces to relevant routing, customer context and measurable outcomes in Bird. - [API and agent integration](/products/apple-messages/api): Integrate Bird Apple Messages around businesses, native content, replies and customer outcomes, with integration guidance for developers and coding agents. - [Apple Messages resource library](/products/apple-messages/resources): Find setup guides, native experience advice and provider comparisons. ## Measure progress toward the customer’s goal. Choose the conversation and business outcomes your team needs, then confirm which events and connected systems establish each result. ## Related resources - [Integrate an Apple Messages customer journey](/docs/guides/apple-messages/api) (docs) - [What is Apple Messages for Business?](/explained/apple-messages/what-is-apple-messages-for-business) (answer) [Get an implementation brief](/learn/workspace?topic=apple-messages)