InAppify

SMS setup and event settings

Enable SMS, configure the recipient phone source, and choose templates for login and subscription events

Prerequisites

Create a project and register its customers in InAppify. Your account needs the relevant project SMS permissions. Ask the project owner to review permissions if a menu is missing.

Dashboard steps

  1. Select the project and open SMS service → Event settings.
  2. Enable the SMS service.
  3. Select the customer phone source.
  4. Enable each required event and select an appropriate template.
  5. Review the preview and variables, then save changes.

The service switch alone is not enough: the event or reminder step must also be enabled and have a template.

Recipient phone source

SourceWhen to use it
App user identifierThe customer's app_user_identifier is their mobile number
Customer attributeThe identifier is not a phone number; store the number in $phoneNumber

InAppify does not infer a phone number from an arbitrary user identifier. Store it in $phoneNumber and select the attribute source instead.

Only valid Iranian mobile numbers are supported here. The normalized format starts with 09 and contains eleven digits. +98 and 0098 prefixes are normalized. Use ASCII digits when storing phone data. Empty, invalid, or non-Iranian numbers cannot be used for these customer events and reminders.

Available events

EventPurpose
Login OTPTemplate for the web SMS login flow; enabling it does not implement login in your app
Subscription purchasedNotify the customer about a subscription purchase
Subscription renewedNotify the customer about renewal
Subscription expiredNotify the customer when subscription access expires

Web OTP uses the phone submitted in the web login flow. The customer phone-source setting applies to subscription messages and reminders.

Only active, approved templates for the matching event are usable. Check template approval if your custom template is unavailable.

Start with a small setup

Enable the service, select the correct phone source, and enable purchase notifications with a default template. Check credit and inspect logs after your own controlled test or actual purchase. Saving settings does not send a test message.

Next: templates and variables.