# Visitor order, ticket, and service status tracking

Source: https://frosvo.com/docs/visitor-order-and-service-tracking
Updated: 2026-11-08

Let website visitors look up real-time order delivery, support ticket progress, or service status directly from the chat widget home screen.

One of the most common questions support teams receive is *"Where is my order?"* or *"What is the status of my ticket?"*. Enabling visitor tracking puts a self-service status lookup card directly on the website chat widget home screen so customers get an instant answer before starting a new conversation, complementing the in-chat [customer progress card](/docs/customer-progress-card).

## Enabling tracking on a website

Workspace owners and administrators with website permissions can enable tracking per website:

1. Open **Settings → Websites** and click your website to open its widget settings.
2. Tick **Show order, ticket, and service status lookup on the widget home screen** under **Order & ticket tracking**.
3. Save your settings. The widget home screen will immediately display the **Track an order, ticket, or service** card above your greeting and help search.

## How visitors look up orders, tickets, and services

The visitor signs in through your site's verified identity integration, opens the tracking card, chooses **Order**, **Ticket**, **Invoice** or **Service**, and enters an exact reference. Frosvo uses the verified session identity; the card does not accept a replacement email as proof of ownership.

- External lookups use the corresponding `order.lookup`, `ticket.status`, `invoice.lookup` or `service.status` scope through the [customer-owned integration gateway](/docs/customer-owned-integration-gateway). Enable only the scopes your adapter supports.
- Hosting pilots can configure the supplied [read-only WHMCS adapter](/docs/whmcs-visitor-tracking), with separate credentials, namespaced verified client identity and exact object ownership checks. Verify it against your installation before customer use.
- Kpanel sites can use the supplied [Kpanel tracking adapter](/docs/kpanel-visitor-tracking) on the panel host with a separate column-restricted database reader and verified Kpanel account identity.
- Local payment matches are restricted to the verified visitor and website. Conversation suffixes and another customer's email cannot unlock records; see [verified tracking and payment status](/docs/verified-tracking-and-payment-status) for security details.

## Step-by-step milestones and carrier links

When a match is found, the widget shows its title, status, next-step guidance, source and lookup time. It shows the source update time only when the source supplied one; otherwise it explicitly reports that time as unavailable. Optional customer-safe details links must pass HTTPS and credential checks. Carrier milestones and delivery estimates are not inferred from a status string.

Unknown statuses remain unknown. A paid invoice is not proof that a service is provisioned. If the source is unavailable, the card reports an unavailable lookup rather than claiming the reference does not exist. Signing out or changing identity clears previous results and discards outstanding responses.

The server also checks the verified session and website permissions again after a source lookup finishes. Signing out, blocking the visitor, changing the verified account, disabling tracking or suspending the website while a lookup is running prevents that response from releasing customer details. Sign in again before retrying after an access-change message.

## Common questions

### How does Frosvo protect customer order lookups from unauthorized guessing?

Lookups require a verified visitor session and an exact reference. The connected source must authorize the verified account against that object. Typing an email address does not establish identity. Requests are rate-limited.

### Where does the widget fetch live order and service status from?

Frosvo can resolve that visitor's local payment requests and query configured customer gateways or account connectors. External ticket, order and service data requires a source integration.
