Events
Single or multi-day, with the whole agenda in one record.
Sessions, speakers, and hosts.
Internal, public, password, or email.
Their own link, branding, and settings.
Attendance joins the relationship history.
Because your attendees are your pipeline. Invites go to your contacts, RSVPs save back to them, and follow-ups land next to the deal.
Attendance becomes history.
One bio, kept current.
Events feed the pipeline.
Across the workspace
Calls, email, tickets, meetings, and events roll up to one account timeline. Client health is calculated from it, with sources you can check.
What this removes
Guessing at account health, and rebuilding the history before every renewal call.
Single or multi-day, with the whole agenda in one record.
Times, rooms, and tracks, editable up to the morning of.
Pulled from your contacts and team.
Internal to fully public, with replies saved on the contact.
Published with their own link, no developer needed.
One workspace, so the records here are the records everything else reads.
Switching from another tool?
If it exports a CSV or a document, it moves. See how to migrate
Don't see your question? Contact us
Yes. Add sessions, rooms, and tracks, all editable up to the day.
Per event: internal, public, password, or email. Each page has its own link and settings.
Onto the contact record, as part of their history.
Yes. Speakers and hosts come from your contacts and team, with bios and sessions on their record.
No. Public pages publish with their own link and branding.