Business Configuration Guide

Business Configuration lets you tailor how Tint Wiz creates proposals, generates invoices, prepares project sheets, and displays your calendar. It also controls defaults for customer appointment messages, proposal follow-ups, project types, and more.

Use this guide to understand each option, choose settings that match the way your business works.

Open Settings > Configuration for the business you want to update. Make your changes, then select Save at the bottom of the page.

Important: Defaults and display settings behave differently. A default generally applies when you create a new proposal, invoice, project, measurement, or appointment. Changing that default does not automatically rewrite existing records. Display settings and shared text can affect existing documents when customers view them again. The sections below explain the distinctions that matter for each option.

Sets the displayed height of your business logo on proposals and Tint Wiz invoices. Choose a whole number from 40 to 100; the default is 40. This changes the size of an existing logo, not the logo image itself.

Example: Set the height to 70 if your logo contains small lettering that is difficult to read at the default size.

Use cases:

Important: Upload or replace your logo in Business Info. This setting applies to image logos and does not turn your business name into a larger text logo. QuickBooks-generated invoices use QuickBooks' own document settings.

Opens the service-management area. Use it to maintain the services you offer rather than entering the same service details repeatedly. This is a shortcut to a separate settings area, not an on/off configuration option.

Example: Maintain reusable services for old-film removal, windshield protection, or installation labor.

Use cases:

Important: Service setup is separate from invoice itemization. To place project services on separate generated invoice lines, use Itemize Services in the Invoices section.

Sets the default expiration period for new proposals. Enter a whole number from 1 to 365, or leave it blank for no expiration. Individual proposals can use a different expiration period. A canned proposal with its own expiration period takes precedence; a canned proposal without one uses the business default.

When a proposal expires, the customer can no longer approve it. Sending or resending the proposal recalculates its expiration using that send's expiration period.

Example: Choose 14 when your supplier's pricing is only reliable for the next two weeks.

Use cases:

Important: Expiration uses calendar days in your business's time zone, not an exact number of 24-hour periods. A proposal sent on October 1 with a one-day expiration remains valid through October 2. Its displayed expiration date is the last valid local date. Changing the business default does not change existing proposals.

Opens the reusable proposal-template area. Canned proposals can contain predefined solutions, services, pricing, notes, approval instructions, deposit settings, and expiration settings. This link opens a separate management screen; it does not apply a template automatically.

Use cases:

Important: Review the template's settings when applying it. A canned proposal can supply its own deposit, expiration period, and approval content, so the result may differ from the business defaults.

Adds shared text to the approval section of proposals. The field allows up to 2,000 characters. Proposal-specific notes appear in the same section in addition to the business notes.

Example: "Please confirm film selection and access arrangements before approving. Installation dates are confirmed separately."

Use cases:

Important: These are shared business notes, not a permanent copy saved into each proposal. Updating them can change the text shown on existing proposal links. Their visibility after approval is controlled by the next option.

Keeps the approval-section notes visible after the customer approves, provided you have entered Proposal Notes above. It is off by default. This setting also keeps a proposal's introductory text visible after approval when that introduction is present.

Use cases:

Important: Enter business Proposal Notes to keep the approval notes section visible. Enabling this checkbox alone does not preserve that section when the business notes field is empty. The introduction's visibility is handled separately by the same checkbox.

Changes the hint inside the customer's approval comments box. The field allows up to 250 characters. The hint disappears when the customer types and is not submitted as their response.

Example: "Add your preferred installation days or any access instructions."

Use cases:

Important: A placeholder is a prompt, not a required question. It does not force the customer to provide comments. Put essential terms in Proposal Notes or Proposal Fine Print rather than relying on placeholder text.

Displays shared small-print text at the bottom of proposals. The field allows up to 2,000 characters and is separate from the approval notes.

Use cases:

Important: This is customer-visible shared text. Changes can affect existing proposal views. Have your business's terms reviewed appropriately; adding fine print is not the same as collecting a separate signed agreement.

Adds up to three labeled links at the bottom of proposals. Enter both a label and a destination URL for each item. Use a complete address such as https://example.com/terms.

Use cases:

