Does Alma integrate with NGP-VAN, NationBuilder, or Action Network?
No native one-click integration. Webhooks and Zapier bridge to all of them — Alma fires a webhook with the full captured profile, your team configures the field mapping into VAN's MyCampaign, NationBuilder's people endpoint, or Action Network's signup hooks. Most campaigns get this wired up in an afternoon; we'll point you at the right docs during onboarding.
Is Alma FEC-compliant?
Alma is a chatbot, not a fundraising platform. The donor-intent capture happens in the conversation; the actual donation, the contribution-limit check, the occupation/employer fields, the FEC reporting — all of that is your fundraising platform's job (ActBlue, WinRed, Anedot, or your campaign's chosen processor). Alma hands off the contact and the intent. Fundraising compliance lives where it should: with the platform that actually moves the money.
What about TCPA and SMS consent?
If your bot collects phone numbers for SMS follow-up, the opt-in language is yours to write — Alma asks whatever you tell it to, including the explicit TCPA consent disclosure (program name, message frequency, msg-and-data rates, STOP-to-cancel). The Email & SMS Signup Bot template ships with double-opt-in scaffolding you can edit in your voice. The actual SMS sending, opt-out handling, quiet-hours enforcement, and consent-record retention live in CampaignCNX+ (or whatever SMS platform you route the captured contact into). Alma's job is to capture intent + the consent acknowledgement in writing; your SMS platform's job is to honor it on every send.
Can it handle multi-state or multi-candidate setups?
Yes — Agency tier ($199/mo) includes sub-account workspaces, isolated per workspace. One workspace per candidate, one per state, or one per ballot measure. State parties and federated PACs use the Agency tier to give each candidate-program their own bot, dashboard, and lead inbox under one master account. 20 active bots, 50,000 subscribers.
What about Spanish or other languages?
You write the prompts; the bot speaks whatever you've configured. Run the volunteer-signup flow in Spanish for one candidate, English for another, both bots under the same workspace. Multi-language switching inside one bot — same flow, different language based on user input — is on the roadmap. Today it's one language per bot.
Will Facebook Messenger and Instagram be live before my campaign cycle ends?
Both channels are in development pending Meta approval. We don't quote ETAs we don't trust. Worth flagging for political teams: Meta's political-content review is its own separate, more onerous process — even after our channel approval lands, your campaign's individual Page would face Meta's political ad-and-content rules. Today, every campaign deploys to the website channel only, and that's the surface that gets the work done.
What about voter-file matching at the doorstep?
That's Beacon — the door-to-door canvassing app in the suite. Alma writes captured contacts to CoreCNX, which can sync with Beacon's contact record so a canvasser knocking the door of someone who already chatted with Alma at 11pm sees that conversation history before they knock at 2pm Saturday. Same supporter, two channels, one record.
How is supporter data stored?
Isolated per workspace — your data is not commingled with any other campaign or organization. Encrypted at rest. Standard data export and deletion on request. For state-AG-bound, consent-decree-bound, or otherwise regulated campaigns, talk to sales for the regulated setup — we've worked with campaigns under specific consent decrees before and can configure accordingly.
Can I run separate bots for the candidate site, the volunteer hub, and the donor portal?
Yes. Growth tier ($79/mo) includes 5 active bots; Agency tier 20. One Volunteer Signup on the main candidate site, one Donation Nudge on the donor portal, one Event RSVP on the events microsite, one Issue Deep-Dive on the policy hub. Each bot has its own dashboard, leads inbox, and conversation log.
