Filter Groups

overview filter groups (also called table filter groups ) let you bundle several existing table filters into named, ordered sets so outbound style campaigns can dial leads in priority tiers —for example “high value” leads first, then a broader pool—instead of applying only a single flat filter set the capability is licensable it applies to outbound voice , parallel predictive voice , and voice blast campaigns groups can be built at system level (administrator) and/or campaign level (supervisor), then assigned on the campaign customers tab under the filter group sub tab how it works end to end journey table and filters exist an administrator defines the customer table and individual table filters (conditions on customer fields) under system settings → table → filters (or equivalent in your edition) build filter groups either the administrator creates system filter groups under system settings → table → filter groups , or the supervisor creates campaign filter groups under manage → lead management → manage filter groups on a supported campaign assign groups to the campaign on manage → campaigns → \[campaign] → customers → filter group tab, move the desired groups from available to assigned , then apply system groups appear alongside campaign groups; supervisors cannot delete system created groups optional fetch order inside a group (licensable) on manage filter groups , the supervisor can attach up to five fetch order policies per filter group so that, within each tier, the dialer also orders leads (for example by upload time or attempts) when used here, these policies override fetch order configured at administrator campaign level for that filter group setup (the ui explains this on the information icon) operate and verify use check impact / check dialable numbers (and enabled only vs all where shown) to see filtered and dialable counts after changes after toggling groups on or off, refresh dialable counts as prompted mutual exclusion filters vs filter groups for a given campaign you use either the filter tab or the filter group tab on customers , not both when the filter group license is active, the manage filters path for that flow is typically hidden or unavailable —plan training so supervisors know which mode the tenant uses system vs campaign groups origin created by type label notes system settings → table → filter groups administrator system can be assigned to multiple supported campaigns; only an administrator removes them at source manage filter groups on a campaign supervisor campaign scoped to that campaign; supervisor can enable/disable, reorder, modify, or delete their own groups; cannot delete system groups prerequisites license for filter groups (and, if used, fetch order policy inside filter groups) on the deployment campaign type is outbound voice , parallel predictive voice , or voice blast a table definition is selected where groups are maintained, and individual table filters already exist for that context for assignment the campaign customers → filter group tab is used; prerequisites for that screen are described in customers / lead filtration configuration steps a administrator — create system filter groups open system settings → table → filter groups under select table , pick the table definition whose filters you will group click create new enter a filter group name , choose campaign type (outbound, parallel predictive, or voice blast), then move filters from available filters to assigned filters using the forward arrow; use the backward arrow to remove members the campaign type you pick determines which filters are offered for grouping click save (or cancel to discard) enable or disable the group with the toggle when needed to edit , select the group, click edit , adjust name, description, or members, then save to delete , select the group, click delete , confirm yes deletion is permanent; if the group was assigned to campaigns, lead filtration for those assignments stops working until you reconfigure a deleted filter group cannot be restored if it was in use on campaigns, dialing logic for those assignments breaks until reassigned b supervisor — campaign filter groups and fetch order use manage → campaigns → open an outbound , parallel predictive , or voice blast campaign → lead management → manage filter groups create groups ( create new ), assign filters from available to assigned , set priority with ↑ / ↓ (top group applies first ) system groups appear as system type and cannot be deleted here for fetch order (licensable), use + to add policies (up to five ) typical policy types include customer upload time (ascending / descending) randomized order of lead upload natural order of lead upload (csv row order) number of attempts (ascending / descending) customer information (sort by a chosen customer field, ascending / descending) user disposition retry time (ascending / descending) custom (custom ordering script where your product edition exposes it) the same logical filter group can use different fetch order stacks when reused across campaigns use check impact / check dialable numbers to refresh filtered and dialable counts after toggles; use enabled only or all tabs in the modal where your build shows them step by step screenshots for the supervisor console live under manage filter groups (licensable) in this documentation set c assign filter groups on the campaign manage → campaigns → select the campaign → customers → filter group tab move groups from available to assigned , then apply do not use the filter tab on the same campaign while filter groups are the active mode see customers / lead filtration for the combined customers tab narrative (filters vs filter groups, check impact ) configuration parameters exact machine keys for filter group limits vary by release and hosting; use the table below for what to configure and confirm storage keys with your platform administrator if you automate configuration key / parameter description how to configure constraints & options sample (ui) filter group license turns on filter group features and related ui license / entitlement for the contact center (administrator or exotel onboarding—not a single campaign toggle) without license, filter group tabs and manage filter groups may be absent enabled for outbound sales tenant (ui) campaign type on system filter group limits which filters appear when building a system group system settings → table → filter groups → create new → campaign type outbound voice , parallel predictive voice , or voice blast outbound voice (ui) filter group members ordered set of table filters inside one group system or manage filter groups editor → available filters → forward arrow → assigned filters at least one filter per group when you intend the group to narrow leads “tier 1 — hot leads” contains filters a + b (ui) group priority dialing order across multiple groups on a campaign manage filter groups → ↑ / ↓ top group runs first “hot” above “nurture” (ui) fetch order policies per group secondary ordering inside a group after filters match manage filter groups → add policies with + (licensable) up to five policies per group in product docs; order matters upload time descending, then attempts ascending (ui) max filter groups per campaign caps how many groups can be assigned documented as backend / deployment tunable; default often 10 in guides—confirm for your build ui only (key not verified) — ask administrator for your limit 10 groups assigned use cases tiered dialing dial “eligible + high score” leads first, then fall back to a wider segment when the first tier is exhausted regional or product campaigns separate groups by geography or product line while reusing the same base table operational fairness combine fetch order (for example random or natural csv order) with tiered filters to balance business priority and even lead treatment benefits clear prioritization of segments instead of one monolithic filter reuse of system defined groups across many campaigns supervisor control over campaign local groups and ordering without redefining base table filters optional fine ordering inside each tier when fetch order policies are licensed and configured limitations filters vs filter groups are mutually exclusive per campaign customers configuration supervisors cannot remove system filter groups at campaign level deletion of a system group is destructive and breaks assignments until you fix campaign settings fetch order inside filter groups overrides administrator campaign level fetch order for that filter group configuration—communicate this to avoid surprises maximum five fetch order policies per filter group and a default cap on assigned groups per campaign (often 10 ) are described in product guides; your deployment may differ—validate with support related topics manage filter groups (licensable) — supervisor console walkthrough, fetch order screenshots, check impact , delete customers / lead filtration — customers tab assigning filters vs filter groups, apply , check impact lead management — broader lead and filter context customer records management — how table definitions and filters relate to agent visible data