Important: Keep linked pages accessible to customers. A private staff document or a link requiring an account may not be usable by the recipient. These links are shared across proposals, not specific to an individual job.

Adds up to two label-and-value entries in the proposal's upper-right information area. A plain-text value displays beside its label. A valid URL becomes a clickable link using the label as the link text. Both the label and value must be filled in for an entry to display.

Examples: Label: "Contractor License"; value: "LIC-123456". Label: "Preparation Guide"; value: "https://example.com/preparation".

Use cases:

Important: These values are business-wide. Do not enter a purchase-order number or private instruction that belongs to only one customer.

Shows a short notice at the top-right of the proposal header, above the business contact information. The field allows up to 50 characters.

Use cases:

Important: This space is intended for a brief notice. Use Proposal Notes, Fine Print, or Footer Links for longer explanations.

Shows a name-entry field on the customer's approval form. It is on by default. The submitted name is saved with the proposal approval.

Use cases:

Important: This is a typed name, not a drawn signature or identity-verification process. For a separate signing workflow, use the appropriate document-signing tools.

Makes the approval name field mandatory in the customer-facing form. It is off by default and only applies when Show Name Field on Approval is enabled.

Use cases:

Important: Enable both checkboxes together. Selecting Required while hiding the name field does not give the customer a visible field to complete.

Hides the detailed room measurement display in the customer-facing room-based proposal scope. It is off by default. Room names remain visible, with a summary of items or panes instead of the expandable measurement detail.

Use cases:

Important: This is a presentation setting, not a change to measurements or pricing. It does not erase measurements, hide every part of the scope, or control invoice descriptions. Invoice measurement visibility has its own option.

When Hide Measurements on Proposals is enabled, replaces the room's descriptive item summary with just the pane count, such as "8 panes." It is off by default.

Use cases:

Important: This option depends on Hide Measurements on Proposals. On its own, it does not replace the normal detailed measurement display.

Routes replies to a proposal email to the account email of the staff member who sent it. It is off by default; otherwise replies use the business's reply-to email. If the sender's email is unavailable, the business reply-to address remains the fallback.

Use cases:

Important: Reply-to is not the email's sending address. This setting does not change the sender's login, the business email displayed on the proposal, or the reply routing of every other automated email.

Displays the project's custom name, when present, above its identifying details on the proposal. It is off by default.

Use cases:

Important: Project names become customer-visible when enabled. Leave this off if your team uses names for internal comments, sales priorities, or other information customers should not see.

These three independent checkboxes control which business contact details appear in the proposal header. They do not change the saved business details.

Use cases:

Important: Update the actual contact details in Business Info. Hiding an email address here does not change where email replies go. Business contact information appears in the header; do not rely on the configuration screen's left/right description for its exact position on every layout.

These independent checkboxes control customer and job contact details shown in the proposal information area. The customer name is included automatically.

Use cases:

Important: These are display controls only. They do not remove contact data or stop proposal emails and text messages.

Sets the deposit request copied into new standard proposals. Available when Stripe or TintWizPay is enabled. Choose No Deposit, a listed percentage, or a listed fixed amount in your business currency. Canned proposals and individual proposals can have their own deposit settings.

The customer is asked to pay after approving. Percentage deposits use the approved total, including tax when applicable. A paid deposit is recorded on the project and applied as a payment when an invoice is created, reducing the balance due rather than reducing the price of the work.

Example: A 25% deposit on an approved, tax-inclusive total of $1,200 requests $300.

Use cases:

Important: Proposal approval and deposit payment are separate steps. An approved proposal does not mean the deposit has been paid. Changing this default does not add deposits to existing proposals. The calculation does not request a deposit when the approved pre-tax total is below 5; do not choose a fixed deposit larger than the job total.

Customizes the deposit request displayed after approval. The field allows up to 300 characters. Include :amount to insert the calculated deposit with the business currency symbol.

Example: "Please pay :amount to reserve your installation. We will confirm your appointment after payment."

Use cases:

Important: The message does not create a reservation or schedule an appointment. It is shared customer-facing wording. When an unpaid deposit is due, the deposit request takes the place of the normal approval message and scheduling button until that payment step is cleared.

