Plan availability: Pro or Scale. On Pro, event/shop-alert texts use purchased credits, while transactional order texts and customer sign-in codes are included and do not use credits. Scale uses its monthly non-rollover allowance for event/shop-alert texts before purchased credits. Lifetime uses prepaid credits for event/shop-alert and transactional order texts; sign-in codes stay included. The active production feature matrix is authoritative if an administrator changes an entitlement.
Open Notifications > Text messaging
Open Notifications in the Communicate group and choose the Text messaging tab (the other tab is Customer alerts). Review Shop-alert credits or Text credits, delivery health, recent sends, and consent records.
Buy and use credits
- Choose Buy credits.
- Select a credit pack or configure auto top-up.
- Use Export compliance when an auditable consent file is needed.
- Review the credit outlook after a send.
Understand the lanes
- Event/shop-alert SMS uses purchased credits on Pro. On Scale, it uses included monthly credits first, then purchased credits.
- Transactional order texts and review-request texts use a separate lane and consent. These do not use credits on Pro or Scale; on Lifetime they use prepaid credits.
- Two-factor authentication SMS is separate from both.
Common problems
- One credit equals one outbound segment; a long message can consume multiple credits.
- Scale included credits are monthly, non-rollover, expire at the allowance boundary, and are used before purchased credits.
- Free and lapsed tenants cannot send event texts even when purchased credits remain.
- Provider opt-outs, STOP suppression, consent gaps, and carrier limits can skip delivery.
Next steps
Keywords
Notifications, text messaging tab, SMS, text messages, text credits, shop alerts, SMS consent, Scale allowance, Twilio, STOP