Text-message consent
SMS terms for Toronto roofing request updates
No SMS program is active in this prototype. The form records a preferred contact method and separates permission to discuss a request from optional marketing consent. Production messaging requires verified sender details and compliant workflows.
Request a roof assessment ↗
01 / Text-message consent
Operational messages relate to a submitted roofing request
If enabled, operational texts may ask for access details, confirm an appointment or communicate project information. Consent to operational contact is tied to the request.
The practical result is a record the owner can review: which roof zone is involved, which details were accessible, what evidence supports the recommendation and what remains outside the present scope. That record is especially important on Toronto roofs where additions, neighbouring walls, interior access or different material generations can change the apparent boundary.
Before authorization, the verified operating company should convert that record into a written document with materials, preparation, exclusions, site protection, schedule assumptions and change control. No web page can replace the property-specific estimate, contract or current public requirements.
02 / Text-message consent
Marketing permission is separate and optional
A marketing checkbox must not be preselected. Declining promotional messages cannot be used to block a legitimate service request.
The practical result is a record the owner can review: which roof zone is involved, which details were accessible, what evidence supports the recommendation and what remains outside the present scope. That record is especially important on Toronto roofs where additions, neighbouring walls, interior access or different material generations can change the apparent boundary.
Before authorization, the verified operating company should convert that record into a written document with materials, preparation, exclusions, site protection, schedule assumptions and change control. No web page can replace the property-specific estimate, contract or current public requirements.
03 / Text-message consent
Frequency, charges, help and opt-out details
Before launch, the operator must publish program name, expected frequency, message and data-rate notice, HELP and STOP handling, carrier terms and a monitored support contact.
The practical result is a record the owner can review: which roof zone is involved, which details were accessible, what evidence supports the recommendation and what remains outside the present scope. That record is especially important on Toronto roofs where additions, neighbouring walls, interior access or different material generations can change the apparent boundary.
Before authorization, the verified operating company should convert that record into a written document with materials, preparation, exclusions, site protection, schedule assumptions and change control. No web page can replace the property-specific estimate, contract or current public requirements.
04 / Text-message consent
Consent records need context
The production system should retain the wording shown, time, source and contact submitted so the operator can demonstrate what permission was given.
The practical result is a record the owner can review: which roof zone is involved, which details were accessible, what evidence supports the recommendation and what remains outside the present scope. That record is especially important on Toronto roofs where additions, neighbouring walls, interior access or different material generations can change the apparent boundary.
Before authorization, the verified operating company should convert that record into a written document with materials, preparation, exclusions, site protection, schedule assumptions and change control. No web page can replace the property-specific estimate, contract or current public requirements.