Suppose a status field allows “Not contacted,” “Contacted,” and “Won,” but an agent submits “Following up.” Does Busabase reject the change, create an option, or leave it for the reviewer to resolve?
I'd like people to maintain the categories and agents to choose from existing options. Should the integration read the field configuration and map values before submission, or is there another validation step? The aim is to avoid accumulating near-duplicate statuses.
If the Status field already defines “Not contacted,” “Contacted,” and “Won,” submitting “Following up” is rejected as an invalid field value. Busabase does not silently add a new option or wait until a reviewer opens the Change Request to check it. Record create/update submissions validate against the field's configured choices, and the merge validates again in case the choices changed during review.
Have the agent read the Base field configuration first, then write an existing option ID or its exact name. Put your approved synonym mapping in a workspace Skill, and ask the agent to stop for a human decision when a phrase has no clear mapping. An empty choice list does not enforce a controlled vocabulary, so define the options before relying on this guard. A review-only credential adds a human check of the proposed classification, but the field validation is the first gate.
Should “Following up” map to “Contacted” in your process, or does it represent a genuinely separate stage? The Chinese version of this discussion covers the same case.
Sign in to join the discussion. Reading is always open; you only need an account to post.
Sign in