One workflow for leads, statuses and records
We connect forms on one website into a shared workflow: each new lead reaches the team’s chatbot and is also recorded in Google Sheets. Contact details, enquiry information, the form and available referral data are retained for follow-up.
The system provides mini-CRM functions: recording enquiries, applying agreed statuses and showing their current state. Your website can have one, several or, for example, 10 forms; we agree on their connections and handling rules around your workflow.
When this workflow fits
Enquiries are scattered
Bring website form submissions into an agreed workflow.
Statuses are unclear
Give the team a shared view of handling and outcomes.
Source data is missing
Compare enquiries with available UTMs and website pages.
What we configure
| Component | What we do | Result |
|---|---|---|
| Website forms | Connect the agreed forms, map their fields and identify the form behind each lead. | Bring the required enquiries into one workflow. |
| Chatbot and buttons | Send lead details with buttons for agreed statuses such as Accepted, In progress and Rejected. | Your team updates an enquiry directly in chat. |
| Google Sheets lead register | Save a copy of each lead as a separate record: ID, submission time, contact details, form fields, available sources and current status. | A shared lead register for viewing, filtering and record keeping. |
| Status updates | Link the chat message and spreadsheet row through a lead ID. Changing a status with a button automatically updates the matching record. | Keep the current status without entering it again in the spreadsheet. |
| Sources and access | Record available UTMs, URLs and referrers; agree on users, fields and access to the register. | Understand lead sources and control access to contact details. |
How a lead moves through the system
A visitor submits a form
The form sends the agreed contact details and enquiry information.
The team receives a message
The bot delivers the lead with buttons, and a copy is saved in Google Sheets.
A team member selects a status
A button below the message sets the relevant handling stage.
The record updates
The matching Google Sheets row receives the lead’s current status.
Before launch, we agree on forms, fields, statuses and access, test data delivery and record updates, and show your team how to use the system.
What your team receives
- A shared Google Sheets lead register with the required fields and current statuses.
- Chatbot messages with convenient handling buttons.
- Automatic status updates from the bot to the matching lead records.
- Connections for agreed website forms and instructions for your team.
Explore a custom automation for an online store: OrderCheck for cart and purchase data validation.
Scope and pricing
Lead automation and management
One website: connect the agreed forms to a chatbot with status buttons and a shared Google Sheets lead register. Status changes automatically update in the spreadsheet. Form count and workflows are agreed before starting.
Starting package. Final scope, timing and fee are agreed before work begins.
We connect the agreed forms on one website. Before starting, we define the forms, fields, buttons, statuses and synchronization logic. The final fee depends on the scope and complexity of the connections.
External CRM connections, additional integrations, paid services, hosting and ongoing support are quoted separately.
What we need to begin
Share your website, forms and an example of how your team handles an enquiry today. Describe required statuses, owners and where data should be stored.
If website conversion measurement is also needed, consider web analytics setup. Discuss your lead workflow.