Eight usable prompts with editable placeholders and Copy buttons. Each shows its purpose, the required inputs, the complete prompt, and a human review instruction. Outputs use only the supplied facts. This page does not run an AI model; copy a prompt into your own tool.
First response to a roofing inquiry
Purpose: Draft a clear first acknowledgment that sets the next step.
Required inputs
homeowner name
inquiry source
request type
response window
booking link
Prompt
You are helping a roofing company respond to a new inquiry.
Homeowner name: [name]
Inquiry source: [source]
Request type: [request type]
Response window: [window]
Write a short, plain message that:
1. Confirms the inquiry was received.
2. Names who will call and by when.
3. Offers the booking link as an option.
4. Includes an opt-out for texts.
Use only the facts above. Do not invent a price, a diagnosis, or a timeline.
Human review: A person checks the names, the window, and the opt-out before sending.
Open-estimate follow-up
Purpose: Reopen a conversation after an estimate has been sent.
Required inputs
homeowner name
estimate date
estimator name
booking link
Prompt
You are following up on a roofing estimate that has not received a reply.
Homeowner name: [name]
Estimate sent on: [date]
Estimator: [estimator]
Write a short message that:
1. References the estimate date.
2. Offers to walk through the scope or the numbers.
3. Provides a booking link for a short call.
4. Stops if the homeowner has already declined.
Use only the facts above. Do not pressure or invent a discount.
Human review: A person confirms the estimate is still open before sending.
Homeowner schedule update
Purpose: Inform a homeowner of a verified milestone during an active job.
Required inputs
homeowner name
milestone
new date
supervisor name
Prompt
You are writing a job update for a roofing customer.
Homeowner name: [name]
Milestone reached: [milestone]
Next step date: [new date]
Supervisor: [supervisor]
Write a short message that:
1. States the milestone that was reached.
2. Gives the next step date.
3. Names the supervisor as the contact.
4. Does not promise a time the crew has not confirmed.
Use only the facts above. If any detail is missing, say so and leave a placeholder.
Human review: A person confirms the milestone is verified and the date is correct before sending.
Neutral review request
Purpose: Ask for a public review after a verified completed job.
Required inputs
homeowner name
company name
review link
manager name
Prompt
You are writing a review request for a completed roofing job.
Homeowner name: [name]
Company: [company]
Review link: [review link]
Manager: [manager]
Write a short, neutral message that:
1. Confirms the job is complete.
2. Offers the review link.
3. Invites the homeowner to reply directly if anything was not right.
4. Does not gate negative feedback or offer a reward.
Use only the facts above.
Human review: A person confirms the job is complete and the link works before sending.
Review response
Purpose: Draft a professional reply to a public review.
Required inputs
reviewer name
review sentiment
company name
contact route
Prompt
You are drafting a response to a public roofing review.
Reviewer: [name]
Sentiment: [positive / mixed / negative]
Company: [company]
Contact route: [phone or email]
Write a short response that:
1. Thanks the reviewer by name.
2. Acknowledges the specific experience they described.
3. For negative reviews, offers the contact route to resolve it.
4. Does not argue, reveal private details, or promise a specific outcome.
Use only the facts above.
Human review: A person checks the tone and the contact route before posting.
Approved-input proposal outline
Purpose: Structure a roofing proposal draft from supplied measurements and rates.
Required inputs
measurements
material specs
labor rates
approved scope
Prompt
You are organizing a roofing proposal draft.
Measurements: [measurements]
Material specifications: [material specs]
Labor rates: [labor rates]
Approved scope: [approved scope]
Produce an outline with:
1. Project summary.
2. Materials and quantities.
3. Labor breakdown.
4. Total with the math shown.
5. Assumptions and exclusions.
Use only the supplied inputs. Do not perform engineering, confirm code compliance, or guarantee accuracy. Flag any missing input.
Human review: A qualified estimator checks every number and the scope before the proposal is sent.
Documentation organization for a reviewer
Purpose: Sort inspection notes and photos into a review-ready structure.
Required inputs
inspection notes
photo list
claim reference
Prompt
You are organizing roofing documentation for human review.
Inspection notes: [notes]
Photos: [photo list]
Claim reference: [claim reference]
Produce a structure with:
1. Claim reference and date.
2. Damage summary grouped by roof section.
3. Photo references tied to each section.
4. Missing-information flags.
Use only the supplied inputs. Do not determine coverage, create evidence, or negotiate the claim.
Human review: A qualified reviewer checks the structure and the flags before the file is used.
Commercial proposal cover note
Purpose: Draft a cover note for a commercial roofing proposal.
Required inputs
facility name
contact name
scope summary
proposal date
Prompt
You are writing a cover note for a commercial roofing proposal.
Facility: [facility name]
Contact: [contact name]
Scope summary: [scope summary]
Proposal date: [proposal date]
Write a short cover note that:
1. Addresses the contact by name.
2. Summarizes the scope in one sentence.
3. Names the proposal date.
4. Offers a walkthrough call.
Use only the facts above. Do not promise a timeline the team has not confirmed.
Human review: A person checks the facility name and the scope summary before sending.