9bx Connect
Messaging settings
Quiet hours, language, privacy and limits for every message your workspace sends.
Contents
- What it is for
- Who can use it
- Where to find it
- The screen explained
- Tasks
- Example scenario
- Tips
- Troubleshooting
- Related pages
What it is for
Global rules that apply to all messages, so customers are not woken at night and you keep data only as long as needed.
Who can use it
Users with the Settings manage permission. Others see the page read-only.
Where to find it
Chat & Messaging → Chat settings → Messaging → Settings
The screen explained
| Section | Field | Meaning |
|---|---|---|
| Quiet hours | Marketing and broadcasts, Transactional messages, From, to | Messages due in these hours wait until they end, in the recipient's time zone. A country rule may add its own window. One-time codes are never held. |
| Sending | Default language | Used when a recipient's language has no text. |
| Fallback wait | Starting value for "then the other channel after N minutes". | |
| Messages written by agents | Off means agents can send only templates. | |
| Smart characters | Replaces curly quotes and dashes so SMS stay in the cheaper standard alphabet. | |
| Privacy & alerts | Keep message text for | After this the text is removed. Delivery records and usage stay. |
| Alert emails | Told when a provider keeps failing (up to 10). | |
| Resend from the customer page | Resends a day, Wait between resends | Lets customers ask for a ticket message again. |
| Daily limits per provider | per provider | After the limit, messages use the next provider in routing. |
| Broadcast approval | Every broadcast needs approval | Always on: someone other than the author approves each broadcast. |
Tasks
Set quiet hours for marketing
- Open Settings → Quiet hours → Marketing and broadcasts.
- Set From 21:00 to 08:00 and save ("Messaging settings saved").
Example scenario
Padma Net Support holds marketing from 21:00 to 08:00. A broadcast prepared at 22:30 shows "N recipients will wait for quiet hours to end" and starts at 08:00.
Tips
- Add two alert emails so failures are seen by a team.
- Keep message text only as long as your policy allows.
Troubleshooting
Settings cannot be saved. Check email format in Alert emails and that you have permission.