Project settings; scheduled reports
Configure InAppify daily, weekly, and monthly SMS reports, choose recipients and metrics, understand reporting periods, and track delivery.
Project reporting sends a scheduled statistics summary by SMS to you and eligible team members. For example, receive yesterday's transaction count and new customers every morning without opening the dashboard.
This differs from charts and data exports, which support detailed analysis, and from customer-event SMS and reminders. These reports target project members, not app customers.
Prerequisites
- Select the correct project.
- Viewing requires report-view permission; creation, editing, and deletion require report-management permission.
- Recipients need a mobile number on their accounts.
- Collaborators must have accepted their invitations; see collaborators.
- Check project SMS credit and delivery status. Reports use the project SMS sending flow; do not assume they are free.
Create a report
- Sign in to the dashboard and select your project.
- Open Project settings → Reporting.
- Select New report.
- Enter a descriptive name, such as “Daily sales summary”.
- Choose the frequency and execution time or starting date.
- Select one or more recipients.
- Select at least one metric.
- Activate and save the report.
Schedule and statistics period
Schedules use Asia/Tehran. The selected time schedules execution, not the end of the statistics window. The window ends at midnight at the beginning of the scheduled execution day; later events belong to a subsequent period.
| Frequency | Execution | Statistics window |
|---|---|---|
| Daily | Every day at the selected time. | The complete previous day. |
| Weekly | The weekday and time established by the selected date. | Seven complete days preceding the execution day. |
| Monthly | The selected day and time in the configured calendar. | From the corresponding previous-month date to the beginning of execution day, not necessarily the previous calendar month. |
A daily report at 09:00 covers yesterday's midnight-to-midnight period, not the 24 hours ending at 09:00. Weekly reports do not necessarily follow a conventional calendar week.
For monthly schedules, Jalali versus Gregorian date selection affects recurrence. A day absent from a shorter month is clamped to that month's last day. Monthly windows are not always exactly 30 days.
Actual SMS arrival depends on execution, queues, and the operator; delivery in the exact scheduled minute is not guaranteed.
Eligible recipients
The current recipient-selection logic includes the owner and accepted Manager or Developer collaborators. This form does not accept arbitrary phone numbers or select app customers.
- Accounts without mobile numbers cannot be selected.
- Each recipient can belong to one report per project.
- Deactivation preserves recipient assignments. Remove the recipient from the old report or delete it before assigning another.
Developer roles have no base financial dashboard permissions, but can appear as report recipients. Consider the information disclosed when selecting transaction amounts; dashboard permissions do not automatically make SMS content confidential.
Metric definitions
All metrics describe the reporting window, not lifetime totals.
| Option | Current calculation |
|---|---|
| Transaction count | Successful payments created within the window. |
| Transaction amount | Sum of those successful payment amounts; SMS labels it in rials. |
| Subscription count | Normal entitlement records created within the window, excluding sandbox records. |
| Free subscription count | Current dashboard label; calculation counts trial entitlement records created in the window, not every zero-price purchase. |
| New customers | Project customers created within the window. |
Subscription count is not unique customers or ending active inventory; renewal or period records can affect it. See active subscriptions for inventory.
Transaction amount is not net revenue after refunds, store commission, gateway costs, or the amount payable in settlements. The current calculation sums successful payments without separately subtracting refunds. Use revenue definitions and settlements for financial analysis.
SMS content
Messages contain the project name, report name, date or window, and selected metrics. Content is generated automatically; this is not a custom message or customer-template editor. The current report body uses Persian text and digits and Jalali display dates. Selecting a monthly calendar does not change the message language.
Additional metrics can produce a multipart SMS and change its cost. See SMS credit and pricing.
Edit, pause, and delete
Select Edit from the report row. Change its name, metrics, recipients, or schedule, or deactivate and save. Saving recalculates the next run; do not expect immediate sending or automatic delivery of every missed period.
Deactivation stops subsequent scheduled execution, but previously queued messages may still send. Deletion removes configuration and recipient assignments, not underlying transactions or customer data.
The list displays send time, recipient count, activation, and last execution. Execution records the message-queueing process, not confirmation that every handset received the SMS. See SMS logs and troubleshooting.
Troubleshooting
- Cannot save: provide a name, schedule, at least one metric, and an eligible recipient.
- Missing recipient: check accepted membership, role, and mobile number.
- Disabled recipient: missing mobile number or assignment to another report.
- No SMS: check activation, next execution, credit, and delivery status.
- Zero statistics: check the previous complete period and metric definition; today's activity is not yesterday's statistics.
- Chart mismatch: align creation times, Tehran boundaries, rial/toman units, filters, refund treatment, and entitlement-record versus customer counts.
Start with one recipient and a few useful metrics. After the scheduled run, check the period, amounts, and message status before adding more recipients.