From first question
to a clearer next step.

In this video, we'll go over how Maple Hollow organizes a new inquiry and gives the owner a clear next step.

Here is the inquiry workflow. A submission from the private demo form creates an opportunity. In the pipeline, Morgan Demo appears under New inquiry, with the form recorded as the source.

An internal task can prompt the team to review the original request, service fit, and urgency. This recording draft illustrates that next step. It has not been activated, and it does not demonstrate a delivered owner notification.

The owner can use these details to decide which requests need attention first. Prioritization should follow agreed business rules. Your website starts the conversation; the customer system helps keep it organized.

In this video, we'll go over a sample follow-up workflow and the checks that keep the next step relevant.

This unpublished Maple Hollow draft starts with a dedicated demo tag, then waits one day. Before the email step, it checks for a booking tag. If that tag is present, the contact takes the end branch.

Otherwise, the draft includes a short consultation email asking about the customer's home repair request and preferred time. Stop on response is enabled for replies to messages from this workflow.

Before a real launch, booking activity must apply the right tag, and the sender, consent, and timing must be configured and tested. This is a configuration walkthrough, not a message-delivery test.

In this video, we'll go over how a customer chooses a consultation time and how the booking appears in the owner's calendar.

Maple Hollow offers available consultation times from the connected calendar. The customer picks a time, then provides a name and email address right inside the chat.

The assistant confirms the consultation for Tuesday at nine a.m. Central. This example books a consultation to discuss the repair, rather than promising a completed service visit.

The owner's appointment record shows Alex Video Demo, the same date and time, and a confirmed thirty-minute consultation. The booking is connected to the customer record, so the team can see the next step.

In this video, we'll go over a sample review-request workflow for following up after a completed visit.

The trigger watches the Visit completed stage in the Maple Hollow demo pipeline. The next step contains a short text message thanking the customer and inviting honest feedback.

For this fictional business, the message links to a private demonstration page. It does not post a real Google review. A client implementation would use that business's own review link and appropriate messaging consent.

The request should welcome feedback from every eligible customer, without filtering by satisfaction or offering incentives. This workflow stays unpublished for the walkthrough; no message delivery is being claimed.