1. Overview

An adapter can be divided into two parts -

• Inbound - Conversion of incoming message object to XMessage
• Outbound - Conversion of outgoing XMessage to message object

2. Building an Adapter

The process of building an adapter can be divided into two broad steps -

2.1. Generic Channel + Provider Implementation - To be done once for each unique combination of communication channel and service provider

2.2. Specific Adapter Implementation - To be done for each specific business account/phone number. Please note, Each generic implementation can have multiple specific implementations.

2.0 Implementing Backend

2.1. Generic Channel + Provider Implementation

Building Block View

Step 1 - Getting the APIs ready The first step is to setup notifications such that UCI is able to receive incoming messages when a user replies, reads or when a message is delivered to users. These API could be similar to what Netcore has. Then if the server queues all the sent requests and send them async later, there needs to be a sent notification as well.