eBonding Wireless Care Order Tutorial
These steps present examples of subscriber Care Order transactions.
Check Device Details in real time
Check the details of a specific Customer Telephone Number (CTN). We will use the careAccountRequest API.
Example Request Data:
Update Subscriber / Primary User information
We will update a Subscriber’s Primary Address and User Defined Label (UDL). We will be using the careOrderRequest API with ("type": "updateSubscriber").
Example Request Data:
Change a Mobile Number (CTN )
We will request a new mobile number (CTN) to be assigned to a device. The area code is driven by the user's zip code. We will be using the careOrderRequest API with ("type": "changeCTN").
(Note: If you want an area code within a new zip code address, you would first complete an updateSubscriber transaction to change the address so that a new area code would then match the zip code.)
Reassign a Mobile Number (CTN) to another device
You can assign a mobile number (CTN) to a new device if the number is active on the AT&T network. First, use the careAccountRequest call (step 1 above) to ensure the existing CTN has compatible Rate Plans and Features with the new device.
If the CTN and new device are compatible, then you will use the careOrderRequest API with ("type": "updateDevice") to assign the CTN to the new device.
If there is a compatibility issue, please use the changeRatePlanWithDeviceUpdate or updateFeaturesWithDeviceUpdate transactions first.
Example Request Data:
Swap a Physical SIM from one device to another
We will move a subscriber’s SIM to a different device. We will use the careOrderRequest API with ("type": "activateSim").
Example Request Data:
Add and remove features
We will update a subscriber's mobile features using the careOrderRequest API with ("type": "updateFeatures").
You can add and remove multiple features in the same request. You can set an effective date and expiration date to schedule feature changes (coordinate with international travel for instance) or backdate features (within the same bill cycle).
Example Request Data:
Change a Rate Plan
The change rate plan API allows clients to change the current plan associated with a device. By using the ‘add’ function with the new rate plan the existing rate plan is automatically replaced (no need to remove it). If you include a rate plan change, you can also add and remove features in the same transaction.
In this step we change a susbscriber’s rate plan. To do this, we will be using the careOrderRequest endpoint with type changeRatePlan.
Example Request Data:
Suspend Service
The Suspend Service API is used to suspend service of a line for extended vacation, if a device is lost or if the device is stolen. In this step, we will suspend a subscriber’s line service because the device was lost. To do this, we will be using the careOrderRequest endpoint with type suspendService.
Example Request Data:
Reinstate Service
In this step, we will reinstate service to a suspended Line. To do this, we will be using the careOrderRequest endpoint with type reinstateService.
Example Request Data:
Cancel Service
Unlike suspending service, the Cancel Service API is used to permanently terminate or disconnect a line. In this step, we will be using the careOrderRequest endpoint with type cancelService.
Example Request Data:
Resume from Cancel
AT&T Mobility eBonding supports resuming a canceled line. Clients have thirty days after a cancel request has been issued to Resume service. In this step we will be using we will be using the careOrderRequest endpoint with type resumeService to resume service to a canceled line.