Meeting outcome and no-show tracking for appointment setting
Record whether every booked meeting was held, a no-show or rescheduled — once — and let the client report, the invoice and SDR commission follow automatically.
- Client portalshows no-show
- Billing recordbillable per rule
- SDR commissionfollows the outcome
- Slack · #northgatenotified
What's in it
Outcomes as states
Held, no-show and no-show with reschedule are recorded outcomes on the booking.
Reschedule in place
Move a meeting from the bookings view without losing its history.
Cancellation flow
A cancellation is requested and approved, with a defined matrix deciding the credit.
Reminders
Appointment reminders go out automatically before the meeting.
Calendar sync
Two-way sync with Google Calendar and Outlook.
Slack notifications
Bookings and no-shows can still post to a client channel — as a notification, not the system of record.
No-shows reported in Slack, copied by hand
A message is not a record. If the contract counts qualified meetings held per month, that count has to be right — and today it is rebuilt from chat.
Today
- The client posts the no-show in a shared Slack or Teams channel
- Someone at the agency reads it
- The meeting count, client report, invoice and commission are updated by hand
With Dialbrew
- The outcome is recorded once, on the booking
- The client portal shows it
- The billing record and SDR commission follow the same outcome
Record the outcome once
Marking a meeting held, no-show or no-show with reschedule happens on the booking, and everything downstream reads from it. There is no second place to update, so nothing to reconcile.
Cancellations follow a rule
- 1
Cancellation requested
On the booking, with a reason.
- 2
Approved
An account manager or admin decides on the request.
- 3
Matrix applied
A defined compensation matrix sets the client credit and the SDR commission.
“Do we bill this one?” becomes a rule, not a monthly negotiation.
Keep the Slack channel, stop the copying
Clients can keep their channel: Dialbrew posts bookings and no-shows to it. The notification comes from the record, instead of the record being rebuilt from the chat.
Related: the lead lifecycle and how to reduce the no-show rate.