whmcsguru
Active member
My apologies... I know this has been posted a couple places, I usually avoid those, but want to seriously get feedback here, as this module has had a good bit of time invested in it lately 
For the past few months, I've been embedded in work on a WHMCS notifications module. While coming along nicely, and released, feedback is always a good thing, so if you would be so kind as to take a look at this and give some honest feedback here. What am I missing? What would you like to see here that's not here? What additional hook points, what additional alert points? Functionality?
The idea behind the module:
Email is outdated. Other points of communication should be built into something like this, methods to communicate with clients and staff alike. A module like this provides redundancy and ensures that everything gets delivered as needed. As well, this removes the excuses:
What current alert methods (aside from email) do you use? What form of communication internally are you using? What am I missing here?
Currently implemented:
On Deck (v 1.3, which should be released next week at the latest)
Hook / Notification points (again, what am I missing here?)
Support tickets:
Staff can receive notifications on new tickets, assigns, client replies (both public and via pm if assigned)
Client can receive notifications on staff replies
New feature - Nags, which can remind via above alert methods about tickets with pending responses at 5 programmable times
Serverping:
I've managed to put together some webhooks which will be included in 1.3 for serverping clients, making notifications just that much easier.
Orders:
Staff can receive notifications on new orders, or when an order is marked as fraudulent (which currently is unacknowledged by WHMCS anywhere else)
Invoices:
Clients and staff can receive notifications on new invoice, payment, creation, late fees, refunds
Services:
Staff can receive notifications of cancellation, suspension, termination, unsuspension
Clients can receive notifications of unsuspension and suspension
Admin only:
More for 'security', admins can be notified when domains, addons, services, or orders are deleted . Since this should happen minimally, ideally no notifications would go out here, again , more of a security thing.
For the past few months, I've been embedded in work on a WHMCS notifications module. While coming along nicely, and released, feedback is always a good thing, so if you would be so kind as to take a look at this and give some honest feedback here. What am I missing? What would you like to see here that's not here? What additional hook points, what additional alert points? Functionality?
The idea behind the module:
Email is outdated. Other points of communication should be built into something like this, methods to communicate with clients and staff alike. A module like this provides redundancy and ensures that everything gets delivered as needed. As well, this removes the excuses:
or
What current alert methods (aside from email) do you use? What form of communication internally are you using? What am I missing here?
Currently implemented:
- Pushbullet
- PUshover
- Slack
- Hipchat
- SMS
On Deck (v 1.3, which should be released next week at the latest)
- BulkSMS
- Pushalot
- Campfire
Hook / Notification points (again, what am I missing here?)
Support tickets:
Staff can receive notifications on new tickets, assigns, client replies (both public and via pm if assigned)
Client can receive notifications on staff replies
New feature - Nags, which can remind via above alert methods about tickets with pending responses at 5 programmable times
Serverping:
I've managed to put together some webhooks which will be included in 1.3 for serverping clients, making notifications just that much easier.
Orders:
Staff can receive notifications on new orders, or when an order is marked as fraudulent (which currently is unacknowledged by WHMCS anywhere else)
Invoices:
Clients and staff can receive notifications on new invoice, payment, creation, late fees, refunds
Services:
Staff can receive notifications of cancellation, suspension, termination, unsuspension
Clients can receive notifications of unsuspension and suspension
Admin only:
More for 'security', admins can be notified when domains, addons, services, or orders are deleted . Since this should happen minimally, ideally no notifications would go out here, again , more of a security thing.
