Working documentation, in your vertical's terms
DirectToAttendees documentation
The Hub is one platform. Its workflows and terminology adapt to the organization running it: on DirectToAttendees, the audience that reaches everyone is called All Attendees and the people you reach are attendees. The pages below are the how, written in that vocabulary; the shared topics further down are identical for every vertical.
Deciding whether the Hub fits a event? That case is made at directtoattendees.com, not here.
DirectToAttendees topics
01Get attendees connectedPut the connection at registration, and it lasts the whole event journey and the next edition too.02Organize attendees by day, track, and roleSend each update to the attendees it affects instead of everyone every time.03Give your event team the right accessVolunteer leads, track chairs and the operations desk each reach their own people; the everyone sends stay with you.04Send a day-of changeGet a gate change, a weather hold or a delay onto every attendee's phone while they can still act on it.05Hear back from attendeesReplies become one-to-one threads your information desk can actually work through.06Plan the run-up in advanceWrite the know-before-you-go run once and let each piece go out on its day.07Follow up on every registration automaticallyA sequence that starts the day each attendee connects, so a February registrant and a June one both get the full welcome.08Run the countdown to event dayBuild the before, day-of, and after messages around one date, once.09Every way people can connectThe standing enrollment link and the printable kit are how an event actually builds its audience.10Data in, data outCSV import, an inbound webhook, signed outbound events and a Zapier app. There is no ticketing connector.11Understand your creditsPrepaid credits that never expire, so an event season buys once and nothing bills in between.
Shared Hub topics
These work the same way on DirectToAttendees as on every other vertical, so they live once, in the platform documentation.
12What the Hub isOne engine behind every Blasts vertical: consent-first connections, audiences people choose, sends, conversations and campaigns.13Blasts and email, side by sidePeople who prefer email still hear everything, from your organization's own address.14Campaigns: three ways to send over timeContent Series on the calendar, Journeys relative to each person, Event Campaigns around one date.15Security, ownership, and leavingThe organization owns everything. Leaving takes one confirmation and emails a complete export.16External content and FlowAutomated producers file content through signed ingest; a human reviews it and explicitly publishes.
Ready to work in your Hub?
Sign in at directtoattendees.com or right here. Inside your Hub, Help shows these same articles next to the screen each one describes.