Bosch Engineers Use Doubao Work Partner to Process Fault Reports: AI Draft Covers 70-80%, Value Lies in Post-Communication Rather Than Judgment Itself
R&D departments in automotive supply chain companies face a common dilemma: an engineer has to do the work of three people. They must monitor R&D details while also handling daily repetitive tasks. An engineer at a certain business unit of Bosch serves on a team that interfaces with various customers to provide comprehensive system solutions. For the same customer, different projects have different chat groups; if any issue arises during testing, road trials, or production, messages pop up one by one—specifying which project, which software, what fault code was reported, and what error occurred.
The engineer's previous workflow was as follows: gather messages scattered across various groups and private chats, integrate them into a complete description based on several dimensions such as project affiliation, software version, vehicle configuration, test conditions, error time, and diagnostic screenshots, and use experience to determine who to contact for troubleshooting. If explanations were unclear, meetings were held to clarify issues before issuing reports to customers. Half a day would pass before fault analysis even began.
Two things prompted him to make a change. First, knowledge accumulation is unreliable: experience resides in individual engineers' minds. While cloud documents and knowledge bases exist, everyone has different templates and habits, and when projects are busy, no one takes the time to input data. When personnel leave, experience is lost. Second, customers do not ask questions according to templates: problems occur in a streaming fashion, with messages constantly popping out. No one can provide fault codes, screenshots, and over a dozen fields all at once in a single message. If fragments cannot be collected completely, subsequent analysis remains stalled.
The addition of Doubao Work and Doubao Work Partner changed this path. The engineer configured scheduled tasks in Doubao Work to patrol private messages received, identify fault-related information, and forward it under their own identity to a dedicated topic group for problem reports. Customer communication habits did not need to change; matters scattered outside the process were pulled back into it. Once messages entered the dedicated group, each problem occupied an independent topic, naturally forming an interface for 'one matter, one discussion.'
Doubao Work Partner crawled historical context from the group, aggregated streaming fragments into complete problem descriptions, then called encapsulated report generation skills to produce drafts according to standard templates. Simultaneously, it registered entries in Feishu (Lark) Bitable, reminding the corresponding engineer to handle them. In one real problem-handling record, the AI organized messages into a Feishu document, marking the problem status as 'In Progress'; information such as drive form and driving mode, which was incomplete, was left as 'To Be Supplemented.' The engineer only needed to verify and fill in the draft, rather than starting from a blank document.
Some details could only be finalized during meetings. The engineer could invite Doubao Work Partner to attend problem communication meetings; it listened throughout and directly synchronized clarified information into the report after the meeting ended, eliminating the step of manual transcription between discussions, records, and reports. According to the engineer's own estimate, the AI draft could cover 70-80% of the content, leaving the remaining 20% for human judgment. After meeting conclusions supplemented the report, making it basically complete, it underwent one more round of manual review before being sent to the customer.
Fuentes:GeekPark