CoreCNX+
Start free trial →

The CNX Suite

CoreCNX is the spine. Three sibling products feed it.

Beacon handles the doors. CampaignCNX+ handles the texts. Alma handles the inbound. CoreCNX is where every one of those events lands: same contact, same timeline, same login, same bill. Buy any product on its own; wire in the rest when you grow into them.

Five sources. One spine.

Beacon Door knocks Field-ops dispositions, surveys, GPS
CampaignCNX+ SMS replies Sends, replies, opt-outs, conversions
Alma Chatbot leads Conversations captured at the website
Email Opens & replies Native email campaigns + SendGrid events
CoreCNX The spine Where every event lands. Where the timeline runs.

Four products, one suite

One login. One contact record. Four jobs.

You can buy any of these standalone. CoreCNX becomes the timeline layer the moment you wire in a second one. Most teams start with two, end up with three, and never need a fourth tool.

CRM & spine

CoreCNX

Contacts, pipeline, email, unified timeline. The data layer that ties the suite together.

Field ops

Beacon

Territories, walk lists, door knocks, mobile canvasser app, live tracking. From $59/mo.

SMS

CampaignCNX+

Broadcast SMS, two-way reply, contact management. From $0.06/SMS.

Website chatbot

Alma

Website chatbot for visitor conversations. Asks the qualifying questions, captures the lead, writes the contact to CoreCNX.

What each one writes to the timeline

Every product has a job. Every job ends in a CoreCNX event.

Each row below is a sibling product and the kind of activity it produces. The timeline doesn't care which product fired the event. It tags it with a colored dot and sorts it in chronologically with everything else.

/A, CoreCNX, the spine

The CRM the other three write to.

Contacts, pipeline stages, email campaigns, tasks, reports. When a Beacon canvasser knocks a door, when a CampaignCNX+ recipient replies "STOP", when Alma captures a chatbot lead: all of it lands here, on one contact's timeline, in chronological order.

  • Phone-first contact resolution across all four products
  • Source-tagged event timeline (color dots above)
  • Pipeline, email, tasks, reports: full CRM out of the box
  • REST API + signed webhooks for everything else
CoreCNX dashboard for Madison Chen for State Senate showing 18,742 contacts and the live activity feed across Beacon, CampaignCNX+, Alma, Email, and Manual sources

/B, Beacon, field ops

Door knocks become timeline events.

Beacon runs the in-person side: walk lists, GPS turf, canvasser shifts, disposition capture on a phone. The moment a canvasser taps "Contacted" or logs a survey response, Beacon fires a signed webhook to CoreCNX and the event lands on that voter's timeline tagged with the teal Beacon dot.

  • Walk lists, turf assignments, canvasser check-in
  • Disposition capture that works without cell signal
  • Survey responses become custom-field updates on the contact
  • GPS-stamped door knocks visible on the timeline
Learn more at beaconcnx.com →

beaconcnx.com

Beacon

Field operations · canvasser app

Writing to CoreCNX

/C, CampaignCNX+, SMS

Texts and replies on the same timeline as the door knock.

CampaignCNX+ does broadcast SMS and two-way reply at scale. Sends, deliveries, replies, opt-outs, link clicks, and conversions each fire a webhook to CoreCNX. A reply from a contact who got knocked on Tuesday, texted on Friday, and donated on Saturday shows up as one continuous thread.

  • Broadcast SMS to segments built in CoreCNX
  • Two-way reply lands as inbound on the timeline
  • Opt-out events sync back to CoreCNX contact preferences
  • Conversions (donations, sign-ups) tagged at the source
Learn more at campaigncnx.com →

campaigncnx.com

CampaignCNX+

Broadcast SMS · two-way reply

Writing to CoreCNX

/D, Alma, Website chatbot

Chatbot conversations feed the same contact record.

Alma is the chatbot widget that sits on your website and answers inbound visitor conversations in your voice. When it captures a name, an email, or an intent, or escalates to a human, the conversation lands on the contact's timeline. The chatbot is no longer a black box. Its leads live next to door knocks and SMS replies.

  • Inbound chat triage on the website or in SMS
  • Name + email + intent extracted to the CoreCNX contact
  • Full transcript pinned to the timeline event
  • Escalation to a human creates a CoreCNX task
Learn more at helloalma.chat →

helloalma.chat

Alma

Website chatbot

Writing to CoreCNX

How contacts flow

Three real chains. Same contact at the end of each one.

What it actually looks like when the suite is wired together. The contact doesn't get duplicated; the events compound on one timeline.

/01

Door → text → donation

The classic full-suite chain. A canvasser meets Maria at her door, dispositions her "supporter," and the contact lands in CoreCNX. A week later she gets a CampaignCNX+ ask. She replies, taps the link, donates $25.

  • Beacon: door knock, "supporter"
  • CampaignCNX+: SMS ask sent
  • CampaignCNX+: reply + click
  • Donation logged
  • Pipeline → "donor"

/02

Chatbot → email → reply

Inbound, no field ops. A visitor to the campaign site asks Alma a policy question. Alma captures the name and email, hands the conversation off, and the contact lands in CoreCNX with the full transcript pinned.

  • Alma: chat captured + transcript
  • Auto-task: human follow-up
  • Email sent (native)
  • Open + reply tracked
  • Pipeline → "engaged"

/03

Import → SMS → field follow-up

Reverse direction. A list comes in via CSV, gets segmented in CoreCNX, sent through CampaignCNX+. The non-responders get a Beacon walk list assigned. Each step writes back to the timeline.

  • CSV import → CoreCNX
  • CampaignCNX+: broadcast sent
  • Replies + opt-outs synced
  • Beacon: non-responders → walk list
  • Door knocks logged

The mechanics

One contract between the four products. Signed webhooks.

The suite isn't an integration soup. It's four products that share an event format and a webhook signing key. Same contract, same handshake, regardless of which product fires.

/01

Source product fires

Beacon, CampaignCNX+, or Alma writes a row locally and queues a webhook. SendGrid does the same for email opens and replies.

/02

Signed webhook lands

POST /api/activity/ingest with a signed payload. CoreCNX verifies the signature before doing anything else.

/03

Contact resolves

Match by phone first, email second, create-if-no-match third. We check a unique source record ID before insert. Same event arriving twice still lands once.

/04

Timeline updates

Event lands on the contact's timeline tagged with the source dot. Visible to every dashboard, report, and segment in seconds.

Run the suite, see it in one place

Wire in your first source today.

Start CoreCNX free for 14 days. Connect Beacon, CampaignCNX+, or Alma during the trial. Every event from that point lands on the timeline. Buy the rest of the suite when you grow into them.

Start free trial → See the demo
Beacon
beaconcnx.com
CampaignCNX+
campaigncnx.com
Alma
helloalma.chat