CRM Settings Overview
CRM Settings Overview
Section titled “CRM Settings Overview”The Settings section in IZI CRM is where you configure both club-level parameters and organization-wide defaults. Club settings control day-to-day operations (like how long your bar team has to fulfill an order), while organization settings manage account-level information and data. Notification rules sit in the same section, letting you route system alerts to the right channels without leaving the CRM.
Two layers matter here: club owner (what thresholds and policies to set) and admin / manager (knowing where to look when something behaves unexpectedly). Both perspectives are covered below.
Club Settings
Section titled “Club Settings”Maximum Order Fulfillment Time
Section titled “Maximum Order Fulfillment Time”This parameter sets the time limit (in minutes) within which a bar order must be handed to the guest. Orders not fulfilled within this window are automatically flagged as overdue in the order queue, making them visible to shift supervisors at a glance.
Default value: 10 minutes.
Adjust this based on your kitchen or bar throughput. A small club with a single bar station may keep 10 minutes; a multi-zone venue with a full menu might raise it to 15–20 minutes to reduce false overdue alerts.
To change the fulfillment time:
- Open Settings in the left navigation.
- Select the target club from the club switcher at the top.
- Under Club Settings, find Maximum Order Fulfillment Time.
- Enter the new value in minutes and save.
Changes apply immediately — no restart or re-login required. The updated threshold takes effect for all new orders placed after you save.
Edge cases to watch:
- If you manage multiple clubs, each club stores its own threshold. Changing the value in one club does not affect others.
- If a bar order is already in the queue when you update the threshold, it is evaluated against the old threshold until the page is refreshed by the operator.
- Setting the value too high (for example, 60 minutes) will suppress the overdue flag for almost all orders, removing its usefulness as an operational signal. Keep the value realistic for your actual service speed.
Organization Settings
Section titled “Organization Settings”Basic Information
Section titled “Basic Information”Here you can edit the organization name as it appears across the system — in reports, receipts, and the manager interface. Changes take effect immediately across all clubs in the organization.
Danger Zone
Section titled “Danger Zone”The Danger Zone contains the option to permanently delete the organization along with all associated data. This action is irreversible. IZI does not keep a soft-deleted snapshot — once confirmed, all clubs, clients, transactions, and settings under that organization are gone. Use this only when decommissioning a test environment or closing a business entity.
Notifications
Section titled “Notifications”The Notifications subsection lets you define rules for how IZI delivers system alerts. Each rule specifies three things:
- Channel — the integration used to deliver the alert (for example, Telegram)
- Clubs — which clubs the rule applies to, or all clubs in the organization
- Notification types — which events trigger the alert (e.g., new order, overdue order, session start/end)
You can have multiple rules with different channel/club combinations. A common setup: one Telegram rule for all clubs covering critical alerts, and a separate rule for a specific club’s manager covering operational events.
To add a notification rule:
- Open Settings → Notifications.
- Click Add Rule.
- Choose the delivery channel from the dropdown (the channel must already be connected under Access Permissions).
- Select which clubs the rule covers — choose one, several, or all.
- Check the notification types you want this rule to deliver.
- Save. The rule becomes active immediately.
Troubleshooting notifications:
- No alerts arriving — verify that the integration (for example, the Telegram bot) is still active under Access Permissions. A disconnected or revoked bot token will silently drop all messages.
- Duplicate alerts — you likely have two overlapping rules targeting the same channel and event type. Review your rule list and remove or narrow the scope of the duplicate.
- Wrong club receiving alerts — check the Clubs field on each rule. If a rule is scoped to “all clubs,” it will fire for every club in the organization, not just the one you intended.
Related Articles
Section titled “Related Articles”- Access Permissions
- Bar Orders
- Roles Overview
Frequently Asked Questions
Section titled “Frequently Asked Questions”faqItems:
- question: “What is the default bar order fulfillment time in IZI?” answer: “The default is 10 minutes. Orders not fulfilled within this window are marked overdue in the order queue.”
- question: “Can I set different fulfillment times for different clubs?” answer: “Yes — the Maximum Order Fulfillment Time is a club-level setting, so each club in your organization can have its own value.”
- question: “What happens if I delete the organization?” answer: “All data — clubs, clients, sessions, orders, and settings — is permanently removed. There is no recovery option. Export any reports you need before proceeding.”
- question: “Can I send notifications to multiple Telegram channels?” answer: “Yes. Create multiple notification rules, each pointing to a different Telegram channel or integration, and scope them to different clubs or event types.”
- question: “Where do I rename my organization in IZI CRM?” answer: “Go to Settings → Organization → Basic Information and update the name field.”
- question: “Who can change settings in IZI CRM?” answer: “Access to the Settings section depends on the role assigned to the user. Typically, only owners and administrators have write access to organization-level settings.”
- question: “Does changing the organization name affect receipts?” answer: “Yes — the organization name updates immediately across the system, including in any generated receipts and reports.”
- question: “What notification types does IZI support?” answer: “IZI can notify on a range of system events. Available types appear in the notification rule editor. Common ones include new bar orders, overdue orders, and session activity.”
- question: “Why are my notification alerts not arriving?” answer: “Check that the integration (e.g., your Telegram bot) is still connected under Access Permissions. A revoked or expired token will silently drop all outgoing messages.”
- question: “Will an in-progress bar order immediately reflect a new fulfillment threshold?” answer: “No. Orders already in the queue are evaluated against the threshold that was active when the order was placed. The new threshold applies only to orders created after you save the change.”