Skip to content

Grow: campaigns, surveys, finance and connectors ​

Campaigns, surveys and KAIA marketing shown to guests once they are online; the payments they make; and the connectors that feed all of it.

Nearly every page below is permission-gated. If a colleague cannot see one, that is their role rather than a fault — Roles is where to look.

Engage ​

Campaign ​

/admin/engagement/campaign

The Campaign list and editor — display ads or triggered notifications shown to guests once they are online.

When you would open it. Creating or editing a campaign, or checking why an active one isn't showing — ad types, triggers, caps and where the results appear are covered on the guide below rather than repeated here.

Needs the view-campaigns permission.

→ Campaigns and surveys

Survey ​

/admin/engagement/survey

The Survey list and editor — name, status and submit-mode, with the questions themselves edited as a separate step.

When you would open it. Creating a survey or changing when it asks (every login, once per session, once per device) — question authoring and where responses land are covered on the guide below.

Needs the view-surveys permission.

→ Campaigns and surveys

KAIA Marketing ​

/admin/engagement/marketing-ai

KAIA Marketing — an AI agent that files marketing send/campaign proposals for a person to approve, reject or execute, rather than sending anything on its own.

When you would open it. Reviewing proposals KAIA has drafted and approving or rejecting them, or checking its settings.

Before it has anything on it. manage-marketing-ai permission. Every send is checked against the guest's consent record first, and that check fails closed: on a tenant where the consent module is not installed, every guest reads as blocked on every channel — the proposal review flow works, but nothing goes out until the tenant has consent tracking and guests with a recorded opt-in.

Needs the manage-marketing-ai permission. Only when the kaia_marketing feature is enabled for the tenant.

→ KAIA marketing

Messages ​

Message Template ​

/admin/captive-portal/message-template

The SMS, WhatsApp, email and voucher templates Kiwire sends — OTP codes, forgot-password emails and voucher delivery during login, plus the expiry and ISP payment reminders sent by Automatic messages — grouped by channel, with per-language translations.

When you would open it. Writing or editing the wording guests receive, adding a translation for a language one of your login methods uses, or writing an expiry or payment reminder (choose the matching purpose).

Before it has anything on it. A login method (or the forgot-password flow) actually referencing a template before it is ever sent to a guest — building one here doesn't wire it up on its own.

Needs the view-message-template permission.

Automatic messages ​

/admin/engagement/messages/schedules

Rules that send a message template automatically: a number of days before, on or after someone's access expires, or (with ISP on) before or after an ISP invoice is due — by email, WhatsApp or SMS, at a set hour, with a send log.

When you would open it. Setting up expiry reminders and renewal offers, or ISP payment reminders, once instead of sending them by hand.

Before it has anything on it. An Email, WhatsApp or SMS connector, people with an expiry date and contact details, and ideally a template with the purpose Expiry reminder (a short standard message is sent without one).

Needs the view-message-schedules permission.

→ Automatic messages

Grow ​

Finance ​

/admin/finance

The tenant's money in one place. Overview: revenue for a month by source (vouchers and plans bought online, ISP subscriptions however they were paid) and by payment method, refunds, ISP expenses, profit and outstanding ISP invoices, with 12 months side by side and a CSV export. Voucher sales and Plan purchases tabs list the online purchases behind those figures.

When you would open it. Seeing how the month went across every revenue source, handing the accountant a 12-month export, or looking up a guest's online purchase when they say they paid but got nothing.

Before it has anything on it. A payment gateway connector for online sales; ISP figures appear once ISP invoices exist. ISP account credit being used is not counted as revenue — it was counted when first paid.

Needs the view-finance permission.

Connectors ​

/admin/connector

The connector hub — every configured instance of the roughly twenty connector types (SMTP, SMS, WhatsApp, directories, CRMs, payment gateways and more) that other parts of the admin pick from a connector dropdown.

When you would open it. Adding or testing a connector before wiring it into a captive-portal journey's login methods, a campaign's messaging channel, or Buy Panel checkout — or sending WiFi events (sign-ins, vouchers, payments, subscriber due dates) to n8n, Zapier or Make through a Webhook connector. The full list of types and what each is for is on the guide below; automation is covered on Integrate › Automation tools.

→ Connectors


This list is read from the admin menu itself, so it cannot fall behind it.

Last updated:

Kiwire platform documentation