Where this workflow sits in day-to-day operations

This workflow is usually owned by the business owner, office admin, estimator, accounts person or operations manager who speaks to customers on behalf of the business. Installers may rely on the outcome of these messages, but the people who manage financial visibility, proposals, project updates and invoice chasing are normally the ones who control the templates and decide when each message goes out.

In practical fencing terms, this workflow starts long before the first reminder is sent. It begins when your business decides how customers should hear from you at each stage:

• sending a quote and proposal link
• following up an open quote after a few days
• sharing neighbour notices when a shared boundary needs attention
• sending project updates or a portal link once work is underway
• requesting variation approval or handover sign-off
• issuing invoices, overdue reminders and payment receipts

When these messages are handled through one consistent process, the customer experience stays clear and your internal record stays easier to review. The same quote, project and invoice records continue to carry the communication history, rather than leaving staff to search old inbox threads for context.

Set the communication foundation before you send anything

Start with the Email Templates area and your wider configuration settings. Fencify lets you manage built-in default templates and also save custom templates that can be selected later from quote and project send windows. Before editing wording, confirm the communication basics your customers will recognise:

• the business name you want customers to see
• the reply-to email the office actually monitors
• branding elements such as logo, colours and footer details if you use them
• which staff role is responsible for quote, project and invoice communication decisions
• which language style fits your customer base and contract process

This preparation matters because Fencify uses purpose-based sender identity. Quote emails, proposal emails, invoice emails and general project client messages all rely on the business details and sender profile settings being sensible before the message leaves the system. If the reply-to address points to the wrong inbox, or if the footer still carries outdated trading details, every later message inherits the same problem.

Build a reusable template library for each stage of the job

Once the sender basics are right, organise your wording in the Email Templates area. Fencify supports template types that match real job stages, including quote emails, quote follow-up emails, neighbour notices, neighbour portal messages, project updates, variation requests, handover sign-off requests, invoice emails, invoice reminders and payment receipts.

A practical way to manage them is to treat each template as a message purpose rather than a generic email draft. For example:

1. Create or refine the main quote template that introduces the proposal clearly and sets expectations about the next step.
2. Prepare a separate follow-up template that works a few days later without repeating the original message word for word.
3. Keep neighbour notices short and factual when a boundary job affects adjoining property owners.
4. Use project update templates for scheduling, access reminders or portal sharing once a quote is already accepted.
5. Use variation and handover templates for actions that need a clear response from the customer.
6. Keep invoice, reminder and receipt wording aligned with your bookkeeping process.

Fencify supports placeholders so the message can pull live record details into the final email. Depending on the template type, you can draw on values such as customer name, customer email, customer phone, project name, site address, suburb, quote number, invoice number, amount, balance due, due date, portal or proposal link, company details, payment amount, payment method and payment date. Project-stage templates can also include an action block when the email is prompting the customer to review something specific.

Use placeholders deliberately. They are most useful when the inserted value removes manual retyping or reduces the chance of sending the wrong job number or payment figure. They are less useful when the sentence still needs careful human wording around it.

Run quote communication from first send through follow-up

The quote communication workflow starts from the individual quote record. When the quote, pricing and proposal details are ready, open the quote and choose the send email action. Fencify lets you choose a saved template, review the subject and body, and send the proposal with record-specific placeholders already available.

Before sending the quote, check these operational points:

• the customer name, email and phone are current
• the quote total and project address are final enough to send
• the proposal wording matches the type of fence, gates and scope you are pricing
• the proposal link and any key files are ready for the customer to review
• the office agrees on whether follow-up should be scheduled straight away

When the quote email is sent, Fencify updates the quote status to sent. You can also set a follow-up schedule at the same time by choosing the cadence in days and the maximum number of reminders. This is useful when the office wants a controlled sequence instead of relying on memory. The timing can later be revised, paused or cleared from the quote if the customer responds, views the proposal, accepts, declines or asks for more time.

Keep the first follow-up email different from the first send. A strong follow-up template usually confirms the quote number, reminds the customer of the job context, and asks for the next decision clearly. When the customer opens the public proposal, Fencify updates the quote activity and uses that view history to keep the follow-up timing relevant. If the quote is accepted or declined, the reminder sequence stops so the office is no longer chasing a finished sales outcome.

For boundary jobs, quote-stage communication can also include neighbour notices. Use that template when the adjoining owner needs early notice about access, shared fencing arrangements or an upcoming portal message connected to the same job.

Move into project communication once the quote becomes live work

After acceptance, customer communication shifts from sales language to delivery language. Open the project record and use the project email action when you need to contact the customer about install timing, site preparation, portal access, approved changes or completion steps. Fencify allows the office to choose a saved project-stage template and then tailor the message before sending.

