Reference number
Your message was recorded before this reference number was issued.
Contact
Send a recorded service request
Share the service need, timing, and useful context. The form records your message before issuing a reference number.
What to include
Include the service requested, location or service area, timing, and any access notes the team should know before replying. After the message is recorded, keep the reference number and receipt hash as delivery evidence.
Receipt proof
What the visitor can keep
The capture flow is meant to be plain and clear: a recorded request, a reference number, a receipt hash on the enhanced path, and a fallback contact.
Receipt hash
A short value shown with the enhanced receipt for delivery evidence.
Fallback contact
demo@raymondporrello.com is listed in the footer and response commitment for follow-up with the reference number.
Response commitment
A recorded request gets a clear next step
This section sets a practical response expectation without promising more than the Cedar Ridge office can verify.
- Person or team
- Cedar Ridge office
- Response window
- One business day
- Fallback contact
- If one business day passes, email demo@raymondporrello.com and include your reference number.
The reference number helps the office trace the recorded message without asking you to resend every detail.
Proof-first form
Record the request and keep the receipt
The same form works as a plain post and as an enhanced receipt flow. A successful submission returns a reference number; the enhanced receipt also shows a receipt hash.
- Reference number
- Issued after the request is recorded.
- Receipt hash
- Shown with the enhanced receipt for delivery evidence.
- Fallback contact
- Use the footer contact and include the reference number.