Customizes the confirmation shown after approval when a pending deposit request is not being displayed. Without a custom message, Tint Wiz confirms approval and says your team will contact the customer to schedule. An individual proposal's approval message takes priority over this business default, including content brought in from a canned proposal.

Example: "Thank you for approving. Our office will call you within one business day to confirm an installation date."

Use cases:

Important: This is an on-screen confirmation, not an automatic appointment or a customizable approval email. The supported :approved_at placeholder inserts the approval date and time in the business time zone.

Adds a button below the approval confirmation. Enter a clear label and a full website or scheduling URL. A proposal-specific approval link takes priority over the business-wide link. If a link has no custom label, the button reads Click Here to Continue.

Examples: Label: "Choose an Installation Time"; URL: your booking page. Label: "Read Preparation Instructions"; URL: your customer preparation page.

Use cases:

Important: This button opens another page; it does not create a Tint Wiz appointment or synchronize a booking by itself. Test the destination as a customer, especially when using different links for different services.

Automatically opens the approval link shortly after a successful approval. It is off by default. The redirect requires a valid approval link and runs on the immediate post-approval confirmation, rather than every time someone later reopens the proposal.

Use cases:

Important: Customers may leave before reading a long approval message. Keep essential instructions on the destination page too. If an unpaid deposit request is displayed instead of the approval message, the normal approval-link redirect is not shown at that stage.

Adds the customer's first name, last name, phone, and email as URL parameters to a proposal-specific approval link. It is on by default. The mobile number is used when available; otherwise the contact phone is used. External booking tools must recognize the parameters to prefill their forms.

Use cases:

Important: The business-wide fallback link currently does not receive these parameters. To use prefilling, set the approval link on the individual proposal or canned proposal and test the actual booking page. Acuity and Calendly are named in the settings, but compatibility depends on the destination's accepted parameters. Contact details are included in the URL and may appear in browser history and the destination's logs, so only use trusted destinations.

Sends an automatic follow-up email approximately 24 hours after the proposal email was sent, if the proposal has not been viewed, approved, or expired. It is on by default. The recipient must have an email send recorded, and the contact must allow proposal follow-ups.

Use cases:

Important: This is email-only, not an SMS reminder or a daily repeating campaign. The follow-up is tracked once per eligible send. Automated checks run about every 10 minutes, so delivery is not guaranteed at the exact 24-hour mark. Enabling the option does not backfill every old proposal.

Sends an automatic follow-up email approximately 48 hours after a tracked customer view, if the proposal remains unapproved and unexpired. It is on by default. It requires an emailed proposal, a recorded view, and a contact who allows proposal follow-ups.

Use cases:

Important: The timer starts from the recorded view, not from the original send. This is separate from the unviewed follow-up, is not a repeating reminder series, and uses scheduled processing rather than an exact-time delivery guarantee.

Important: QuickBooks invoices have their own settings. If QuickBooks Online sends your invoices, most Tint Wiz layout and presentation settings below do not customize the QuickBooks invoice. Use QuickBooks to customize that version, or enable Send Tint Wiz Invoices to use Tint Wiz's customer-facing invoice while continuing to sync.

Appears when QuickBooks Online is connected. It is off by default. Enable it to send the Tint Wiz invoice instead of the QuickBooks version while retaining QuickBooks synchronization.

Use cases:

Important: This changes invoice delivery and presentation, not whether QuickBooks is integrated. Do not assume Tint Wiz appearance options also change the invoice stored or viewed in QuickBooks.

Shows Stripe's online payment button on eligible Tint Wiz invoices with an outstanding balance. It is on by default. The setting appears when Stripe is enabled and TintWizPay is not enabled.

Use cases:

Important: This is a Stripe-specific display control. It does not activate Stripe, control TintWizPay's payment button, or add a payment button to a QuickBooks-generated invoice. Paid invoices do not need an outstanding-balance payment button.

Requests a shipping address during Stripe invoice checkout. It is off by default and appears under the same Stripe-without-TintWizPay condition as the PAY NOW setting. The permitted shipping country follows the business's configured country.

Use cases:

Important: This applies to Stripe invoice checkout, not your general contact form or appointment location. Enabling it adds checkout work for the customer and does not automatically update the project's installation address.

