From Export Inquiry Form to an Internal Follow-Up Brief

Concept illustration; not a product screenshot or customer result.

A submitted inquiry may contain a product name but omit dimensions, order quantity or destination. Organizing the row is only the start: the sales team needs to know what is confirmed, what is missing and where each detail came from. The example below is a proposed process.

Identify the Inquiry

Keep the original record ID, submission time, buyer contact and source. Read attachments only when accessible. Treat matching contacts or similar wording as duplicate candidates, not proof that two requests are identical.

Separate Requirements and Commitments

Extract product, specifications, quantity, destination and requested delivery date. Mark missing units and contradictory dates. Leave the internal owner unassigned unless a source or your instruction identifies one. Prepare questions instead of inventing a price or delivery promise.

Hand Off a Reviewable Brief

Return a summary, unresolved questions and a proposed follow-up draft. Ask the reviewer to check the buyer and product details before external contact. Creating tasks, sending email or changing the source sheet needs the corresponding tool capability and authorization.

Task Prompt

Review [record IDs/time range] in [authorized source or supplied file]. Preserve IDs and sources. Extract purchase requirements, flag missing fields and possible duplicates, and draft questions. Distinguish requested dates from confirmed commitments. Return an internal brief only.

Start manually. After checking a sample, a scheduled read can review new records using a defined window and processing ledger. A form submission does not by itself trigger Leina; event delivery, identity, duplicate handling and recovery must be tested for the actual integration.

Related Workflow · Turn Your Export Inquiry Checklist into a Reusable Skill