Ask at the right point.
Choose the minimum information needed for one task. Before collecting personal information, include Apple’s required clarifying question and the appropriate Quick Reply.
Ask what you need. Keep every answer.
Collect a focused service request inside the conversation. Preserve the answers and their context for the team or application that handles the task.
A short intake.
A request ready to review.
Change the item or location, then review the same answers in the service application.
Service details · 1 of 1
Let’s take a look.
Tell us which item needs attention. Our team will review your request.
Local form illustration · no request is sentExample request · Ready for review
Keep the answers together.
- Item
- Everyday vase
- Location
- Amsterdam studio
- Reported issue
- The rim was chipped in transit.
- Context
- Original conversation + request
Submitting details starts an assessment. It does not approve a replacement or refund.
Service team reviewKeep the form focused.
Validate the result.
Collect the information needed to complete a request.
Preserve meaningful answers.
Give pages and choices stable references. Keep an unanswered optional question distinct from an explicit answer. Let customers revise a selection without repeating unrelated details.
Confirm the business action separately.
Bind the returned answers to the business, conversation and original request. Validate them in the receiving system, then explain whether the task completed or needs another step.
Scale without
losing control.
Organize teams in workspaces, control API access, and trace changes through audit logs.
HarborOrganizationWorkspacesProductionSandbox
Delivery agent
API key · Customer operations teamALAlex Lee AdminPermissions updated
Audit log
Production- Workspace
- Production
- Resource
- Delivery agent
- Read accessRead & write
Team Customer operationsActor role AdminOutcome SucceededTime 22 Sep, 09:42:18 UTC
Succeeded