From a custom table you maintain. For US petitions, OpenStates and the Sunlight Foundation legacy datasets are common sources; for UK, TheyWorkForYou; for EU, the European Parliament data portal. Most countries have a maintained dataset. Import it into wp_sleek_reps, refresh after each election, and the bot queries it inline.

Yes. Multibot lets each petition have its own scoped bot, with the right target, current count, and constituent rules. A supporter on /clean-heat-act/ sees the Clean Heat Act bot, and a supporter on /school-funding/ sees the school-funding bot. The signature records share the underlying CRM but stay separable for delivery.

Email uniqueness is enforced on the signature record. CAPTCHA can be triggered after a configurable threshold. IP-based rate limiting blocks scripted floods. The conversation flow itself is a soft filter because automated submissions struggle with the open-comment question. Combined, this catches most adversarial activity without blocking real supporters.

Yes. After signing, the bot offers a personalised share link with the supporter's first name and the petition's social card. Campaigns see referral chains in the CRM, which helps identify high-influence supporters worth deeper engagement (volunteer asks, coalition invites).

The bot can ask for age confirmation where required and route younger supporters to a youth-action sign-up instead of the main petition. Consent text is configurable per petition, and the chat records consent timestamp and full text used. This supports compliance with election-law and youth-data rules in many jurisdictions.

Yes. Some petitions target a single official (e.g. the governor), others target every member of a chamber, others split by issue. The bot can identify the supporter's chamber-specific representative and add their signature to the right delivery bucket. Multi-target delivery is handled at the campaign-ops layer, not the bot.

CSV export from the CRM with name, address, district, comment, and consent fields. For large deliveries, the campaign team often produces a printed booklet with constituent quotes organised by district. The bot's structured data makes that production fast and the booklet itself becomes part of the press hit.

Yes. The lead-capture hook can push the signature payload to any of these via REST or their published webhook formats. Custom fields (district, rep ID, personal comment) map cleanly to standard fields in each platform. Configuration takes one PHP filter per platform, and once set up, the chat behaves like a native form to the CRM.