Welcome to Nimbus, Microsoft Teams’ sidekick to save customer service. Nimbus allows you to set up your own service team  with minimal configuration effort. 


Nimbus has been developed from the ground up, combining years of Luware Know-How with modern web standards:

  • Luware Nimbus is Software as a Service which is cloud-native and runs on the Microsoft Azure cloud. 
  • Lightweight user interface with responsive controls that work just as quick as any locally installed application. (learn more )
  • An intuitive design that seamlessly integrates into the layout of Microsoft Teams as an App, while working just as good within your browser.
  • Highly customizable Service Settings each with their individual Configuration that doesn't require extensive user training.
  • Free to define of your service with individual opening hours and workflows.
  • Lots of Features included right from the start, with many more to come in future!
As a good starter topic we highly recommend reading   Nimbus in a Flash.

Luware Support

Questions? Need help with Nimbus Installation or any other topic? Don't hesitate to contact us:

You can reach us via the following means: 

Safety and warning messages

Please pay special attention to these messages as they convey important aspects of this product manual. Below are some examples that you might find in this documentation:

Type: Tip / Hint / Checklist

Tips / Checklists / Before you start

Hints like these contain recommended or pre-required topics to consider, such as:

  • Installation conditions
  • Checklists / actions
  • Prerequisites
  • Preemptive steps 
    → and their results

(lightbulb) The goal of tips is to save you time or recommend doing things in an efficient order. 

(tick) This is the mini-variant that you might find within text or instructional steps.


Type: Info / Navigation

Information

Here we emphasize directly related topics and concepts for you to keep in mind. Among these you'll find;

  • Related chapters
  • Sources on the web
  • Listings and overviews
  • Links to diagrams, appendices and concepts
  • The next logical topics for your reading flow

(info) This is the mini-variant that you might find within text or instructional steps, usually in combination with a link to further topics.


Type: Note / Attention

Important Notes

This is an important note that warns you of: 

  • Necessary precautions to avoid issues
  • Important user or system requirements
  • Potential sources for error via either a misconfiguration or during usage
  • Tricky fallacies that might not be obvious at first glance
  • Known issues and their workarounds

Negligence of notes usually leads to erratic system behavior, minor loss of time or other (recoverable) issues. We therefore highly recommend you read these warnings carefully.

(warning) This is the mini-variant that you might find within text or instructional steps.


Type: Warning / Critical

Warning of Critical Conditions

We use this one sparingly because it's very important. A critical message warns you of problems that may result in severe infrastructure impediments. 

  • Multiple sources ...
  • ... or follow-up problems could be mentioned here
    → Consequences like permanent loss of data or widespread infrastructure malfunctions are highlighted.
  1. Instructions might be included in these warnings
  2. ... or shortly thereafter in numbered steps.
    → The expected result state follows for those steps (if there is a system reaction or result to be verified).

Negligence of warnings usually leads to a faulty system behavior, considerable loss of time, up to a point where your system might be unrecoverable without severe loss of data. We highly recommend not to skip these warnings at all.

(error) This is the mini-variant that you (rarely) find within paragraphs or instructional steps.