Sets the leading description used when generating the main invoice line from a project. The field allows up to 50 characters. When blank, Tint Wiz builds its standard film-installation wording, which can include "Material and" when appropriate.

The generated line can also include job identity, approved scope, vehicle details, installation-event titles, services, and inventory item codes. This setting changes the opening wording, not all of that supporting content.

Example: Use "Window Film Installation" or "Automotive Tint Package" as your standard opening description.

Use cases:

Important: This does not rewrite existing invoice lines. Entering a single hyphen (-) or period (.) suppresses the generated opening phrase, but other generated job details can remain. Use the separate measurement and event-title settings to control those parts.

Defaults the invoice-generation workflow to separate approved project services into their own lines. It is off by default. The main installation line remains, with service amounts allocated to the additional lines rather than counted twice.

Example: An $800 project with a $100 approved removal service can produce a $700 main line and a separate $100 removal line.

Use cases:

Important: This itemizes approved services, not every pane, room, or vehicle area. Review the generated lines before saving. Changing this default does not split previously saved invoices.

Adds the title of the project's first active installation appointment to the generated invoice description, when that appointment has a title. It is off by default.

Example: An installation titled "After-hours access - North Lobby" can be included in the invoice description.

Use cases:

Important: Appointment titles become customer-visible through the generated description. Do not use private crew instructions as event titles if you enable this option. It does not add every appointment or retroactively update saved invoices.

Sets the default due date when preparing a new invoice. Choices are Upon Receipt, NET 7, NET 21, and NET 30. Upon Receipt is the default. NET terms add the selected number of calendar days to the invoice-generation date in the business time zone.

Use cases:

Important: Terms set a due-date default, not automatic collection, late fees, or a reminder campaign. Check the actual due date before saving, especially if you change the invoice date. Existing invoice due dates are not recalculated when you change the business default.

Selects the tax rate used as a default when preparing proposals and applicable project or invoice data. Choose a saved rate or No Tax. Tax-exempt contacts are handled separately. New invoices generally carry forward the project's existing tax details rather than replacing an agreed tax setup with a newly selected business default.

Example: Choose your normal sales-tax rate for local residential work, then review exceptions on individual jobs.

Use cases:

Important: This is not a location-based tax engine or tax advice. Confirm the correct treatment for each job. With QuickBooks connected, the default-rate list only includes rates linked to a QuickBooks tax code. Changing the default does not automatically recalculate existing proposals or invoices.

Opens the separate area for creating and maintaining named tax rates. A rate needs a name and a numeric percentage from 0 to 99.99. When QuickBooks is connected, rates also require a QuickBooks tax-code reference.

Use cases:

Important: You cannot delete the tax rate currently selected as the business default. First change Default Tax Rate to another rate or No Tax, save, then remove the old rate. Creating a rate does not make it the default automatically.

Removes the detailed measurement breakdown from descriptions generated for new room-based invoices. It is off by default. Room names and item summaries can still be included.

Use cases:

Important: This only changes newly generated descriptions. It does not remove measurements from the project, hide all job details, or edit an existing saved invoice. It is independent of Hide Measurements on Proposals.

Provides business-wide footer notes, up to 2,000 characters. How they reach an invoice depends on Save Notes with New Invoices below. When shared notes are displayed and no custom text is set, the standard footer says "Thank you for your business."

Use cases:

Important: Shared invoice notes can change on existing invoice views. Enable Save Notes with New Invoices when you need the wording copied into each new invoice instead of remaining shared live text.

Controls whether Invoice Notes are copied into newly generated invoices. It is off by default.

Use cases:

Important: Switching this setting also changes the shared-footer display on older invoices. Turning it on does not backfill notes into existing invoices. If an old invoice relied entirely on shared notes, those notes may disappear from its view after the switch. Review representative older invoices before changing the setting.

Adds up to two business-wide label-and-value entries in the invoice's upper-right information area. Both parts are required for an entry to appear. A valid URL becomes a clickable link using the label as its text; otherwise the label and value display as text.

Examples: "VAT Number" with your registration number, or "Payment Instructions" with a full HTTPS URL.

Use cases:

Important: These fields are shared across invoices, not custom fields for a particular customer. Use full URLs, and do not enter information that should only appear on one job.