This stage is where reusable wording saves the most time, because the same project often needs several different customer messages over a few weeks. Keep your project templates grouped by purpose:

• a project update template for scheduling or progress information
• a neighbour portal template when a shared fence customer or adjoining owner needs access to the correct public page
• a variation request template when extra work, scope changes or site conditions require approval
• a handover sign-off template when practical completion is ready for final acknowledgement

Project emails can include a portal link, which helps the customer move from the email into the job record you want them to review. If there are pending variations, the send window can also prompt the office to request sign-off as part of the same communication step. If the project is ready for handover and the sign-off is still outstanding, the handover request can be included in the message flow as well.

Before sending a project email, pause on the job details that matter operationally:

• install dates and access details are current
• the right customer or neighbour contact is attached to the job
• the portal information matches the audience receiving it
• any variation amount or wording has already been internally approved
• the handover request is being sent only when the job is genuinely ready for that stage

This check is especially important on larger commercial, strata or shared boundary jobs where several people may be watching the same project from different angles.

Carry the same discipline into invoice emails, overdue reminders and receipts

Once billing starts, the communication workflow moves into Invoicing. Fencify uses the invoice template to send the initial invoice email, then supports reminder wording for overdue balances and receipt wording once payment is confirmed.

A reliable finance communication sequence usually looks like this:

1. Send the invoice from the invoice record after checking the customer email, invoice number, amount and due date.
2. Let the invoice email template explain what the invoice relates to and what payment timing applies.
3. Use the reminder template when the invoice remains overdue and still carries a balance due.
4. Use the payment receipt wording once the customer payment has been recorded and confirmed.

Fencify can track overdue reminders in stages, which means the office can keep a measured chasing rhythm instead of sending ad hoc messages. The reminder flow supports the initial overdue point and then later reminder intervals, so it is worth reviewing the wording carefully. The best reminder templates stay firm, mention the invoice number and balance due clearly, and give the customer a simple next step.

Payment receipts deserve the same care. A receipt template can pull in the payment amount, method and date, which makes it useful for deposits, progress claims and final payments. Customers often keep these messages for their own records, so the wording should confirm what was received without creating confusion about any remaining balance.

Know what Fencify records or updates as you communicate

Each part of this workflow changes or supports a different Fencify record, so it is worth understanding what moves behind the scenes as the office communicates.

Saved templates

Your default and custom email wording is stored for reuse by the account owner, which keeps later send windows faster and more consistent.

Quote send and follow-up activity

Sending the quote updates the quote status to sent, and the follow-up schedule stores the cadence and reminder limits attached to that quote until the sales outcome changes.

Proposal engagement

When the customer opens the proposal, the quote activity reflects that engagement so the office can follow up with better timing.

Project communication prompts

Project-stage emails can carry portal access, variation requests and handover requests that move the customer toward the next operational step.

Invoice communication history

Sending an invoice updates its status to sent, and reminder tracking helps the office see whether overdue chasing is still current.

Payment confirmation

Receipt wording supports the record of money received, especially when the office needs a clean audit trail across deposit, progress and final payment stages.

This matters because customer communication is not separate from job control. In Fencify, the message timing, stage changes and financial steps all stay closer to the same lead, quote, project and invoice history.

Practical fencing example and the checks that keep the workflow clean

Imagine a residential colourbond replacement job that begins as a website enquiry. The estimator prepares the quote, sends it with the main quote template, and adds a follow-up schedule for later in the week. The customer opens the proposal but does not decide immediately, so the office uses the follow-up wording rather than sending a brand new manual message from scratch.

Once accepted, the project team sends a project update with install timing and a portal link. A site issue later requires an extra retaining detail, so the office sends a variation request using the dedicated project template instead of burying that request inside a casual update. After installation, the handover request goes out with the completion wording already prepared. The accounts person then sends the invoice, monitors the balance due, and issues a payment receipt after the final payment comes through.

That whole sequence stays easier to manage when every stage follows the same review habits:

• choose the template that matches the job stage instead of editing the wrong one each time
• check placeholders against the actual record before sending
• confirm the audience, especially on neighbour and portal messages
• check quote, project or invoice status before scheduling more follow-up
• keep variation and handover requests tied to the correct project step
• review overdue invoices before another reminder leaves the office
• keep receipt wording clear when a payment covers only part of the total job value

If you want one final discipline for this workflow, make it this: always start from the record that owns the communication. Open the quote for sales-stage messages, the project for delivery-stage messages, and the invoice or payment record for finance-stage messages. That keeps the communication aligned with the right customer, the right amount, the right action and the right stage of the fencing job.