✖︎️



Notice
By Using the On Ciraconnect website, you are agreeing to the following:

This website and all the information in it is intended for CiraConnect Internal Users and SaaS Clients only. It is not to be shared externally or to be read by external parties

🚧️ For Internal Use Only

Rush Tiers Coming Monday June 5
⏩

Rush Tiers Coming Monday June 5

We are planning to release the new Closing Portal Delivery Tiers, or Rush Tiers, next Monday, June 5th, into production. We can now add multiple tiers of delivery for a different fee. This project includes a new Closing Portal configuration UI (Closing Portal Delivery Tiers) and a new Business Hours configuration (currently set at 9a-5p CT). It is only available in the new Management Portal in the Administration menu. We also have re-architected the Closing Request Queue to support the new process with 2 new tabs to segregate the different types of orders.

In order to support the initial release, it required:

1) Supporting the new Instant / 2-hr delivery tier for requests that can be systematically processed.

2) Mapping our existing process, as it was loosely defined with only one rush fee option, irrespective of what is requested, to new tiers.

3) Linking the pricing to Revenue Management Module (RMM) Products

  • It was necessary to add a new Product to support the systematic Instant / 2-hr tier. The price has been configured at $275, but can certainly be updated depending on feedback. A few of us debated initial pricing between $250 and $300.

Here are some example configurations for the initial release.

Closing Portal Delivery Tier Configuration:

image

RMM applicable Products (pricing is controlled in the RMM, which can be configured at a node level and overridden at any lower level, including the Community level):

image

Please Note:

  • The Closing Portal will indicate an estimated delivery date/time based on the available delivery tiers (we are updating the verbiage, and screenshots / additional support documentation will be released once we do).
  • The actual delivery date/time deadline will be determined once the up-front payment is received, if required, otherwise when the order is submitted.
  • The Closing Agent will receive an update with the actual delivery date/time deadline after the up-front payment is received, if required, otherwise after the order is submitted.
  • The ability for an agent to upscale an order without canceling and re-ordering is not officially supported yet.
  • The Closing Requests Work Queue will now reflect the delivery deadline along with the segregation of requests by those requiring manual fulfillment, requests that will be systematically fulfilled (now held until the deadline as described), and requests pending payment.
image

Notes on Configuration:

  • Tiers can be defined by hour and/or day.
  • Tiers can be defined by the type of request (e.g., SOA, Questionnaire).
  • Tiers can be configured to include/exclude accounts "In Collections."
  • Collection accounts can be configured independently.
  • We did NOT include the ability to define a tier by Seller type or Seller/Buyer combination. We can add the Seller type if we deem it necessary to configure different tiers for developing communities without too much more code dev. The Seller/Buyer combination type gets much more complex in the configurations. If we add this dimension, we will need to add additional RMM Products for the pricing.
  • Company holidays are not incorporated yet