Skip to main content

​
Configure messaging delivery

The provider marketplace is country-aware and allows one active provider per channel. Credential fields are generated from the current provider catalog and saved values feed the live sender implementations.

​
Current SMS catalog

The provider catalog can be filtered by country. A provider in the code catalog may not appear for every account/region. NextSMS and KiboNet both serve Tanzania only: an account whose country is set to anything else does not see them, and KiboNet also stays hidden until the account has set a country at all. NextSMS and KiboNet both report their prepaid credit and their own delivery status. The provider page shows the remaining credit read-only (KiboNet as an SMS count), and Centipid polls the vendor for each message rather than marking it delivered at send time — a message stays pending in the log until the vendor confirms it.

​
Current WhatsApp catalog

Notiva, Apiwap, Infobip, and Twilio. See WhatsApp for exact fields.

​
Connect a provider

  1. Complete the provider’s merchant/business onboarding.
  2. Open the matching channel in Settings.
  3. Select the provider.
  4. Enter each required field; conditional Host Pinnacle fields change with authentication method.
  5. Save to make it active.
  6. Send a controlled test and verify the provider dashboard/log.

​
Sender IDs

A sender ID is the name shown as the SMS sender where networks support alphanumeric identity. Approval is provider/country specific. A configured text value is not proof that carriers have approved it. Use Settings → Sender ID where available to follow the request/payment/status process. Do not advertise a new sender identity until approval and a live-network test are complete.

​
Low-balance alerts

Centipid SMS can show current balance, top up, enable a low-balance threshold, and notify one or more phone numbers. A top-up request can have its own payment-status lifecycle; verify balance changed before sending a large campaign.

​
Switching providers

Resolve queued/failed messages, record the old provider configuration owner, connect/test the new provider, verify sender identity, then enable automated templates. Old failed records should not be bulk-resubmitted through a new provider without reviewing content, recipients, and duplication risk.