Skip to main content
Campaigns let you send a templated message to many people at once—from a small team to thousands of recipients—and attach a workflow so each person submits structured answers inside Serval. Responses are real workflow runs, so everything your team already builds in the workflow builder—branching, approvals, integrations, tickets, and access steps—can run from campaign replies, not just static survey data. Configure campaigns from Team Settings → Capabilities → Campaigns.

​
Recipients and personalization

  • Users and groups — Target people already in Serval.
  • CSV upload — Upload a recipient list; columns become merge fields in the message body (for example a first name or any custom column).

​
Scheduling

Send immediately, at a scheduled time, or at a local time per recipient so messages land in sensible hours across timezones.

​
Message, workflow, and delivery

  • Rich text editor with preview for the outbound message.
  • Attach a workflow to collect replies; recipients see Serval workflow input types and you can preview the form while you build.
  • Slack DMs are supported in this release. Recipients open the DM from Serval and tap Respond to complete the workflow.
  • Insights show who has submitted, who is still pending, and the answers that came back.
Microsoft Teams, email, and recurring campaigns are on the roadmap.

​
Why workflows matter for campaigns

Because each response starts a workflow execution, you can operationalize replies: route exceptions, open tickets, request approvals, or call integrations based on what someone submitted—instead of only exporting a spreadsheet.

​
Common campaign ideas (and how workflows help)

Think of campaigns as broadcast + survey + automation. A few patterns teams reuse:
  • Rollout pulse — satisfaction after a new app or process → branch on low scores or rough comments so only hot spots become tickets or follow-ups; everything else stays in insights
  • Quarterly tool check-in — what people still use vs. what they’d retire → turn “sunset this” picks into cleanup tasks or flag weird answers for review
  • Office / event logistics — RSVP, dietary or accessibility needs, shirt size → approve exceptions, notify facilities or HR, or drop people into the right Slack channels
  • Training interest — session picks → enroll people in the right roster or group, notify facilitators when a session fills, or short-circuit an opt-out path so L&D does not chase them
  • All-hands input — questions or topics before a town hall → route to comms or leadership, dedupe similar asks, or send a lightweight acknowledgment workflow
  • New-hire or refresh preferences — monitor, dock, keyboard, OS-style choices → drive provisioning steps or open procurement when someone picks an unusual combo
  • IT health pulse — periodic score + optional comment → auto-escalate detractors only; let promoters close without a ticket
You can mix multiple choice, scales, short text, and file uploads (whatever your workflow inputs support), personalize with CSV fields, and still keep the same insights view for completion and exports.

​
Next steps