Product · Pro
Confirmation without chasing.
Assign each recipient to the teammate who owns the relationship. Alerts fire when something delivers or fails — even if nobody opens a tab. Messages keep store and gift team in one thread.
14-day Pro trial. No charge until it ends.
Exception loop
From alert to owner to resolved thread.
Work a realistic address exception across the gift team and store without screenshot chains or lost context.Address needs review
OpenHow assign, alerts, and tickets work
Assign recipients
Each row belongs to the teammate who owns the relationship. Needs a gift-team seat.
Scoped alerts
Server-side alerts on delivery and failure for assigned rows — not a global noise firehose of every carrier scan.
Messages
The gift team raises an issue; the store works it in one shared thread. Starter escalates by mailto.
Assign to the relationship ownerPro
Teammates see the recipients they own. Alert value depends on assign — and on the store running Pro.
Alerts that do not wait for a clickPro
Delivery and failure fire for assigned rows. Optional Slack outbound on Pro. Confirmation never depends on the recipient opening a link.
Exceptions still need a humanPro
When an address cannot be validated, the assigned owner is alerted to fix it — often by contacting that person — before the recipient has to chase the shop. The desk surfaces the problem; it does not invent a silent fix.
FAQ
Scoped alerts, full in-app tickets, Slack outbound, and the assign-driven alert loop need Pro (or trial). Starter desks still create, share, and track; exceptions escalate by mailto.
No. Stores pay for campaign capacity. Gift teams pay for seats separately — two free, then $9 each.
No. Confirmation never depends on the recipient. Alerts fire for the gift team without anyone opening a recipient link. Resolving a bad address may still require the assigned owner to contact that person.
Delivery and exceptions that need a human — not every scan. Exactly one owner per recipient row so the signal stays trustworthy.