Assign Airtable form responses: category rules and an unassigned queue

Write the assignment policy first

Route brochure requests to sales, existing-customer questions to support and everything else to an intake reviewer. Store that mapping on the operator's side instead of trusting a submitted staff name. Success includes retaining unmatched work for review. Decide who covers absent owners and who is responsible for noticing a request that could not be assigned.

Keep the public questionnaire focused

Collect category, subject, reply address and message. Assign internal ownership after intake instead of exposing the owner field for submitters to control. When adding a new category, update its routing rule as well. Submit a practice response for each category through the published form and inspect the actual saved choices, rather than assuming similar labels always correspond to the same value.

Establish a manual unassigned queue

Create a view for unfinished records with no owner. Let an intake reviewer assign them manually at first; this reveals ambiguous categories before those decisions become automation. Confirm assigned work appears in the relevant owner's view. Assignment is not acknowledgement or active handling, so preserve a separate state for whether someone has actually started the work.

Preserve existing owners when automating

Check the Airtable plan, automation capabilities and run allowances available to the team. For a matching-record trigger, require both the category condition and an empty owner before updating. This helps avoid overwriting a deliberate human reassignment. Use the record ID from the triggering record as the update target. A successful action on a different record is still an incorrect assignment.

Treat notification as a separate action

Updating ownership and notifying the person are different outcomes. Choose internal destinations from an approved mapping, not from arbitrary addresses in the submitted message. A subject, category and authorized record link may be enough for the notification. Decide whether reassignment should notify a second owner and how repeated processing avoids identical messages to the same person.

Check activation and re-entry behavior

Before enabling the rule, inspect whether existing matching records are included or only new transitions. Test a new brochure request, an unknown category and a record that already has an owner. Also test a record leaving and later re-entering the conditions; a trigger may run again. Compare stored ownership and notification results rather than relying solely on a green automation status.

Include absence and policy changes in daily operation

Review unassigned counts and overdue work regularly. When the mapping changes, state whether it applies only to future intake or also requires reassignment of existing cases. Consider Make when the process must involve an external CRM or messaging service. For a simple internal field update, compare the native Airtable option first. No tested account configuration or guaranteed run allowance is claimed by this setup guide.

• Build an Airtable enquiry tracker: intake, owners and follow-up states
• Find unfinished work in Airtable views: filters, sorting and sharing checks
• Connect Make and Airtable: search, create and update intake records