Starting a conversation

To start a conversation, messages must be sent from Sender IDs that are capable of receiving traffic. We provide two options for this:

Owned sender IDs

We can buy and reserve inbound-compatible sender IDs for you to send traffic out from. These can receive traffic without needing an initial message to be sent.

Contact us at support@cymba.co.uk to enquire.

Shared sender IDs

Messaging Plus provides a pool of shared sender IDs through which you can start conversations.

You cannot choose which shared sender ID to send from. Once you start a conversation between a shared sender ID and a mobile number, that shared sender ID is locked to the account and mobile number. No other account will be assigned your shared sender ID to contact that mobile number.

Future shared sender ID messages to that mobile number will go through the previously assigned shared sender ID.

Sending via Owned SID

To send via an Owned sender ID, simply specify that as the sender ID in the request.

In this example, I'm using my owned sender ID 441234567890

---

POST https://mplus.instagiv.com/message

{
    "messages": [
        {
            "from": {
                "type": "custom",
                "value": "441234567890"
            },
            "to": "441111111111",
            "body": "This is a test message!"
        }
    ]
}

---

response body

{
    "messages": [
        {
            "to": "441111111111",
            "body": "This is a test message!",
            "from": {
                "type": "custom",
                "value": "441234567890"
            },
            "batchUuid": "f99b2962-4a0a-41a4-a84b-4d37c8c92ad1",
            "messageUuid": "473107f1-ae0f-4a8b-834f-3dd36a764c5b",
            "scheduled": false
        },
    ]
}

Ownership

Attempting to send from a sender ID not owned by an account is restricted, and will return an error

Sending via Shared SID

To send via Shared sender ID, specify the shared type in your request

---

POST https://mplus.instagiv.com/message

{
    "messages": [
        {
            "from": {
                "type": "shared"
            },
            "to": "441111111111",
            "body": "This is a test message!"
        }
    ]
}

---

response body

{
    "messages": [
        {
            "to": "441111111111",
            "body": "This is a test message!",
            "from": {
                "type": "shared",
                "value": "448888888888"
            },
            "batchUuid": "ae9293fc-8af6-4dcc-87c9-c73a95b8ad49",
            "messageUuid": "93eb613f-453f-4062-9bc5-763c05b5a65b",
            "scheduled": false
        },
    ]
}

We return the shared sender ID that got assigned in the response, so you know what sender ID you're sending from

---

Maintaining the conversation

As mentioned earlier, you cannot specify a shared sender ID in your outbound request.

In order to continue a conversation with somebody who you initially contacted via shared sender ID, simply specify shared again in your request.

Messaging Plus will at your accounts messaging history to find the last message sent from a shared sender ID to that individual. If it successfully finds one, it will re-assign that same shared sender ID.