Where to configure
- Open Devices in the InfiniReach dashboard.
- Select your device, then open the Settings tab.
- Expand Limits & send window.
Phone numbers and GoHighLevel locations are configured separately in Phone numbers & GHL on the same Settings tab.
Daily message limit (per SIM)
The Daily message limit (per SIM) switch controls whether any per-SIM daily cap is enforced. The in-app help text states it is intended for warmup: the count resets at midnight in the SIM timezone. When the switch is off, no daily limit is enforced (the UI shows: "Daily limit is disabled. Messages are not limited by a per-SIM daily count.").
When the limit is on
- When daily limit is reached — choose Queue messages (retry when limit resets) or Reject / fail messages immediately. This applies when any SIM on the device has a daily limit set.
- For each SIM slot, set Limit (messages per day) or leave no limit for that slot.
- When a slot has a positive limit, set Timezone (limit reset) so midnight aligns with the SIM; the UI notes the limit resets at midnight in this timezone.
Send window
The Send window switch controls whether outbound sends are restricted to a daily time range (and selected days). Help text in the product: when on, messages only send within the time range; end time must be on or after start time (for example 09:00–17:00). You can set start, end, timezone, and Days of week (Sun–Sat), then click Save send window before or after enabling the switch (if the window is on, both times are required and end must not be before start).
When outside send window
When the send window is enabled, choose either Queue (send when window opens) or Reject (fail immediately) for traffic that arrives outside the configured window.
Queue depth, pause, and flush (Overview tab)
On the device Overview tab, the Capacity & queue card shows per-SIM queue depth and actions:
- Pause queue / Unpause queue — temporarily stop or resume draining the device send queue.
- Per-slot depth — shows how many messages are waiting per slot (and may show DB vs in-memory counts when they differ).
- Flush — appears when there is queued work or when the device is offline with queued messages in the database; confirming will mark queued messages as failed and clear the queue for that slot.
Related
- Understand "scheduled" status and hold reasons
- Troubleshooting — if messages are not leaving the queue, check device online status and integration errors.