Inquiry workflow kit: bilingual briefs, handoff tables and examples
Inquiries arrive through inboxes, websites and WhatsApp. Define a process, its output and approval points so a salesperson can take over with confidence.
Three steps to describe one process
- Download and extract the kit. Choose one process to improve first.
- Fill in known conditions; leave unknowns as “to confirm”. Use the blank CSV to agree handoff fields.
- If you want an assessment, voluntarily share a redacted brief via WeChat or WhatsApp to discuss scope, access and acceptance.
Read the 12 brief fields before downloading
These fields match B01–B12 in the kit. This is a reading version, not a submission form.
| ID | Question |
|---|---|
| B01 | What should improve first: classification, extraction, translation, reply drafts or salesperson handoff? |
| B02 | Who handles it today, using which inbox, spreadsheet or business system? Roughly how many inquiries per day and in which languages? |
| B03 | What triggers the workflow, and what must not trigger it? |
| B04 | Which input materials are permitted? What are their versions, owners and sources? |
| B05 | Which output fields, format and recipient are needed? How will the source be retained for review? |
| B06 | Who approves each action: price, delivery date, commitments, sending and system updates? |
| B07 | Which accounts, APIs and permissions are available? Which are read-only or writable? Which eligibility requirements or costs still need confirmation? |
| B08 | How should missing data, conflicts, duplicates or API failures be flagged and handed to a person? |
| B09 | Which approved samples will be used for acceptance? Define expectations for fields, sources, missing data, approval and failure paths. |
| B10 | What is explicitly outside the first phase? |
| B11 | Who maintains materials, handles exceptions and approves updates? How will provider usage costs and maintenance be agreed? |
| B12 | What is still missing, and who will confirm it? You may separately provide a business contact if you wish. |
Inside the kit
- Bilingual guide: steps, file formats and links to website resources.
- Chinese and English briefs: B01–B12 plus a pre-sharing checklist.
- A blank handoff CSV, fictional example CSV and bilingual workflow JSON.
- Partner referral guide: a way to describe a need, not evidence of an existing partnership.
Fictional example: turn “please quote” into reviewable information
When an inquiry asks only for a price, flag missing product, quantity and destination details. Organize known information with sources for the salesperson to review. Price, delivery, commitments and external sending still require approval.
This fictional process illustrates inputs, outputs and review boundaries. The kit does not connect to inboxes, send messages or update a CRM.
Use your own tools
Open Markdown in a text editor; JSON is for technical colleagues. CSV uses UTF-8 with a BOM and comma separators. If it opens in one column, import it as a comma-delimited CSV. Compatibility depends on your software version.
Share only redacted material you are entitled to share. Keep customer lists, original inquiries, commercial documents and credentials out of public repositories. This kit is not a quote, contract or integration commitment. Costs and maintenance depend on the actual project.
Maintained by Chenfeng AI. This is general guidance for scoping a discussion; project feasibility, security, compliance, price and timing require assessment against actual conditions.