Incorporate a DND (Do Not Disturb) function

[piajesse]

iOS version needs a better DND system, currently it relies on iOS and doesn't allow you to completely ignore calls, just set them to vibrate. We should also add an option to set the time windows to enable/disable calls and configure them from provisoning

[LawOfSynergy]

This task needs a more thorough design document. Things to consider:

• Do we use iOS's DND as a first pass, then apply app logic on top of it?
• What level(s) are time windows configured at? AN, client company, local app?
  • Does more local override less local?
  • Does provisioning provide defaults that are overwritten on the local app?
  • Do clients have a way to self service their configuration for company/local defaults? Do we need to build out an admin area for clients to do so?
• What actions can be configured for when an out of window call comes in?
  • e.g. Go to voicemail, continue call tree, route to phone bot to attempt self help?
• Do these call windows apply to individual extensions? ring groups? both?
  • if they apply to both
    • do groups override individual time windows or vice versa?
      • is this configurable?
    • If an individual is out of window, do we preempt even trying to call them and skip straight to the next extension in the tree?

[LawOfSynergy]

First draft of how to split this ticket. It is by no means complete and requires more refinement

DND Mode Implementation

The local app’s implementation of DND mode. This uses the following settings to control how calls and messages are handled. The only setting that is controlled non-locally is Enabled and this will be to respect time windows.

For parity implement for both android and iOS

Enabled - bool
Calls

• System - relies on System level DND configuration
• Custom
  • Ring - enum
    • Silent
    • Ring
    • Vibrate Only
    • Ring + Vibrate
    • Decline
    • Voicemail
• Messaging - enum
  • Silent
  • Vibrate
  • Notify
  • Notify + Vibrate

DND Time Window Supplier

All time-windows stored on the phone locally, with periodic server sync for company time windows

• Enabled
• Default
• Disabled

//TODO figure out how merge logic should work, whether disabled or enabled gets priority, and can a time window have an option to force override a local time window

• Initial thoughts:

  • Priority: Disabled favors companies controlling their employees as it would allow them to force the phone to be responsive during work hours (aside from system DND, which this does not have control over)
  • Priority: Enabled favors employee autonomy, since they are able to allow DND even when they might be during an active call window.
  • If we keep Priority: Enabled and allow an option for time windows to force a state, then that gives the most flexibility for how each company wants to approach it.
  • Time Window definitions should be stored in an ordered list (which means each editor should allow them to be reordered) such that the first entry encountered with a forced state is the one that takes precedence.

• Generally, local overrides company

//TODO do call groups already have time windows/schedules? What does the serialized form look like? Does it matter, since we can have the retrieval endpoint use whatever schema it wants after scraping the window for rules applying to the extension?

Local time window editor

//TODO android implementation details/mockup
//TODO iOS implementation details/mockup

Endpoint to retrieve time window data for an individual extension

This could be used to allow the local DND scheduling to have a difference serialized form from the company’s time window/scheduling serialized form

Company time window editor

//TODO web implementation details/mockup
Does one already exist? If so, can we safely add a boolean to its serialized form for overriding local?

[LawOfSynergy]

Minimum viable implementation is to just complete DND Mode implementation, and have it controlled entirely locally. ALL of the rest is feature creep centered around scheduling/time windowing