Operations

Campaigns, consent and policies

Ask everyone something in the chat they already use, get the answers structured, and chase the ones who have not replied. Consent is a versioned document with a tamper-evident signature.

Collections

A prompt is a templated question of a given kind; a campaign sends it to an audience once or on a schedule. Replies are parsed by kind and recorded; some kinds write straight onto the person’s profile so admins stop chasing people for details.

  • Audience: everyone, a team, a role or a list of people. Schedule: once, daily, weekly or monthly.
  • Non-responders are re-asked hourly, up to three times per question by default, always in their own direct message and only on working days.
  • A refusal to share is recognised and recorded as such rather than nagged.
  • Admins can ask people to self-report their contact details in one message.
collections.pending_reminder_hours
collections.pending_max_reminders
text, number, ratingfree text, a single number such as an NPS score, a 1 to 5 rating
choice, multipick one, or several, of the offered options
ackan acknowledgement, affirmative or negative
day_off, whatsapp, phone, email, contact_bundleprofile fields, normalised, with overflow into a sibling field
objective, objective_outcomea personal goal, and its due-date outcome

Announcements

Announcements track per-recipient reads. An optional escalation, off by default, messages people who have not opened one after a configurable number of hours, once.

pulse.announcement_escalate_enabled
pulse.announcement_escalate_hours

Agreements and e-signatures

  • An agreement has a key, a title, a body and a version; publishing a new version deactivates the old one and every signature of the old version becomes outstanding.
  • Signing records the signer, the typed full name, the channel, the source IP, the timestamp and a SHA-256 hash over the exact title, version and body. Any later edit produces a different hash.
  • Admins see who signed and who is outstanding, and can send a signing reminder to everyone who has not.
  • A printable completion certificate is available to the signer and to managers and admins.

Policies per team

Each team has a Markdown policies document editable by admins and readable by its members, with an org-wide default for teams without their own. Every save is audited with who edited it, the document is capped at 50,000 characters, and the renderer escapes HTML before applying Markdown so a policy can never inject anything into a reader’s session.