Campaigns

Campaigns turn your agent loose on outbound — phone, SMS, and email — and move contacts through a pipeline based on what happens in each conversation. Think of it as a Kanban board your agent works for you.

The model

  • Lists— the columns of the board (e.g. "New leads", "Contacted", "Booked"). A contact is always in exactly one list.
  • Contacts — the people the campaign reaches. Add them manually or import from a connected CRM.
  • Conditions — rules that move a contact from one list to another after a conversation, based on the outcome.

Configuring a list

Each list defines how the agent works it:

  • Agent & channel— which agent does the outreach, and whether it's phone, SMS, or email.
  • Trigger on enter — when on, a contact entering the list is automatically queued for outreach.
  • Persona override— extra instructions appended to the agent's persona for this campaign, so one agent can run different scripts in different campaigns without changing its base persona.
  • Approval gate — require a human to approve outreach before it goes out.

The send window and daily capsare set on the campaign itself, not per list: only dial/send during set hours in the campaign's timezone, and never exceed a per-day volume per channel (phone, SMS, email).

Conditions & routing

After each conversation Seny evaluates the list's conditions against what happened. Rules can reference outcome, intent, sentiment, captured facts and variables (lead_facts.<key> and var.<key>), plus touch_count, tick_count, and days_since_reply. A matching condition moves the contact to another list, removes them, or marks them complete. That's how a contact flows from "New" to "Booked" (or "Not interested") on its own.

Conditions don't only fire after conversations: a condition can also run on a schedule — after a contact has sat in a list for a set dwell time, or on a cron — so stale contacts keep moving even when nobody picks up.

Contacts

Add contacts directly, or import them from a linked CRM list with property filters and optional scheduled auto-sync. Each contact can carry variables the agent uses and the conditions can route on.

Beyond rules

Campaigns can also run in agentic mode: instead of fixed conditions you give the campaign an objective and the agent decides each next touch itself, with an optional human-approval queue and a cap on touches per contact. Campaigns can push results back out via write-back rules that update your CRM as contacts move through the pipeline, and pull contacts in through an inbound webhook — mint a token and POST leads from your website or ad forms straight into a list. You can even have Seny generate a campaign — lists, conditions, and personas — from a plain-English description, then edit before activating.

Templates & analytics

Save a campaign's list structure and conditions as a template to spin up new campaigns fast. The campaign's Analytics view shows contacts per list, conversion through the pipeline, and outreach volume.

Going live

A campaign stays in draftuntil you activate it — nothing dials or sends while it's a draft. Set it to active and the dispatcher starts working queued contacts within the send window and caps. Pause or stop any time.