Top-Up Order Fulfillment

A Beam agent reads an incoming top-up request, whether it arrives from a support ticket, a customer account, or a scheduled recharge list, and checks the mobile number, country, and carrier against DingConnect's supported list. Where a customer-approved rule allows it, the agent submits the top-up through DingConnect and updates the order record once a confirmation comes back. A number that does not match a known carrier, a denomination outside the usual range, or a repeated failure on the same number gets routed to a human instead of being retried automatically.

Balance and Denomination Lookup

A Beam agent checks the denominations and pricing DingConnect makes available for a given carrier and country before a top-up is placed, comparing them against what a customer's order actually requested. Where the figures line up, the agent proceeds with the order and notes the confirmed amount in the order record. Where a requested denomination is not offered, pricing looks different from a prior order for the same carrier, or the carrier itself is unavailable, the agent holds the order and routes it to a human rather than substituting a different amount.

Failed Transaction Handling

A Beam agent reads the status DingConnect returns for each submitted top-up and separates confirmed transactions from failed or pending ones. For a failure with a clear, customer-approved reason, such as an unsupported number format, the agent updates the order as failed and notifies the requester. A failure with an unclear cause, a delayed confirmation past the expected window, or repeated failures for the same customer are held back from that automatic notice and routed to a human to look into before the order is closed out.