Avoca has several notification systems with different audiences. Use the page that matches who should receive the message.
Email Notifications
The page title is Email Notifications, even though the sidebar item is Notifications. Editing it requires the appropriate settings access.
- Use Call to choose which call-reason groups send emails and whether action items generate follow-up emails.
- Configure callback and supported Simple Scheduler dropoff emails separately.
- Use Text for the available text booking-email preference.
These are team-wide event preferences. Delivery to a particular employee can also depend on that person’s settings under Business Info → Members → Employee Contacts.
Outbound Customer Notifications
Customer Notifications requires the relevant Outbound setup and ServiceTitan data. Available cards can include Job Scheduled, Job Cancelled, Job Rescheduled, and Appointment Reminder.
Before activating a card:
- Resolve any listed ServiceTitan sync requirement.
- Confirm the outbound or universal sending number shown by the page.
- Scope the correct business units and job types.
- Review the SMS template and timing.
- Save, test, and then enable the notification.
Customer Notifications sends messages to customers. It is not an internal alert system. Check for overlapping Dispatching ETA messages before enabling a similar customer event.
Create and track a support ticket
Open Settings → Support. Support appears when it is enabled and your role has access to it.
Choose New Ticket to report an issue. Include the affected product, what you expected, what happened, the approximate timestamp and timezone, and a non-secret identifier such as a call, conversation, or job ID. Never include passwords or API secrets.
The Tickets page also includes tickets created from calls or messages. Use the date range and filters to find a ticket, then open it to review status, priority, lifecycle, linked context, and updates. The summary cards show total, active, resolved, and median resolution time for the current filters.
If an existing ticket covers the same incident, update that ticket instead of creating a duplicate. 
