Every one of these is built in and already connected to the others. Nothing here is an integration you have to buy or wire up.
FormsCommunity intake through a public form
Build request forms for service issues, complaints and program interest, with a dropdown for the category and text fields for the address and details. Share the link on your site, on printed notices or as a QR code from the Sharing Hub. Each submission can open a Customer Care case shortly after it arrives. Forms have no file-upload or photo field, so applications that need documents are handled another way.
- Public service-request form for issues like drainage, lighting and collection
- Program interest forms that capture the resident's name, email and phone
- A case opened for each submission, with the priority and tags you set
FormsCustomer CareConstituent cases, from report to resolution
Each request is a case with a status from New to Closed, a priority, a category, assignees, a due date, internal notes, image attachments and a resolution summary with the root cause. A history of field changes shows who changed what and when. Residents cannot see or reply to cases: it is an internal case desk.
- Cases linked to the resident's record
- Duplicate reports closed against the first case with a note
- A reopened issue handled on the original case
Customer CareCustomer ManagementResidents, businesses and community organizations
A contact record holds the address, phone, email, preferred contact method and language, labels and custom fields, and shows the cases linked to that person. Staff can send a one-off email from the record, and it is kept in the record's Communications tab. It is not a complete log of every call or visit.
- Resident and business records with their linked cases
- Neighborhood associations and community contacts under one label
- Preferred language on each record, so a reply goes out in the right one
Customer ManagementWork BoardField work and referrals you can see
Create a Work Board ticket of the work-order type for work that goes to a crew, with the address, a priority from P0 to P5, assignees, labels and a due date. The board's statuses are yours to define and labels can mark the department. Moving the card is the status update, visible to everyone in the project.
- Labels per department, program or district
- Referrals with the receiving owner named on the ticket
- Overdue work visible on the board before someone complains
Work BoardRoutesCrews, inspections and service runs
Build the day's stops for a public-works crew, a collection run or an inspector in the order you choose, and open the route as Google Maps directions. The field marks each stop done from a phone, which saves when and by whom. You set the order: there is no route optimization and no vehicle tracking.
- Daily crew routes built from open requests
- Inspection runs grouped by district
- Completion saved from the field the same day, with who marked it
RoutesDocumentsFiles and the record of what was decided
Upload permits, applications, correspondence and reports as documents, link each to the resident or business it belongs to, and give it labels, assignees and a due date. Documents can be searched and filtered, and a person can run an analysis for a summary, text extraction or translation. There are no folders and no version history.
- Permit and application files linked to the resident's record
- Scanned letters summarized or translated on request
- Documents labeled by department or program
DocumentsEmailsNotices to residents by email
Send a service notice or program update as an email campaign to residents in your records, or to a list imported by CSV, with a visual or AI-generated layout and each recipient's first name. Sending is queued and goes out shortly after you send it; each recipient shows as sent, viewed or failed, and people who unsubscribed are skipped. There is no scheduling for later and no inbox for replies.
- Service interruption notices to affected residents
- Program announcements to a CSV list
- A test send to one address before the real one
EmailsContent CreatorPublic explainer and event pages
Build a simple web page for a program, an event or a process residents keep asking about with a guided wizard: pick a type, answer the questions Atty asks, approve the plan and review the page before you share it by link. Nothing is posted to social networks, and each page is reviewed by a person before anyone sees it.
- An explainer page for a process residents keep asking about
- A community event page shared by link and QR code
- A program page linked from an email notice
Content CreatorWhatsApp + AttyField reports from staff over WhatsApp
Where your organization has WhatsApp enabled, a field officer can send Atty a voice note, a text or a photo. Atty drafts a case or an update for approval, and a photo is saved to the project's documents and can be attached to the case once approved. Location pins are ignored, so the address goes in the message. Atty does not talk to residents.
- A field report drafted as a case from a voice note
- A photo attached to the right case once approved
- Open cases listed without opening the app
WhatsApp + Atty