How can I set the time duration for an added user who receives calls?

How can I set the time duration for an added user who receives calls?

How do I set call‑receiving hours for a user in MyOperator?

Short answer: Edit the user’s Advanced Settings to define time slots (start time, end time, days). Calls outside these windows won’t be routed to that user; they’ll follow your flow’s fallback (team/queue/voicemail/next available).

Contents

Prerequisites

  • Permissions: You can access Manage → Users and edit user profiles.
  • Time zone: Confirm your account time zone in settings; schedules follow that time zone.
  • Fallback behavior: Know where calls should go outside the user’s hours (e.g., team/queue, voicemail, next available user) and configure that in your call flow.
  • Multiple slots: If your plan supports it, you can add more than one slot per day (e.g., lunch break).

Set a user’s call‑receiving hours (step‑by‑step)

  1. Sign in to MyOperator.
  2. Go to Manage → Users.
  3. Click Edit next to the user you want to schedule.
  4. Scroll to Advanced Settings (Availability/Time Slots).
  5. Set Start Time, End Time, and select the Days of the Week.
  6. (Optional) Click Add time slot to create additional windows (e.g., 9:00–13:00 and 14:00–18:00), if available.
  7. Click Save.

Screenshot

Screenshot 2025-08-08 at 16.46.30.pngScreenshot 2025-08-08 at 16.48.56.pngScreenshot 2025-08-08 at 16.49.57.png


Caption: Define the user’s working window and days; add extra slots if needed.

Examples you can copy

Standard weekday schedule

Mon–Fri: 09:00–18:00 (account time zone)Sat–Sun: Off

With lunch break (two slots)

Mon–Fri: 09:00–13:00 and 14:00–18:00Sat–Sun: Off

Split‑week coverage

Mon–Thu: 10:00–19:00Fri: 12:00–20:00Weekend: Off

Verify and confirm behavior

  1. Place a test call during the user’s active hours and confirm the call can route to them.
  2. Place another test outside their hours; confirm routing skips the user and follows your fallback (e.g., queue/voicemail).
  3. Open Call Logs and verify the path reflects the schedule (e.g., Queue → Agent (in hours) or Queue → Voicemail (out of hours)).

Success criteria: Calls during scheduled windows can reach the user; calls outside windows never ring the user and follow your defined fallback.

Edge cases & tips

  • No time slot configured: If no availability is set, behavior follows your flow defaults (the user may receive calls anytime or never, depending on configuration).
  • Do Not Disturb/Busy: DND or ongoing calls can still prevent ringing even within hours; ensure queues have timeouts and voicemail fallbacks.
  • Holidays/After‑hours rules: Global Business Hours/Holidays can override user schedules; check those settings if behavior differs.
  • Daylight Saving Time (DST): If your account time zone observes DST, verify times after transitions.
  • Mobile app status (if enabled): App‑level availability can affect routing to the user.

Get help

If schedules don’t behave as expected, email support@myoperator.co with:

  • User name/ID and Call Flow name
  • Screenshots of the user’s Advanced Settings
  • Example call timestamps (inside and outside hours) and Caller ID
  • Brief description of the observed vs expected behavior

Related articles