Tickets on one platform, conversations on the other, and the join that makes both useful
A conference runs on two systems: the one that sells tickets and hosts sessions, and the one that talks to sponsors, speakers, and attendees. EventHash is the first. CommsOperator is the second. Wired together, an organizer knows who bought, who applied, and which email brought them.
EventHash is an event management platform for tickets, sessions, speaker portals, and booths, built by Tech Family Ventures. It connects to CommsOperator two ways. Attendee lists come into the organizer's CRM through the leads API or a CSV import with email matching; there is no live per-ticket sync yet. Call-for-papers applicants are matched back to the outreach campaign that produced them by email, because CFP forms strip tracking parameters. EventHash's own site runs the chat, feedback, and roadmap widgets, so product feedback lands in its workspace.
- Import
- attendee lists matched into the CRM by email; no live sync yet
- Email match
- CFP applications attributed to campaigns without tracking links
- 3
- widgets on eventhash.com
- 1
- workspace per organizer brand on the CommsOperator side
The situation
Ticket buyers lived in the event platform. Sponsor and speaker conversations lived in mailboxes. When a speaker applied through the call-for-papers form, nobody could say which outreach had brought them, because the form emits no webhook and strips campaign parameters on the way in.
What changed
- Attendees become contacts (CRM). Attendee lists from EventHash are imported into the organizer's CommsOperator workspace and matched by email, so a ticket buyer is a contact with a timeline. A live per-ticket sync is not built yet, and we will say when it is.
- Speaker outreach gets its credit (Campaigns). Outreach runs as CommsOperator sequences. Applications land on EventHash's CFP form and are joined back to campaign contacts by normalised email, with a name fallback. The result is recorded on the campaign.
- The product listens (Widgets). Feedback board, public roadmap, and chat on eventhash.com, with product feedback flowing to EventHash's own workspace.
The result
The Women in Tech Global Conference runs on exactly this split: tickets, sessions, and the speaker portal on EventHash; tasks, CRM, campaigns, inbox, and knowledge base on CommsOperator. One workspace per organizer brand, and no tracking links needed to know which email did the work.
Solutions this story proves
Run your brands the same way
One workspace per brand, one subscription, and by default nothing the AI drafts leaves without a person approving it.