Displays a short notice at the top-right of the invoice, above the business contact details. The field allows up to 50 characters.

Use cases:

Important: Use Invoice Notes for longer instructions. This notice is shared across Tint Wiz invoices and is separate from the document label below the logo.

Adds a custom document label beneath the logo in the invoice's customer-information area. The field allows up to 50 characters. It is optional; the example "TAX INVOICE" shown in the empty field is a prompt, not an automatically saved label.

Use cases:

Important: A label does not calculate tax or establish legal compliance. Configure the actual tax rate separately and confirm local invoicing requirements.

Sets the background surrounding the online Tint Wiz invoice. Enter a valid color value, preferably a hexadecimal code such as #E8EEF0. This does not recolor every invoice section or change the invoice's saved financial data.

Use cases:

Important: Select a named Invoice Text Font when applying a custom background. Background styling is applied alongside the custom font styling in the current online template. Preview the invoice after saving. The downloaded PDF uses a separate layout and does not use this background setting.

Chooses a typeface from the available font list for the online Tint Wiz invoice. Options include Open Sans, Lato, Montserrat, Nunito, Roboto, and many others. Default leaves the standard invoice styling in place; you cannot upload an arbitrary font through this control.

Use cases:

Important: The downloaded invoice PDF uses its own standard font. The online font is loaded from Google Fonts, so appearance can fall back if external fonts are blocked or unavailable. Preview real invoices rather than assuming the PDF will match the online typography.

These independent checkboxes control business contact details in the Tint Wiz invoice header.

Use cases:

Important: These controls change visibility, not the stored business information or email reply routing. Consider invoice-document requirements before hiding your business address.

These independent checkboxes control recipient details on the Tint Wiz invoice. The customer name remains included.

Use cases:

Important: A hidden email address does not stop invoice email delivery. These are presentation controls, and they do not automatically replace an invoice address with a customer's general contact address.

Adds custom payment-type choices to the payment-recording forms. Enter a comma-separated list, up to 500 characters, such as Venmo,Zelle,Customer Credit. Your entries are added alongside the built-in payment types rather than replacing them.

Use cases:

Important: A custom type is a reporting label, not a payment integration. Adding "Venmo" does not create checkout, move funds, or confirm that money was received. Use consistent spelling, avoid unnecessary spaces, and do not put commas inside a single type name.

Shows individual active payments, including their type and amount, on Tint Wiz invoices. It is off by default. When off, payments are summarized as one Paid total instead of a list.

Use cases:

Important: This only displays recorded payments. It does not create a payment, charge a card, or replace checking that payment records are accurate. It does not add a bank statement or a processor's full transaction details to the invoice.

Switches inventory roll-label output from the standard size to the larger format. It is off by default. The dimensions shown in Configuration depend on the business's country.

Use cases:

Important: Your printer and label rolls must support the selected size. Changing this option switches the generated label format; it does not resize physical labels already printed or change film-roll measurements. Print a test label before producing a batch.

Prefills the project type in the standard new-project workflow. Choices are Residential, Commercial, Automotive, Marine, or Default (Not Selected). The default is no selection. You can still choose a different type for a particular job.

Use cases:

Important: This does not convert existing projects or restrict your business to one type. Starting a project through a type-specific shortcut can take precedence over the general business default.

Prefills new projects as mobile work. It is off by default. This is especially relevant to automotive or marine jobs where work may happen at the customer's location instead of your shop.

Use cases:

Important: Mobile means the job's service location, not use of the mobile app. Check the project address before scheduling. This default does not provide routing, create travel time, or update older projects.

Changes the date shown beside a project in the contact's overview. When on, it shows the project's installation scheduling date. When off, it shows the project creation date. It is off by default.

Use cases:

Important: This changes the displayed date, not the appointment or project history. A project with no installation scheduled may not have an installation date to display.

Sets the default Round Up choice for new measurements. It is off by default and can be overridden on an individual measurement. When enabled, a measurement entry's calculated area is rounded up to the next whole area unit instead of retaining two decimal places.

Example: A measurement entry calculated at 12.34 square feet becomes 13 square feet with rounding enabled. An entry already at 12.00 remains 12.

