We are expanding Chatwoot’s automation capabilities by introducing **Conversation Workflows**, a dedicated section in settings where teams can configure rules that govern how conversations are closed and what information agents must fill before resolving. This feature helps teams enforce data consistency, collect structured resolution information, and ensure downstream reporting is accurate. Instead of having auto‑resolution buried inside Account Settings, we introduced a new sidebar item: - Auto‑resolve conversations (existing behaviour) - Required attributes on resolution (new) This groups all conversation‑closing logic into a single place. #### Required Attributes on Resolve Admins can now pick which custom conversation attributes must be filled before an agent can resolve a conversation. **How it works** - Admin selects one or more attributes from the list of existing conversation level custom attributes. - These selected attributes become mandatory during resolution. - List all the attributes configured via Required Attributes (Text, Number, Link, Date, List, Checkbox) - When an agent clicks Resolve Conversation: If attributes already have values → the conversation resolves normally. If attributes are missing → a modal appears prompting the agent to fill them. <img width="1554" height="1282" alt="CleanShot 2025-12-10 at 11 42 23@2x" src="https://github.com/user-attachments/assets/4cd5d6e1-abe8-4999-accd-d4a08913b373" /> #### Custom Attributes Integration On the Custom Attributes page, we will surfaced indicators showing how each attribute is being used. Each attribute will show badges such as: - Resolution → used in the required‑on‑resolve workflow - Pre‑chat form → already existing <img width="2390" height="1822" alt="CleanShot 2025-12-10 at 11 43 42@2x" src="https://github.com/user-attachments/assets/b92a6eb7-7f6c-40e6-bf23-6a5310f2d9c5" /> #### Admin Flow - Navigate to Settings → Conversation Workflows. - Under Required attributes on resolve, click Add Required Attribute. - Pick from the dropdown list of conversation attributes. - Save changes. Agents will now be prompted automatically whenever they resolve. <img width="2434" height="872" alt="CleanShot 2025-12-10 at 11 44 42@2x" src="https://github.com/user-attachments/assets/632fc0e5-767c-4a1c-8cf4-ffe3d058d319" /> #### NOTES - The Required Attributes on Resolve modal should only appear when values are missing. - Required attributes must block the resolution action until satisfied. - Bulk‑resolve actions should follow the same rules — any conversation missing attributes cannot be bulk‑resolved, rest will be resolved, show a notification that the resolution cannot be done. - API resolution does not respect the attributes. --------- Co-authored-by: Sivin Varghese <64252451+iamsivin@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> Co-authored-by: iamsivin <iamsivin@gmail.com> Co-authored-by: Pranav <pranav@chatwoot.com>
98 lines
3.2 KiB
JavaScript
98 lines
3.2 KiB
JavaScript
import { computed } from 'vue';
|
|
import { useMapGetter } from 'dashboard/composables/store';
|
|
import { useAccount } from 'dashboard/composables/useAccount';
|
|
import { FEATURE_FLAGS } from 'dashboard/featureFlags';
|
|
import { ATTRIBUTE_TYPES } from 'dashboard/components-next/ConversationWorkflow/constants';
|
|
|
|
/**
|
|
* Composable for managing conversation required attributes workflow
|
|
*
|
|
* This handles the logic for checking if conversations have all required
|
|
* custom attributes filled before they can be resolved.
|
|
*/
|
|
export function useConversationRequiredAttributes() {
|
|
const { currentAccount, accountId } = useAccount();
|
|
const isFeatureEnabledonAccount = useMapGetter(
|
|
'accounts/isFeatureEnabledonAccount'
|
|
);
|
|
const conversationAttributes = useMapGetter(
|
|
'attributes/getConversationAttributes'
|
|
);
|
|
|
|
const isFeatureEnabled = computed(() =>
|
|
isFeatureEnabledonAccount.value(
|
|
accountId.value,
|
|
FEATURE_FLAGS.CONVERSATION_REQUIRED_ATTRIBUTES
|
|
)
|
|
);
|
|
|
|
const requiredAttributeKeys = computed(() => {
|
|
if (!isFeatureEnabled.value) return [];
|
|
return (
|
|
currentAccount.value?.settings?.conversation_required_attributes || []
|
|
);
|
|
});
|
|
|
|
const allAttributeOptions = computed(() =>
|
|
(conversationAttributes.value || []).map(attribute => ({
|
|
...attribute,
|
|
value: attribute.attributeKey,
|
|
label: attribute.attributeDisplayName,
|
|
type: attribute.attributeDisplayType,
|
|
attributeValues: attribute.attributeValues,
|
|
}))
|
|
);
|
|
|
|
/**
|
|
* Get the full attribute definitions for only the required attributes
|
|
* Filters allAttributeOptions to only include attributes marked as required
|
|
*/
|
|
const requiredAttributes = computed(
|
|
() =>
|
|
requiredAttributeKeys.value
|
|
.map(key =>
|
|
allAttributeOptions.value.find(attribute => attribute.value === key)
|
|
)
|
|
.filter(Boolean) // Remove any undefined attributes (deleted attributes)
|
|
);
|
|
|
|
/**
|
|
* Check if a conversation is missing any required attributes
|
|
*
|
|
* @param {Object} conversationCustomAttributes - Current conversation's custom attributes
|
|
* @returns {Object} - Analysis result with missing attributes info
|
|
*/
|
|
const checkMissingAttributes = (conversationCustomAttributes = {}) => {
|
|
// If no attributes are required, conversation can be resolved
|
|
if (!requiredAttributes.value.length) {
|
|
return { hasMissing: false, missing: [] };
|
|
}
|
|
|
|
// Find attributes that are missing or empty
|
|
const missing = requiredAttributes.value.filter(attribute => {
|
|
const value = conversationCustomAttributes[attribute.value];
|
|
|
|
// For checkbox/boolean attributes, only check if the key exists
|
|
if (attribute.type === ATTRIBUTE_TYPES.CHECKBOX) {
|
|
return !(attribute.value in conversationCustomAttributes);
|
|
}
|
|
|
|
// For other attribute types, only consider null, undefined, empty string, or whitespace-only as missing
|
|
// Allow falsy values like 0, false as they are valid filled values
|
|
return value == null || String(value).trim() === '';
|
|
});
|
|
|
|
return {
|
|
hasMissing: missing.length > 0,
|
|
missing,
|
|
all: requiredAttributes.value,
|
|
};
|
|
};
|
|
|
|
return {
|
|
requiredAttributeKeys,
|
|
requiredAttributes,
|
|
checkMissingAttributes,
|
|
};
|
|
}
|