AT&T Alliance APIs

The End Customer Lookup serves as the initial step in the Ordering API flow. At this stage, it allows SPs to gather essential data such as Alliance status, existing LOA agreements, and customer specifics like sub-account ID. If no accounts are found, the solution provider (SP) receives a message stating ‘No customer found.’

However, if a customer is found under Alliance only status, the SP can submit an exception request for that specific end-customer to the operations team.   

The Quote API enables creation of Quote ID, Opportunity ID and Quote. These unique identifiers serve as strategic enablers, helping SPs to drive the rest of the Ordering APIs stages.

The Opportunity ID is created when the SP has an opportunity to do business with an end customer. By associating a Quote ID with a particular product configuration that includes Price offer (Access, Port, Installation, Discount Range, Available Promotions), SPs will be able to record their agreed discussions. It ensures alignment between both parties on offerings, rates, promotions, and discounts.  

Other configuration details like product options, access speeds, port speeds, billing preferences, sites and more are recorded to ensure seamless execution. 

The LOA which stands for Letter of Authorization serves as a formal agreement between end customers and Solution Providers (SPs). It maintains mutual consent, ensuring clarity and alignment. The Letter of Authorization (LOA) gives solution providers access to crucial information like credit checks, which are necessary for the next stages in the ordering APIs process. If a valid LOA is not found on file during the end-customer lookup phase, the solution provider must initiate LOA to obtain the customer’s signature before proceeding for the future sale.  

The LOA API is initiated when the Process ID, End Customer details, End Customer Contact details, effective date, and contract term details are sent as a request. Once the LOA document is created and sent to the End Customer for e-signature, an acknowledgment that the e-sign process has been initiated will be sent back as a response to the SP.  

Starting from the LOA  and continuing through the next two phases, which include credit check  and contract creation, there is a feature that allows retrieval of status updates. This feature confirms what action item is pending and what can be done next.

After the successful signing of the Letter of Authorization (LOA) by the end-customer, the Credit Check process becomes relevant. This step allows the Solution Provider (SP) to verify the end-customer’s eligibility for credit approval.

Both the LOA and Credit Check approvals are critical prerequisites before proceeding further. The credit check is performed after process ID validation, LOA verification and AVPS (Address Validation of Postal Service) validation steps are completed. 

The contract creation phase formalizes agreements between the Solution Provider (SP) and the end customer. During this phase, essential details such as customer details, end customer contact details, effective date and contract term are incorporated into the contract.

Prerequisites, including successful e-sign completion of the LOA and credit check approval, must be met before initiating contract creation. Creating the contract at this stage ensures that the terms remain consistent with the agreed-upon quote.

Once the contract is signed, it becomes legally binding, and subsequent changes to the quote are restricted, ensuring stability and clarity throughout the contractual relationship.

This API allows SPs to create new orders and enrich existing orders. The order enrichment process captures details related to fulfillment which includes below aspects .

1. Installation enrichment  involves gathering of additional information about installation contacts, including customer requested start date, customer requested due date, and premise notes.
2. Shipping address enrichment enhances details such as email IDs, addresses, and any relevant notes associated with shipping.
3. Product billing configuration enrichment  includes optional inputs for process IDs, ordered items, suborders, and invoice numbers.
4. The CDG (Customer Defined Group) enrichment  helps SP to group orders together. These enrichments collectively contribute to a smoother order fulfillment process.

In this stage, the Solution provider (SP) submits the order. This action confirms and completes the order created during the order enrichment stage.  

All relevant details, including the main order, sub-orders, and installation specifics, are reviewed and solidified. Once the SP submits the order, they receive an acknowledgment, affirming that the order has been successfully submitted.