Use cases:

Important: Rounding is applied to the calculated total for a measurement entry, including its quantity, not simply once to the entire project's final area. It can affect area-based pricing. It does not round the entered width and height, change measurement units, or recalculate every existing measurement when the business default changes.

Shows perimeter measurements on project sheets by default. It is off by default. The unit follows your business's measurement setup. For rectangular measurements, the perimeter represents the total edge length, including quantity, rather than square area.

Use cases:

Important: This is a sheet-display default, not an additional invoice charge. It is relevant to measured room-based work rather than automotive application areas. The sheet's own perimeter toggle can change the output for the current sheet.

Includes project appointment information on project sheets by default. It is off by default. The sheet can show appointment dates, times, titles, assigned staff, and descriptions. The sheet view also has its own Show Appointments toggle.

Use cases:

Important: Review event descriptions before sharing a sheet with a customer. They may contain internal instructions. Technician access remains subject to role restrictions; this setting does not grant extra appointment access.

Adds shared notes to printable project sheets. The field allows up to 2,500 characters and offers a formatting guide for the browser-rendered sheet.

Example: "Protect surrounding surfaces before starting. Confirm glass condition with the site contact. Leave aftercare instructions when complete."

Use cases:

Important: These notes appear on all applicable project sheets, not just one project. Do not include customer-specific or confidential information in the shared default. Formatting styles do not carry over to the PDF version, and raw HTML is not a reliable way to style the notes.

Sets the default SMS text staff can send from an automotive project when a vehicle is ready. The field allows up to 200 characters. Use :customer_name for the customer's first name and :vehicle_make for the vehicle make/model. If vehicle details are missing, the vehicle text falls back to "vehicle."

Example: "Hi :customer_name, your :vehicle_make is ready for pickup. Please contact us with any questions."

Use cases:

Important: Saving this template does not send a message automatically. Staff review the number and message in the vehicle-ready dialog and select Send Message. The business-name prefix and SMS suffix are added automatically; the template's character limit is not a guarantee that the final SMS fits in one segment.

Appointment communications have several layers. The business defaults determine the initial selections, each appointment has its own customer-notification choice, and reminder delivery also checks the contact's reminder preference. These options are separate from Settings > Notifications, which controls internal staff alerts.

Important: An enabled option is not a guarantee that both channels can deliver. Email needs a usable customer email address; SMS needs a usable mobile number and is subject to carrier delivery and recipient opt-outs. Customer messages require an appointment linked to a project/contact. Standalone "Other" calendar events are not customer-reminder appointments. SMS messages include a business-name prefix, an appointment link when available, and the business's SMS suffix.

Sets the default customer-notification selection when scheduling a new appointment. It is on by default. Staff can override the selection for an individual appointment.

Use cases:

Important: This is a default, not a master switch for every existing appointment or every message type. Changing it does not clear the notification choices already saved on appointments. The separate new-appointment and reminder options below must also be enabled for their respective messages. Cancellation notifications use their own setting.

Sends a customer notification after an appointment is first scheduled, when that appointment's customer-notification option is enabled. It is on by default. The notification is prepared at creation time; actual delivery depends on email/SMS processing.

Use cases:

Important: This option is for newly scheduled appointments. It is not a promise that every later date change, reassignment, or edit will trigger another customer notification. Check how you will communicate rescheduling rather than assuming the original creation notification repeats.

Customizes the main text used in the new-appointment SMS and email. The field allows up to 200 characters. Use :event_datetime to insert the appointment date and time.

Example: "Your installation is scheduled for :event_datetime. Please contact us if you need to change the appointment."

Use cases:

Important: This edits the message text, not the entire email template. The email still includes its greeting, applicable address, appointment button, and footer. The replacement date/time can be longer than the placeholder you enter. Customer-name variables are not supported in this field.

Enables the reminder sent approximately 24 hours before a scheduled appointment. It is on by default. Delivery requires the appointment's customer reminders to be enabled and the contact's appointment-reminder preference to allow them. Cancelled appointments are excluded.

Use cases:

Important: The schedule uses a processing window, not exact-to-the-minute delivery. An appointment created after its 24-hour reminder window has already passed does not get a retroactive day-before reminder. Disabling this option stops this reminder type for eligible appointments, including previously created ones that have not yet reached their send window.

Customizes the main text of the day-before SMS and email. The field allows up to 200 characters. Use :event_time for the scheduled start time.

Example: "A reminder that your appointment is tomorrow at :event_time. Please ensure access to all windows."

Use cases:

Important: Keep relative wording consistent with the reminder. "Tomorrow" is suitable for this day-before message, not the one-hour reminder. Editing the text does not turn on the reminder or override a contact's reminder preference.

Enables the reminder sent approximately one hour before the appointment. It is on by default. It has the same project/contact, appointment-reminder, and contact-preference requirements as the day-before reminder. Cancelled appointments are excluded.

Use cases:

Important: This is based on the appointment's scheduled start, not a technician's live location or arrival estimate. It is not an "on the way" message. Appointments created too close to their start may miss the reminder window, and delivery time can vary.

Customizes the main text of the one-hour SMS and email. The field allows up to 200 characters. Use :event_time to insert the start time.

Example: "Your appointment is today at :event_time. Please contact our office if you are delayed."

Use cases:

Important: Do not describe this as a guaranteed arrival time. The placeholder is the booked time, not live tracking. The reminder toggle and delivery requirements apply independently of this wording.

Sets the default for sending customer cancellation notifications on new appointments. It is on by default. The appointment stores its own cancellation-notification choice, which staff can review or override in the appointment/cancellation workflow.

Use cases:

Important: This is separate from Appointment Notifications / Reminders. Turning off the general customer-reminder default does not automatically turn off cancellation messages. Changing the business cancellation default does not rewrite the choice saved on existing appointments.

Customizes the main text of the cancellation SMS and email. The field allows up to 200 characters. Use :event_datetime to identify the cancelled appointment.

Example: "Your appointment for :event_datetime has been cancelled. Please contact our office to arrange a new date."

Use cases:

Important: Cancellation wording does not create a replacement appointment. Avoid promising a new date unless staff have actually booked it. A custom cancellation message is only sent when that appointment's cancellation-notification choice allows it.

The appointment-message replacement system supports these date/time placeholders in the configurable appointment messages:

Use cases:

Important: The settings screen recommends :event_datetime for new/cancel messages and :event_time for reminders, but the shared replacement system supports all three above. Use these exact placeholders. Do not assume proposal, vehicle-ready, or customer-name placeholders work in appointment messages.

Adds a shared ending to customer SMS messages that use the business messaging template. The field allows up to 50 characters. Use it for your preferred contact instructions.

Example: "Call 555-123-4567 for changes."

If no custom suffix is supplied, Tint Wiz uses the business phone number when available. The generated suffix also includes Reply STOP to opt out.

Use cases:

Important: The opt-out instruction is added separately and remains part of the generated suffix. This setting does not change the SMS sending number or the footer of emails. The message prefix, inserted variables, link, and suffix all add length, so a 200-character message field does not mean the final SMS will fit in one segment.

Controls whether the customer-facing appointment page offers a Cancel Appointment link for an upcoming, uncancelled appointment. It is on by default.

Use cases:

Important: This is not a configurable cancellation-policy engine. It does not set a 24-hour cutoff, charge a cancellation fee, or provide online rescheduling. The normal appointment page stops showing its cancel link once the appointment's start time has passed. Check recurring bookings carefully because cancelling one occurrence can also cancel linked recurring dates.

Changes the on-screen confirmation shown after a customer cancels their appointment. The field allows up to 500 characters.

Example: "Your appointment has been cancelled. Please call our office when you are ready to arrange a new time."

Use cases:

Important: This is the cancellation-page confirmation, not the cancellation SMS/email. It does not refund payments, schedule a replacement visit, or change your cancellation policy.

Hides the start time on the customer-facing appointment details page while leaving the date visible. It is off by default. The underlying appointment still has a start time for scheduling and reminders.

Use cases:

Important: This does not remove times from SMS or emails. Time-bearing placeholders such as :event_datetime and :event_time still insert the booked time. Review all appointment-message wording if the customer should only receive a date.

