How to turn off one channel per trigger in Inkwelly

1. Open Communications → Triggers

In Inkwelly open Communications → Triggers. The matrix lists every event your school can dispatch on (fee receipt, fee reminder, attendance absent, attendance present, exam admit card, exam result published, homework assigned, and so on) with one row per event. The master ON/OFF column is the leftmost toggle for the row; the four channel columns to its right (WhatsApp, SMS, Email, Push) are independent and each can be ON or OFF regardless of the others.

2. Confirm the master toggle is ON

For per-channel control to work, the master ON/OFF must stay ON. If the master is OFF, every channel column is greyed out and the per-channel toggle has no effect — Inkwelly sends nothing on that event regardless of channel state. If you see the row greyed, click the master toggle once to bring it back to ON; the channel columns turn interactive and reflect their last saved state. Most schools leave the master ON permanently and use the channel toggles as the day-to-day lever.

3. Flip the channel you want silenced to OFF

Click the channel column toggle on the event row — for example, WhatsApp on the Attendance — Absent row. The toggle turns grey. The change saves instantly; Inkwelly has no Save button on this page. The other channel columns on the same row stay ON (or whatever state you set them in), so the next time a teacher marks a student absent the SMS, Email and Push messages still go out — only the WhatsApp dispatch is skipped. The provider receives no API call for the silenced channel, so there is no cost line item for it.

4. Mirror the change across related triggers if needed

A single decision ("we are cutting WhatsApp on daily-volume events") often spans more than one event. If that is your case, walk down the trigger list and turn WhatsApp OFF on Attendance — Absent, Attendance — Present, and Homework Assigned together. The Triggers page lets you do this in one sitting without leaving the screen. Schools that batch the decision this way usually finish the entire reconfigure inside two minutes and see the cost drop on the next day's usage report.

5. Fire the event and verify the channel was skipped

Go back into the system and fire the underlying event — mark a student absent, post a homework. Then open Communications → Messages and filter by that event. You should see the SMS, Email and Push messages with delivered/sent status and an empty row for WhatsApp — Inkwelly logs the skip with a channel_disabled_by_trigger reason so audit trails stay clear. The Communications dashboard's Recent activity strip shows the same — successful sends on the kept channels, none on the silenced channel.

6. Adjust per-school-event when the calendar changes

Schools often re-enable a silenced channel for short windows — fee deadline week, admission result day, parent-teacher meeting day. The same per-channel toggles let you turn WhatsApp back ON for Fee Reminder the day before the deadline and OFF the day after, without touching the rest. Treat the Triggers page as a calendar-driven dashboard rather than a one-time setup — the schools that get the most out of Inkwelly Communications revisit it monthly.

7. Lock the configuration with a quick audit check

Once you have the channel mix you want, open Communications → Audit Logs and filter by triggerToggledAt to confirm the changes are stamped against your user id with the right timestamps. This becomes useful when a parent asks why they got an SMS but no WhatsApp — you can show the audit row and the policy decision in one minute. For a multi-school chain on Inkwelly, the Org Admin can roll this audit up across all schools to compare configurations.