Petitions

A petition collects signatures for a demand, apart from campaigns: signers leave their name and email, and the counter shows how many have joined. Right after signing, the petition can offer a campaign to go further, and a campaign can invite its supporters to share a petition. A petition starts, like a campaign, from a description of the demand: what is asked, to whom and why, in the petition's language. The AI turns it into a draft, with a title, a description, a full text written in Activoice and a form header, which the steps below let you edit. This page walks through the petition editor step by step. Your AI assistant reads it too when it works on a petition with you.

Each step has its own page in your Activoice admin, at https://admin.activoice.org/petitions/<petition_id>/edit/<step>; the step slug is given with each section below. A step opens once every step before it is complete: while the content is missing, the later steps stay locked in the admin, as in the campaign editor.

Content (content)

• Title and description — the description (pitch in the API) is a few sentences shown under the title, before the form, with basic formatting (headings, bold, lists, links). Who the petition addresses belongs in the title, the description or the full text.
• Cover images — desktop and mobile, uploaded in the admin only.
• Full text — either a link to a page hosted elsewhere, optional, opened in a new tab by "Read the petition"; or a text written in Activoice, which visitors expand on the petition page without leaving the form. The draft comes with the generated text written in Activoice; switch to a link to host it elsewhere.

Blocks publishing: a missing title or description, or an empty text when the full text is written in Activoice.

Form (form)

• Form header (form_header in the API) — the heading above the signature form, written in the petition's language. Left empty, the form shows "Add your name", translated for each visitor.
• Fields — first name, last name and email are always asked. Phone, postal code, country and address are each hidden, optional or required. The CRM fields picked for the petition are asked too.

A new petition is connected to your CRM integration from the start; the Form step lets you disconnect it. Signers join the mailing list only when they tick the newsletter box, set up by your CRM integration (checked by default or not, required or not, with your privacy policy link). A visitor who already gave consent to your organization does not see the box again, and their signature still reaches the CRM. Signing again with the same email updates the signature and counts once.

Follow-up (follow-up)

The campaign offered right after signing, with the signer's name and email already filled in. The thank-you page lists the campaign's channels, the most effective first; the signer picks one and lands in the campaign with that channel already chosen. When the campaign has several recipient groups or finds the recipient from the signer's address, the channel depends on that choice, so the thank-you page names the channels and offers a single Take action button instead. It is shown only while that campaign is live. When you choose it, you are asked whether that campaign should also invite its supporters to share this petition on its success page; answering yes replaces any petition the campaign already shares. The two links are independent: the campaign side is also set in the campaign's Settings step.

Settings (settings)

• URL — the slug of the petition page, /petitions/<slug>/, on your organization's custom domain when it has one.
• Publication — a draft is not public. On a draft, the step's Publish button (in place of Next) saves the settings, publishes the petition and opens the Share step. Once published, the petition collects signatures; ended, it keeps its counter visible and accepts no more signatures. The counter appears from 100 signatures, with automatic milestones like the campaign counter.

Blocks publishing: a missing slug, which the step proposes from the title and requires before saving. Publish stays disabled, and the status box lists what is missing, while another step is incomplete. Publishing is refused, and nothing is changed, while anything listed on this page is missing.

Share (share)

The petition's public link, the personalized link for your CRM's contacts, and the snippet to embed it on your website: the signature form alone by default, or the full petition page. See Embedding a petition.

Signatures are listed on the petition's page in the admin, where each one can be deleted, for example to answer a data protection request, and all of them exported as CSV.