Follow one request through the workflow
A design agency receives a website inquiry from a company seeking a new site. The form captures the website, requested outcome and timeline. The workflow checks the submission ID to avoid duplication, matches an existing CRM contact, and creates one opportunity with a named owner. The visitor can select a discovery call; the booking event updates that opportunity. A request for a service the agency does not offer goes to manual review rather than an automatic sales sequence.
- 01Receive website inquiry
- 02Match contact and route request
- 03Offer a discovery call
- 04Record booking and next owner action
If the normal path fails: If booking is abandoned, the record stays “inquiry received.” An assigned person decides the next action; an acknowledgment is not counted as a held call.
Where this approach stops
- A calendar booking does not establish budget, authority or project fit. Those remain discovery questions.
- Stop follow-up when the prospect replies or opts out; do not start overlapping sequences from different tools.
What changes the cost
A single form, CRM and owner rule can fit the $1,500 starting scope. Multiple lead sources, territory rules, calendar reconciliation and recovery commonly require a broader $2,500–$5,000 scope. These are GoodHandoff planning ranges, not a fixed quote.
Acceptance checks before launch
| Test input | Expected result |
|---|---|
| Same form submitted twice | One opportunity; repeated submission linked to it. |
| Existing client requests help | Route to the client owner instead of new-business outreach. |
| Call is cancelled | Update the opportunity and stop treating the call as booked. |
Capture enough to make the next decision
For a marketing, creative, or other project-based agency, an inquiry often needs a service match before it needs a sales sequence. Capture the prospect’s contact details, requested service, project context, and intended timing. Ask about budget only when it helps your team route the conversation.
The website should explain who the agency helps and what the first conversation covers. The automation begins after the person submits the inquiry. It cannot compensate for an unclear offer, and it should not invent missing details to make a lead look qualified.
Use explicit routing before adding AI scoring
Start with rules the team can explain: service requested, location if relevant, project timing, or an existing-client match. Route uncertain submissions for human review. An AI summary can help someone read a long brief, but a generated score should not silently discard a potential client.
Keep qualification evidence visible. If someone states a budget or deadline, save that statement with its source. A short summary should distinguish what the prospect said from what the system inferred. Let the team correct routing without editing several different records.
An example: a website redesign inquiry
Illustrative workflow: a company submits a redesign brief. The workflow creates or matches the CRM contact, attaches the inquiry to an opportunity, and assigns the website-service owner. An acknowledgment explains what happens next. A task keeps the opportunity visible until a person reviews it.
For a clear fit, the team can send the appropriate discovery-call link. Store a separate booked status only after the calendar confirms the appointment. If the prospect reschedules or cancels, update that status and the follow-up task. An email containing a calendar link is not a booked meeting.
Make follow-up respect the conversation
Define a limited follow-up sequence with stop conditions. A reply, booked call, explicit decline, or request not to be contacted should change what happens next. Keep direct human replies visible so an automated message does not ask a question the prospect already answered.
Preserve the page and campaign source when available, but do not put personal information into analytics URLs. Source data helps compare qualified inquiries from a service page, a guide, or a referral. It is less useful to optimize for total submissions when most are irrelevant.
- Duplicate inquiry: update the existing opportunity or flag for review.
- Existing client: notify the account owner.
- Unclear fit: create a review task instead of an automatic rejection.
- Failed CRM save: retain the inquiry and alert the owner.
- Booked or declined: stop the pending invitation reminders.
Measure held calls and useful opportunities
Track inquiry-to-review time, qualified inquiries, booked calls, held calls, proposals, and paid projects as separate stages. A higher reply count can conceal poor qualification. Review a sample of lost or stalled inquiries to learn whether the offer, routing, timing, or follow-up needs work.
A good first build connects one website form, one CRM pipeline, and one ownership rule. GoodHandoff projects start at $1,500 for a narrow workflow; calendar synchronization, multiple pipelines, and more complex qualification need an agreed scope. Bring the form, your CRM stages, and one example of an inquiry that slipped through.
Put this into practice.
Bring your workflow to a short conversation. We’ll review the problem and identify whether a scoped project makes sense.
Talk through your workflow →