Table of Contents:
...
If the credit has expired, DP will not approve an M1 extension. The installer needs to cancel the workflow, requote, rerun credit, generate a new contract, and complete all milestone tasks:
'Hello,
The credit qualification is expired; therefore, we are unable to grant a milestone extension for M1. To proceed, you will need to re-run credit, create a new quote and contract, and complete all milestone tasks per the new workflow inclusive of the welcome call.
Regards,'
Info |
---|
If the previous contract was generated using expired pricing, the installer will have to requote with updated pricing. EB will not honor expired pricing for pre-M1 cancellations. |
...
If an Account Manager is requesting an extension of M2, the agent should create a Jira ticket, if one has not been created already. Advise the Account Manager only to reach out to Richie Slaney (Unlicensed) and close the ticket.
M3 Requests and Setoffs
No M3 extensions will be granted. If a job passes the M3 deadline the red deadline has passed banner will display, but the installer will still be able to complete M3 tasks and then submit for approval.
Info |
---|
Some workflows still have the ability to submit for an M3 extension as of 1/5/2023, however no M3 extensions will be granted. The M3 milestone extension request |
...
task will be removed from all workflows per
|
Workflows that were created on or after 5/15/2023 will have their PTO milestone configured to set off when the milestone deadline passes.
The milestone deadline passed banner will display on
The installer should complete the required tasks. Once complete, they will be able to submit for approval.
The first workflows that are eligible for setoffs will be in February.
This feature will trigger a setoff of all funds released to date for the project, not a claw back.
Once the installer has reached PTO approval, the setoff will be reversed.
The ability to exempt specific workflows from being setoff past the M3 submission deadline will be available.
This will be determined by DP only.
...
Back in the ticket, ‘reply to customer’ with the following canned response with a screenshot included:
Hello,
Thank you for contacting EverBright support. We are pleased to inform you that milestone extensions can be requested in the Operations phase of the platform. Please follow the instructions below to submit your request:
Navigate to the Operations phase of your workflow.
Select the milestone needing an extension.
Click on the ‘Request Milestone Extension’ task.
A window will pop up allowing you to add others to the request and/or leave a custom note for deal processing.
Click ‘Send’
That’s it! An extension request will automatically be sent to deal processing for review. No further action is required on your part. Please allow 1-2 business days to complete the review. The result will be posted in the milestone feed section of the platform (see screenshot below for details). We are closing this ticket. Feel free to reach out if you need additional assistance.
Regards,
Once the milestone extension request has been sent to DP, the ticket can be closed.
Resolution type - account management
If the Milestone Extension Request button is not available (M1 or M3 only)
No M2 extensions will be granted. Otherwise, add deal processing to the request participants field before replying:
Deal Processing team:
[Organization], copied on this email, is seeking an extension for [customer name and address] for milestone [x]. Please let us know if this is approved or if you need additional information.
Thanks,
The M3 extension request capabilities will be removed for jobs on or after 5/15/2023.
Workflows that were created on or after 5/15/2023 will have their PTO milestone configured to set off when the milestone deadline passes.
...
Note |
---|
Agents should NOT be reaching out to Deal Processing until the 3rd business day. Please allow DP 2 full business days. |
...