Open and context
The incident opens from the order (or support creates it) and pulls all the context: items, provider, shipment and status. Zero copy-paste.
When a gift doesn’t arrive or arrives wrong, your team resolves it from a single thread linked to the order, with the real provider masked and your brand always facing the recipient.

Already gifting with TPP
A case arrives from the recipient, support or tracking itself, routes to whoever can resolve it (provider, courier, customs) and returns to a single closed thread.
The recipient always talks to your brand, even while you coordinate with the provider or courier behind the scenes. The veil holds, even mid-incident.
Hover to lift the veil
Reshipments, refunds and claims across 20+ countries, coordinated from one panel in your language.
Incidents, shipments and orders — the full case context, with no tool-hopping.

Thread, linked order, priority and owner — everything support needs to resolve on the first try.

Every incident update reaches the recipient as an email under your brand, never the provider’s.
Behind "one thread" sits a case linked to the order, routed to an owner and audited end to end. Here is what happens under the hood.
The incident opens from the order (or support creates it) and pulls all the context: items, provider, shipment and status. Zero copy-paste.
It is assigned to whoever can resolve it — provider, courier or your team — with priority and SLA. Reshipments and refunds fire from the same thread.
On close, everything is logged and linked back to the order and the charge, ready for finance and compliance.
From the order, via API, or support creates it. It is always linked to the order and its shipment.
Everything the gifting engine does, one surface at a time.
A 30-minute demo is enough to see support resolving from one panel, under your brand.