:orphan:

.. include:: ../variables.rst
.. _requestingaquote:

Requesting a Quote
==================

.. figure:: /images/banners/hospitalbuilding.jpg
   :align: center

|br|

We would be happy to put together a |APPNAME| quote tailored to
your organisation. The more detail you can give us up front, the
quicker we can turn a quote around — most of our follow-up emails
exist because one of the fields below was missing.

What to Send Us
---------------

Send the following to |SALESEMAIL|:

* **Contact name** — who should receive the quote and any
  follow-up questions.
* **Organisation name** and **full address**.
* **Phone number** and **email address**.
* **Number of facilities** you are planning to monitor.
* **Number of administrator accounts** — at least one per site is
  required.
* **Number of auditors** — auditor accounts are not charged for;
  we only ask so we can size the deployment.
* **Legacy data migration** — if you would like historical data
  brought across from another system, tell us what format it is in
  and how many years of data are involved.

Optional but helpful:

* **Target go-live date** — if you have one, it helps us schedule
  onboarding and training.
* **Integrations** — if you plan to pull data from other systems
  (EHR feeds, staffing, incident-reporting tools, etc.), mention
  them so we can scope any connectors up front.

What to Expect Next
-------------------

We normally turn a quote around within **two business days**. The
quote is sent by email along with a short covering note explaining
which edition of |APPNAME| best matches what you have described
and any assumptions we have made.

If you have not heard back in that time, follow up with
|SALESEMAIL| or |SUPPORTEMAIL| — the quote may have been caught by
your spam filter, or we may need one more piece of information
before we can complete it.

Presentation
------------

If you'd like to brief your team before (or during) the quote
process, we have a short slide deck you can download and share:

* :download:`clearPath Presentation<../support/documents/clearPath_Presentation.pdf>`

Resources
---------

The pages below are useful background while you are deciding
whether |APPNAME| is a good fit:

* :ref:`Introduction to clearPath<about>` — what |APPNAME| is and
  how the pieces fit together.
* :ref:`Getting Started with cp2go<auditingsoftware>` — a tour of
  the auditing software your team will use on the floor.
* :ref:`Report Matrix<reportsbyedition>` — which reports are
  included in each edition.
* :ref:`Additional Documents<documents>` — sample reports, auditor
  training, and the full product presentation.
* :ref:`Create a Support Ticket<openticket>` — how to reach support
  once you are up and running.
* :ref:`Contact Us<contactus>` — every way to get in touch with us.