Bulk SMS Global White-Label Sub-Account Provisioning (Onboarding)

Bulk SMS Global White-Label Sub-Account Provisioning (Onboarding)

1. 01

   Register the client's sender ID in the Bulk SMS Global dashboard, including the Arabic sender ID variant when the client targets GCC recipients.

   Sender ID approval is the longest lead time in onboarding. Submit it before any other configuration so carrier approval runs in parallel with list work.

2. 02

   Create a sub-account under the agency's white-label reseller domain and map the client's billing to the agency's own invoice terms.

   The reseller program allows rebranding the interface with a custom domain and agency billing, so the client never sees Bulk SMS Global branding. Confirm the sub-account inherits the agency's negotiated per-message rate rather than list rate.

3. 03

   Import the client's contact list and apply segmentation tags for opt-in status, geography, and channel preference.

   Segment before the first send. A single unsegmented blast across SMS and WhatsApp burns sender reputation and makes delivery report analysis useless for the monthly retainer review.

4. 04

   Connect the client's CRM (Salesforce, HubSpot, or Zoho) so lead capture writes back to the client's pipeline instead of sitting in the messaging dashboard.

   Verify the field mapping for lead source and opt-in timestamp. Without write-back, the agency cannot show attribution in the monthly report and the retainer becomes a cost line the client questions.

5. 05

   Build the first automated sequence: one welcome SMS and one promotional SMS, with the WhatsApp Business API template submitted for approval.

   WhatsApp template approval is separate from sender ID approval. Submit both on day one of onboarding to avoid a stalled launch.

6. 06

   Run a test send to internal numbers and confirm OTP delivery lands under 3 seconds and delivery reports (DLR) return accurate status.

   Test on the same route the client will use in production. A test on a different route proves nothing about live deliverability.

7. 07

   Hand the client a one-page operating note covering opt-in keyword, escalation contact, and monthly delivery report schedule.

   This is the handoff artifact. It sets the boundary between what the agency operates and what the client owns, which protects the retainer when the client asks for ad hoc sends.