Groups and dynamic segments

Groups are how you decide who receives something in Arino One. There are two kinds: static groups, which you curate by hand, and dynamic segments, which are saved rules recalculated from live contact data. Both are selectable anywhere an audience is required — campaigns, journeys and automations.

Static groups

A static group is a named list with a description and a colour. You add contacts to it from the contact picker and remove them the same way. Membership never changes on its own, which is exactly what you want for a fixed list: a launch pilot, a VIP list, a set of contacts handed over by a partner.

Dynamic segments

A dynamic segment stores rules instead of members. Rules run against:

• standard contact fields — name, phone, email, country, language
• custom fields you defined for your business
• channel identity — which channels the contact is reachable on
• consent state per channel
• tags and group membership
• activity — last inbound message, last campaign interaction, order history

Membership is recalculated automatically and can be recalculated on demand, either for one segment or for every dynamic segment at once.

Build a segment by describing it

The segment builder accepts plain language. Type something like *"contacts in Spain who opted in to WhatsApp marketing and have not been messaged in 60 days"* and the AI drafts a rule set against the fields that genuinely exist on your instance. Nothing is saved until you accept it — treat the output as a first draft you check and edit.

AI use here is metered at cost with no Arino markup, on Lovable credits or your own key.

Always preview before sending

Preview returns the current match count and a sample of matching contacts. A segment that matches far more or far fewer people than expected is nearly always a rule problem — an empty custom field, a consent filter, or a country stored inconsistently on import.

Consent is still enforced at send time

A segment is an audience, not a permission. Marketing sends are filtered against each contact's live consent on the target channel at execution time, so a contact who opted out after the segment was calculated will not receive the message. See consent and opt-in.

Where segments are used

• Campaigns — the audience of a one-off broadcast, resolved at execution time.
• Journeys — entry conditions and branch conditions.
• Automations — add to or remove from a group as an action.
• Inbox — filter conversations by group to triage by customer type.

Steps at a glance

1. Open GroupsGo to Groups in the console. Every group shows its name, colour, type (static or dynamic) and current member count.
2. Create a static groupCreate a group, give it a name, description and colour, then add contacts to it by hand from the contact picker. Membership only changes when someone changes it.
3. Create a dynamic segmentCreate a group and switch it to dynamic. Build rules against contact fields, custom fields, channel, consent state, tags and activity — membership is then calculated, not maintained.
4. Describe the segment with AIInstead of building rules by hand, type what you want in plain language — for example 'opted-in WhatsApp contacts in Spain who bought in the last 90 days'. The AI drafts the rule set against your real contact fields for you to review and edit.
5. Preview before you commitRun a preview to see how many contacts currently match and a sample of who they are. Adjust the rules until the count and the sample look right.
6. Recalculate and use the segmentSave the segment. It recalculates on a schedule and can be recalculated on demand, and is then selectable as the audience for a campaign, a journey or an automation.

Frequently asked