Our internal practice · Published 11 October 2026
From a website inquiry to a record the team can follow up.
We connected the ManDoNothing website to our existing Feishu CRM. The workflow receives an inquiry, gives it a reference, delivers it to a dedicated intake table and leaves qualification to a person. It is an example from our own operations, with deterministic integration rather than a model making sales decisions.
Discuss your workflow ↗The workflow
The form asks for a request and an email address. Name, company and phone or WeChat are optional. An inquiry can enter the workflow even when the visitor has not supplied a company name.
- Receive and validate the request, then assign a server-generated inquiry reference.
- Deliver the inquiry to the existing CRM intake table; the email and team notification paths remain in place.
- Track delivery by reference and check the stored record. Repeated delivery of the same reference is handled as the same inquiry.
- Start the CRM record as pending. A team member reviews it and decides whether to link it to a contact, company or opportunity.
What we verified
During the integration checks on 26 September 2026, concurrent delivery of the same inquiry reference produced one CRM record. An independent read checked the stored fields and pending status. This check used a marked test record; it did not establish a sales opportunity.
On 27 September 2026, the reporting integration read inquiry statuses and explicitly linked opportunities, excluding marked tests. It keeps received inquiries, qualified inquiries and recorded wins as separate measures.
Keeping useful source information
The website records the first published page visited in the current browser tab, a referring hostname when available, and limited campaign labels. That context travels with the inquiry reference to support page-level reporting.
These are browser-reported hints. Missing referrers remain unknown, and the workflow does not identify the search query used by an individual visitor. Raw URL query strings, fragments and advertising click identifiers are excluded from the attribution record.
What this practice demonstrates
It shows how an existing business system can receive work with clear identifiers, delivery checks and a human decision point. Those foundations are also useful when an AI agent is added to a workflow.
This integration does not use a model to qualify leads. It is not a customer case study or evidence of increased traffic, revenue or conversion. A fresh form submission receives a new reference; handling repeated delivery of one reference does not identify two different submissions as the same person.
Start with work worth improving.
Tell us how the work happens today, which systems it involves and what you want to change.
Discuss your workflow ↗