Changes the calendar's first day from Monday to Sunday. It is off by default.

Use cases:

Important: This changes calendar layout, not appointment dates, working hours, or the business time zone.

Hides the map when opening the calendar. It is off by default, and the map can still be toggled on when needed. Smaller-screen layouts also start with the map hidden to preserve space.

Use cases:

Important: Hiding the map does not remove addresses or disable mapping. It is a view preference, not a change to the location data saved on projects.

Excludes cancelled appointments from the calendar. It is off by default. Cancelled appointments remain part of their projects rather than being deleted.

Use cases:

Important: Hidden cancelled appointments are still records. Use the project to review them; hiding them does not erase history, reverse payments, or remove cancellation notifications already sent.

Sets the initial appointment length when scheduling. The app default is 2 hours. The menu provides 15 minutes to 12 hours, using 15-minute increments below six hours and 30-minute increments from six hours onward. Staff can adjust individual appointments.

Use cases:

Important: One business default cannot represent every service duration. It does not update existing appointment lengths, calculate travel time, or prevent staff from overlapping events. Calendar Slot Duration below controls the grid, not booking length.

Changes the initial calendar filter for consultants and installers from their own events to all events. It is off by default. Administrators already start with an all-events default.

Use cases:

Important: This is a default filter, not a permission change. It does not grant technician-role users unrestricted calendar access. Remembered filters can take precedence, so a returning user's calendar may retain their previous selection.

Opens the calendar on today's date instead of restoring the date last viewed. It is off by default.

Use cases:

Important: Staff can still navigate to other dates. This sets the initial date; it does not continuously snap the view back to today while someone is working.

Marks unassigned appointments with a red UNASSIGNED tag on the calendar. It is on by default.

Use cases:

Important: The tag is a visual warning only. It does not assign a staff member, notify a dispatcher by itself, or prevent saving the appointment. Use Assignee Required when an assignment should be requested during creation.

Requires staff to select an assignee when creating an appointment through scheduling. It is off by default.

Use cases:

Important: This does not automatically assign staff or check their availability. It does not repair existing unassigned appointments, and should not be treated as a guarantee that later edits cannot leave an appointment unassigned. Check your team's role and assignment options before enabling it.

Shows available public-holiday entries on the calendar. It is on by default. Holiday information depends on the selected country/year and the external holiday data available to Tint Wiz.

Use cases:

Important: Holiday markers do not close your business or block bookings. They are not a complete company closure calendar, and not every local or regional observance is guaranteed to appear. Add your own time-off or closure entries where needed.

Sets the size of the calendar's time-grid intervals. Choices are 5, 15, 30, or 60 minutes; the app default is 30 minutes.

Use cases:

Important: Grid spacing is not appointment duration. This does not shorten or lengthen appointments, enforce service times, or create a booking interval rule for an external scheduling system.

Enlarges the calendar's time-grid rows. Choose App Default or 125%, 150%, 175%, 200%, 225%, 250%, 275%, or 300%. Larger rows give events more visual space.

Use cases:

Important: Larger rows can require more scrolling. This changes visual spacing, not appointment length, text content, or the total hours displayed.

Sets the earliest visible time in the calendar's time-grid view. The default is midnight, showing the full day. Custom choices run from 1:00 a.m. through noon in one-hour steps.

Use cases:

Important: This is a visibility limit, not a booking restriction. An appointment scheduled earlier can exist but be outside the visible calendar range. Keep the full day visible if early or overnight appointments are possible.

Sets the latest visible boundary in the calendar's time-grid view. The default is midnight at the end of the day, showing all hours. Custom choices run from 1:00 p.m. through 11:00 p.m. in one-hour steps.

Use cases:

Important: Bookings outside the visible range are not prevented. Events entirely after the end boundary may not be visible, and an event extending beyond it may be clipped. Use hours that cover all work your team might schedule.

Sets a custom calendar height from 500 to 1,000. The standard calendar starts at 600. This option is explicitly marked experimental and is intended to be considered together with visible start/end times.

Use cases:

Important: Leave this at the standard behavior unless you have a specific display need. Test on the desktop and mobile devices your team uses. This setting does not change event length, working hours, or staff access, and a fixed height may create additional scrolling.