Create useful Apple Messages entry points

Connect discovery, website and app entry points to the right business, service task and conversation context.

You need the correct Apple business identity, its approved service experience and access to the website, app or business property where the entry point will appear.

Place the entry where a question naturally arises: a location, product, order or service page. Explain what the team can help with and use an appropriate channel entry experience.

Use Apple’s entry-point URL format for the business. For a studio visit, the URL can carry a service intent, a receiving group and a draft message:

https://bcrw.apple.com/urn:biz:BUSINESS_ID?biz-intent-id=studio_visit&biz-group-id=customer_care&body=I%20would%20like%20to%20book%20a%20visit

Replace BUSINESS_ID with the identifier Apple issued to your business. Configure biz-intent-id and biz-group-id to match the receiving workflow. The body value prefills the customer’s composer; the customer still sends the first message. Public URLs must not contain credentials or protected account details.

Map the starting context to the correct service flow or team. Prepare the welcome to acknowledge the likely task without assuming the customer’s account identity.

Open the entry point on representative supported devices. Send the first message, inspect the resulting business and conversation context, then finish the task. Test a device or environment that needs another contact path.

Record conversation origin consistently and join it to the completed service event. Keep website clicks, conversation starts and business outcomes distinct.

Test a product page and a location page as separate entry points. Open each link, inspect the intended business in Messages and send the suggested message. Verify the receiving conversation’s service context and destination team. Repeat the test without sending: a composer open must remain distinct from an inbound customer message.

If an entry point opens the wrong conversation, verify the business identifier and route context. If a click produces no conversation, investigate device support and the actual customer path before counting it as a conversation start.