Example
Sort and prepare customer enquiries.
An illustrative workflow for email and form enquiries: collect them, spot missing details, prepare a reply, and keep sending under human control.
Illustrative example.
- 01 Input
- 02 Triage
- 03 Approval
- 04 Status
Approval stays visible
For enquiries that should not sit unseen.
This workflow fits when new requests arrive through several channels and the next step has to be sorted manually each time.
- Useful for email enquiries, forms, and messages that need triage before anyone replies.
- A first version collects the request, marks missing details, and prepares a follow-up or reply.
- Should you require complex routing rules across multiple departments or deep CRM configurations, we will scope a larger, separate project.
Typical sources / tools
The system only accesses the specific shared mailboxes and web forms where incoming customer leads are received.
- Contact form
- WhatsApp Business
- CRM
- Spreadsheet
Starting Point
Requests arrive by email, form, and informal messages. Key information is missing, status is unclear, and someone has to decide manually whether the next step is a follow-up, a quote, a callback, or an internal task.
The hard part is rarely one reply. The hard part is keeping the overview: what is new, what is waiting for information, what has already been answered, and where the next step sits.
First System
A shared intake view collects new requests in one place. The system spots missing information, suggests a category, and prepares the next step.
A scattered message becomes a reviewable request card: original text, short summary, missing information, suggested status, and a draft for the next reply.
Human Approval
You retain full control over every outgoing email: a team member reviews the generated draft, adjusts any specific details, and manually releases the reply for delivery.
Pricing, acceptance, rejection, and sending remain deliberate decisions. The system prepares the work, but it does not take responsibility away.
Result
The team can see in one place what is new, waiting, answered, and ready for the next step.
Whether fewer enquiries sit unseen, and how much upkeep the shared view needs, shows up in daily use. We look at both together after the first weeks.
Possible First System Scope
To start, we deliberately ignore complex corporate processes. A useful first prototype focuses only on these core elements:
- shared intake list for new requests
- status per request
- marker for missing information
- draft follow-up or next reply
- visible approval action
- short handover note for the team
Not Included
To keep this initial version manageable and quick to deploy, we exclude the following points from the first sprint:
- full CRM replacement
- automatic pricing decisions
- sending without approval
- cleanup of historical data
- legal or commercial evaluation of the request
Excerpt from a workflow and implementation plan
What should be decided before the first build.
This illustrative excerpt shows what you receive from the paid planning engagement. In a real engagement, its contents are derived from conversations, observed handovers, and anonymized cases from your operation.
Illustrative example, not a client project or binding proposal. Time and budget assume a simple enquiry flow without deep CRM customization.
Enquiries are triaged in several places.
Email, forms, and individual messages are read manually. Missing details, ownership, and the next action partly live in an inbox or in the knowledge of individual team members.
One shared intake view makes the next action visible.
Deterministic rules record the source and required details. Ambiguous content is structured as a reviewable suggestion. A person decides the category, follow-up, reply, and sending.
Keep the existing inboxes and add one bounded enquiry view.
The options compared are the current workflow, improving an existing tool, connecting existing systems, and a focused new build. For this example, the recommendation is to keep the inboxes and add one shared enquiry view. A plan can just as legitimately recommend clarifying first or deliberately not automating.
Visibility and approval become testable.
Example acceptance condition: every included test case shows an owner and next action. No outgoing message leaves the review path without documented approval.
Planning and implementation remain separate decisions.
Illustrative assumption: a one-to-two-week planning phase for 1,000 to 2,500 EUR. A subsequent simple build typically falls within 2,500 to 8,000 EUR. Dates and price become binding only after access and exceptions are clarified.
Access, data quality, and responsibility need resolution.
Open points include permitted inboxes, form formats, typical volume, duplicates, data protection, reply ownership, and unavailable-system behavior.
Evaluation sample
The cases we agree on before anything goes live.
For each of these, the expected behavior is agreed and checked before production use.
| Case | Expected behavior |
|---|---|
| Complete enquiry | Classify the request and prepare the next reply step. |
| Important detail is missing | Prepare a precise follow-up and keep the case visibly waiting. |
| The request is unclear or contradictory | Hand it to a person for classification without pretending the category is certain. |
| A price or contractual commitment is needed | Require explicit approval before any binding statement. |
| The enquiry looks like a duplicate | Flag the possible relationship without silently merging or creating a duplicate. |
From practice
How this approach continues in a real operation.
The Solar CRM is the internal system used in the solar installation business Paul Kahle also operates. The case study shows protected intake, clear responsibility boundaries, difficult exceptions, and controlled external handovers.
Read the Solar CRM case studyPrice Range
A workflow like this usually falls in the Automation sprint range: 2,500-8,000 EUR.
Automation sprintDoes scattered customer inquiry handling sound familiar? Let us check how we can bring structure to your inbox.