Extraglaze Secondary Glazing

Adding Extraglaze to your skill set is a fabulous way to get additional, genuinely rewarding work.

• it pays well
• there is high demand especially in the winter months
• it is all indoors, light joinery only and no windows get taken out
• you don't have to look far for customers. Any of your previous customers still living with single glazing will almost certainly be glad to talk to you about Extraglaze.
• Extraglaze makes such an impressive impact that both you and your customers will be completely sold on it
• we will pass high quality leads your way completely free, all of them looking for an installer

All we want in return is...

• every time an enquiry comes in from your location we can say...
        “We do have a local fitter for you. Here are their details.”
        Your details!
• to become your supplier for exceptional secondary glazing.

• Call us now
• Contact us

What our other fitters have to say...

Ken and Mark describe their experience of this in the following short videos.

• Ken Elms - Accredited

  Experience: 35 Extraglaze projects

  • {fitterInfo 2136}
  • Experience: {fitterExperience 2136} Extraglaze projects
  • {fitterType 2136}

• Mark Cass - Accredited

  Experience: 16 Extraglaze projects

  • {fitterInfo 1626}
  • Experience: {fitterExperience 1626} Extraglaze projects
  • {fitterType 1626}

Need to learn more?

• Check out our existing Network. This is one of the ways we will promote you too.
• Have a look around this web site. Read the independent Feefo reviews
• Order a free sample and Measuring Guide
• Tell someone you already know: someone that will benefit. Then offer to solve their “Old-house is a Cold-house” problem. Or maybe their home's need for sound proofing
• Contact Nic, Extraglaze's founder and Master Fitter, about your first potential project and take it from there.

Tip: if you want to stop reminders being sent to a customer see "A" (below).

A summary of the logic of the Reminders function is shown at "B" (below).

Generally the Reminders function operates automatically, using a Cron. You can manually run the function using the Check button above the Reminders table.

This article describes what happens when Reminders are sent to customers. It centres around what is controlled and recorded here:
- aiExtraglaze > Settings > (Control panel) > Reminders: here you can set many parameters and edit the reminder messages
- aiExtraglaze > Customers > Reminders (tab): a table showing a log of Reminder activity

The "Reminders" table is used to remind the customer that he has calculated projects that were not ordered.
It records a new row in the Reminders Log  for each change in the status of a reminder (one for each project). Note: this is a log, so it does not update a record in this table, it keeps the old record and if a change is made it adds a new one*. It can, however, change a project status in the Projects table**.

For example, one of the following statuses is applied:
- when an order is found that is more recent than the project being verified (checking "Last updated" field of the project compared to "Created" field of the order) then "Project backdates an order" is added in the "reminders" table for all this customer's projects
- when the first reminder is sent a new record is added with the id of the project and the id of the status "Reminder 1 sent"
- when the second reminder is sent a new record is added with the id of the project and the id of the status "Reminder 2 sent"
- when a customer clicks the "unsubscribe" type link in his email then a new record is added for all his projects (one per project) with the id of the project and the id of the status "Cancelled by customer".

This is why the project will have a history i.e. multiple records in the "Reminders" table showing each of the actions taken on the project.
**The most recent record in this history is identified and this status is applied to the most recent project for this customer i.e. it updates that project in the "Projects" table. Therefore you can see the Reminders status of the most recent project for that customer in the Project table. The older projects for that customer are not updated in this way.

* Note: each record has "Date added" and "Last update". The latter infers what is described now...
Admin can manually edit a record in the "Reminders", selecting the project there (in the record) and setting it (for example) to the status "Cancelled by Admin". This is an excepetion to the history principle. The actual record is updated. Note that "Last update" now shows the date it was cancelled.

A - How Reminders can be stopped
As decribed in the paragraph immediately above here, therefore Admin can...
- change the status of a project Reminder in the Reminders table
- apply a customer's request manually

To cancel reminders for a specific project use the Add button above the Reminders table: choose the project and set the status to "Cancelled by Admin".

To cancel reminders for all the projects of a customer manually then select any one of that customer's projects (in the Reminders table) and set it to the status "Admin cancelled all projects".

When a customer clicks the "unsubscribe" type link in his reminder message he will automatically have all his projects added in the Reminders table with the status "Cancelled by customer".

When an existing project (one that has a reminder recorded) is modified then a new record is added automatically into the Reminders table with the status "Reminder reset" and the counting of days until the first reminder is due will start again.
If the last status is already set to "Reminder reset" when modifying the project no other records will be added in the Reminders table.

If a project is added/modified by a user with an email address (or @domain) defined in the "Exclude emails" field from the Settings, the record added in the Reminders table will have the status "Email excluded". No reminders will ever be sent to this customer.

If a user is deleted but there are still projects recorded in the database this will be added in the Reminders table with the status "Email not found".

The status "Switched to email communication" was defined so you can mark a project opened by a customer that sent you an email or called you (started the conversation through other channels).

B - the logic of the Reminders function
Some activity is logged and some Project statuses are changed without the Reminders function (i.e. the Cron) being operated (described in more detail above). For example:
- if the Admin user edits a record manually
- if the customer clicks the Cancel reminders link (like unsubscribe) which is incuded in his reminder message
- if the user updates a project.

When this function operates it checks every customer to find all their valid projects within a particular timeframe - in Settings see "Check back: <x> days". It will ignore all projects older than this timeframe.

Therefore for valid projects only...

It will also check how long since the customer was sent the last reminder (if any) to see if another reminder is due. It uses the following three Check dates (again in the settings):
1 - Reminder 1 after: <30> days (for example)
2 - Reminder 2 after: <40> days         "
3 - Reminder 3 after: <50> days         "

If it finds a project that is older than an order placed by the customer then it updates the status of the project (in the Projects table) with the status "Project backdates an order".

If it finds a project that is attached to an excluded email address then it updates the status of the project (in the Projects table) with the status "Email excluded" - in Settings see "Excluded emails:".

If it finds a project that is no longer attached to a customer (the customer was deleted) then it updates the status of the project (in the Projects table) with the status "Email not found".

If it finds a project that is newer than their order(s) then it will check the status of the most recent project. One of the following happens, depending on the status of this project only:
- no reminder status found or Reminder reset - First it will check to see if the project is older than 30 days. Only if YES: then the Reminder 1 message is now sent, the status of this project is updated (in the Projects table) to "Reminder 1 sent", and a record is logged in the Reminders table, and a record is logged in the Reminders table with this status. PLUS, reminders are logged for any of this customer's other projects (those within the timeframe having one of these statuses): one record is logged per project and each with the status "Reminder 1 sent" - but note these do not also generate Reminder 1 messages (therefore the customer only gets one reminder at this time).
- Reminder 1 sent - it will check to see if the project is older than 40 days. Only if YES: the Reminder 2 message is now sent, the status of this project is updated (in the Projects table) to "Reminder 2 sent", and a record is logged in the Reminders table with this status
- Reminder 2 sent - it will check to see if the project is older than 50 days. Only if YES: the Reminder 3 message is now sent, the status of this project is updated (in the Projects table) to "Reminder 3 sent", and a record is logged in the Reminders table with this status
- all other statuses - no reminder is sent. Nothing is updated.