Roofing Referral Automation
Give Customers a Simple Way to Refer Your Roofing Business
A customer shares an approved link with someone they know who needs a roofer. The referred person chooses to request contact. The system preserves the attribution and assigns the inquiry. This workflow is distinct from public review requests.
The happy customer who had no way to refer you
A homeowner is thrilled with the new roof your crew installed. A month later, their neighbor mentions they need a roof replacement. The homeowner says, "You should call my roofer." The neighbor asks for the number. The homeowner cannot remember it off the top of their head and promises to look it up later.
Later never comes. The homeowner gets busy, forgets, and the neighbor searches online and picks a different roofer. Your company lost a warm referral not because the customer was unwilling, but because there was no easy way to share.
A referral link changes this. The customer shares a link with the neighbor. The neighbor clicks it, sees your company, and submits a request. The system records the referral source so you know who sent the lead. The customer did not have to remember a phone number. They just had to share a link.
Process diagram
Trigger, action, update, owner
Trigger
A customer is identified as eligible for a referral prompt.
Action
An approved referral link is provided to the customer with a simple way to share.
System update
The record moves to Referral Prompted with the share tracked.
Responsible person
The office manager owns the referral prompt coverage and the source tracking.
Trigger
A referred person submits a request through the shared link.
Action
The system creates a new inquiry with the referral source recorded.
System update
The new inquiry enters the pipeline at New Inquiry with the referral attribution logged.
Responsible person
The coordinator owns the assignment of the referred inquiry.
Trigger
The referred inquiry is assigned.
Action
The inquiry is routed to the defined owner following the standard routing rules.
System update
The record is updated with the assigned owner and the referral source is noted.
Responsible person
The assigned person owns the conversation from the assignment forward.
Trigger
The referred person does not submit a request.
Action
No contact is made. The share is tracked but no inquiry is created.
System update
The referral share is logged without a resulting inquiry.
Responsible person
The office manager owns the share tracking and the follow-up decision.
How the referral workflow behaves
The workflow starts with a referral prompt. A customer is identified as eligible: they had a completed job, they are opted in to messaging, and they have not already received a referral prompt recently. The system provides an approved link with a simple way to share it: by text, by email, or by copying the link.
The link carries a source identifier. When the referred person clicks the link and submits a request, the system records the referral source on the new inquiry. The coordinator can see which customer referred the new lead. The attribution is preserved from the share to the inquiry to the booking.
The referred person chooses to request contact. They submit a request through the shared link, which means they opted in to being contacted. If they do not submit a request, no contact is made. The referral flow does not scrape contacts or reach out to people who did not request it.
The referred inquiry is assigned following the standard routing rules, not a separate referral-only path. A residential referral goes to the residential coordinator. A storm referral goes to the storm team. The referral source is noted on the record so the team can thank the referring customer if appropriate.
Any referral incentive must be supplied and approved by your business. The default flow has no invented reward. We do not create a reward program on your behalf. If you have an approved incentive, we build it into the workflow. If you do not, the referral flow asks the customer to share without offering a reward.
Exception handling
When the referred person does not submit a request
A customer shares the referral link with their neighbor. The neighbor clicks the link, looks at your company's page, but does not submit a request. Maybe the timing is not right. Maybe they are still gathering estimates. Maybe they decided to wait.
The system logs the share without creating an inquiry. No contact is made with the neighbor because they did not request it. The office manager can see the share in the referral tracking, and the team can decide whether to follow up with the referring customer to see if the neighbor is still interested. The referral flow respects the referred person's choice not to request contact.
Deliverables
What RoofMaxing builds
Approved referral link
A shareable link with a source identifier that preserves attribution from the share to the inquiry.
Referral prompt
An approved prompt that provides the link with a simple way to share by text, email, or copy.
Attribution tracking
The referral source recorded on the new inquiry so the team can see which customer referred the lead.
Inquiry assignment
Referred inquiries assigned following the standard routing rules, with the referral source noted.
Opt-in respect
Contact made only with referred persons who submit a request through the shared link. No scraped contacts.
Incentive handling
Any referral incentive built in only when supplied and approved by your business. The default flow has no invented reward.
What your team supplies
Inputs we need from you
- Your approved referral prompt content
- Your referral incentive if you have one approved
- Your routing rules for referred inquiries
- Your eligibility criteria for the referral prompt
A sample referral share
Illustrative sample
Referral prompt to customer
Hi David, glad you are happy with the new roof. If you know someone who needs a roofer, here is a link they can use to reach us: [referral link]. We will take good care of them.
Referred person's page
David thought you did a great job on his roof. Tell us about your project and we will get back to you. [Form: name, phone, address, project type]
Illustrative sample. Shows the referral share format. No real customer data.
Measurement
What we measure
Each measure is defined in plain language. Baselines start as "Set your baseline" until your data is connected. The review period is agreed with your team.
—
Referral requests
The count of referral shares initiated by customers during the review period, by channel.
—
Opted-in referred inquiries
The count of new inquiries submitted through a referral link, with the referral source recorded.
—
Resulting appointments
The count of referred inquiries that reached a booked inspection, tracked from the referral to the booking.
—
Referral source breakdown
The breakdown of referred inquiries by the referring customer, showing which customers are generating referrals.
Software and access
Referral automation connects to your CRM, your SMS and email channels, and your lead capture process. We assess your current setup during planning. Attribution depends on the referred person using the shared link. We plan the integration before promising a specific referral outcome.
Illustrated workflows
Approved case studies will appear once a real case is documented. Until then, these illustrated workflows show how the referral process connects to the rest of the system.
Questions
Common questions about this service
- No. The referral process is distinct from public review requests. A review asks a customer to share their experience publicly. A referral asks a customer to share your contact information with someone they know who needs a roofer. The two workflows are separate, with different triggers, different messages, and different tracking.
Plan the Next Step for Your Roofing Business
Use a 30-minute strategy session to walk through the workflow that needs attention and discuss how RoofMaxing can help.
30 minutes. For roofing owners and operating leaders.