Usage & Limits
What This Helps You Do
Section titled “What This Helps You Do”See how many requests FSRevs can send and how many team notifications remain in your workspace’s current monthly cycle.
Open Usage & Limits
Section titled “Open Usage & Limits”- Open the user menu in the portal header.
- Select Usage & Limits.
The panel shows how much has been used, the current allowance, how much remains, and the Next monthly reset. Your workspace resets monthly on its own recurring date; this is not a rolling 30-day window.
Request Allowances
Section titled “Request Allowances”| Allowance | What uses it |
|---|---|
| Request Email | Review Request, Review Reminder, and Custom Form request emails sent by FSRevs |
| Request SMS/MMS | Review Request and Custom Form request texts sent by FSRevs |
| QR & Smart Links | Unlimited; opening a shared Smart Link or QR code does not use an email or SMS allowance |
Request Email and Request SMS/MMS each have their own monthly pool. Each pool is shared across all enabled Locations, and every enabled Location increases both allowances. Locations do not receive separate balances; the workspace can use each combined allowance wherever requests are needed.
The standard monthly request allowance is 500 emails and 100 SMS/MMS per enabled Location. For example, three enabled Locations contribute 1,500 request emails and 300 request texts to the workspace’s shared pools. Your Usage & Limits panel shows the effective allowances, including any higher allowance arranged for your workspace.
FSRevs briefly shows space held for provider-backed delivery as Pending. A request counts after the delivery service accepts it, and it may remain counted when the final result cannot be safely confirmed. A request that is confirmed to have stopped before reaching the delivery service does not use the allowance. For delivery details, open the request’s Message History.
Read the request balance as Used + Pending + Remaining = current allowance. Pending capacity is already held for requests in progress, so it is not available for another send. A delivered request that the customer never opens still uses sending allowance; a later bounce does not necessarily return that capacity.
Notification Allowances
Section titled “Notification Allowances”The same panel shows separate monthly allowances for:
- Notification Email
- Notification SMS
- Notification Voice / Call
These are separate monthly notification pools for alerts sent to your team. They do not share balances with Request Email or Request SMS/MMS. A notification can also depend on user eligibility, verified contact details, responsibilities, and the selected Flow or Form settings. See Notifications for those rules.
Notification allowances also scale with enabled Locations. Standard allowances are 2,000 notification emails, 100 notification SMS, and 50 notification calls per enabled Location, shared across the workspace. A workspace with no enabled Locations keeps one base notification allowance, although that does not make unavailable events or recipients eligible for delivery. Check the panel for your actual totals.
Each team delivery channel uses its own notification balance. One event sent by both Email and SMS can use both balances. In-App alerts do not use those email, SMS, or call pools.
The notification totals may slightly exceed an allowance when several notifications are sent at the same time. The request rows reserve their Pending capacity before sending.
The Usage & Limits panel is read-only. Contact FSRevs support if your workspace needs a higher allowance.
When Sending Is Unavailable
Section titled “When Sending Is Unavailable”- The monthly allowance is exhausted: Nothing is sent through that FSRevs email or text channel. Use another available channel, wait for the displayed reset, or contact FSRevs support. A Smart Link, QR code, NFC experience, or Send from Your Device may be appropriate instead.
- FSRevs says requests are being sent unusually quickly: Nothing was sent. This is a short safety delay rather than a monthly reset. Wait a little, then try once more.
- Sending safety controls are temporarily unavailable: Nothing was sent. Try again later; contact support if the message continues.
- A send control is missing or unavailable while allowance remains: Check that the Flow or Form is Running, the intended Location is available to you, and the customer has the contact method you want to use.
- The displayed allowance or enabled-Location count looks wrong: Contact FSRevs support before sending a large batch.
The reset restores monthly sending capacity; it does not remove customer responses, change responsibilities, or clear unsubscribes and delivery restrictions. If a request failed before the reset, review its history before choosing whether to send it again.