Pass design and issuance

PassSlot builds passes for wallet apps on major phones, and a Beam agent issues them on demand. When a customer buys a ticket, joins a loyalty program, or an approved list adds a member, the agent reads the order or record, fills the pass template with the right name, code, and expiry, and sends the download link. Requests missing a required field, or ones that fall outside the issuance rule the customer set, are held for a person, so a wrong or blank pass never lands in someone's wallet by accident.

Push updates to live passes

A pass already saved on a phone can change, and an agent keeps it current. When a balance, seat, gate, or expiry date updates in the source system, the agent reads the new value, applies the approved rule for what to push, and updates the pass so the holder sees it without reinstalling. Changes that would void a pass, drop a large batch at once, or conflict with another pending update are routed to a human first, so no mass push goes out on a bad trigger.

Distribution across platforms

Passes need to reach the right wallet on the right device, and an agent handles delivery. After a pass is issued, the agent reads the recipient's contact and platform, applies your delivery rule, and sends the pass by the channel each person expects. Bounced links, unsupported devices, or recipients missing a valid address are set aside for a person to resolve, so the agent keeps working through the clean list while the edge cases wait for a human decision instead of failing silently.