Creating your first outbound campaign
A campaign is one form — its purpose, its audience segment, and a channel ladder that decides where a message goes first and what happens if it isn't opened.
Outbound campaigns are Kav reaching residents proactively — a payment reminder, a waste-collection change, an emergency broadcast — as opposed to the assistant answering a question a resident asked. Creating one is a single form, not a wizard: a campaign can be saved as a Draft with an incomplete channel ladder and finished later, so there's nothing here that has to be filled in a fixed order.
The campaign's own facts
- Slug — lowercase, hyphenated, e.g.
autumn-arnona-reminder. - Purpose — a fixed, closed list: payment reminder, ticket deadline, appointment reminder, waste collection, service-request update, marketing, or emergency broadcast. This isn't decoration — it's the same purpose value the consent and quiet-hours systems key off of.
- Display name, in both English and Hebrew — both are required.
- Audience segment — the Manual segment this campaign sends to (see the audience-import guide for how a segment gets its members).
The channel ladder
A campaign doesn't pick one channel — it picks an order. Add a rung for each channel you want tried, in sequence: WhatsApp first, say, falling back to SMS after a set number of seconds, then email. Each rung needs:
- a channel (WhatsApp, SMS, Email, Facebook Messenger, Instagram Direct, Telegram, mobile push, voice, or web inbox),
- a template slug — which message template this rung sends (see the template-authoring guide),
- an optional fallback delay in seconds — how long to wait for this rung to land before trying the next one.
A campaign can be saved with an empty ladder — it just can't be scheduled that way. Only the schedule action requires at least one rung.
Reorder or remove a rung at any point before scheduling; nothing about the ladder is locked in until the campaign actually goes out.
What happens after you create it
A newly created campaign lands in Draft. From there it moves toward being scheduled — a separate action once its ladder and templates are ready — and reporting on a sent campaign is its own read-only screen, not part of this form.