How do I confirm that user and dashboard changes have been successfully implemented in MyOperator?

How do I confirm that user and dashboard changes have been successfully implemented in MyOperator?

Quick Answer

Save every edited section, publish call-flow changes, and then confirm the corresponding entries in System Logs › Activities; if the live system still shows old settings after one hour, contact MyOperator Support with your Business Account Number or Service Number and log details.

Why changes sometimes do not appear immediately

Most dashboard and user edits propagate almost instantly, but backend actions such as new user provisioning, user removals, or route refreshes can take a few minutes to a few hours to synchronise across every server. Unsaved drafts and unpublished call-flow versions never reach the live system at all.

How to save dashboard and user configuration edits

Edits made under Manage Users or Manage Departments only reach the live platform after each subsection is saved.

  1. Open Manage Users or Manage Departments and make your changes.
  2. After changing a user profile, department routing order, or shift timing, click the Save button that sits inside that specific subsection.
  3. If you alter more than one subsection, repeat the save action for each one before leaving the page.
  4. When you set agent shift schedules, read the AM/PM indicator carefully before you click Save so that the intended hours are recorded.
  5. Never close the tab or navigate away until you have clicked Save; unsaved exits discard the edit and nothing reaches the servers.

How to publish call-flow modifications

IVR trees and other call-flow edits created under Call Design › Callflow must be both saved and published to affect live callers.

  1. In Call Design › Callflow, click the three-dot (⋮) menu next to your active flow and choose View and Edit.
  2. Apply the desired adjustments to menus, audio, or routing.
  3. Scroll to the bottom and click Save to Preview to store the version you just built.
  4. Once satisfied, click Publish Confirm to push the new flow live for every incoming call.
  5. If you select Save as Draft instead, the version stays in a staging area and live call handling continues to use the last published flow.

Verifying edits with System Logs › Activities

The System Logs › Activities screen records every saved or published change, the exact timestamp, and the username that performed it. Open it after making changes to confirm that the platform acknowledged your action. To be certain your browser is not showing cached data, press Ctrl + F5 to reload the page.

Managing user licences and avoiding overage charges

  • Adding user profiles beyond your contracted seat limit triggers an extra-payment alert or a temporary billing lock.
  • If you are merely replacing a team member, edit the existing user profile instead of creating a new one.
  • When you delete a user, allow up to 24 hours for backend seat clearing before you add a replacement, otherwise the platform may still count the old seat.

Troubleshooting checklist and contacting support

  • Wait up to one hour for backend synchronisation after you have saved and/or published your changes.
  • If the live behaviour still reflects legacy settings, email support@myoperator.com or call 08129-81029 or 092129 92129.
  • Provide your Business Account Number (BAN) or Service Number, a short description of what you changed, and the matching timestamp copied from System Logs › Activities.

What MyOperator internal teams will do after you report an issue

  • Support Team verification & guided audit. The agent validates your BAN or Service Number, opens System Logs › Activities to confirm whether the change was saved or is still a draft, checks whether the correct call-flow version is published, and may guide you through a browser-cache clear.
  • Account Manager hand-off & licence additions. When the issue is a seat-limit lock, the support agent tags the assigned Account Manager (AM). The AM contacts you to add seats, issue commercial add-on quotes, or upgrade your subscription tier.
  • Escalation to Internal Tech Support. If System Logs confirm that updates were saved and published but live routing still follows old parameters, the support agent creates a child ticket for Internal Tech Support in Zoho Desk or emails tech.support@myoperator.co. The ticket must include your BAN, Service Number, Call Flow ID, a screenshot of System Logs › Activities, and four to five recent plain-text Call UIDs of test calls so engineers can trace the routing.

Keywords

save user edits, publish call flow, System Logs Activities, dashboard changes not reflecting, BAN, Service Number, shift timing AM PM, seat limit overage, billing lock, Ctrl F5, support phone 08129-81029, support@myoperator.com, Call Design Callflow, Zoho Desk child ticket