Segments

Save the list, not just the label

Saved contact lists built from a filter across everything the CRM knows — fields, tags, activity, deals and past campaign engagement.

  • Filter on fields, tags, activity, deals & broadcasts
  • Combine rules with all-of or any-of, with a live count
  • Snapshots, so a past campaign's audience stays answerable
  • Runs in the database, so big lists stay whole
RaabtaHQ — New segment
Lapsed high-value1,284match
Matchallof the following
Last messagein the last30 days
Deal valueat leastPKR 50,000
Broadcastnever replied toany campaign
In English: everyone who messaged in the last 30 days, has a deal worth at least PKR 50,000, and has never replied to a campaign.
1,284 contacts added — the filter ran in the database, so none were dropped at a row cap
New broadcast · audienceLapsed high-value1,284

Ask a question, get a list

Stack rules of the form field, operator, value, joined by all-of or any-of, with a free-text search always applied on top. A live count of matching contacts updates as you build, and the rules are restated back in plain English before anything is committed.

  • Contact fields — name, phone, email, company, date added
  • Tags — is any of, has all of, is none of
  • Every custom field you've defined, as its own filterable field
  • Conversation activity — last message window, inbound channel, status
  • Pipeline & deals — open / won / lost, stage, and value ranges
  • Broadcast engagement — received, read, replied, failed, never received

A snapshot on purpose

Membership freezes the moment contacts are added. A contact created tomorrow that matches yesterday's filter does not join on its own — and that is deliberate, because the main consumer of a segment is a broadcast, and 'who did this campaign actually go to' has to stay answerable months later. The filter is stored alongside the list, so topping it up is something you choose rather than something that happens to you.

Big lists stay big

Rules compile to SQL inside the database and the add is a single statement, so the matching set never travels through the browser and nothing silently truncates at a row cap — a segment built from a 40,000-contact filter contains 40,000 contacts. Field and operator names are checked against a fixed whitelist and every value is parameterised, so an unrecognised combination is rejected rather than executed.

  • Filters run with your own permissions, inheriting contact visibility
  • A colleague's private contacts are counted but not listed — and the gap is labelled, not hidden
  • Deleting a segment removes the list only, never the contacts

Getting contacts in, and out again

Build a filter and add everyone who matches, or select rows in the contacts table and push them into a segment — existing or created on the spot. Each contact's page lists the segments it belongs to. From the segment itself, 'Send broadcast' opens the campaign wizard with that list already selected.

Explore more

Works well with

Ready to answer every customer in one place?

Bring WhatsApp, Messenger and Instagram together with AI that actually helps. Talk to us and we'll get you set up.