Working documentation, in your vertical's terms
DirectToResidents documentation
The Hub is one platform. Its workflows and terminology adapt to the organization running it: on DirectToResidents, the audience that reaches everyone is called All Residents and the people you reach are residents. 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 municipality? That case is made at directtoresidents.com, not here.
DirectToResidents topics
01Invite residents to connect, and let them choosePublish a code on the bill, the calendar and the counter, approve the requests, and never upload a list residents did not join.02Organize by service, not by householdPublic works, collection, parks, meetings and urgent operations, plus the neighbourhoods and routes you name yourself.03Give each department the right accessPublic works sends about roads and water, parks sends about parks, and only the communications office reaches everyone.04Send a closure, a schedule change or a meeting noticeGet a detour, a collection change or an agenda onto the phones of the residents who chose to connect.05Answer residents about a service one to oneReplies land in one inbox the office shares, and the right department picks each one up.06Schedule the notices you already know aboutWrite the collection reminders or a construction update once, and let each one go out on its day.07Welcome each newly connected residentGive every newly connected resident the same short orientation, timed from the day they join.08Build the notices around one civic dateThe notice, the reminder, the details on the day and the summary after, all timed from one date you set once.09Where the Hub fits beside your municipal systemsYour municipal systems keep the record and the statutory notice. The Hub adds one voluntary channel to residents who chose to connect.10Where this channel fits beside your required noticesOne voluntary channel more, read by a self-selected part of the town, and never the notice of record.
Shared Hub topics
These work the same way on DirectToResidents as on every other vertical, so they live once, in the platform documentation.
11What the Hub isOne engine behind every Blasts vertical: consent-first connections, audiences people choose, sends, conversations and campaigns.12Blasts and email, side by sidePeople who prefer email still hear everything, from your organization's own address.13Campaigns: three ways to send over timeContent Series on the calendar, Journeys relative to each person, Event Campaigns around one date.14Every way people can connectEnrollment code, QR code, printed kit, connect links, invitations, CSV, and a webhook.15Understand credits, refills and Hub ProPrepaid credits from BlastCredits that never expire, a separate email balance, and Hub Pro at $500 in purchases.16Security, ownership, and leavingThe organization owns everything. Leaving takes one confirmation and emails a complete export.17External content and FlowAutomated producers file content through signed ingest; a human reviews it and explicitly publishes.18Manage delivery problems and reconnectionSee why a send did not reach someone, and what, if anything, to do about it.
Ready to work in your Hub?
Sign in at directtoresidents.com or right here. Inside your Hub, Help shows these same articles next to the screen each one describes.