CoreCNX+
Start free trial →

The CNX Suite

CoreCNX is the spine. Three sibling products feed it.

Beacon is for door-to-door canvassing, CampaignCNX+ for texting, and Alma for your website's visitors. CoreCNX, the spine of the suite, is the central contact record that stores all of that activity on one timeline per contact, on one bill. You can buy any product on its own and connect the others later.

Five sources, one central record.

Beacon Door knocks Door results, surveys, GPS locations
CampaignCNX+ Text replies Texts sent, replies, opt-outs, keyword replies
Alma Chatbot leads Conversations captured at the website
Email Opens & clicks Built-in email campaigns and SendGrid events
CoreCNX The central record Stores every event on the timeline

Four products, one suite

One bill and one contact record for four products.

You can buy any product on its own. Once you connect a second one, CoreCNX keeps the shared timeline. Most teams start with two products, later add a third, and never need a tool outside the suite.

CRM & central record

CoreCNX

A CRM (a shared database of your contacts and your history with them) with contacts, a pipeline (a board showing where each contact stands), email and the unified timeline.

Field work

Beacon

Territories, walk lists (the lists of addresses a volunteer visits), door knocks, a mobile app for canvassers and live tracking. From $59/mo.

Texting (SMS)

CampaignCNX+

Mass texts, two-way replies and contact management. From $0.06/SMS.

Website chatbot

Alma

A website chatbot that asks visitors your screening questions, records the lead and adds the contact to CoreCNX.

What each one writes to the timeline

Each product has its own job, and each job ends in a CoreCNX event.

The timeline treats every product the same way, marking each event with a colored dot and placing it in date order.

/A, CoreCNX, the central record

The CRM the other three products report to.

When a Beacon canvasser knocks on a door, when a CampaignCNX+ recipient replies "STOP", or when Alma captures a chatbot lead, the activity is recorded here on one contact's timeline in date order.

  • Contacts matched by phone number first, then by email address, across all four products
  • Each event marked with its source (the color dots above)
  • Pipeline, email, tasks and reports: a full CRM, ready to use
  • A REST API and signed webhooks (automatic, verified messages between systems) so other software can read and write your data
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 work

Door knocks are recorded as timeline events.

Beacon manages in-person outreach: walk lists, GPS-mapped turf (the area assigned to a canvasser), canvasser shifts and door results recorded on a phone. When a canvasser taps "Contacted" or records a survey answer, Beacon sends a webhook to CoreCNX that carries a private key only the suite products hold, and the event appears on that voter's timeline with the teal Beacon dot.

  • Walk lists, turf assignments, canvasser check-in
  • Door results recorded even without a cell signal
  • Door knocks shown on the timeline
Learn more at beaconcnx.com →

beaconcnx.com

Beacon

Field work · canvasser app

Sending to CoreCNX

/C, CampaignCNX+, texting

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

CampaignCNX+ sends mass texts and handles two-way replies in large volumes. Each text sent, delivery, reply, opt-out and keyword reply (such as VOLUNTEER) sends a webhook to CoreCNX. If a contact had a door knock on Tuesday and received a text on Friday, her reply appears with that activity as one continuous history.

Learn more at campaigncnx.com →

campaigncnx.com

CampaignCNX+

Mass texts · two-way replies

Sending to CoreCNX

/D, Alma, Website chatbot

Chatbot conversations feed the same contact record.

Alma is a chatbot on your website that answers visitors' questions in your organization's voice. When it records a visitor's email address or phone number, the lead and the finished conversation are added to the contact's timeline, next to door knocks and text replies.

  • Sorts and answers incoming chats on your website
  • Name, email and phone saved to the CoreCNX contact
  • Each finished conversation recorded on the timeline
  • Appointments booked in the chat recorded on the timeline
Learn more at helloalma.chat →

helloalma.chat

Alma

Website chatbot

Sending to CoreCNX

How contacts flow

Three real examples, each ending on a single contact record.

When the suite products are connected, the contact is not duplicated, and each new event is added to the same timeline.

/01

Door → text → donation

A canvasser meets Maria at her door, records her as a "supporter," and the contact is added to CoreCNX. A week later, she receives a text request through CampaignCNX+, replies, taps the link and donates $25.

  • Beacon: door knock, "supporter"
  • CampaignCNX+: text request sent
  • CampaignCNX+: reply
  • Pipeline → "donor"

/02

Chatbot → email → open

This example involves no door-to-door work. A visitor to the campaign site asks Alma a policy question. Alma records the visitor's name and email and adds the contact to CoreCNX.

  • Alma: lead and finished chat recorded
  • Task: follow-up by a person, added by staff
  • Email sent from CoreCNX
  • Open and click tracked
  • Pipeline → "engaged"

/03

Import → text → door-to-door follow-up

This example runs in the opposite direction. A list is imported into CoreCNX as a CSV (spreadsheet) file, and the same list is texted through CampaignCNX+. A staff member then uses the people who did not reply to build a walk list in Beacon. The texts, replies and door knocks are recorded on the timeline.

  • CSV import → CoreCNX
  • CampaignCNX+: mass text sent
  • Replies and opt-outs copied to CoreCNX
  • Beacon: walk list built by staff from the people who did not reply
  • Door knocks recorded

How it works

The four products share one set of rules and one private key.

The four products share one event format and one shared private key, so every product follows the same rules and passes the same security check when it sends an event.

/01

Source product sends the event

Beacon, CampaignCNX+ or Alma saves the activity and prepares a webhook. SendGrid, the email delivery service, does the same for email opens, clicks, bounces and unsubscribes.

/02

The webhook arrives

The webhook goes to POST /api/activity/ingest carrying a private key that only the suite products hold. CoreCNX checks the key first and accepts only genuine messages.

/03

Contact is matched

CoreCNX matches the contact by phone number, then by email address, or creates a new one. It checks each event's unique source record ID, so an event that arrives twice is recorded only once.

/04

Timeline updates

The event appears on the contact's timeline, marked with its source dot. Within seconds, it is visible in every dashboard, report and saved group.

Run the suite and see it in one place

Connect your first source today.

Start CoreCNX free for 14 days and ask us to connect Beacon, CampaignCNX+ or Alma during the trial. The events that product sends then appear on the timeline. Add the rest of the suite when you need it.

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