Keep this link private. Anyone with it can view this order, change an available appointment, cancel an active service, or message its assigned provider.
Open your order in the same browser you used to book. Your secure booking session protects your payment status and service details; an order number alone cannot unlock them.
No login requiredProtected by your secure booking sessionRequests stay in review until confirmedCustomer-safe status updates
Manage your service
Need to change something?
Verify your order through the lookup first, then submit your request for review. Your order stays unchanged until confirmed. Contact support
Cal
Schedule review Request Reschedule
Send a preferred window for team review. Your appointment stays unchanged until confirmed.
Submitted reschedule requests are reviewed before the schedule changes.
Preview hooks are declared before live order data is connected.
These contracts identify the future AI.OS boundary for lookup, service-change requests, customer/provider chat review, and audit evidence. They are metadata only today.
Secure lookup POST access check before private details/api/order-lookup
Live order reads stay disabled until CustomerOrderAccess proof passes.
Request staging Reschedule and cancellation requests enter review first/api/customer-order-action
No ServiceOrders schedule or cancellation mutation happens from this route.
Chat preview Customer notes stage as message requestsServiceOrderMessages
No customer/provider chat delivery or provider contact unlock is sent.
Audit boundary Backend-owned evidence before visible state changesSystemAuditEvents
The public route may reference review state, but it cannot append audit payloads.
Lifecycle launch gate
CustomerOrderAccess and action queues must pass proof before live order data is connected.
Tracking can show customer-safe preview receipts, but provider contact, queue internals, payout details, messages, uploads, and order mutations stay blocked.
blocked until access proof Customer tracking and action readiness/api/order-lookup
Order lookup explains the POST-only access boundary before private details are connected.
GIA-TEST only GIA-TEST-*/api/test-data-manager
GIA-TEST-* tracking and action proof must hide provider payout, queue internals, private contacts, and audit payloads.
Blocked live effects 5 customer-facing effectsNo provider contact unlock
no live private order read no ServiceOrders mutation no customer/provider chat, SMS, or email send
Review-first actions No direct order changes/api/customer-order-action
Customer action queues must stage requests before any ServiceOrders status, schedule, message, file, or audit write.
Disabled-state receipts
Preview receipts are explicit about what stays off.
Customer receipts confirm what was submitted and what the team will review next.
Private order details stay limited to the customer who can verify the order.
Reschedule, cancel, message, and media requests are reviewed before provider contact details are shared.
Owner-approved future hooks
Promotion stays blocked until these hooks have proof.
CustomerOrderAccess reader after GIA-TEST lookup and access-denied proof
ServiceOrderStatusEvents customer-visible filter after timeline proof
Request queues and SystemAuditEvents after review receipt proof
Status updates
Use the secure lookup form to review customer-safe timeline updates, visible service notes, and verified line items.Review tracking
Message request
Use the message request card to send access notes, gate codes, missing-part questions, or project context for review.Open message request
Talk to the team
When you need a broader support handoff, use the support page and our team will help route the request.Contact support
Service support
Order tracking keeps customers informed without requiring an account.
Customers can check status without creating a member account.
Service details stay focused on the order, schedule, visible status, add-ons, and support options.
Reschedule, cancellation, message, and media requests are received for review before anything changes.
Provider details appear only when the service is ready for that information to be shown.
The support path stays simple for customers while the operations team handles the details behind the scenes.
